From: Viresh Kumar <viresh.kumar@linaro.org>
To: trivial@kernel.org
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V1 Resend 00/10] trivial: Drop unlikely before IS_ERR(_OR_NULL)
Date: Tue, 18 Aug 2015 14:38:13 +0530 [thread overview]
Message-ID: <20150818090813.GC31148@linux> (raw)
In-Reply-To: <cover.1439375087.git.viresh.kumar@linaro.org>
On 12-08-15, 15:59, Viresh Kumar wrote:
> Hi Jiri,
>
> Andrew Morton suggested to take these patches through your tree and so
> another resend.
>
> This cleans up the usage of IS_ERR(_OR_NULL)(), where the callers have
> added additional unlikely compiler flag to them. It also fixes the
> definition of IS_ERR_OR_NULL(), to use unlikely for all checks it does.
Ping !!
--
viresh
prev parent reply other threads:[~2015-08-18 9:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 10:29 [PATCH V1 Resend 00/10] trivial: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 01/10] err.h: add (missing) unlikely() to IS_ERR_OR_NULL() Viresh Kumar
2015-10-07 10:35 ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 02/10] PM / OPP: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-28 14:17 ` Rafael J. Wysocki
2015-08-28 13:52 ` Jiri Kosina
2015-08-28 14:30 ` Rafael J. Wysocki
2015-09-09 2:43 ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 03/10] drivers: devfreq: " Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 04/10] drivers: misc: " Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 05/10] drivers: net: " Viresh Kumar
2015-08-12 10:29 ` [rtc-linux] [PATCH V1 Resend 06/10] drivers: rtc: Drop (un)likely " Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-12 10:41 ` [rtc-linux] " Alexandre Belloni
2015-08-12 10:41 ` Alexandre Belloni
2015-08-12 10:41 ` Alexandre Belloni
2015-08-12 10:46 ` [rtc-linux] " Viresh Kumar
2015-08-12 10:46 ` Viresh Kumar
2015-08-12 10:46 ` Viresh Kumar
2015-08-12 11:42 ` [rtc-linux] " Alexandre Belloni
2015-08-12 11:42 ` Alexandre Belloni
2015-08-12 11:42 ` Alexandre Belloni
2015-08-12 11:47 ` [rtc-linux] " Viresh Kumar
2015-08-12 11:47 ` Viresh Kumar
2015-08-12 11:47 ` Viresh Kumar
[not found] ` <cover.1439375087.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-12 10:29 ` [PATCH V1 Resend 07/10] fs: Drop unlikely " Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-12 18:28 ` Jeff Layton
2015-08-20 16:08 ` Steve French
2015-08-20 16:08 ` Steve French
[not found] ` <CAH2r5mvUC2WO6sVqhe_QCgiCJbRbahDsSj=-Uzk7LB_peTqjLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-20 16:14 ` Viresh Kumar
2015-08-20 16:14 ` Viresh Kumar
2015-08-20 16:14 ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 08/10] blk-cgroup: " Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 09/10] mm: " Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 10/10] net: " Viresh Kumar
2015-08-12 10:41 ` Viresh Kumar
2015-08-12 10:29 ` Viresh Kumar
2015-08-18 9:08 ` 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=20150818090813.GC31148@linux \
--to=viresh.kumar@linaro.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 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.