[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160517.122527.1937360418899371800.davem@davemloft.net>
Date: Tue, 17 May 2016 12:25:27 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: mcoquelin.stm32@...il.com
Cc: alexandre.torgue@...il.com, peppe.cavallaro@...com,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
robh@...nel.org, manabian@...il.com, wens@...e.org
Subject: Re: [RESEND PATCH v6 0/6] Add Ethernet support on STM32F429
From: Maxime Coquelin <mcoquelin.stm32@...il.com>
Date: Tue, 17 May 2016 11:20:16 +0200
> Hi David,
>
> 2016-05-09 21:06 GMT+02:00 David Miller <davem@...emloft.net>:
>> From: Alexandre TORGUE <alexandre.torgue@...il.com>
>> Date: Mon, 9 May 2016 12:31:33 +0200
>>
>>> STM32F429 Chip embeds a Synopsys 3.50a MAC IP.
>>> This series:
>>> -enhance current stmmac driver to control it (code already
>>> available) and adds basic glue for STM32F429 chip.
>>> -Enable basic Net config in kernel.
>>
>> I assume this will go via the ARM tree, for the networking bits:
> I would expect patches 1, 2 & 3 to got via your tree, to avoid conflicts.
I don't think putting them all via the ARM tree is going to create much
in the way of conflicts, and right now during the merge window offloading
that work from me would really help my backlog a lot.
Thanks.
Powered by blists - more mailing lists