From: Jeff Garzik <jgarzik@pobox.com>
To: Jochen Friedrich <jochen@scram.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
mike_phillips@urscorp.com, phillim2@comcast.net
Subject: Re: [BUG] smctr.c changes in latest BK
Date: Thu, 13 Feb 2003 18:34:51 -0500 [thread overview]
Message-ID: <3E4C2B9B.8000509@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302140001160.28838-100000@gfrw1044.bocc.de>
Jochen Friedrich wrote:
> After taking a second look, i just recognized that both cases (MAC adress
> all-zero or not) are handled exactly the same (by duplicated code), so the
> whole stuff is unnecessary.
>
> The whole function just reduces to a simple copy loop:
yep, you're right. applied.
next prev parent reply other threads:[~2003-02-13 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 22:46 [BUG] smctr.c changes in latest BK Jochen Friedrich
2003-02-13 23:05 ` Jochen Friedrich
2003-02-13 23:34 ` Jeff Garzik [this message]
2003-02-14 9:48 ` Olivier Galibert
2003-02-14 10:15 ` Jochen Friedrich
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=3E4C2B9B.8000509@pobox.com \
--to=jgarzik@pobox.com \
--cc=jochen@scram.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike_phillips@urscorp.com \
--cc=phillim2@comcast.net \
--cc=torvalds@transmeta.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