git trees which are not yet in linux-next - Kernel

This is a discussion on git trees which are not yet in linux-next - Kernel ; Hi Pekka, On Mon, 5 May 2008 21:41:53 +0300 (EEST) Pekka J Enberg wrote: > > Well, I only really have three kinds of patches: (1) testing, (2) > for-linus asap (fixes in the middle of a release cycle) and ...

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 21 to 29 of 29

Thread: git trees which are not yet in linux-next

  1. Re: git trees which are not yet in linux-next

    Hi Pekka,

    On Mon, 5 May 2008 21:41:53 +0300 (EEST) Pekka J Enberg wrote:
    >
    > Well, I only really have three kinds of patches: (1) testing, (2)
    > for-linus asap (fixes in the middle of a release cycle) and (3) for-linus
    > when the merge window opens. Up until now, I've put (1) in for-mm and
    > after enough exposure (and no bug reports) they graduate into (2) or (3).
    >
    > So the problem here is where I put the patches in category (1)? If
    > they can go into for-next, then for-mm can disappear. Stephen?


    Stefan Richter is right: if they have passed your review and testing in
    isolation, then they are allowed into -next for testing against other
    subsystems. So (2), (3), and (1b) ... :-)

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIH+FwTgG2atn1QN8RArC+AJ0WkPw6xLKyt/N2xAcfuxZeHTznGQCgg6tG
    DLeEjgOiJRbirJd1TMSE0Bs=
    =XO82
    -----END PGP SIGNATURE-----


  2. Re: git trees which are not yet in linux-next

    On Mon, 5 May 2008 10:57:28 -0700 Andrew Morton wrote:
    >
    > On Mon, 05 May 2008 17:52:16 +0100
    > Liam Girdwood wrote:
    >
    > > On Fri, 2008-05-02 at 15:12 -0700, Andrew Morton wrote:
    > >
    > > >
    > > > (This list is probably incomplete - there might be other trees which are
    > > > presently empty but which aren't in linux-next yet)

    > >
    > > Any chance the voltage/current regulator tree could be added :-
    > >
    > > ´╗┐git-regulator: git://opensource.wolfsonmicro.com/linux-2.6-audioplus.git#for-akpm
    > >

    >
    > Yup, I added that, thanks.


    Was there a request in there for linux-next as well? ;-)

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIH+KBTgG2atn1QN8RAtTgAKCYaJXuoS6b/D2Rx14YxpVRj0aNPQCfQTCe
    xdk5Rj7JrVbdIw4L8E3avEM=
    =Lm28
    -----END PGP SIGNATURE-----


  3. Re: git trees which are not yet in linux-next

    On Mon, 5 May 2008 11:31:28 -0700 Andrew Morton wrote:
    >
    > So I'd suggest that you have a #for-next which contains material for 2.6.26
    > and 2.6.27 and a #for-mm which contains material for 2.6.28+.
    >
    > Only problem is, I'd need to generate the #for-next -> #for-mm diff, and
    > that particular git operation has been troublesome in the past.


    Yeah, it is fine if one is a subset of the other but otherwise fraught
    with danger.

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIH+H1TgG2atn1QN8RAtopAJ9s6CVvLcN56/yMlkPxM5ztOyAk3wCeOiBP
    GFjfJAKh4g1jIX36IDKqvpo=
    =dWus
    -----END PGP SIGNATURE-----


  4. Re: git trees which are not yet in linux-next

    On Tue, 6 May 2008 14:45:49 +1000 Stephen Rothwell wrote:

    > On Mon, 5 May 2008 10:57:28 -0700 Andrew Morton wrote:
    > >
    > > On Mon, 05 May 2008 17:52:16 +0100
    > > Liam Girdwood wrote:
    > >
    > > > On Fri, 2008-05-02 at 15:12 -0700, Andrew Morton wrote:
    > > >
    > > > >
    > > > > (This list is probably incomplete - there might be other trees which are
    > > > > presently empty but which aren't in linux-next yet)
    > > >
    > > > Any chance the voltage/current regulator tree could be added :-
    > > >
    > > > ___git-regulator: git://opensource.wolfsonmicro.com/linux-2.6-audioplus.git#for-akpm
    > > >

    > >
    > > Yup, I added that, thanks.

    >
    > Was there a request in there for linux-next as well? ;-)


    I thought about it. It's a once-off tree rather than a permanent thing.
    Do you do those?

    Getting it into linux-next would of course give better testing coverage.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: git trees which are not yet in linux-next

    On Mon, 5 May 2008 22:50:09 -0700 Andrew Morton wrote:
    >
    > On Tue, 6 May 2008 14:45:49 +1000 Stephen Rothwell wrote:
    >
    > > Was there a request in there for linux-next as well? ;-)

    >
    > I thought about it. It's a once-off tree rather than a permanent thing.
    > Do you do those?


    I do, as long as I am kept informed. Willy's semaphore trees for example.

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIIAY0TgG2atn1QN8RAntkAJ0bwypnFJjkdchch+0as9 KBmfpTHACfTh5v
    qycW1Js5odMoQXkknYiTgbU=
    =aRg3
    -----END PGP SIGNATURE-----


  6. Re: git trees which are not yet in linux-next

    On Fri, 2 May 2008 15:12:06 -0700
    Andrew Morton wrote:

    >
    > git-mmc: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git#for-andrew
    >


    The stuff I've pushed to Andrew has always been what I've been hoping
    to merge in the next window, so it should just be a matter of renaming
    the branch. There is a #next at the above URI now.

    Rgds
    --
    -- Pierre Ossman

    Linux kernel, MMC maintainer http://www.kernel.org
    rdesktop, core developer http://www.rdesktop.org
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  7. Re: git trees which are not yet in linux-next

    Hi Pierre,

    On Tue, 13 May 2008 08:36:15 +0200 Pierre Ossman wrote:
    >
    > On Fri, 2 May 2008 15:12:06 -0700
    > Andrew Morton wrote:
    >
    > >
    > > git-mmc: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git#for-andrew
    > >

    >
    > The stuff I've pushed to Andrew has always been what I've been hoping
    > to merge in the next window, so it should just be a matter of renaming
    > the branch. There is a #next at the above URI now.


    I have added that for tomorrow, thanks.

    I noticed that that tree also has a for-linus branch. Would that be bug
    fixes and stuff lined up for this release i.e. 2.6.26? If so, I could
    add that to linux-next as well as one of the early merge trees.

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIKTysTgG2atn1QN8RArOmAJ91N2OSlxJ++pTVc8Oj0o teA1XctgCeN+q4
    MLS6vQmdscXf1lawUtavSfU=
    =x8W1
    -----END PGP SIGNATURE-----


  8. Re: git trees which are not yet in linux-next

    On Tue, 13 May 2008 17:00:52 +1000
    Stephen Rothwell wrote:

    > Hi Pierre,
    >
    > On Tue, 13 May 2008 08:36:15 +0200 Pierre Ossman wrote:
    > >
    > > The stuff I've pushed to Andrew has always been what I've been hoping
    > > to merge in the next window, so it should just be a matter of renaming
    > > the branch. There is a #next at the above URI now.

    >
    > I have added that for tomorrow, thanks.
    >
    > I noticed that that tree also has a for-linus branch. Would that be bug
    > fixes and stuff lined up for this release i.e. 2.6.26? If so, I could
    > add that to linux-next as well as one of the early merge trees.
    >


    That's correct. But I've always made sure that for-linus is the base for
    for-andrew (now next), so that should not be necessary.

    --
    -- Pierre Ossman

    Linux kernel, MMC maintainer http://www.kernel.org
    rdesktop, core developer http://www.rdesktop.org
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: git trees which are not yet in linux-next

    Hi Pierre,

    On Tue, 13 May 2008 12:47:45 +0200 Pierre Ossman wrote:
    >
    > That's correct. But I've always made sure that for-linus is the base for
    > for-andrew (now next), so that should not be necessary.


    What it allows me to do, though, is drop your "next" tree if things go
    really bad without dropping fixes for Linus' current tree that you deem
    necessary.

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIKYqrTgG2atn1QN8RAkyVAJsEkNxMvuyM+qe6UdmcbK RBMkMSmgCePHC8
    jnyYOD+pXwAdXKn/1e8wnKo=
    =pQxf
    -----END PGP SIGNATURE-----


+ Reply to Thread
Page 2 of 2 FirstFirst 1 2