From: Andi Kleen <ak@muc.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org,
khawar.chaudhry@amd.com, reeja.john@amd.com
Subject: Re: [PATCH] amd8111e endian & barrier fixes
Date: Fri, 08 Oct 2004 13:47:18 +0200 [thread overview]
Message-ID: <m3u0t5a0u1.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2MWTy-5mO-5@gated-at.bofh.it> (Benjamin Herrenschmidt's message of "Fri, 08 Oct 2004 09:00:12 +0200")
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> Hi Jeff !
>
> This patch against the amd8111e makes it work on some about-to-be-released
> piece of PPC hardware. It does:
>
> - Fix endian
> - Search for the PHY on MII instead of hard coding the ID
> - Add a couple of wmb's where needed on descriptor updates
>
> I must appologize for having re-indented one of the rx functions, but I
> just couldn't read/understand it without doing so, it was going back
> leftward in the middle of a { } block ...
It's basically impossible to review the patch properly because
of that change. Can you please separate the arbitary white space
change into a different patch?
Also I would suggest you send the patch to the driver
maintainers for review first (cc'ed)
>From a quick look the change to clear the ring rx flags completely
instead of clearing the bit looks bogus. Why did you not just add a
endian conversion there?
I can test it when it's properly reviewd.
-Andi
next parent reply other threads:[~2004-10-08 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2MWTy-5mO-5@gated-at.bofh.it>
2004-10-08 11:47 ` Andi Kleen [this message]
2004-10-09 1:06 ` [PATCH] amd8111e endian & barrier fixes Benjamin Herrenschmidt
2004-10-08 6:41 Benjamin Herrenschmidt
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=m3u0t5a0u1.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=khawar.chaudhry@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reeja.john@amd.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 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.