linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org,
	Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: libata TODO: ioread/iowrite work (was Re: [PATCH libata:upstream] remove compiler warnings)
Date: Mon, 22 Aug 2005 15:50:41 -0400	[thread overview]
Message-ID: <430A2C91.4060803@pobox.com> (raw)
In-Reply-To: <20050822091129.GA15373@htj.dyndns.org>

Tejun Heo wrote:
>  Hello, Jeff.
> 
>  This patch removes compiler warnings which are caused by using
> ioports values (unsigned long) for the address argument of
> read/write[bwl]() functions without casting.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>

NAK...  These warnings exist as a reminder of the remaining 
ioread/iowrite() work that must occur.  Look at the 'iomap' and 
'iomap-step1' branches of libata-dev.git for incomplete examples of this 
work.

One must:

- create a data structure to store a bunch of I/O port values, as 
returned by pci_iomap() and ioport_map()
- update legacy PCI IDE (aka looks like ISA IDE) code path to use 
ioport_map() to obtain the I/O addresses we need
- update native mode PCI IDE (aka looks like PCI) code path to use 
pci_iomap()
- update all the other drivers that use ioremap() to use pci_iomap()
- change struct ata_ioports, s/unsigned long/void __iomem */
- fix up the last few bits in each driver, such as
	* eliminating the 'unsigned long base' variable in each
	  xxx_init_one() function
	* changing the xxx_setup_port() function to indicate
	  void __iomem * rather than unsigned long
- one last check for any last s/long/void iomem */ changes to be made
- install Linus's "sparse" source checker
- run 'make C=1' in the kernel tree, and make sure libata and drivers 
don't spew warnings


So... it's not as simple as just killing the warnings ;-)

  reply	other threads:[~2005-08-22 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22  9:11 [PATCH libata:upstream] remove compiler warnings Tejun Heo
2005-08-22 19:50 ` Jeff Garzik [this message]
2005-08-22 20:39   ` libata TODO: ioread/iowrite work (was Re: [PATCH libata:upstream] remove compiler warnings) Sam Ravnborg

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=430A2C91.4060803@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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).