From: gregkh@linuxfoundation.org (Greg KH)
Subject: patch "staging: erofs: keep corrupted fs from crashing kernel in" added to staging-linus
Date: Wed, 30 Jan 2019 19:19:09 +0100 [thread overview]
Message-ID: <20190130181909.GA16326@kroah.com> (raw)
In-Reply-To: <1e5bad91-3d65-c086-d42c-f87d642e3204@huawei.com>
On Wed, Jan 30, 2019@11:42:41PM +0800, Gao Xiang wrote:
>
>
> On 2019/1/30 23:05, Gao Xiang wrote:
> >
> > Hi Greg,
> >
> > Dan raised some suggestions to me. And I want to get some review ideas from Chao...
> > Current EROFS works good for the normal image, this patch is used for corrupted image only...
> >
> > Could you kindly drop this patch temporarily and I want to get them reviewed...
> > Not soon... Thanks!
>
> It seems this patch is the top of staging-linus...Could you kindly drop it and
> it is better to get "Reviewed-by:" tag for all EROFS bugfix patches from corresponding
> people (Chao, Dan, or Al if possible) first... Thank you very much!
>
> sorry to trouble you...
No problem, now reverted.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: stable@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-erofs@lists.ozlabs.org,
linux-staging mailing list <devel@driverdev.osuosl.org>
Subject: Re: patch "staging: erofs: keep corrupted fs from crashing kernel in" added to staging-linus
Date: Wed, 30 Jan 2019 19:19:09 +0100 [thread overview]
Message-ID: <20190130181909.GA16326@kroah.com> (raw)
In-Reply-To: <1e5bad91-3d65-c086-d42c-f87d642e3204@huawei.com>
On Wed, Jan 30, 2019 at 11:42:41PM +0800, Gao Xiang wrote:
>
>
> On 2019/1/30 23:05, Gao Xiang wrote:
> >
> > Hi Greg,
> >
> > Dan raised some suggestions to me. And I want to get some review ideas from Chao...
> > Current EROFS works good for the normal image, this patch is used for corrupted image only...
> >
> > Could you kindly drop this patch temporarily and I want to get them reviewed...
> > Not soon... Thanks!
>
> It seems this patch is the top of staging-linus...Could you kindly drop it and
> it is better to get "Reviewed-by:" tag for all EROFS bugfix patches from corresponding
> people (Chao, Dan, or Al if possible) first... Thank you very much!
>
> sorry to trouble you...
No problem, now reverted.
greg k-h
next prev parent reply other threads:[~2019-01-30 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:33 patch "staging: erofs: keep corrupted fs from crashing kernel in" added to staging-linus gregkh
2019-01-30 15:05 ` Gao Xiang
2019-01-30 15:42 ` Gao Xiang
2019-01-30 15:42 ` Gao Xiang
2019-01-30 18:19 ` Greg KH [this message]
2019-01-30 18:19 ` Greg KH
2019-01-30 20:00 ` Dan Carpenter
2019-01-30 20:00 ` Dan Carpenter
2019-01-30 22:57 ` Gao Xiang
2019-01-30 22:57 ` Gao Xiang
-- strict thread matches above, loose matches on Subject: below --
2019-03-29 16:25 gregkh
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=20190130181909.GA16326@kroah.com \
--to=gregkh@linuxfoundation.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.