From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Heiko Carstens <hca@linux•ibm.com>
Cc: Vasily Gorbik <gor@linux•ibm.com>,
Christian Borntraeger <borntraeger@de•ibm.com>,
linux-next@vger•kernel.org
Subject: Re: linux-next: add s390 set_fs branch?
Date: Thu, 17 Sep 2020 08:54:29 +1000 [thread overview]
Message-ID: <20200917085138.0bd1998e@canb.auug.org.au> (raw)
In-Reply-To: <20200916162846.GE7076@osiris>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Hi Heiko,
On Wed, 16 Sep 2020 18:28:46 +0200 Heiko Carstens <hca@linux•ibm.com> wrote:
>
> 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#fixes
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git#features
> git://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).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-16 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 15:55 linux-next: add s390 set_fs branch? Heiko Carstens
2020-09-15 23:54 ` Stephen Rothwell
2020-09-16 16:28 ` Heiko Carstens
2020-09-16 22:54 ` Stephen Rothwell [this message]
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=20200917085138.0bd1998e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=gor@linux$(echo .)ibm.com \
--cc=hca@linux$(echo .)ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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