From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] fs: Removal of unlikely likelys
Date: Mon, 13 Dec 2010 19:38:07 -0500 [thread overview]
Message-ID: <20101214003807.693481687@goodmis.org> (raw)
Not sure who to send this to. I've separated out my patch set
per system, and I'm sending them out individually. You can simply
pull from my repo, or take the patches directly from me.
Or just ignore me and I'll come and bother you again next year ;-)
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: unlikely/fs
Steven Rostedt (2):
fs: Remove unlikely() from fput_light()
fs: Remove unlikely() from fget_light()
----
fs/file_table.c | 2 +-
include/linux/file.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2010-12-14 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 0:38 Steven Rostedt [this message]
2010-12-14 0:38 ` [PATCH 1/2] fs: Remove unlikely() from fput_light() Steven Rostedt
2010-12-14 0:38 ` [PATCH 2/2] fs: Remove unlikely() from fget_light() Steven Rostedt
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=20101214003807.693481687@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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