From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] MCA recovery: Montecito support
Date: Mon, 23 Oct 2006 00:53:21 +0000 [thread overview]
Message-ID: <453C1281.80106@jp.fujitsu.com> (raw)
In-Reply-To: <200610201555.k9KFtnvu20317790@clink.americas.sgi.com>
Russ Anderson wrote:
> + /*
> + * Look through the cache checks for a valid target identifier
> + */
> + for (i = 0; i < peidx_cache_check_num(peidx); i++) {
> + smei = (sal_log_mod_error_info_t *)peidx_cache_check(peidx, i);
> + if (smei->valid.target_identifier && smei->target_identifier)
> + return smei->target_identifier;
> + }
This says there would be more than 1 cache_check in the sal log.
I suppose it also means there would be more than 1 identifier.
Are there any reason why you don't handle identifiers other than
listed earliest?
Thanks,
H.Seto
next prev parent reply other threads:[~2006-10-23 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 15:55 [patch] MCA recovery: Montecito support Russ Anderson
2006-10-21 5:22 ` Keith Owens
2006-10-23 0:53 ` Hidetoshi Seto [this message]
2006-10-23 4:09 ` Russ Anderson
2006-10-25 22:59 ` Russ Anderson
2006-10-26 0:21 ` Hidetoshi Seto
2006-10-26 23:20 ` Russ Anderson
2006-10-27 0:25 ` Hidetoshi Seto
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=453C1281.80106@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox