From: Hariprasad Kelam <hariprasad.kelam@gmail.com>
To: Gao Xiang <hsiangkao@aol.com>, Gao Xiang <gaoxiang25@huawei.com>,
Chao Yu <yuchao0@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-erofs@lists.ozlabs.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [Patch v2] staging: erofs: fix Warning Use BUG_ON instead of if condition followed by BUG
Date: Sun, 19 May 2019 15:41:32 +0530 [thread overview]
Message-ID: <20190519101132.GA22620@hari-Inspiron-1545> (raw)
In-Reply-To: <b32e6bca-60ec-2004-f1d6-16d2b8a478ae@aol.com>
On Sun, May 19, 2019 at 05:50:40PM +0800, Gao Xiang wrote:
>
>
> On 2019/5/19 下午5:34, Hariprasad Kelam wrote:
> > fix below warning reported by coccicheck
> >
> > drivers/staging/erofs/unzip_pagevec.h:74:2-5: WARNING: Use BUG_ON
> > instead of if condition followed by BUG.
> >
> > Signed-off-by: Hariprasad Kelam <hariprasad.kelam@gmail.com>
> > -----
> > Changes in v2:
> > - replace BUG_ON with DBG_BUGON
> > -----
> > ---
> > drivers/staging/erofs/unzip_pagevec.h | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/erofs/unzip_pagevec.h b/drivers/staging/erofs/unzip_pagevec.h
> > index f37d8fd..7938ee3 100644
> > --- a/drivers/staging/erofs/unzip_pagevec.h
> > +++ b/drivers/staging/erofs/unzip_pagevec.h
> > @@ -70,8 +70,7 @@ z_erofs_pagevec_ctor_next_page(struct z_erofs_pagevec_ctor *ctor,
> > return tagptr_unfold_ptr(t);
> > }
> >
>
> I'd like to delete this line
>
> > - if (unlikely(nr >= ctor->nr))
> > - BUG();
> > + DBG_BUGON(nr >= ctor->nr);
> >
>
> and this line.. I have already sent a new patch based on your v1 patch,
> could you please check it out if it is acceptable for you? :)
>
> Thanks,
> Gao Xiang
Hi Gai Xiang,
The patch which you sent has all required.
Thanks for the patch. We can ignore this v2 patch.
Thanks,
Hariprasad k
> > return NULL;
> > }
> >
next prev parent reply other threads:[~2019-05-19 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 9:34 Hariprasad Kelam
[not found] ` <b32e6bca-60ec-2004-f1d6-16d2b8a478ae@aol.com>
2019-05-19 10:11 ` Hariprasad Kelam [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-18 17:33 [PATCH] " Hariprasad Kelam
[not found] ` <20190519093557.20982-1-hsiangkao@aol.com>
2019-05-20 2:19 ` [PATCH v2] " 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=20190519101132.GA22620@hari-Inspiron-1545 \
--to=hariprasad.kelam@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gaoxiang25@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=hsiangkao@aol.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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
all inboxes | Powered by JetHome®