From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: 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 20:48:00 +1000 [thread overview]
Message-ID: <20200818204800.1bce48de@canb.auug.org.au> (raw)
In-Reply-To: <2193240.1597738758@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
Hi David,
On Tue, 18 Aug 2020 09:19:18 +0100 David Howells <dhowells@redhat.com> wrote:
>
> Please drop the fsinfo branch for now, thanks.
OK, done. What about the notifications tree? (not pushing, just wondering)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-08-18 10:48 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
2020-08-18 10:48 ` Stephen Rothwell [this message]
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=20200818204800.1bce48de@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@kernel.org \
/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