linux-next: add s390 set_fs branch?
Hi Stephen,
could you please add the 'set_fs' branch of the s390 kernel.org repository to linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git set_fs
I'm wondering what the best way would be to deal with additional s390 specific topic branches and how to get them merged into linux-next?
As far as I can tell other maintainers merge all their branches into a 'for-next' branch, so that you only need to pull one branch (and don't need to deal with requests like this one ;) ).
Would that the best way for you? If so we could simply do the same for s390 as well. Please let us know.
Thank you!
Hi Heiko,
Quoted 9 lines · On Tue, 15 Sep 2020 17:55:34 +0200 Heiko Carstens <[email protected]> wrote:
could you please add the '
set_fs' branch of the s390 kernel.org repository to linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.gitset_fsI'm wondering what the best way would be to deal with additional s390 specific topic branches and how to get them merged into linux-next?
Quoted 6 lines
As far as I can tell other maintainers merge all their branches into a 'for-next' branch, so that you only need to pull one branch (and don't need to deal with requests like this one ;) ).
Would that the best way for you? If so we could simply do the same for s390 as well. Please let us know.
Yes, normally maintainers merge their topic branches into a single "for-next" (or similar) branch for me to merge. However, in some cases I carry separate topic branches. So what ever is easiest.
I have added the set_fs branch today (I called it s390-setfs). If this is going to be short lived (or you decide to do the merge yourself), please try to remember to tell me to remove it when it is done with.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Signature · 3 lines
Cheers, Stephen Rothwell [email protected]
Hi Stephen,
Quoted 10 lines
Quoted 9 lines
I'm wondering what the best way would be to deal with additional s390 specific topic branches and how to get them merged into linux-next?
As far as I can tell other maintainers merge all their branches into a 'for-next' branch, so that you only need to pull one branch (and don't need to deal with requests like this one ;) ).
Would that the best way for you? If so we could simply do the same for s390 as well. Please let us know.
Quoted 7 lines
Yes, normally maintainers merge their topic branches into a single "for-next" (or similar) branch for me to merge. However, in some cases I carry separate topic branches. So what ever is easiest.
I have added the
set_fsbranch today (I called it s390-setfs). If this is going to be short lived (or you decide to do the merge yourself), please try to remember to tell me to remove it when it is done with.
Ok, so we have a "for-next" branch now:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-next
If you would include that in linux-next then you can drop the following ones:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#fixesgit://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#featuresgit://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#set_fs
Thanks a lot!
Hi Heiko,
Quoted 11 lines · On Wed, 16 Sep 2020 18:28:46 +0200 Heiko Carstens <[email protected]> wrote:
Ok, so we have a "for-next" branch now:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.gitfor-nextIf you would include that in linux-next then you can drop the following ones:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#fixesgit://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#featuresgit://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#set_fs
I have removed the s390-setfs tree and updated the s390 tree. I like to keep the s390-fixes tree separate as I merge all the pending fixes
early and they get tested separately. That should not stop you
merging your fixes branch into your for-next branch as well (to get rid of conflicts or you local testing).
Signature · 2 lines
Cheers, Stephen Rothwell
Hi Stephen,
Quoted 13 lines · Stephen Rothwell
Quoted 11 lines · On Wed, 16 Sep 2020 18:28:46 +0200 Heiko Carstens <[email protected]> wrote:
Ok, so we have a "for-next" branch now:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.gitfor-nextIf you would include that in linux-next then you can drop the following ones:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#fixesgit://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#featuresgit://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#set_fs
Quoted 5 lines
I have removed the s390-setfs tree and updated the s390 tree. I like to keep the s390-fixes tree separate as I merge all the pending fixes
early and they get tested separately. That should not stop you
merging your fixes branch into your for-next branch as well (to get rid of conflicts or you local testing).
Great, thank you!