From: Jonathan Nieder <jrnieder@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org,
"Mirosław Zalewski" <miniopl@poczta.onet.pl>,
linux-acpi@vger.kernel.org, "Len Brown" <len.brown@intel.com>,
"Lin Ming" <ming.m.lin@intel.com>
Subject: Re: [2.6.32] Please cherry-pick Toshiba Satellite DSDT corruption workaround
Date: Tue, 22 Nov 2011 16:47:13 -0600 [thread overview]
Message-ID: <20111122224713.GD6274@elie.hsd1.il.comcast.net> (raw)
In-Reply-To: <20111122223601.GB31434@kroah.com>
Greg KH wrote:
> These all do not look like the match up with the stable_kernel_rules.txt
> file, do they?
I assume you mean because they are too big / nontrivial? If so, then
that makes sense.
Thanks for explaining.
Jonathan
prev parent reply other threads:[~2011-11-22 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111118200908.3274.86645.reportbug@pingwin>
2011-11-19 5:14 ` [2.6.32] Please cherry-pick Toshiba Satellite DSDT corruption workaround Jonathan Nieder
2011-11-22 22:36 ` Greg KH
2011-11-22 22:47 ` Jonathan Nieder [this message]
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=20111122224713.GD6274@elie.hsd1.il.comcast.net \
--to=jrnieder@gmail.com \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=miniopl@poczta.onet.pl \
--cc=stable@vger.kernel.org \
/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