From: bryan.wu@canonical.com (Bryan Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] LED CPU trigger driver and ARM LED code consolidation (v2)
Date: Wed, 1 Aug 2012 12:59:09 +0800 [thread overview]
Message-ID: <CAK5ve-KuB=5evdiJDSQbN0N=56fofNeaof==GuRXFWhA44KcAw@mail.gmail.com> (raw)
In-Reply-To: <CAOesGMhK3bkk+86jDM7bd6rFUE_RuTGWiWsB7SYJ=i2NocOiLA@mail.gmail.com>
On Wed, Aug 1, 2012 at 12:55 PM, Olof Johansson <olof@lixom.net> wrote:
> On Tue, Jul 31, 2012 at 9:48 PM, Bryan Wu <bryan.wu@canonical.com> wrote:
>> On Tue, Jul 31, 2012 at 9:46 PM, Bryan Wu <bryan.wu@canonical.com> wrote:
>>> Russell, Arnd and Olof,
>>>
>>
>> I felt very sorry about this issue, the email was archived
>> automatically in my Gmail account. I found the root cause of the issue
>> Russell met and actually that code about trigger_data is totally
>> useless, which was removed just now. I pushed an update version again
>> to the same branch of my git tree. Please consider a pull. If I did
>> something bad, please let me know, I will fix it as soon as possible.
>
> Hi,
>
> We'll pull this in for staging again once the merge window is done.
> It's definitely not 3.6 material at this time.
>
OK, I will rebase to 3.6-rc1 after merge window close and send out
pull request again.
Thanks,
--
Bryan Wu <bryan.wu@canonical.com>
Kernel Developer +86.186-168-78255 Mobile
Canonical Ltd. www.canonical.com
Ubuntu - Linux for human beings | www.ubuntu.com
next prev parent reply other threads:[~2012-08-01 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 13:46 [GIT PULL] LED CPU trigger driver and ARM LED code consolidation (v2) Bryan Wu
2012-08-01 4:48 ` Bryan Wu
2012-08-01 4:55 ` Olof Johansson
2012-08-01 4:59 ` Bryan Wu [this message]
2012-08-01 5:10 ` Olof Johansson
2012-08-11 6:57 ` Bryan Wu
2012-08-11 8:04 ` Russell King - ARM Linux
2012-08-11 14:23 ` Bryan Wu
2012-08-12 4:51 ` Nicolas Pitre
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-KuB=5evdiJDSQbN0N=56fofNeaof==GuRXFWhA44KcAw@mail.gmail.com' \
--to=bryan.wu@canonical.com \
--cc=linux-arm-kernel@lists.infradead.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).