public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Xufeng Zhang <xufeng.zhang@windriver.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
	<nhorman@tuxdriver.com>, <vyasevich@gmail.com>,
	<davem@davemloft.net>
Subject: Re: [PATCH] sctp: set association state to established in dupcook_a handler
Date: Wed, 5 Jun 2013 10:20:26 +0800	[thread overview]
Message-ID: <51AEA06A.7040206@windriver.com> (raw)
In-Reply-To: <1370391220.21654.73.camel@deadeye.wl.decadent.org.uk>

On 06/05/2013 08:13 AM, Ben Hutchings wrote:
> On Tue, 2013-06-04 at 10:00 +0800, Xufeng Zhang wrote:
>    
>> On 06/03/2013 10:28 PM, Greg KH wrote:
>>      
>>> On Mon, Jun 03, 2013 at 03:52:58PM +0800, Xufeng Zhang wrote:
>>>
>>>        
>>>> 3.4-stable review patch.  If anyone has any objections, please let me know.
>>>>
>>>>          
>>> Really?  What are you going to do with it if no one objects?
>>>
>>>        
>> Sorry, I don't have any experience with stable patch and I consult
>> stable_kernel_rules.txt, there are not much special rules and here I just
>> want to specify the kernel version I wish it to be applied to.
>>
>>      
>>> I know I'm sure not going to do anything with it...
>>>
>>> (hint, this isn't how you ask for networking stable patches to be
>>> applied.)
>>>
>>>        
>> Ok, thanks for your hint, I'll resend the patch.
>>      
> The heading you used should only be used by a stable branch maintainer
> sending out a series of patches they've already accepted, prior to
> making a new release.  If you want a fix to be added to be applied to
> one or more stable branches, you should write in the form of a request.
> And if you're just not sure, then you should write in the form of a
> question.
>
> Networking is a special case in that the subsystem maintainer, David
> Miller, generally collects together and backports fixes for all the
> official 3.x branches.  So you should send your request to him (but do
> cc the stable and subsystem lists as well).
>    
Thank you, Ben!
Now it's more clear.


Thanks,
Xufeng
> Ben.
>
>    


  reply	other threads:[~2013-06-05  2:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  7:52 [PATCH] sctp: set association state to established in dupcook_a handler Xufeng Zhang
2013-06-03 14:28 ` Greg KH
2013-06-04  2:00   ` Xufeng Zhang
2013-06-05  0:13     ` Ben Hutchings
2013-06-05  2:20       ` Xufeng Zhang [this message]
2013-06-05  2:55 ` Xufeng Zhang
2013-06-07 10:39   ` Xufeng Zhang

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=51AEA06A.7040206@windriver.com \
    --to=xufeng.zhang@windriver.com \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=stable@vger.kernel.org \
    --cc=vyasevich@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox