From: Viresh Kumar <viresh.kumar@linaro.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: akpm@linux-foundation.org, linaro-kernel@lists.linaro.org,
linux-kernel@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com
Subject: Re: [PATCH V1 Resend 04/11] drivers: md: Drop unlikely before IS_ERR(_OR_NULL)
Date: Tue, 11 Aug 2015 07:12:04 +0530 [thread overview]
Message-ID: <20150811014203.GF5766@linux> (raw)
In-Reply-To: <20150810200503.GA24638@redhat.com>
On 10-08-15, 16:05, Mike Snitzer wrote:
> On Mon, Aug 10 2015 at 2:12am -0400,
> Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> > IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> > is no need to do that again from its callers. Drop it.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> I picked this up for 4.3, staged in linux-dm.git's 'for-next', see:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=e2545d97b6cc0556fbd1099fca9271e3ca1d0b01
I had no clue about it as I didn't look at individual maintainer's
tree. But rebased things over linux-next/master.
Why isn't your branch merged into linux-next ?
--
viresh
next prev parent reply other threads:[~2015-08-11 1:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 6:12 [PATCH V1 Resend 00/11] vial: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 01/11] err.h: add (missing) unlikely() to IS_ERR_OR_NULL() Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 02/11] PM / OPP: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-08-10 21:15 ` Pavel Machek
2015-08-10 6:12 ` [PATCH V1 Resend 03/11] drivers: devfreq: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 04/11] drivers: md: " Viresh Kumar
2015-08-10 20:05 ` Mike Snitzer
2015-08-11 1:42 ` Viresh Kumar [this message]
2015-08-11 2:43 ` Mike Snitzer
2015-08-10 6:12 ` [PATCH V1 Resend 05/11] drivers: misc: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 06/11] drivers: net: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 07/11] drivers: rtc: Drop (un)likely " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 08/11] fs: Drop unlikely " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 09/11] blk-cgroup: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 10/11] mm: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 11/11] net: " Viresh Kumar
2015-08-10 11:51 ` Neil Horman
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=20150811014203.GF5766@linux \
--to=viresh.kumar@linaro.org \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.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