From: Aaron Young <ayoung@google.engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix prom revision checks in SN kernel
Date: Tue, 27 Jun 2006 22:09:16 +0000 [thread overview]
Message-ID: <200606272209.PAA86361@google.engr.sgi.com> (raw)
In-Reply-To: <200606271946.MAA19328@google.engr.sgi.com>
>
> > Yeah, I didn't go for any clean up. We *shouldn't* be adding
> > any more explicit prom rev. checks to the code because we
> > now have an interface to check for prom "features" - see
> > sn_prom_feature_available().
>
> Recollections of that in the hind-brain prompted me to think
> that there should be a better way.
>
> > Unfortunately these checks were added before the interface
> > was available and therefore the checks have to stay.
>
> Makes sense.
>
> > I can still do some clean up if preferred.
>
> No, 3-places doesn't really justify invention of a generic
> method ... and since you've already got a better method that
> will prevent this from spreading elsewhere, I'll take it
> as-is.
>
Tony, hold up. I was just informed there is a patch in-play which
will conflict with this one:
http://marc.theaimsgroup.com/?l=linux-ia64&m\x113944733900687&w=2
It removes the prom rev. check from
drivers/pci/hotplug/sgi_hotplug.c replacing it with
a sn_prom_feature_available() call. It's obviously
the preferrable code.
Should I resubmit without a change to drivers/pci/hotplug/sgi_hotplug.c?
Thanks,
-Aaron
next prev parent reply other threads:[~2006-06-27 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 19:46 [PATCH] fix prom revision checks in SN kernel Aaron Young
2006-06-27 21:00 ` Luck, Tony
2006-06-27 21:24 ` Aaron Young
2006-06-27 21:54 ` Luck, Tony
2006-06-27 22:09 ` Aaron Young [this message]
2006-06-27 22:16 ` Luck, Tony
2006-06-28 10:44 ` Prarit Bhargava
2006-06-28 10:50 ` Prarit Bhargava
2006-06-28 11:08 ` Prarit Bhargava
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=200606272209.PAA86361@google.engr.sgi.com \
--to=ayoung@google.engr.sgi.com \
--cc=linux-ia64@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.