From: Christian Engelmayer <cengelma@gmx.at>
To: linux-fsdevel@vger.kernel.org
Cc: Evgeniy Dushistov <dushistov@mail.ru>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] fs: ufs: Remove unused pointer
Date: Tue, 11 Feb 2014 01:20:12 +0100 [thread overview]
Message-ID: <20140211012012.6384d52f@spike> (raw)
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
This is a cleanup throughout ufs regarding pointers that are set up, but no
longer used in the affected functions. The ubh_get_usb_(first|second|third)
macros found in the changesets all resolve to
static inline void *get_usb_offset(struct ufs_sb_private_info *uspi,
unsigned int offset)
{
unsigned int index;
index = offset >> uspi->s_fshift;
offset &= ~uspi->s_fmask;
return uspi->s_ubh.bh[index]->b_data + offset;
}
and differ in the passed offset value. get_usb_offset() does not alter the
passed ufs_sb_private_info struct. Those calls can be thus removed safely
where the return value is not further used.
The series applies against v3.14-rc2 and is compile tested.
Christian Engelmayer (3):
fs: ufs: Remove unused ufs_super_block_first pointer.
fs: ufs: Remove unused ufs_super_block_second pointer.
fs: ufs: Remove unused ufs_super_block_third pointer.
fs/ufs/balloc.c | 12 ------------
fs/ufs/ialloc.c | 4 ----
fs/ufs/super.c | 6 ------
3 files changed, 22 deletions(-)
--
1.8.3.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-02-11 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 0:20 Christian Engelmayer [this message]
2014-02-11 0:22 ` [PATCH 1/3] fs: ufs: Remove unused ufs_super_block_first pointer Christian Engelmayer
2014-02-11 0:23 ` [PATCH 2/3] fs: ufs: Remove unused ufs_super_block_second pointer Christian Engelmayer
2014-02-11 0:24 ` [PATCH 3/3] fs: ufs: Remove unused ufs_super_block_third pointer Christian Engelmayer
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=20140211012012.6384d52f@spike \
--to=cengelma@gmx.at \
--cc=dushistov@mail.ru \
--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).