lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130418012041.GH5815@zion.uk.xensource.com>
Date:	Thu, 18 Apr 2013 02:20:41 +0100
From:	Wei Liu <wei.liu2@...rix.com>
To:	David Miller <davem@...emloft.net>
CC:	Wei Liu <wei.liu2@...rix.com>,
	"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
	"xen-devel@...ts.xen.org" <xen-devel@...ts.xen.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"wdauchy@...il.com" <wdauchy@...il.com>,
	Ian Campbell <Ian.Campbell@...rix.com>
Subject: Re: [Xen-devel] [PATCH V6] Bundle fixes for Xen netfront / netback

On Wed, Apr 17, 2013 at 10:21:20PM +0100, David Miller wrote:
> From: Wei Liu <wei.liu2@...rix.com>
> Date: Wed, 17 Apr 2013 20:43:17 +0100
> 
> > On Wed, Apr 17, 2013 at 08:31:19PM +0100, Konrad Rzeszutek Wilk wrote:
> >> On Wed, Apr 17, 2013 at 06:41:59PM +0100, Wei Liu wrote:
> >> > Final round of this series. All acked and ready to go in.
> >> 
> >> Should you put CC: stable@...r.kernel.org on some of them?
> > 
> > I don't think so: Ian Campbell told me that DaveM would like the patches
> > to go through his tree.
> 
> That's rather irrelevant.

Sorry I'm still learning the process of doing netdev. If you can
straighten it out for me that would be very helpful.

The handle I have is:
http://marc.info/?l=xen-devel&m=136552034026257&w=2

QUOTE
"> This should probably also CC stable@...r.kernel.org

DaveM prefers net patches to not do so and he takes care of forwarding
patches once he is happy (i.e. after they've been in his/Linus' tree for
a bit)."
/QUOTE

But it seems that Ian got you wrong. Or I misunderstood him.

So this patch series is considered both for net-next and stable because
it is basement for our future development and we would also like it to
get backported to stable. What should I do with it? Should I rebase it
against net-next or net? Or should I send out two series against
different branches?

Furthur question, now that I know there is actually two branches for
network related development, should I explicitly point out which branch
my series is against in the future?

Thank you for your time. :-)


Wei.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ