All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Pryzby <justinpryzby@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5isms
Date: Wed, 7 Jan 2004 02:28:40 -0500	[thread overview]
Message-ID: <20040107072840.GA2903@andromeda> (raw)
In-Reply-To: <20031230213050.GA3301@andromeda>

And again ;)

arch/i386/kernel/irq.c:
 * (mostly architecture independent, will move to kernel/irq.c in 2.5.)

Justin
On Tue, Dec 30, 2003 at 04:30:50PM -0500, pryzbyj wrote:
> It seems I've found another 2.5ism.  2.6.0, arch/i386/kernel/dmi_scan.c
> has
> 
> #ifdef CONFIG_SIMNOW
>         /*
>          *      Skip on x86/64 with simnow. Will eventually go away
>          *      If you see this ifdef in 2.6pre mail me !
>          */
>         return -1;
> #endif
> 
> I don't know whose file this is ..
> 
> Also, 2.6.0 still has the previously mentioned problem in
> include/asm/io.h.
> 
> Not subscribed, CC me.
> 
> Justin
> 
> On Thu, Jul 03, 2003 at 01:01:34PM -0700, pryzbyj wrote:
> > Linux 2.4.21, include/asm/io.h:51 says "Will be removed in 2.4".  Its
> > there in 2.5.74 as well.
> > 
> > I can understand why it would be in 2.5; the comment should say 2.6,
> > though.
> > 
> > Justin

  parent reply	other threads:[~2004-01-07  7:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 20:01 "Will be removed in 2.4" Justin Pryzby
2003-07-03 23:19 ` Jeff Garzik
2003-12-30 21:30 ` 2.5isms Justin Pryzby
2004-01-03 15:18   ` 2.5isms Pavel Machek
2004-01-07  7:28   ` Justin Pryzby [this message]
2004-03-29 15:40   ` 2.5isms Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-12-31 23:06 2.5isms Justin Pryzby
2005-01-01  2:34 ` 2.5isms Nick Piggin
2005-01-01  8:40   ` 2.5isms Arjan van de Ven
2005-01-01  9:13   ` 2.5isms Andi Kleen
2005-01-02  0:43     ` 2.5isms Nick Piggin
2005-01-02  8:58       ` 2.5isms Arjan van de Ven
2005-01-03  0:49         ` 2.5isms Nick Piggin
2005-01-02 12:04       ` 2.5isms Andi Kleen
2005-01-03  0:44         ` 2.5isms Nick Piggin

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=20040107072840.GA2903@andromeda \
    --to=justinpryzby@users.sourceforge.net \
    --cc=linux-kernel@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.