All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: "David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, stable@vger.kernel.org,
	Sony Chacko <sony.chacko@qlogic.com>,
	Ana Guerrero <ana@debian.org>,
	Michael Mastrogiacomo <mmastrogiacomo@ultralogistics.com>,
	Amit Kumar Salecha <amit.salecha@qlogic.com>,
	Ameen Rahman <ameen.rahman@qlogic.com>,
	Anirban Chakraborty <anirban.chakraborty@qlogic.com>
Subject: Re: [PATCH 2.6.32.y] netxen: support for GbE port settings
Date: Mon, 12 Mar 2012 04:40:39 -0500	[thread overview]
Message-ID: <20120312093919.GA17642@burratino> (raw)
In-Reply-To: <20120312090950.GC11569@1wt.eu>

Hi Willy,

Willy Tarreau wrote:
> On Sun, Mar 11, 2012 at 11:35:39PM -0500, Jonathan Nieder wrote:

>> From: Sony Chacko <sony.chacko@qlogic.com>
>> Date: Tue, 15 Mar 2011 14:54:55 -0700
>>
>> commit bfd823bd74333615783d8108889814c6d82f2ab0 upstream.
[...]
> One very important requirement for merging such a
> fix is that it is already present in more recent stable releases :
> when users upgrade from 2.6.32 to 3.0, we don't want them to get
> the bug again.

Thanks for explaining.  To answer this question: since the patch
(v2.6.39-rc1~468^2~23) was in mainline in 2.6.39, it gets the
privilege of inclusion in 3.0.y by default.

> If this requirement is satisfied and David is not opposed to merging
> the patch, then we can include it (even in this release, considering
> the authors and reviewers are already CC'd).

Cheers,
Jonathan

  reply	other threads:[~2012-03-12  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  6:56 [PATCHv2 NEXT 1/1] netxen: support for GbE port settings Amit Kumar Salecha
2011-03-15 21:55 ` David Miller
2012-03-12  4:35 ` [PATCH 2.6.32.y] " Jonathan Nieder
2012-03-12  9:09   ` Willy Tarreau
2012-03-12  9:40     ` Jonathan Nieder [this message]
2012-03-13 17:43   ` Rajesh Borundia
2012-03-15  9:32     ` Willy Tarreau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120312093919.GA17642@burratino \
    --to=jrnieder@gmail.com \
    --cc=ameen.rahman@qlogic.com \
    --cc=amit.salecha@qlogic.com \
    --cc=ana@debian.org \
    --cc=anirban.chakraborty@qlogic.com \
    --cc=davem@davemloft.net \
    --cc=mmastrogiacomo@ultralogistics.com \
    --cc=netdev@vger.kernel.org \
    --cc=sony.chacko@qlogic.com \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.