From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Paul Mundt <lethal@linux-sh.org>
Subject: linux-next tree addition request (fbdev)
Date: Wed, 24 Aug 2011 13:40:46 +0000 [thread overview]
Message-ID: <4E54FF5E.5050308@gmx.de> (raw)
Hi Stephen,
can you please add
git://github.com/schandinat/linux-2.6.git fbdev-next
to linux-next. It collects patches for the frame buffer subsystem.
Can you please add the linux-fbdev@vger.kernel.org mailing list as additional
contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated
patches that will conflict with the newer versions.
Thanks,
Florian Tobias Schandinat
next reply other threads:[~2011-08-24 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 13:40 Florian Tobias Schandinat [this message]
2011-08-24 14:33 ` linux-next tree addition request (fbdev) Stephen Rothwell
2011-08-28 16:19 ` Stephen Rothwell
2011-08-29 6:02 ` Paul Mundt
2011-08-29 10:47 ` Florian Tobias Schandinat
2011-08-29 23:43 ` Stephen Rothwell
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=4E54FF5E.5050308@gmx.de \
--to=florianschandinat@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).