From: Joe Perches <joe@perches.com>
To: Mike Frysinger <vapier.adi@gmail.com>,
Tobias Klauser <tklauser@distanz.ch>,
Alessandro Zummo <a.zummo@towertech.it>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Jiri Kosina <trivial@kernel.org>,
uclinux-dist-devel@blackfin.uclinux.org,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/15] rtc: Remove duplicate unlikely from IS_ERR
Date: Thu, 09 Dec 2010 12:28:47 -0800 [thread overview]
Message-ID: <1291926527.20677.18.camel@Joe-Laptop> (raw)
In-Reply-To: <AANLkTikUTdCRZP9FR1-16MmH4zysKha7m2o_DH6As-HJ@mail.gmail.com>
On Thu, 2010-12-09 at 15:06 -0500, Mike Frysinger wrote:
> On Thu, Dec 9, 2010 at 15:03, Joe Perches wrote:
> > IS_ERR already uses unlikely, remove unlikely from the call sites.
> Tobias already submitted a patch for this.
Thanks Tobias. Turns out you did them all after all.
Could you please cc linux-kernel for these sorts of patches?
As far as I can tell, the rtc-bfin patch didn't hit lkml,
only the c2port patch did for whatever reason.
The patches aren't marked as an n/m series which would also help
identify the patch scope. I thought it was a singleton.
Jiri and all others, please ignore my duplicate patchset.
cheers, Joe
next prev parent reply other threads:[~2010-12-09 20:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 15:00 [PATCH] c2port: Remove redundant unlikely() Tobias Klauser
2010-12-09 15:00 ` Tobias Klauser
2010-12-09 15:00 ` Tobias Klauser
2010-12-09 15:00 ` Tobias Klauser
[not found] ` <1291906801-1389-2-git-send-email-tklauser-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
2010-12-09 20:03 ` [trivial PATCH 00/15] remove duplicate unlikely from IS_ERR Joe Perches
2010-12-09 20:03 ` Joe Perches
2010-12-09 20:03 ` Joe Perches
2010-12-09 20:03 ` Joe Perches
2010-12-09 20:03 ` Joe Perches
2010-12-09 20:03 ` Joe Perches
2010-12-09 20:03 ` [PATCH 01/15] drm: Remove " Joe Perches
2010-12-09 20:03 ` Joe Perches
2010-12-09 20:03 ` [PATCH 02/15] stmmac: " Joe Perches
2010-12-09 20:03 ` [PATCH 03/15] rtc: " Joe Perches
2010-12-09 20:06 ` Mike Frysinger
2010-12-09 20:28 ` Joe Perches [this message]
2010-12-09 20:03 ` [PATCH 04/15] s390: " Joe Perches
2010-12-09 20:03 ` [PATCH 05/15] osd: " Joe Perches
2010-12-09 20:03 ` [PATCH 06/15] serial: " Joe Perches
2010-12-09 21:08 ` David Brown
2010-12-09 20:04 ` [PATCH 07/15] brcm80211: " Joe Perches
2010-12-09 20:04 ` [PATCH 08/15] gadget: " Joe Perches
2010-12-09 20:04 ` [PATCH 09/15] exofs: " Joe Perches
2010-12-09 20:04 ` [PATCH 10/15] ext2: " Joe Perches
2010-12-09 20:04 ` [PATCH 11/15] ext3: " Joe Perches
2010-12-09 20:04 ` [PATCH 12/15] ext4: " Joe Perches
2010-12-09 20:04 ` [PATCH 13/15] nfs: " Joe Perches
2010-12-09 20:04 ` [PATCH 14/15] mm: " Joe Perches
2010-12-09 20:04 ` Joe Perches
2010-12-09 20:04 ` [PATCH 15/15] ipv6: " Joe Perches
2010-12-09 20:04 ` Joe Perches
2010-12-09 20:32 ` [trivial PATCH 00/15] remove " Joe Perches
2010-12-09 20:32 ` Joe Perches
2010-12-09 20:32 ` Joe Perches
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=1291926527.20677.18.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=tklauser@distanz.ch \
--cc=trivial@kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@gmail.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 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.