From: Greg KH <greg@kroah.com>
To: Nigel Cunningham <nigel@tuxonice.net>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
kernel-janitors@vger.kernel.org, linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Template of what you're after? (Was [ANNOUNCE] linux-staging tree created)
Date: Wed, 11 Jun 2008 09:23:03 -0700 [thread overview]
Message-ID: <20080611162303.GA22134@kroah.com> (raw)
In-Reply-To: <1213157025.16146.40.camel@nigel-laptop>
On Wed, Jun 11, 2008 at 02:03:45PM +1000, Nigel Cunningham wrote:
> Hi again.
>
> On Tue, 2008-06-10 at 20:29 -0700, Greg KH wrote:
> > Is the patch "stand-alone", only adding new code in discrete chunks like
> > a new driver or filesystem would?
>
> Just another thought - I should have said that I don't really know what
> patches to add a new driver or filesystem look like. I can only imagine
> a filesystem going in all-in-one-patch, so I'd probably appreciate an
> example/template to work off, as might others.
If you look in the -staging tree, there are 17 "template/example"
patches in there to go off of :)
Basically, one patch per feature. It sounds like the tuxonice is much
too big for this kind of thing.
Just respin your patches and post them to lkml for review. You should
be able to set up your own tree for inclusion in linux-next if they are
ready to go in.
thanks,
greg k-h
next prev parent reply other threads:[~2008-06-11 16:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:05 [ANNOUNCE] linux-staging tree created Greg KH
2008-06-10 19:06 ` linux-staging status for June 10, 2008 Greg KH
2008-06-10 22:52 ` [ANNOUNCE] linux-staging tree created Theodore Tso
2008-06-10 23:05 ` Greg KH
2008-06-11 0:07 ` Felipe Balbi
2008-06-11 3:28 ` Greg KH
2008-06-11 1:05 ` Nigel Cunningham
2008-06-11 3:29 ` Greg KH
2008-06-11 4:00 ` Nigel Cunningham
2008-06-11 16:24 ` Greg KH
2008-06-11 4:03 ` Template of what you're after? (Was [ANNOUNCE] linux-staging tree created) Nigel Cunningham
2008-06-11 16:23 ` Greg KH [this message]
2008-06-11 9:27 ` [ANNOUNCE] linux-staging tree created Benny Halevy
2008-06-11 9:50 ` Boaz Harrosh
2008-06-11 9:58 ` Felipe Balbi
2008-06-11 16:25 ` Greg KH
2008-06-11 17:43 ` Boaz Harrosh
2008-06-11 16:25 ` Greg KH
2008-06-11 10:45 ` Will Newton
2008-06-11 16:26 ` Greg KH
2008-06-12 11:37 ` Will Newton
2008-06-12 23:54 ` Greg KH
2008-06-13 14:14 ` Luis R. Rodriguez
2008-06-13 14:33 ` John W. Linville
2008-06-13 15:51 ` Luis R. Rodriguez
[not found] ` <20080613143328.GA16506-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-14 0:28 ` Greg KH
[not found] ` <43e72e890806130714k535b041evaf750209ea492c47-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-14 0:27 ` Greg KH
2008-06-17 12:51 ` Pavel Machek
2008-07-02 23:11 ` Greg KH
2008-07-14 2:50 ` Jike Song
2008-07-14 2:56 ` Greg KH
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=20080611162303.GA22134@kroah.com \
--to=greg@kroah.com \
--cc=devel@linuxdriverproject.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nigel@tuxonice.net \
--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).