From: Viresh Kumar <viresh.kumar@linaro.org>
To: trivial@kernel.org, akpm@linux-foundation.org
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V1 resend] err.h: add (missing) unlikely() to IS_ERR_OR_NULL()
Date: Mon, 30 Nov 2015 11:53:16 +0530 [thread overview]
Message-ID: <20151130062316.GP3373@ubuntu> (raw)
In-Reply-To: <20151113082351.GI3576@ubuntu>
On 13-11-15, 13:53, Viresh Kumar wrote:
> On 29-10-15, 07:57, Viresh Kumar wrote:
> > On 13-10-15, 13:57, Viresh Kumar wrote:
> > > IS_ERR_VALUE() already contains it and so we need to add this only to
> > > the !ptr check. That will allow users of IS_ERR_OR_NULL(), to not add
> > > this compiler flag.
> > >
> > > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > > ---
> > > @Jiri: You have applied all other patches, but this one. Can you please
> > > apply this one as well, as all others were applied based on the
> > > assumption that this one is applied. :)
> > >
> > > include/linux/err.h | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/include/linux/err.h b/include/linux/err.h
> > > index a729120644d5..56762ab41713 100644
> > > --- a/include/linux/err.h
> > > +++ b/include/linux/err.h
> > > @@ -37,7 +37,7 @@ static inline bool __must_check IS_ERR(__force const void *ptr)
> > >
> > > static inline bool __must_check IS_ERR_OR_NULL(__force const void *ptr)
> > > {
> > > - return !ptr || IS_ERR_VALUE((unsigned long)ptr);
> > > + return unlikely(!ptr) || IS_ERR_VALUE((unsigned long)ptr);
> > > }
> >
> > Ping !!
>
> Another Ping !!
@Andrew: Will it be possible for you to apply this patch ? Its been on
the lists for over 2 months now.
--
viresh
prev parent reply other threads:[~2015-11-30 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:27 [PATCH V1 resend] err.h: add (missing) unlikely() to IS_ERR_OR_NULL() Viresh Kumar
2015-10-29 2:27 ` Viresh Kumar
2015-11-13 8:23 ` Viresh Kumar
2015-11-30 6:23 ` Viresh Kumar [this message]
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=20151130062316.GP3373@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox