linux-kernel - Re: [PATCH 08/12] ide: remove no longer needed IDE_HFLAG[_FORCE]_LEGACY

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 19 Jan 2009 15:41:41 +0100
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	petkovbb@...il.com
Cc:	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/12] ide: remove no longer needed IDE_HFLAG[_FORCE]_LEGACY_IRQS

On Monday 19 January 2009, Borislav Petkov wrote:
> Hi,
> 
> On Mon, Jan 19, 2009 at 3:14 PM, Bartlomiej Zolnierkiewicz
> <bzolnier@...il.com> wrote:
> 
> [.. ]
> 
> > Index: b/include/linux/ide.h
> > ===================================================================
> > --- a/include/linux/ide.h
> > +++ b/include/linux/ide.h
> > @@ -1347,10 +1347,6 @@ enum {
> >        IDE_HFLAG_ERROR_STOPS_FIFO      = (1 << 19),
> >        /* serialize ports */
> >        IDE_HFLAG_SERIALIZE             = (1 << 20),
> > -       /* use legacy IRQs */
> > -       IDE_HFLAG_LEGACY_IRQS           = (1 << 21),
> > -       /* force use of legacy IRQs */
> > -       IDE_HFLAG_FORCE_LEGACY_IRQS     = (1 << 22),
> >        /* host is TRM290 */
> >        IDE_HFLAG_TRM290                = (1 << 23),
> >        /* use 32-bit I/O ops */
> 
> maybe contigious numbering of the enums here?

I plan to re-use these two flags quite soon for other purposes so I thought
that I may save some time/noise on moving the rest of flags around... :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/