From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jens Axboe <axboe@kernel.dk>, David Howells <dhowells@redhat.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: build warnings after merge of the fsinfo tree
Date: Thu, 28 May 2020 15:44:25 +0200 [thread overview]
Message-ID: <20200528134425.GA16083@lst.de> (raw)
In-Reply-To: <20200528201104.529e9bc5@canb.auug.org.au>
On Thu, May 28, 2020 at 08:11:04PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> This should have been the block tree, not the fsinfo tree, of course.
Fix sent to Jens and the linux-block list, thanks for the report.
next prev parent reply other threads:[~2020-05-28 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 8:40 linux-next: build warnings after merge of the fsinfo tree Stephen Rothwell
2020-05-28 10:11 ` Stephen Rothwell
2020-05-28 13:44 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-04 7:34 Stephen Rothwell
2020-08-04 8:10 ` David Howells
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=20200528134425.GA16083@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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