From: Heiko Carstens <hca@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Christoph Hellwig <hch@lst.de>,
linux-next@vger.kernel.org
Subject: linux-next: add s390 set_fs branch?
Date: Tue, 15 Sep 2020 17:55:34 +0200 [thread overview]
Message-ID: <20200915155534.GA11180@osiris> (raw)
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!
next reply other threads:[~2020-09-15 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 15:55 Heiko Carstens [this message]
2020-09-15 23:54 ` linux-next: add s390 set_fs branch? Stephen Rothwell
2020-09-16 16:28 ` Heiko Carstens
2020-09-16 22:54 ` Stephen Rothwell
2020-09-17 7:17 ` Heiko Carstens
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=20200915155534.GA11180@osiris \
--to=hca@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-next@vger.kernel.org \
--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).