From: Tony Lindgren <tony@atomide.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jacob Tanenbaum <Jacob.Tanenbaum@logicpd.com>,
Russell King <rmk@arm.linux.org.uk>,
linux-omap@vger.kernel.org
Subject: Re: beginner questions on being added to the linux tree
Date: Tue, 10 Aug 2010 09:50:47 +0300 [thread overview]
Message-ID: <20100810065046.GF32480@atomide.com> (raw)
In-Reply-To: <20100810110915.9e2ddc27.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> [100810 04:02]:
> Hi Jacob,
>
> On Mon, 9 Aug 2010 19:36:01 -0500 "Jacob Tanenbaum" <Jacob.Tanenbaum@logicpd.com> wrote:
> >
> > I work for LogicPD and am trying to add new support for
> > there OMAP3 development boards to the kernel, I have a working version
> > of some of the base support and was wondering how to get that ready to
> > be merged in during this merge window. We have tested the code against
> > the most recent version of linux-next I can get to build and was
> > wondering where to go. Do I send merge requests to the linux-next list
> > or a series of patches. I have sent patches to the omap and arm lists
> > and got some minor syntax errors reported by them (spaces instead of
> > tabs and the like) and was wondering where to go from here.
>
> I only merge other people's trees, so you need to set up a git tree
> somewhere and tell me (cc'ing linux-next and all other appropriate
> lists/people) where it is and which branch to fetch. I then fetch that
> branch each day and merge it with everything else.
>
> Getting your code merged by Linus during this merge window is up to Linus
> and Russell or Tony, I guess. But I cannot take new trees now until
> after -rc1 is out. So if you really want your code merged during this
> merge window, your best bet is to convince Russell and/or Tony.
Yeah, it's too late for this merge window. But after -rc1 I'll start
queuing things up for the next merge window. That way your patches will
go to Stephen's for-next tree and then get pulled into the mainline
tree during the next merge window.
> Having your tree in linux-next may be useful for ongoing development
> unless Tony thinks it may be better for you to just submit your code
> through his omap tree.
If you have patches coming on continuous basis, then maintaining
a git branch makes sense. For occasional sets of patches, it's probably
easier to just email them to the list.
Regards,
Tony
prev parent reply other threads:[~2010-08-10 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <77A0A4DB5BF2A44283E5522C27234AC6021A5F78@EDPRSRV011.logicpd.com>
2010-08-10 1:09 ` beginner questions on being added to the linux tree Stephen Rothwell
2010-08-10 6:50 ` Tony Lindgren [this message]
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=20100810065046.GF32480@atomide.com \
--to=tony@atomide.com \
--cc=Jacob.Tanenbaum@logicpd.com \
--cc=linux-omap@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--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 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.