From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Sascha Sommer <saschasommer@freenet.de>
Cc: Jiri Slaby <jirislaby@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
rmk+mmc@arm.linux.org.uk, Elladan <elladan@eskimo.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: Experimental driver for Ricoh Bay1Controller SD Card readers
Date: Tue, 13 Feb 2007 06:47:41 +0100 [thread overview]
Message-ID: <45D150FD.8080901@drzeus.cx> (raw)
In-Reply-To: <200702112122.38440.saschasommer@freenet.de>
Sascha Sommer wrote:
> I still consider this driver experimental, but without documentation this is
> probably not going to change anytime soon.
> The question is now what I should do with the driver?
> Is it worth to be included in the kernel? If yes where and against what
> kernelversion should I send the patch?
>
>
That's up to you. The most important thing for any part of the kernel is
that it must have a maintainer. So if you are ready to keep the driver
up to date and handle the support requests that show, then you should
really submit it.
Patches should always be sent against the current version of the kernel
(i.e. git HEAD). Usually the latest packaged release will also do.
(Note that I haven't had time to review your latest version of the driver)
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-02-13 5:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 23:32 Experimental driver for Ricoh Bay1Controller SD Card readers Sascha Sommer
2007-01-07 9:56 ` Jiri Slaby
2007-02-11 20:22 ` Sascha Sommer
2007-02-13 5:47 ` Pierre Ossman [this message]
2007-02-13 9:48 ` Samuel Thibault
2007-02-13 11:42 ` Sascha Sommer
2007-01-09 20:57 ` Samuel Thibault
2007-01-10 20:10 ` Pierre Ossman
-- strict thread matches above, loose matches on Subject: below --
2007-02-15 22:34 Ivan Babkin
2007-03-09 13:23 ` James
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=45D150FD.8080901@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=elladan@eskimo.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+mmc@arm.linux.org.uk \
--cc=samuel.thibault@ens-lyon.org \
--cc=saschasommer@freenet.de \
/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