All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@aol.com>
To: Richard Weinberger <richard@nod.at>,
	devel <devel@driverdev.osuosl.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Miao Xie <miaoxie@huawei.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	linux-erofs <linux-erofs@lists.ozlabs.org>
Subject: Re: [PATCH v3 RESEND] staging: erofs: fix an error handling in erofs_readdir()y
Date: Sun, 18 Aug 2019 17:18:05 +0800	[thread overview]
Message-ID: <20190818091804.GA18675@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <20190818091037.GB17909@hsiangkao-HP-ZHAN-66-Pro-G1>

On Sun, Aug 18, 2019 at 05:10:38PM +0800, Gao Xiang via Linux-erofs wrote:
> Hi Richard,
> 
> On Sun, Aug 18, 2019 at 10:33:33AM +0200, Richard Weinberger wrote:
> > ----- Urspr?ngliche Mail -----
> > > changelog from v2:
> > > - transform EIO to EFSCORRUPTED as suggested by Matthew;
> > 
> > erofs does not define EFSCORRUPTED, so the build fails.
> > At least on Linus' tree as of today.
> 
> Thanks for your reply :)
> 
> I write all patches based on staging tree and do more cleanups further
> than Linus' tree, EFSCORRUPTED was already introduced by Pavel days before...

Sorry, I mean "introduced which was suggested by Paval"...

> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-testing&id=a6b9b1d5eae61a68085030e50d56265dec5baa94
> 
> which can be fetched from
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git -b staging-next
> 
> Thanks,
> Gao Xiang
> 
> > 
> > Thanks,
> > //richard

WARNING: multiple messages have this Message-ID (diff)
From: hsiangkao@aol.com (Gao Xiang)
Subject: [PATCH v3 RESEND] staging: erofs: fix an error handling in erofs_readdir()y
Date: Sun, 18 Aug 2019 17:18:05 +0800	[thread overview]
Message-ID: <20190818091804.GA18675@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <20190818091037.GB17909@hsiangkao-HP-ZHAN-66-Pro-G1>

On Sun, Aug 18, 2019@05:10:38PM +0800, Gao Xiang via Linux-erofs wrote:
> Hi Richard,
> 
> On Sun, Aug 18, 2019@10:33:33AM +0200, Richard Weinberger wrote:
> > ----- Urspr?ngliche Mail -----
> > > changelog from v2:
> > > - transform EIO to EFSCORRUPTED as suggested by Matthew;
> > 
> > erofs does not define EFSCORRUPTED, so the build fails.
> > At least on Linus' tree as of today.
> 
> Thanks for your reply :)
> 
> I write all patches based on staging tree and do more cleanups further
> than Linus' tree, EFSCORRUPTED was already introduced by Pavel days before...

Sorry, I mean "introduced which was suggested by Paval"...

> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-testing&id=a6b9b1d5eae61a68085030e50d56265dec5baa94
> 
> which can be fetched from
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git -b staging-next
> 
> Thanks,
> Gao Xiang
> 
> > 
> > Thanks,
> > //richard

  reply	other threads:[~2019-08-18  9:18 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18  1:48 [PATCH] staging: erofs: fix an error handling in erofs_readdir() Gao Xiang
2019-08-18  1:48 ` Gao Xiang
2019-08-18  1:56 ` [PATCH v2] " Gao Xiang
2019-08-18  1:56   ` Gao Xiang
2019-08-18  2:20   ` Matthew Wilcox
2019-08-18  2:20     ` Matthew Wilcox
2019-08-18  2:32     ` Gao Xiang
2019-08-18  2:32       ` Gao Xiang
2019-08-18  2:53       ` Matthew Wilcox
2019-08-18  2:53         ` Matthew Wilcox
2019-08-18  3:01         ` Gao Xiang
2019-08-18  3:01           ` Gao Xiang
2019-08-18  3:18           ` [PATCH] " Gao Xiang
2019-08-18  3:18             ` Gao Xiang
2019-08-18 12:07             ` kbuild test robot
2019-08-18 12:07               ` kbuild test robot
2019-08-18 12:07               ` kbuild test robot
2019-08-18 13:17             ` kbuild test robot
2019-08-18 13:17               ` kbuild test robot
2019-08-18 13:17               ` kbuild test robot
2019-08-18 13:25               ` Gao Xiang
2019-08-18 13:25                 ` Gao Xiang
2019-08-20  6:50                 ` Philip Li
2019-08-20  6:50                   ` Philip Li
2019-08-20  6:50                   ` Philip Li
2019-08-20  6:50                   ` Gao Xiang
2019-08-20  6:50                     ` Gao Xiang
2019-08-20  6:50                     ` Gao Xiang
2019-08-20  6:58                     ` Li, Philip
2019-08-20  6:58                       ` Li, Philip
2019-08-20  6:58                       ` Li, Philip
2019-08-20  7:16                       ` Gao Xiang
2019-08-20  7:16                         ` Gao Xiang
2019-08-20  7:16                         ` Gao Xiang
2019-08-18  3:21           ` [PATCH v3 RESEND] " Gao Xiang
2019-08-18  3:21             ` Gao Xiang
2019-08-18  8:33             ` Richard Weinberger
2019-08-18  8:33               ` Richard Weinberger
2019-08-18  9:10               ` Gao Xiang
2019-08-18  9:10                 ` Gao Xiang
2019-08-18  9:18                 ` Gao Xiang [this message]
2019-08-18  9:18                   ` [PATCH v3 RESEND] staging: erofs: fix an error handling in erofs_readdir()y Gao Xiang
2019-08-18 11:52             ` [PATCH v3 RESEND] staging: erofs: fix an error handling in erofs_readdir() Sasha Levin
2019-08-18 12:29             ` Chao Yu
2019-08-18 12:29               ` Chao Yu
2019-08-18 12:33             ` Matthew Wilcox
2019-08-18 12:33               ` Matthew Wilcox
2019-08-18 12:38               ` Gao Xiang
2019-08-18 12:38                 ` Gao Xiang
2019-08-18 12:54                 ` [PATCH v4] " Gao Xiang
2019-08-18 12:54                   ` Gao Xiang
2019-08-19  0:08                   ` Sasha Levin
2019-08-18 10:39         ` [PATCH v2] " Chao Yu
2019-08-18 10:39           ` Chao Yu
2019-08-18 10:52           ` Gao Xiang
2019-08-18 10:52             ` Gao Xiang
2019-08-18 12:28             ` Chao Yu
2019-08-18 12:28               ` Chao Yu

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=20190818091804.GA18675@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=hsiangkao@aol.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    --cc=willy@infradead.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.