From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Miller <davem@davemloft.net>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 0/4] sh_eth: Remove obsolete platform_device_id entries
Date: Thu, 08 Oct 2015 13:49:05 +0000 [thread overview]
Message-ID: <CAMuHMdUsB+9v6T=p0FivcymVFTFtOR8-tf2sOpOMBgV_CH7Hfw@mail.gmail.com> (raw)
In-Reply-To: <20151008.051023.991121515814557831.davem@davemloft.net>
Hi David,
[CC Arnd wearing the arm-soc merge hat]
On Thu, Oct 8, 2015 at 2:10 PM, David Miller <davem@davemloft.net> wrote:
> From: Geert Uytterhoeven <geert+renesas@glider.be>
> Date: Wed, 7 Oct 2015 10:14:13 +0200
>
>> Since commit 3d7608e4c169af03 ("ARM: shmobile: bockw: remove legacy
>> board file and config"), which is now in arm-soc/for-next, shmobile SoCs
>> are only supported in generic DT-only ARM multi-platform builds.
>> The sh_eth driver doesn't need to match platform devices by name
>> anymore, hence this series removes the corresponding platform_device_id
>> entries.
>>
>> Changes since v1:
>> - Protect some data and functions by #ifdef CONFIG_OF to silence
>> unused compiler warnings on SH,
>> - New patches 3 and 4.
>
> Since that commit isn't in any of my trees why don't you merge this
> via arm-soc/for-next?
This series just changes the sh_eth driver. There's no direct dependency on
the arm-soc changes. Hence I think the sh_eth changes should go in through
the netdev tree.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2015-10-08 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 8:14 [PATCH v2 0/4] sh_eth: Remove obsolete platform_device_id entries Geert Uytterhoeven
2015-10-07 8:14 ` [PATCH v2 1/4] sh_eth: Remove obsolete r7s72100-ether platform_device_id entry Geert Uytterhoeven
2015-10-07 8:14 ` [PATCH v2 2/4] sh_eth: Remove obsolete r8a779x-ether platform_device_id entries Geert Uytterhoeven
2015-10-07 8:14 ` [PATCH v2 3/4] sh_eth: Remove obsolete r8a7740-gether platform_device_id entry Geert Uytterhoeven
2015-10-08 2:07 ` Simon Horman
2015-10-07 8:14 ` [PATCH v2 4/4] sh_eth: Remove obsolete r8a777x-ether " Geert Uytterhoeven
2015-10-08 2:07 ` Simon Horman
2015-10-08 11:54 ` [PATCH v2 0/4] sh_eth: Remove obsolete platform_device_id entries David Miller
2015-10-08 13:49 ` Geert Uytterhoeven [this message]
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='CAMuHMdUsB+9v6T=p0FivcymVFTFtOR8-tf2sOpOMBgV_CH7Hfw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).