From: Tony Prisk <linux@prisktech.co.nz>
To: FlorianSchandinat@gmx.de
Cc: fbdev-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: fb: vt8500: Unmerged patches for 3.9
Date: Thu, 24 Jan 2013 18:40:21 +1300 [thread overview]
Message-ID: <1359006021.21499.3.camel@gitbox> (raw)
Hi Florian,
I have a couple of patches that were submitted 02/Jan/13 that are still
floating around - I couldn't see them added to your fbdev-next branch
either.
https://patchwork.kernel.org/patch/1924971/
https://patchwork.kernel.org/patch/1925021/
https://patchwork.kernel.org/patch/1924961/
https://patchwork.kernel.org/patch/1924951/
Still on Christmas holidays or did they slip through the cracks?
Regards
Tony Prisk
reply other threads:[~2013-01-24 5:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1359006021.21499.3.camel@gitbox \
--to=linux@prisktech.co.nz \
--cc=FlorianSchandinat@gmx.de \
--cc=fbdev-linux@vger.kernel.org \
--cc=linux-kernel@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