From: Bob Copeland <me@bobcopeland.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Chris Mason <chris.mason@oracle.com>,
trivial@kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org,
linux-karma-devel@lists.sourceforge.net
Subject: Re: [PATCH 04/37] Remove unneeded version.h includes from fs/
Date: Fri, 24 Jun 2011 09:26:20 -0400 [thread overview]
Message-ID: <20110624132620.GA5694@hash.lan> (raw)
In-Reply-To: <alpine.LNX.2.00.1106232358330.17688@swampdragon.chaosbits.net>
On Thu, Jun 23, 2011 at 11:59:32PM +0200, Jesper Juhl wrote:
> It was pointed out by 'make versioncheck' that some includes of
> linux/version.h were not needed in fs/ (fs/btrfs/ctree.h and
> fs/omfs/file.c).
> This patch removes them.
>
> Signed-off-by: Jesper Juhl <jj@chaosbits.net>
Thanks, omfs part was leftover cruft from its time out-of-tree.
FWIW,
Acked-by: Bob Copeland <me@bobcopeland.com>
--
Bob Copeland %% www.bobcopeland.com
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
prev parent reply other threads:[~2011-06-24 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1106232344480.17688@swampdragon.chaosbits.net>
2011-06-23 21:59 ` [PATCH 04/37] Remove unneeded version.h includes from fs/ Jesper Juhl
2011-06-24 13:26 ` Bob Copeland [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=20110624132620.GA5694@hash.lan \
--to=me@bobcopeland.com \
--cc=chris.mason@oracle.com \
--cc=jj@chaosbits.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-karma-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).