From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-ide@vger.kernel.org, htejun@gmail.com
Subject: Re: [patch 3/9] libata: xfer_mask is unsigned int not unsigned long
Date: Mon, 17 Dec 2007 21:49:06 -0500 [thread overview]
Message-ID: <47673522.5080706@garzik.org> (raw)
In-Reply-To: <20071217184425.1b6dc8c0.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 17 Dec 2007 20:30:33 -0500 Jeff Garzik <jeff@garzik.org> wrote:
>
>> akpm@linux-foundation.org wrote:
>>> From: Tejun Heo <htejun@gmail.com>
>>>
>>> xfer_mask is unsigned int not unsigned long. Change ->mode_filter to
>>> take and return unsigned int.
>>>
>>> While at it, rename @adev of ata_pci_default_filter() to @dev for
>>> consistency.
>>>
>>> [akpm@linux-foundation.org: fix types]
>>> Signed-off-by: Tejun Heo <htejun@gmail.com>
>>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>>> ---
>>>
>>> drivers/ata/libata-sff.c | 5 +++--
>>> drivers/ata/pata_acpi.c | 2 +-
>>> drivers/ata/pata_ali.c | 2 +-
>>> drivers/ata/pata_amd.c | 10 +++++-----
>>> drivers/ata/pata_hpt366.c | 2 +-
>>> drivers/ata/pata_hpt37x.c | 4 ++--
>>> drivers/ata/pata_pdc2027x.c | 4 ++--
>>> drivers/ata/pata_scc.c | 2 +-
>>> drivers/ata/pata_serverworks.c | 4 ++--
>>> include/linux/libata.h | 9 +++++----
>>> 10 files changed, 23 insertions(+), 21 deletions(-)
>> patch is outdated...
>>
>
> What does this mean??
>
following discussion, was superceded by
commit 52fc241b4c5ef60d73327d9468634694a1f7d359
Author: Tejun Heo <htejun@gmail.com>
Date: Tue Nov 27 19:43:42 2007 +0900
libata: xfer_mask is unsigned long not unsigned int
which has been in netdev#upstream for a few weeks, and probably at least
one -mm release.
prev parent reply other threads:[~2007-12-18 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 0:01 [patch 3/9] libata: xfer_mask is unsigned int not unsigned long akpm
2007-12-18 1:30 ` Jeff Garzik
2007-12-18 2:44 ` Andrew Morton
2007-12-18 2:49 ` Jeff Garzik [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=47673522.5080706@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=linux-ide@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.