From: Bryan Wu <cooloney@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christian Gmeiner <christian.gmeiner@gmail.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks
Date: Tue, 14 May 2013 10:36:19 -0700 [thread overview]
Message-ID: <CAK5ve-+jBNTLrU5jRqj7LyxrQBWAE7GC634qYRJ4zDy2_LqgcA@mail.gmail.com> (raw)
In-Reply-To: <20130514101608.60c64b73.akpm@linux-foundation.org>
On Tue, May 14, 2013 at 10:16 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 14 May 2013 10:12:04 -0700 Bryan Wu <cooloney@gmail.com> wrote:
>
>> On Tue, May 14, 2013 at 12:06 AM, Christian Gmeiner
>> <christian.gmeiner@gmail.com> wrote:
>> > 2013/5/12 Christian Gmeiner <christian.gmeiner@gmail.com>:
>> >> 2013/3/8 Christian Gmeiner <christian.gmeiner@gmail.com>:
>> >>> 2013/3/5 Bryan Wu <cooloney@gmail.com>:
>> >>>> On Sun, Mar 3, 2013 at 11:40 PM, Christian Gmeiner
>> >>>> <christian.gmeiner@gmail.com> wrote:
>> >>>>> ping
>> >>>>> --
>>
>> I found this patch is still in linux-next, I'm not sure whether it
>> will be merged into 3.10 like a bug fixing. We need to wait Andrew's
>> reply. I'm OK to pick up and send out to Linus as a bug fixing.
>
> whome, I'd forgotten I had this. I stuck a cc:stable on the end and
> shall send it in to Linus in the next 3.10 batch, OK?
>
No problem for me at all. I bet it's OK for Christian as well, since
merging into 3.10-rc1 has no difference with merging into 3.10-rc2 or
later. It will eventually show up in 3.10 release.
Thanks,
-Bryan
next prev parent reply other threads:[~2013-05-14 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 15:58 [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks Christian Gmeiner
2013-02-13 15:54 ` Greg KH
2013-02-15 22:47 ` Bryan Wu
2013-02-23 9:20 ` Christian Gmeiner
2013-03-04 7:40 ` Christian Gmeiner
2013-03-05 18:46 ` Bryan Wu
2013-03-08 7:26 ` Christian Gmeiner
2013-05-12 10:11 ` Christian Gmeiner
2013-05-14 7:06 ` Christian Gmeiner
2013-05-14 17:12 ` Bryan Wu
2013-05-14 17:16 ` Andrew Morton
2013-05-14 17:36 ` Bryan Wu [this message]
2013-05-15 6:38 ` Christian Gmeiner
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=CAK5ve-+jBNTLrU5jRqj7LyxrQBWAE7GC634qYRJ4zDy2_LqgcA@mail.gmail.com \
--to=cooloney@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christian.gmeiner@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).