LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Guenter Roeck <linux@roeck-us.net>,
Joshua Thompson <funaho@jurai.org>,
Greg Ungerer <gerg@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet
Date: Mon, 28 May 2018 17:20:33 +1200 [thread overview]
Message-ID: <2ffd0de6-e8d6-6449-7c05-cbbfd8a99a97@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.21.1805271547090.9@nippy.intranet>
Hi Finn,
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 ...
Cheers,
Michael
next prev parent reply other threads:[~2018-05-28 5:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 23:53 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 [this message]
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
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=2ffd0de6-e8d6-6449-7c05-cbbfd8a99a97@gmail.com \
--to=schmitzmic@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux@roeck-us.net \
--subject='Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet' \
/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
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).