[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3744167b-7f37-4a86-8569-2a17bd5d3845@CH1EHSMHS035.ehs.local>
Date: Thu, 13 Feb 2014 08:00:10 +0100
From: Michal Simek <michal.simek@...inx.com>
To: David Miller <davem@...emloft.net>
CC: <michal.simek@...inx.com>, <netdev@...r.kernel.org>,
<sthokal@...inx.com>, <devicetree@...r.kernel.org>,
<monstr@...str.eu>, <John.Linn@...inx.com>, <anirudh@...inx.com>,
<linux-kernel@...r.kernel.org>, <grant.likely@...aro.org>,
<robh+dt@...nel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/14] Xilinx axi ethernet patches
On 02/13/2014 01:18 AM, David Miller wrote:
> From: Michal Simek <michal.simek@...inx.com>
> Date: Wed, 12 Feb 2014 16:55:34 +0100
>
>> I have exctracted patches which I have in our
>> xilinx git tree which are missing in the mainline.
>>
>> The first two patches fix compilation error and
>> warnings. Then 5 feature patches
>> and the rest is OF cleanup and with kernel-doc
>> and checkpatch problems.
>
> You should not combine bug fix and feature patches.
>
> Rather, you should submit bug fixes against the 'net' tree. Then when
> those bug fixes get applied and propagate to the 'net-next' tree you
> can submit the feature patches and cleanups against the 'net-next'
> tree.
Ok. I will.
Thanks,
Michal
--
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