From: Juan Manuel Cabo <juanmanuel.cabo@gmail.com>
To: Kieran Clancy <clancy.kieran@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Joseph Salisbury <joseph.salisbury@canonical.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Li Guang <lig.fnst@cn.fujitsu.com>,
Lan Tianyu <tianyu.lan@intel.com>,
Dennis Jansen <dennis.jansen@web.de>
Subject: Re: [PATCH v2] ACPI / EC: Clear stale EC events on Samsung systems
Date: Wed, 05 Mar 2014 22:36:05 -0300 [thread overview]
Message-ID: <5317D105.6050206@gmail.com> (raw)
In-Reply-To: <CAGf84QK-N+C6eHct4XDzOCHwfN649F2okJ1y2V70wWz-wHFKEA@mail.gmail.com>
Beware, the context line:
static struct dmi_system_id ec_dmi_table[] __initdata = {
has changed in recent kernels, so that line of the patch would need
to be different for it to apply older kernels.
It used to be this:
static struct dmi_system_id __initdata ec_dmi_table[] = {
until 3.11 I guess.
It is just a context line and is not important for the patch itself.
See:
http://lxr.free-electrons.com/source/drivers/acpi/ec.c?v=3.11
http://lxr.free-electrons.com/source/drivers/acpi/ec.c?v=3.12
Cheers!
--Juan Manuel Cabo
On 03/05/2014 10:24 PM, Kieran Clancy wrote:
> On Thu, Mar 6, 2014 at 11:22 AM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>> On Thursday, March 06, 2014 11:04:14 AM Kieran Clancy wrote:
>>> Rafael, is it a separate process to get this in the stable tree or
>>> will it naturally happen after being merged into the mainline?
>> I need to add a proper "CC stable" tag to your patch for this to happen.
>>
>> Which -stable kernels should it go to?
> 3.2 and 3.10 seem like natural choices (3.4?), but I don't know the
> norm for this kind of fix. Would there be any reason not to include it
> in some particular stable kernels?
>
> Cheers,
> Kieran.
>
next prev parent reply other threads:[~2014-03-06 1:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 15:42 [PATCH] ACPI / EC: Clear stale EC events on Samsung systems Kieran Clancy
2014-02-26 23:45 ` Rafael J. Wysocki
2014-02-27 0:45 ` Kieran Clancy
2014-02-27 0:59 ` Kieran Clancy
2014-02-27 1:16 ` Rafael J. Wysocki
2014-02-27 1:09 ` Kieran Clancy
2014-02-27 22:02 ` Rafael J. Wysocki
2014-02-27 1:15 ` Rafael J. Wysocki
2014-02-27 1:59 ` Li Guang
2014-02-27 2:33 ` Juan Manuel Cabo
2014-02-27 3:14 ` Li Guang
2014-02-27 3:31 ` Juan Manuel Cabo
2014-02-27 3:45 ` Li Guang
2014-02-27 3:49 ` Kieran Clancy
2014-02-27 4:47 ` Li Guang
2014-02-27 13:41 ` Hello Kieran Juan Manuel Cabo
2014-02-28 14:12 ` [PATCH v2] ACPI / EC: Clear stale EC events on Samsung systems Kieran Clancy
2014-03-02 0:40 ` Rafael J. Wysocki
2014-03-05 18:30 ` Joseph Salisbury
2014-03-06 0:34 ` Kieran Clancy
2014-03-06 0:52 ` Rafael J. Wysocki
2014-03-06 1:24 ` Kieran Clancy
2014-03-06 1:36 ` Juan Manuel Cabo [this message]
2014-03-06 12:32 ` Rafael J. Wysocki
2014-03-06 23:12 ` Joseph Salisbury
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=5317D105.6050206@gmail.com \
--to=juanmanuel.cabo@gmail.com \
--cc=clancy.kieran@gmail.com \
--cc=dennis.jansen@web.de \
--cc=joseph.salisbury@canonical.com \
--cc=lenb@kernel.org \
--cc=lig.fnst@cn.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tianyu.lan@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).