From: Pete Zaitcev <zaitcev@redhat.com>
To: Cornelia Huck <COHUCK@de.ibm.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
netdev@oss.sgi.com, Utz Bacher <utz.bacher@de.ibm.com>
Subject: Re: Bug in qeth in 2.6
Date: Thu, 4 Sep 2003 11:45:12 -0400 [thread overview]
Message-ID: <20030904114512.A12054@devserv.devel.redhat.com> (raw)
In-Reply-To: <OFCF0074F3.0CE8CF77-ONC1256D97.00308924-C1256D97.0030F005@de.ibm.com>; from COHUCK@de.ibm.com on Thu, Sep 04, 2003 at 10:54:43AM +0200
On Thu, Sep 04, 2003 at 10:54:43AM +0200, Cornelia Huck wrote:
> could you please elaborate what's exactly wrong with qeth_verify_dev()?
>
> It has the same behaviour as in 2.4, and it looks correct to us...
2.4 was like this:
result = 0;
for (all in list) {
if (something)
result = QETH_VERIFY_IS_SOMETHING;
}
2.6 is:
result = 0;
for (all in list) {
result = (something)? QETH_VERIFY_IS_SOMETHING: foo();
}
Results are different if two cards are present on the list
and the function is asked to verify the first card.
-- Pete
next prev parent reply other threads:[~2003-09-04 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 8:54 Bug in qeth in 2.6 Cornelia Huck
2003-09-04 15:45 ` Pete Zaitcev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 16:01 Cornelia Huck
2003-09-03 18:54 Pete Zaitcev
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=20030904114512.A12054@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=COHUCK@de.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=utz.bacher@de.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).