From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]udf:super.c Fix warning: variable 'sbi' set but not used
Date: Mon, 02 Aug 2010 06:30:18 -0700 [thread overview]
Message-ID: <4C56C86A.2050208@gmail.com> (raw)
In-Reply-To: <20100802125110.GD3278@quack.suse.cz>
On 08/02/2010 05:51 AM, Jan Kara wrote:
> On Sat 31-07-10 12:03:03, Justin P. Mattock wrote:
>> any ideas on the status of this?
> I have it in my tree and will push it to Linus in this merge window.
>
> Honza
o.k. cool..
>>
>>> This fixes this warning when building the kernel:
>>> CC fs/udf/super.o
>>> fs/udf/super.c: In function 'udf_load_sequence':
>>> fs/udf/super.c:1582:22: warning: variable 'sbi' set but not used
>>> Please have a look, when you have time and let me know.
>>>
>>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>>>
>>> ---
>>> fs/udf/super.c | 2 --
>>> 1 files changed, 0 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/fs/udf/super.c b/fs/udf/super.c
>>> index 612d1e2..12bb651 100644
>>> --- a/fs/udf/super.c
>>> +++ b/fs/udf/super.c
>>> @@ -1579,9 +1579,7 @@ static int udf_load_sequence(struct super_block *sb, struct buffer_head *bh,
>>> {
>>> struct anchorVolDescPtr *anchor;
>>> long main_s, main_e, reserve_s, reserve_e;
>>> - struct udf_sb_info *sbi;
>>>
>>> - sbi = UDF_SB(sb);
>>> anchor = (struct anchorVolDescPtr *)bh->b_data;
>>>
>>> /* Locate the main sequence */
>>
Justin P. Mattock
prev parent reply other threads:[~2010-08-02 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 4:42 [PATCH]udf:super.c Fix warning: variable 'sbi' set but not used Justin P. Mattock
2010-07-31 19:03 ` Justin P. Mattock
2010-08-02 12:51 ` Jan Kara
2010-08-02 13:30 ` Justin P. Mattock [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=4C56C86A.2050208@gmail.com \
--to=justinmattock@gmail.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.