[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20151124.112253.2276973557484332376.davem@davemloft.net>
Date: Tue, 24 Nov 2015 11:22:53 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: mw@...ihalf.com
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
netdev@...r.kernel.org, linux@....linux.org.uk,
sebastian.hesselbarth@...il.com, andrew@...n.ch,
jason@...edaemon.net, thomas.petazzoni@...e-electrons.com,
gregory.clement@...e-electrons.com, simon.guinot@...uanux.org,
nadavh@...vell.com, alior@...vell.com, xswang@...vell.com,
myair@...vell.com, nitroshift@...oo.com, jaz@...ihalf.com,
tn@...ihalf.com
Subject: Re: [PATCH 00/13] mvneta Buffer Management and enhancements
This patch series has a lot of problems.
The worst one is that you are mixing bug fixes and new
features/cleanups.
You cannot do that.
You _especially_ can't do that if you expect some of this stuff
to be submitted to -stable too.
Therefore you _must_ extract out the bug fixes, and submit those
against 'net'. And you must then wait for 'net' to be merged
into 'net-next' before submitting the new feature patches.
Furthermore, you should explicitly show what tree you are targetting
your patches at, in your Subject lines. In the form:
Subject: [PATCH $(TREE) N/M]
Where $(TREE) is either 'net' or 'net-next'.
THanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists