From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, Masahiro Yamada <masahiroy@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the fsinfo tree with the kbuid tree
Date: Tue, 18 Aug 2020 09:19:18 +0100 [thread overview]
Message-ID: <2193240.1597738758@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200817090523.68692855@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> This is now a conflict between the fsinfo tree and Linus' tree.
Please drop the fsinfo branch for now, thanks.
David
next prev parent reply other threads:[~2020-08-18 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 6:32 linux-next: manual merge of the fsinfo tree with the kbuid tree Stephen Rothwell
2020-08-16 23:05 ` Stephen Rothwell
2020-08-18 8:19 ` David Howells [this message]
2020-08-18 10:48 ` Stephen Rothwell
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=2193240.1597738758@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@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