From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: Submitting fbdev tree patches
Date: Tue, 26 Mar 2013 19:37:36 +1300 [thread overview]
Message-ID: <1364279856.25738.4.camel@gitbox> (raw)
In-Reply-To: <25978865.106801364189231752.JavaMail.weblogic@epv6ml06>
On Mon, 2013-03-25 at 05:27 +0000, Jingoo Han wrote:
> On Monday, March 25, 2013 2:11 PM, Tony Prisk wrote:
> >
> > Is anyone taking patches for fbdev at the moment?
> >
> > I sent in some patches for 3.9 but didn't hear back - checking the lists
> > it doesn't appear Florian has posted much since the end of Oct 2012.
>
> CC'ed Tomi Valkeinen, Andrew Morton
>
>
> Hi Tony Prisk,
>
> Tomy Valkeien will take care of fbdev fixes for 3.9.
> (http://www.spinics.net/lists/linux-fbdev/msg10243.html)
>
> How about sending a pull request to Tomy?
>
> Best regards,
> Jingoo Han
>
> >
> > Regards
> > Tony Prisk
> >
These are not fixes but new features/changes for 3.10 - I don't want to
create too much work for someone. Any idea when Florian will be back on
board?
Regards
Ton
next parent reply other threads:[~2013-03-26 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25978865.106801364189231752.JavaMail.weblogic@epv6ml06>
2013-03-26 6:37 ` Tony Prisk [this message]
2013-03-25 5:11 Submitting fbdev tree patches Tony Prisk
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=1364279856.25738.4.camel@gitbox \
--to=linux@prisktech.co.nz \
--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).