linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc C <marc.ceeeee@gmail.com>
To: tj@kernel.org, linux-ide@vger.kernel.org
Cc: Marc Carino <marc.ceeeee@gmail.com>
Subject: [PATCH] Remove endianness attribute in ata_tf_to_fis
Date: Sat, 31 Aug 2013 09:20:32 -0700	[thread overview]
Message-ID: <1377966033-12256-1-git-send-email-marc.ceeeee@gmail.com> (raw)

From: Marc Carino <marc.ceeeee@gmail.com>

This patch cleans up the following build warning:

---
reproduce: make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/ata/libata-core.c:574:19: sparse: restricted __le32 degrades to integer
>> drivers/ata/libata-core.c:575:20: sparse: restricted __le32 degrades to integer
>> drivers/ata/libata-core.c:576:20: sparse: restricted __le32 degrades to integer
>> drivers/ata/libata-core.c:577:20: sparse: restricted __le32 degrades to integer

vim +574 drivers/ata/libata-core.c

   568
   569          fis[12] = tf->nsect;
   570          fis[13] = tf->hob_nsect;
   571          fis[14] = 0;
   572          fis[15] = tf->ctl;
   573
 > 574          fis[16] = aux & 0xff;
   575          fis[17] = (aux >> 8) & 0xff;
   576          fis[18] = (aux >> 16) & 0xff;
   577          fis[19] = (aux >> 24) & 0xff;
   578  }
   579
   580  /**
---

Marc Carino (1):
  libata: Remove unneeded __le32 in ata_tf_to_fis

 drivers/ata/libata-core.c | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

-- 
1.8.1.2


             reply	other threads:[~2013-08-31 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31 16:20 Marc C [this message]
2013-08-31 16:20 ` [PATCH] libata: Remove unneeded __le32 in ata_tf_to_fis Marc C
2013-09-01 13:21   ` Tejun Heo
2013-09-01 13:21 ` [PATCH] Remove endianness attribute " Tejun Heo

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=1377966033-12256-1-git-send-email-marc.ceeeee@gmail.com \
    --to=marc.ceeeee@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=tj@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).