From: Jeff Garzik <jeff@garzik.org>
To: Bryan Wu <cooloney@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Blackfin EMAC Driver: code cleanup
Date: Tue, 29 Apr 2008 01:59:28 -0400 [thread overview]
Message-ID: <4816B940.1080203@garzik.org> (raw)
In-Reply-To: <1209095591-20920-2-git-send-email-cooloney@kernel.org>
Bryan Wu wrote:
> - replace specific "bf537" function or data structure name to "bfin_mac"
> - cleanup bfin_mac_probe with error checking
> - punt set_pin_mux function, call peripheral request/free list functions directly
>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
applied 1-2
next prev parent reply other threads:[~2008-04-29 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 3:53 [PATCH 0/2] Blackfin on-chip EMAC driver updates Bryan Wu
2008-04-25 3:53 ` [PATCH 1/2] Blackfin EMAC Driver: code cleanup Bryan Wu
2008-04-29 5:59 ` Jeff Garzik [this message]
2008-04-25 3:53 ` [PATCH 2/2] Blackfin EMAC Driver: Initial version of ethtool support was checked in and more ethtool operations will be supported in the future Bryan Wu
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=4816B940.1080203@garzik.org \
--to=jeff@garzik.org \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).