From: Tony Prisk <linux@prisktech.co.nz>
To: linux-arm-kernel@lists.infradead.org
Subject: Submitting fbdev tree patches
Date: Mon, 25 Mar 2013 05:11:27 +0000 [thread overview]
Message-ID: <1364188287.25442.4.camel@gitbox> (raw)
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.
Regards
Tony Prisk
WARNING: multiple messages have this Message-ID (diff)
From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: Submitting fbdev tree patches
Date: Mon, 25 Mar 2013 18:11:27 +1300 [thread overview]
Message-ID: <1364188287.25442.4.camel@gitbox> (raw)
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.
Regards
Tony Prisk
WARNING: multiple messages have this Message-ID (diff)
From: Tony Prisk <linux@prisktech.co.nz>
To: linux-fbdev@vger.kernel.org
Cc: FlorianSchandinat@gmx.de, linux-kernel@vger.kernel.org,
Arm Kernel Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Submitting fbdev tree patches
Date: Mon, 25 Mar 2013 18:11:27 +1300 [thread overview]
Message-ID: <1364188287.25442.4.camel@gitbox> (raw)
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.
Regards
Tony Prisk
next reply other threads:[~2013-03-25 5:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 5:11 Tony Prisk [this message]
2013-03-25 5:11 ` Submitting fbdev tree patches Tony Prisk
2013-03-25 5:11 ` Tony Prisk
2013-03-25 5:27 ` Jingoo Han
2013-03-25 5:27 ` Jingoo Han
2013-03-26 6:37 ` Tony Prisk
2013-03-26 6:37 ` Tony Prisk
2013-03-26 6:37 ` 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=1364188287.25442.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 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.