From: Benjamin Valentin <benpicco@zedat.fu-berlin.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
STAGING SUBSYSTEM <devel@driverdev.osuosl.org>
Subject: Re: [PATCH] add exFAT driver
Date: Wed, 25 Sep 2013 18:36:32 +0200 [thread overview]
Message-ID: <20130925183632.08a0d073@rechenknecht2k7> (raw)
In-Reply-To: <20130830154205.GA1411@kroah.com>
Am Fri, 30 Aug 2013 08:42:05 -0700
schrieb Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> For staging drivers I need a maintainer that is going to take the time
> to shephard it into the core kernel tree. See other TODO files for
> how that person is defined. Are you going to be willing to do this?
I can see what I can do.
I've cleaned up the code a bit, especially where it would redefine
kernel functions. [1] Should I submit the end result, one file per
patch, or begin with the original code and submit patches on top of
that?
Also, the driver would define it's own data types like
typedef unsigned int UINT32;
I've replaced that with u32, etc as the naming implied the bit size
would matter. (And it probably does for the on-disk file system
structures, but they are used for everything) Is there any disadvantage
to this over using the standard C types?
> Also, I would really like to get a signed-off-by: from the Samsung
> authors for this patch, can you do that as well please?
I've tried reaching them by their last public e-mail addresses I could
find, but they would either bounce or I got no reply.
[1] https://github.com/benpicco/linux_exfat-staging/commits/exfat
next prev parent reply other threads:[~2013-09-25 16:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 10:46 [PATCH] add exFAT driver Benjamin Valentin
2013-08-30 11:08 ` Vyacheslav Dubeyko
2013-08-30 15:42 ` Greg Kroah-Hartman
2013-09-25 16:36 ` Benjamin Valentin [this message]
2013-09-25 16:59 ` Anca Emanuel
2013-09-25 17:27 ` Greg Kroah-Hartman
2013-09-25 18:32 ` Matthew Garrett
2013-09-25 18:45 ` Greg Kroah-Hartman
2013-09-25 19:28 ` Alexander Holler
2013-09-25 20:21 ` Greg Kroah-Hartman
2013-09-25 20:43 ` Alexander Holler
2013-09-25 21:44 ` Anton Altaparmakov
2013-09-25 22:00 ` Alexander Holler
2013-09-25 22:10 ` Greg Kroah-Hartman
2013-09-25 22:29 ` Alexander Holler
2013-09-25 22:53 ` Matthew Garrett
2013-09-26 7:54 ` Anton Altaparmakov
2013-09-26 10:41 ` Dan Carpenter
2013-09-26 10:48 ` Alexander Holler
2013-09-26 11:06 ` Dan Carpenter
2013-09-26 7:50 ` Anton Altaparmakov
2013-09-25 21:57 ` Benjamin Valentin
2013-09-25 22:11 ` Greg Kroah-Hartman
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=20130925183632.08a0d073@rechenknecht2k7 \
--to=benpicco@zedat.fu-berlin.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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 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.