From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: "linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
ext Tony Lindgren <tony@atomide.com>
Subject: Re: [Linux-fbdev-devel] Getting DSS2 to mainline
Date: Mon, 17 Aug 2009 14:17:17 +0200 [thread overview]
Message-ID: <4A894A4D.4000501@gmx.de> (raw)
In-Reply-To: <4A893DF4.3050705@nokia.com>
Hi,
Tomi Valkeinen schrieb:
> Hi,
>
> As I'm new to sending patches upstream, I'm not sure how to go forward
> with DSS2 now. Should I send it to linux-arm-kernel mailing list, or
> directly to main linux kernel mailing list? Or is there a route through
> fbdev-devel list for DSS2 to go forward?
I am also new to this process but from what I've heard I decided to
always cc Andrew Morton <akpm@linux-foundation.org> when I think that
something is mature enough for inclusion. That works very well, thanks
Andrew.
Sending them only to linux-fbdev-devel looks rather like a dead end at
least if I look on the fate of some patches in the archive.
I always cc the LKML but until now I didn't hear anything from there
either so I doubt that would be the right way.
I'm sorry if anything of the above is incorrect, it's just my experience.
Regards,
Florian Tobias Schandinat
next prev parent reply other threads:[~2009-08-17 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 11:24 Getting DSS2 to mainline Tomi Valkeinen
2009-08-17 12:17 ` Florian Tobias Schandinat [this message]
2009-08-17 13:54 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2009-08-17 13:46 ` Tony Lindgren
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=4A894A4D.4000501@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.com \
/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).