From: Christoph Hellwig <hch@lst.de>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 2/4] pnfs/objlayout: fix endianess annotation in objio_alloc_deviceid_node
Date: Wed, 10 Sep 2014 17:36:29 -0700 [thread overview]
Message-ID: <1410395791-2385-3-git-send-email-hch@lst.de> (raw)
In-Reply-To: <1410395791-2385-1-git-send-email-hch@lst.de>
The kbuild test robot complained about a new sparse warning in
objio_alloc_deviceid_node, but it turns out that this was just a moved
reference to an existing variable. Fix it to have the right big endian
annotated type.
Note that there are some other endianess issues in this file that I didn't
bother to sort out as they involve global headers.
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/nfs/objlayout/objio_osd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfs/objlayout/objio_osd.c b/fs/nfs/objlayout/objio_osd.c
index c502f64..c6e4bda 100644
--- a/fs/nfs/objlayout/objio_osd.c
+++ b/fs/nfs/objlayout/objio_osd.c
@@ -93,7 +93,7 @@ objio_alloc_deviceid_node(struct nfs_server *server, struct pnfs_device *pdev,
struct osd_dev *od;
struct osd_dev_info odi;
bool retry_flag = true;
- u32 *p;
+ __be32 *p;
int err;
deviceaddr = kzalloc(sizeof(*deviceaddr), gfp_flags);
--
1.9.1
next prev parent reply other threads:[~2014-09-11 0:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 0:36 a few more pnfs/blocklayout fixes Christoph Hellwig
2014-09-11 0:36 ` [PATCH 1/4] pnfs/blocklayout: remove some debugging Christoph Hellwig
2014-09-11 0:36 ` Christoph Hellwig [this message]
2014-09-11 0:36 ` [PATCH 3/4] pnfs/blocklayout: allocate separate pages for the layoutcommit payload Christoph Hellwig
2014-09-11 14:16 ` Anna Schumaker
2014-09-11 15:27 ` Christoph Hellwig
2014-09-11 15:59 ` Anna Schumaker
2014-09-11 16:00 ` Anna Schumaker
2014-09-11 0:36 ` [PATCH 4/4] pnfs: remove GETDEVICELIST implementation Christoph Hellwig
2014-09-11 14:51 ` Peng Tao
2014-09-11 15:29 ` 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=1410395791-2385-3-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=linux-nfs@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.