From: David Sterba <dsterba@suse•cz>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: "Linux ARM" <linux-arm-kernel@lists•infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"David Sterba" <dsterba@suse•cz>,
"Josef Bacik" <josef@toxicpanda•com>, "Chris Mason" <clm@fb•com>,
linux-btrfs <linux-btrfs@vger•kernel.org>,
"Johannes Thumshirn" <jthumshirn@suse•de>,
"David Sterba" <dsterba@suse•com>,
"Andreas Färber" <afaerber@suse•de>, "Qu Wenruo" <wqu@suse•com>
Subject: Re: [PATCH next 1/2] btrfs: tree-checker: Fix error format string
Date: Tue, 26 Nov 2019 16:44:53 +0100 [thread overview]
Message-ID: <20191126154452.GG2734@twin.jikos.cz> (raw)
In-Reply-To: <CAMuHMdVbcfB0FFS=gLDathXFM3x0WYXJEq99S_g7mjAPS94rAQ@mail.gmail.com>
On Tue, Nov 26, 2019 at 11:36:58AM +0100, Geert Uytterhoeven wrote:
> > > Fixes: a31ccb4b7ba2 ("btrfs: tree-checker: Check item size before reading file extent type")
> >
> > As the patch is still in the devel branch, the commit id is not stable
>
> It indeed is not:
> Fixes: 153a6d299956983d ("btrfs: tree-checker: Check item size before
> reading file extent type")
>
> > and I'll fold the change to to the patch. Thanks.
>
> Apparently that was forgotten, and now the issue is part of Linus' tree.
Mistake on my side so I'll apply the full fixup patch, thanks for
noticing.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-26 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 21:38 [PATCH next 0/2] btrfs: Fix build warnings for arm Andreas Färber
2019-11-08 21:38 ` [PATCH next 1/2] btrfs: tree-checker: Fix error format string Andreas Färber
2019-11-11 18:31 ` David Sterba
2019-11-26 10:36 ` Geert Uytterhoeven
2019-11-26 15:44 ` David Sterba [this message]
2019-11-08 21:38 ` [PATCH next 2/2] btrfs: extent-tree: " Andreas Färber
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=20191126154452.GG2734@twin.jikos.cz \
--to=dsterba@suse$(echo .)cz \
--cc=afaerber@suse$(echo .)de \
--cc=clm@fb$(echo .)com \
--cc=dsterba@suse$(echo .)com \
--cc=geert@linux-m68k$(echo .)org \
--cc=josef@toxicpanda$(echo .)com \
--cc=jthumshirn@suse$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-btrfs@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=wqu@suse$(echo .)com \
/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