* Re: beginner questions on being added to the linux tree [not found] <77A0A4DB5BF2A44283E5522C27234AC6021A5F78@EDPRSRV011.logicpd.com> @ 2010-08-10 1:09 ` Stephen Rothwell 2010-08-10 6:50 ` Tony Lindgren 0 siblings, 1 reply; 2+ messages in thread From: Stephen Rothwell @ 2010-08-10 1:09 UTC (permalink / raw) To: Jacob Tanenbaum; +Cc: Russell King, Tony Lindgren, linux-omap [-- Attachment #1: Type: text/plain, Size: 1570 bytes --] 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. 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. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ [-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --] ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: beginner questions on being added to the linux tree 2010-08-10 1:09 ` beginner questions on being added to the linux tree Stephen Rothwell @ 2010-08-10 6:50 ` Tony Lindgren 0 siblings, 0 replies; 2+ messages in thread From: Tony Lindgren @ 2010-08-10 6:50 UTC (permalink / raw) To: Stephen Rothwell; +Cc: Jacob Tanenbaum, Russell King, linux-omap * 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-08-10 6:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 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).