[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdUsB+9v6T=p0FivcymVFTFtOR8-tf2sOpOMBgV_CH7Hfw@mail.gmail.com>
Date: Thu, 8 Oct 2015 15:49:05 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: David Miller <davem@...emloft.net>
Cc: Geert Uytterhoeven <geert+renesas@...der.be>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Linux-sh list <linux-sh@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2 0/4] sh_eth: Remove obsolete platform_device_id entries
Hi David,
[CC Arnd wearing the arm-soc merge hat]
On Thu, Oct 8, 2015 at 2:10 PM, David Miller <davem@...emloft.net> wrote:
> From: Geert Uytterhoeven <geert+renesas@...der.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@...ux-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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists