From: Greg KH <gregkh@suse.de>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 1/2]: Renumber PCI error enums to start at zero
Date: Tue, 12 Dec 2006 12:35:43 -0800 [thread overview]
Message-ID: <20061212203543.GA4991@suse.de> (raw)
In-Reply-To: <20061212195524.GG4329@austin.ibm.com>
On Tue, Dec 12, 2006 at 01:55:24PM -0600, Linas Vepstas wrote:
>
> Greg, Andrew,
>
> This patch fixes an annoying numbering mistake.
> Please apply this (and the next patch).
>
> --linas
>
> Subject: [PATCH 1/2]: Renumber PCI error enums to start at zero
>
> Renumber the PCI error enums to start at zero for "normal/online".
> This allows un-initialized pci channel state (which defaults to zero)
> to be interpreted as "normal". Add very simple routine to check
> state, just in case this ever has to be fiddled with again.
No, as you have a specific type for this state, never test it against
"zero". That just defeats the whole issue of having a special type for
this state.
So you should not have to change the values of the enumerated type for
the code to work properly. In fact, I would argue that we should not
change it for this very reason :)
So, care to respin these without the enum changes to provide the new
function and use it?
thanks,
greg k-h
next prev parent reply other threads:[~2006-12-12 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 19:55 [PATCH 1/2]: Renumber PCI error enums to start at zero Linas Vepstas
2006-12-12 20:01 ` [PATCH 2/2]: Use newly defined PCI channel offline routine Linas Vepstas
2006-12-12 21:27 ` Auke Kok
2006-12-12 20:35 ` Greg KH [this message]
2006-12-12 21:35 ` [PATCH 1/2]: Renumber PCI error enums to start at zero Linas Vepstas
2006-12-12 21:42 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-11-01 23:54 Linas Vepstas
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=20061212203543.GA4991@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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.