From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DaVinci fix for v3.7
Date: Tue, 20 Nov 2012 10:41:00 +0530 [thread overview]
Message-ID: <50AB10E4.9080806@ti.com> (raw)
In-Reply-To: <CAOesGMjK_DXx_n7aL85SP7azqFsEOAJgfpTd-rpDCisvT_mysQ@mail.gmail.com>
On 11/19/2012 10:23 PM, Olof Johansson wrote:
> On Mon, Nov 19, 2012 at 1:42 AM, Sekhar Nori <nsekhar@ti.com> wrote:
>> Hi Arnd, Olof,
>>
>> Can you please pull the following DaVinci fix for v3.7? I know its pretty late,
>> I was out of office for most of the -rc cycle this time.
>>
>> The change deserves a stable tag, I did not add it though since the patch
>> does not apply cleanly to any of the previous kernel releases. It will have
>> to be backported and send to the stable team once it makes it into mainline.
>>
>> Thanks,
>> Sekhar
>>
>> The following changes since commit f4a75d2eb7b1e2206094b901be09adb31ba63681:
>>
>> Linux 3.7-rc6 (2012-11-16 17:42:40 -0800)
>>
>> are available in the git repository at:
>>
>> git://gitorious.org/linux-davinci/linux-davinci.git tags/davinci-fixes-for-v3.7
>
> Pulled, thanks. Gitorious wasn't horribly slow this morning so I'll
> take care of the remainder of your 3.8 pull requests too. :)
Thanks! I had requested a k.o account earlier but got no response. That
was before k.o was hacked. I will request again, but I guess I will be
rejected since my PGP key is signed by just one kernel developer (I
guess I need to start traveling and meeting people more often).
Sekhar
prev parent reply other threads:[~2012-11-20 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 9:42 [GIT PULL] DaVinci fix for v3.7 Sekhar Nori
2012-11-19 16:53 ` Olof Johansson
2012-11-20 5:11 ` Sekhar Nori [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=50AB10E4.9080806@ti.com \
--to=nsekhar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.