linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
	linux-acpi@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [BUGFIX] ACPI, APEI, Avoid too much error reporting in runtime
Date: Tue, 12 Jun 2012 11:08:10 +0800	[thread overview]
Message-ID: <1339470490.7404.34.camel@yhuang-dev> (raw)
In-Reply-To: <1339421127.4942.8.camel@deadeye.wl.decadent.org.uk>

On Mon, 2012-06-11 at 14:25 +0100, Ben Hutchings wrote:
> On Mon, 2012-06-11 at 14:23 +0800, Huang Ying wrote:
> > This patch fixed the following bug.
> > 
> > https://bugzilla.kernel.org/show_bug.cgi?id=43282
> > 
> > This is caused by a firmware bug checking (checking generic address
> > register provided by firmware) in runtime.  The checking should be
> > done in address mapping time instead of runtime to avoid too much
> > error reporting in runtime.
> > 
> > Reported-by: Pawel Sikora <pluto@agmk.net>
> > Signed-off-by: Huang Ying <ying.huang@intel.com>
> > Tested-by: Jean Delvare <khali@linux-fr.org>
> [...]
> 
> This is not the correct way to submit a patch for stable.  See
> Documentation/stable_kernel_rules.txt.

Thanks for reminding.  Will resend the patch.

Best Regards,
Huang Ying


  reply	other threads:[~2012-06-12  3:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  6:23 [BUGFIX] ACPI, APEI, Avoid too much error reporting in runtime Huang Ying
2012-06-11 13:25 ` Ben Hutchings
2012-06-12  3:08   ` Huang Ying [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-12  3:20 Huang Ying
2012-06-12  4:18 ` Len Brown
2012-06-13  8:03   ` Xiao, Hui

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=1339470490.7404.34.camel@yhuang-dev \
    --to=ying.huang@intel.com \
    --cc=ben@decadent.org.uk \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).