From: Matthew Wilcox <matthew@wil.cx>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Removing i_sock
Date: Sun, 19 Dec 2004 06:57:39 +0000 [thread overview]
Message-ID: <20041219065739.GE7113@parcelfarce.linux.theplanet.co.uk> (raw)
The i_sock member of struct inode is redundant with S_ISSOCK(i_mode).
Here's a series of 6 patches to remove it:
http://ftp.linux.org.uk/pub/linux/willy/patches/i_sock/
I'm sending them to their respective maintainers now, and I'll submit
a series after 2.6.10 is out.
Removing i_sock from struct inode actually doesn't reduce the size of
struct inode -- it fits into a gap between two other members. But it may
help someone else put struct inode on a diet, and it reduces confusion.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
reply other threads:[~2004-12-19 6:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041219065739.GE7113@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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).