stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gong <gong.chen@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: mchehab@redhat.com, bp@amd64.org, tony.luck@intel.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH V3] edac: avoid mce decoding crash after edac driver unloaded
Date: Tue, 08 May 2012 14:59:22 +0800	[thread overview]
Message-ID: <4FA8C44A.3070700@linux.intel.com> (raw)
In-Reply-To: <20120507155202.GA3934@kroah.com>

...
> 
> <formletter>
> 
> This is not the correct way to submit patches for inclusion in the
>  stable kernel tree.  Please read 
> Documentation/stable_kernel_rules.txt for how to do this properly.
> 
> </formletter> -- To unsubscribe from this list: send the line 
> "unsubscribe linux-edac" in the body of a message to 
> majordomo@vger.kernel.org More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> 

Hi, Greg

Do you mean I need to add some information in my patch as below:

Cc: <stable@vger.kernel.org> # 3.3.y:
Cc: <stable@vger.kernel.org> # 3.2.y: 3653ada: x86, mce: Add wrappers
Cc: <stable@vger.kernel.org> # 3.2.y:


For 3.3.y, commit 3653ada has been there so it is not necessary. Is it
OK to send one patch to two -stable trees?


  reply	other threads:[~2012-05-08  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05  1:20 [PATCH] edac: avoid mce decoding crash after edac driver unloaded Chen Gong
2012-05-05  1:57 ` Chen Gong
2012-05-05 10:05 ` Borislav Petkov
2012-05-07  7:03 ` Chen Gong
2012-05-07 10:42   ` Mauro Carvalho Chehab
2012-05-07 13:05   ` [PATCH V3] " Chen Gong
2012-05-07 15:52     ` Greg KH
2012-05-08  6:59       ` Chen Gong [this message]
2012-05-08 13:24         ` Greg KH
2012-05-08 23:40         ` [PATCH RESEND " Chen Gong

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=4FA8C44A.3070700@linux.intel.com \
    --to=gong.chen@linux.intel.com \
    --cc=bp@amd64.org \
    --cc=greg@kroah.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).