From: Chris Mason <clm@fb.com>
To: <dsterba@suse.cz>, Laszlo Fiat <laszlo.fiat@gmail.com>,
<linux-btrfs@vger.kernel.org>
Subject: Re: errors with linux-next-20160701
Date: Fri, 8 Jul 2016 09:57:55 -0400 [thread overview]
Message-ID: <cff292c2-2969-df61-24c3-c6fdca202f05@fb.com> (raw)
In-Reply-To: <20160708135108.GH13336@twin.jikos.cz>
On 07/08/2016 09:51 AM, David Sterba wrote:
> On Thu, Jul 07, 2016 at 08:15:18PM +0200, Laszlo Fiat wrote:
>> I have a simple btrfs filesystem on a single device. It worked well so far.
>>
>> Recently I compiled a new kernel linux-next-20160701, with this new
>> kernel I get warnings and errors in the logs.
>
> I hope you're aware that using linux-next can lead to all sorts of
> problems.
>
This should be easy to verify by pulling Dave's for-next branch on top
of Linus' current git. Either the bugs will disappear or not.
-chris
prev parent reply other threads:[~2016-07-08 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 18:15 errors with linux-next-20160701 Laszlo Fiat
2016-07-08 13:51 ` David Sterba
2016-07-08 13:57 ` Chris Mason [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=cff292c2-2969-df61-24c3-c6fdca202f05@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=laszlo.fiat@gmail.com \
--cc=linux-btrfs@vger.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;
as well as URLs for NNTP newsgroup(s).