From: Jingoo Han <jg1.han@samsung.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: Call for fbdev fixes for 3.9
Date: Mon, 25 Mar 2013 02:40:03 +0000 [thread overview]
Message-ID: <00b501ce2902$0debe580$29c3b080$%han@samsung.com> (raw)
In-Reply-To: <514C1125.9040000@ti.com>
On Friday, March 22, 2013 5:07 PM, Tomi Valkeinen wrote:
>
> Hi,
>
> If nobody objects, I'll collect fbdev fixes for 3.9. Note that I'll only
> take fixes, as it's already -rc3.
CC'ed Andrew Morton.
Hi Tomi Valkeinen,
I do not object. :)
I agree with you.
Thank you for taking care of fbdev fixes for 3.9.
Best regards,
Jingoo Han
>
> So, send the patches to me if there's only a few of them, but for bigger
> series please send a proper pull request, with annotated tag shortly
> describing the changes.
>
> And only reviewed and good patches, nothing controversial =).
>
> Tomi
prev parent reply other threads:[~2013-03-25 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 8:07 Call for fbdev fixes for 3.9 Tomi Valkeinen
2013-03-25 2:40 ` Jingoo Han [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='00b501ce2902$0debe580$29c3b080$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=linux-fbdev@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).