public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] fix sparse warning in xfs_da_btree.c
Date: Wed, 07 Feb 2007 17:57:59 +0000	[thread overview]
Message-ID: <45CA1327.2030005@sgi.com> (raw)
In-Reply-To: <20070207125437.GA7740@lst.de>

Christoph,

I merged this change a while ago but it looks like the take message
didn't make it to oss.

mod xfs-linux-melb:xfs-kern:27702a TAKE message
================================================
Subject: TAKE 954580 -

fix sparse warning in xfs_da_btree.c

Date:  Tue Dec 12 13:15:55 AEDT 2006
Workarea:  vpn-emea-sw-emea-160-4.emea.sgi.com:/home/lachlan/isms/2.6.x-xfs
Inspected by:  hch
Author:  lachlan

The following file(s) were checked into:
   longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb


Modid:  xfs-linux-melb:xfs-kern:27702a
fs/xfs/xfs_da_btree.c - 1.173 - changed

Lachlan

Christoph Hellwig wrote:
> On Wed, Nov 29, 2006 at 04:44:41PM +0100, Christoph Hellwig wrote:
> 
>>The first use in xfs_da_node_lookup_int would have to be __be32.
>>But we can just remove this temporary variable use completely and
>>make sparse happy.  The variable is used later in the function for
>>a native endian variable so we'll have to keep it.
> 
> 
> ping?
> 
> 
>>
>>Signed-off-by: Christoph Hellwig <hch@lst.de>
>>
>>diff --git a/fs/xfs/xfs_da_btree.c b/fs/xfs/xfs_da_btree.c
>>index a68bc1f..cccf69e 100644
>>--- a/fs/xfs/xfs_da_btree.c
>>+++ b/fs/xfs/xfs_da_btree.c
>>@@ -1090,8 +1090,7 @@ xfs_da_node_lookup_int(xfs_da_state_t *s
>> 		if (blk->magic == XFS_DA_NODE_MAGIC) {
>> 			node = blk->bp->data;
>> 			max = be16_to_cpu(node->hdr.count);
>>-			btreehashval = node->btree[max-1].hashval;
>>-			blk->hashval = be32_to_cpu(btreehashval);
>>+			blk->hashval = be32_to_cpu(node->btree[max-1].hashval);
>> 
>> 			/*
>> 			 * Binary search.  (note: small blocks will skip loop)
> 
> ---end quoted text---
> 
> 

  reply	other threads:[~2007-02-07 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 15:44 [PATCH] fix sparse warning in xfs_da_btree.c Christoph Hellwig
2007-02-07 12:54 ` Christoph Hellwig
2007-02-07 17:57   ` Lachlan McIlroy [this message]
2007-02-08 20:33     ` Christoph Hellwig

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=45CA1327.2030005@sgi.com \
    --to=lachlan@sgi.com \
    --cc=hch@lst.de \
    --cc=xfs@oss.sgi.com \
    /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