From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Fix IDE host_flags regression.
Date: Tue, 23 Oct 2007 21:50:14 +0200 [thread overview]
Message-ID: <200710232150.14284.bzolnier@gmail.com> (raw)
In-Reply-To: <20071022.020900.41634188.davem@davemloft.net>
Hi,
Thanks for debugging & fixing this.
On Monday 22 October 2007, David Miller wrote:
>
> Bart, please test your changes.
Well, I do. However due to hardware diversity it is not practically
possible to test them all myself...
> Thank you.
>
> [IDE]: Expand hwif->host_flags so that it fits new flags.
>
> This fixes regressions added by:
> 238e4f142c33bb34440cc64029dde7b9fbc4e65f
Yeah, sorry for that. ->host flags were expanded in struct ide_pci_device_s
(now struct ide_port_info) but not in struct hwif_s. This went unnoticed
because majority of new flags are used only through struct ide_pci_device_s.
The exceptions are:
- IDE_HFLAG_NO_LBA48 (only user is trm290, exotic hardware)
- IDE_HFLAG_NO_LBA48_DMA (only user is alim15x3, revisions <= 0xC4)
- IDE_HFLAG_ERROR_STOPS_FIFO (the error path of pdc202xx_{old,new})
What worries me a bit is that commit 238e4f142c33bb34440cc64029dde7b9fbc4e65f
was in -mm since 2.6.23-rc4-mm1 (released on Sep 1 2007) and nobody reported
the issue earlier...
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> diff --git a/include/linux/ide.h b/include/linux/ide.h
> index 2e4b8dd..4ed4777 100644
> --- a/include/linux/ide.h
> +++ b/include/linux/ide.h
> @@ -667,7 +667,7 @@ typedef struct hwif_s {
> u8 straight8; /* Alan's straight 8 check */
> u8 bus_state; /* power state of the IDE bus */
>
> - u16 host_flags;
> + u32 host_flags;
>
> u8 pio_mask;
next prev parent reply other threads:[~2007-10-23 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 9:09 [PATCH]: Fix IDE host_flags regression David Miller
2007-10-23 19:50 ` Bartlomiej Zolnierkiewicz [this message]
2007-10-23 21:45 ` Alan Cox
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=200710232150.14284.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.