From: Joe Perches <joe@perches.com>
To: netdev@vger.kernel.org, Tobias Klauser <tklauser@distanz.ch>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
rtc-linux@googlegroups.com, linux-s390@vger.kernel.org,
osd-dev@open-osd.org, linux-arm-msm@vger.kernel.org,
linux-usb@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-mm@kvack.org,
Jiri Kosina <trivial@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-wireless@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: Re: [trivial PATCH 00/15] remove duplicate unlikely from IS_ERR
Date: Thu, 09 Dec 2010 12:32:53 -0800 [thread overview]
Message-ID: <1291926773.20677.26.camel@Joe-Laptop> (raw)
In-Reply-To: <cover.1291923888.git.joe@perches.com>
On Thu, 2010-12-09 at 12:03 -0800, Joe Perches wrote:
> Tobias Klauser <tklauser@distanz.ch> sent a patch to remove
> an unnecessary unlikely from drivers/misc/c2port/core.c,
> https://lkml.org/lkml/2010/12/9/199
It seems that Tobias did send all the appropriate patches,
not as a series, but as individual patches to kernel-janitor.
c2port was the only one that went to lkml.
Please ignore this series and apply Tobias' patches.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-12-09 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291906801-1389-2-git-send-email-tklauser@distanz.ch>
2010-12-09 20:03 ` Joe Perches
2010-12-09 20:04 ` [PATCH 14/15] mm: Remove " Joe Perches
2010-12-09 20:32 ` Joe Perches [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=1291926773.20677.26.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=rtc-linux@googlegroups.com \
--cc=tklauser@distanz.ch \
--cc=trivial@kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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