LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Finn Thain <fthain@telegraphics.com.au>,
Christoph Hellwig <hch@lst.de>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
Joshua Thompson <funaho@jurai.org>,
linux-m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet
Date: Wed, 30 May 2018 10:28:15 +1000 [thread overview]
Message-ID: <10880132-7686-78f6-7f9f-3fc29c3e554a@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdWXnP96p9swox6FXg2-2doeNGK+G9eQyZ-td+xWGSKKoQ@mail.gmail.com>
Hi Geert,
On 28/05/18 20:15, Geert Uytterhoeven wrote:
> On Mon, May 28, 2018 at 7:26 AM, Finn Thain <fthain@telegraphics.com.au> wrote:
>> On Mon, 28 May 2018, Michael Schmitz wrote:
>>> Am 27.05.2018 um 17:49 schrieb Finn Thain:
>>>> On Sun, 27 May 2018, Michael Schmitz wrote:
>>>>
>>>>> That should have fixed the warning already ...
>>>>
>>>> It's still not fixed (hence my "acked-by" for Geunter's patch).
>>>>
>>>
>>> Odd - does link order still matter even though the
>>> arch_setup_dev_archdata() function from the core platform code is
>>> declared as a weak symbol?
>>>
>>> I'll see what I can find out on elgar ...
>>>
>>
>> Any one of the numerous patches/rfcs/suggestions that I sent will avoid
>> the WARN splat.
>>
>> When I said "it's still not fixed", what I meant to say was, "it's still
>> not fixed in mainline and no proposed fix was accepted to the best of my
>> knowledge".
>
> Indeed.
>
> Do we have a consensus on the way forward? The merge window for
> v4.18 will open soon.
For whatever it is worth I thought Finn's patch was the best approach
(https://lkml.org/lkml/2018/5/17/333, "m68k: Set default dma mask for
platform device").
We seem to be hitting quite a few places (within m68k) that otherwise
need individual fixes. There is no immediate need to revert existing
changes that have already been applied if we use this now either
(like my FEC fix, commit f61e64310b75 "m68k: set dma and coherent
masks for platform FEC ethernets").
Regards
Greg
next prev parent reply other threads:[~2018-05-30 0:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 23:53 [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet Guenter Roeck
2018-05-27 3:01 ` Finn Thain
2018-05-27 4:15 ` Guenter Roeck
2018-05-28 5:33 ` Christoph Hellwig
2018-05-27 5:22 ` Michael Schmitz
2018-05-27 5:49 ` Finn Thain
2018-05-28 5:20 ` Michael Schmitz
2018-05-28 5:26 ` Finn Thain
2018-05-28 10:15 ` Geert Uytterhoeven
2018-05-28 19:59 ` Michael Schmitz
2018-05-29 7:08 ` Christoph Hellwig
2018-05-29 2:15 ` Finn Thain
2018-05-29 3:23 ` Michael Schmitz
2018-05-29 5:38 ` Finn Thain
2018-05-29 7:11 ` Christoph Hellwig
2018-05-29 11:59 ` Finn Thain
2018-05-29 20:10 ` Michael Schmitz
2018-05-29 12:04 ` Finn Thain
2018-05-30 0:28 ` Greg Ungerer [this message]
2018-05-30 19:55 ` Geert Uytterhoeven
2018-05-31 0:38 ` Greg Ungerer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10880132-7686-78f6-7f9f-3fc29c3e554a@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=fthain@telegraphics.com.au \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=schmitzmic@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).