From: Sasha Levin <Alexander.Levin@microsoft.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "ben.hutchings@codethink.co.uk" <ben.hutchings@codethink.co.uk>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 4.4 1/2] Revert "Btrfs: fix scrub to repair raid6 corruption"
Date: Tue, 19 Jun 2018 20:15:13 +0000 [thread overview]
Message-ID: <20180619201508.GB81030@sasha-vm> (raw)
In-Reply-To: <20180619201002.GA17428@kroah.com>
On Wed, Jun 20, 2018 at 05:10:02AM +0900, gregkh@linuxfoundation.org wrote:
>On Tue, Jun 19, 2018 at 04:33:49AM +0000, Sasha Levin wrote:
>> On Mon, Jun 18, 2018 at 06:20:30AM +0200, gregkh@linuxfoundation.org wrote:
>> >On Fri, Jun 15, 2018 at 02:39:22AM +0000, Sasha Levin wrote:
>> >> This reverts commit 95b286daf7ba784191023ad110122703eb2ebabc.
>> >>
>> >> This commit used an incorrect log message.
>> >>
>> >> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
>> >> ---
>> >> fs/btrfs/raid56.c | 18 ++++--------------
>> >> fs/btrfs/volumes.c | 9 +--------
>> >> 2 files changed, 5 insertions(+), 22 deletions(-)
>> >
>> >You forgot a reported-by: tag :(
>>
>> Sorry, I'll resend!
>
>No need, I fixed it up already :)
Too late :)
Nothing like some jetlag to catch up on work...
next prev parent reply other threads:[~2018-06-19 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 2:39 [PATCH 4.4 1/2] Revert "Btrfs: fix scrub to repair raid6 corruption" Sasha Levin
2018-06-15 2:39 ` [PATCH 4.4 2/2] Btrfs: make raid6 rebuild retry more Sasha Levin
2018-06-18 4:20 ` [PATCH 4.4 1/2] Revert "Btrfs: fix scrub to repair raid6 corruption" gregkh
2018-06-19 4:33 ` Sasha Levin
2018-06-19 20:10 ` gregkh
2018-06-19 20:15 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-19 20:09 Sasha Levin
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=20180619201508.GB81030@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.