From: Jeff Garzik <jgarzik@pobox.com>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: netdev@oss.sgi.com, Ralf Baechle <ralf@linux-mips.org>,
Manish Lachwani <mlachwani@mvista.com>,
Brian Waite <brian@waitefamily.us>,
"Steven J. Hill" <sjhill@realitydiluted.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] mv643xx enet update + ethtool support
Date: Thu, 24 Feb 2005 00:02:11 -0500 [thread overview]
Message-ID: <421D5FD3.9020107@pobox.com> (raw)
In-Reply-To: <20050217224239.GA16609@xyzzy>
Dale Farnsworth wrote:
> Here is an update to mv643xx ethernet support.
> There are several small bugfixes. The two larger issues are
> the beginning of ethtool support and the fact that I've disabled
> hardware tcp/udp checksum generation. It now looks like there's
> a hardware bug with the checksums, but I'm still characterizing it.
>
> ChangeSets before 1.2065 are already in -netdev.
> I've included a cumulative patch of the new changesets below.
>
> Thanks,
> -Dale Farnsworth
>
> Please do a
>
> bk pull bk://dfarnsworth.bkbits.net/linux-2.5-mv643xx-enet
Pulled. Two comments:
1) Your descriptions MUST follow the "one line summary" format found in
other changesets.
When Linus, myself and others use automated tools to summarize a large
number of changesets, the first line from each changeset description is
used. You should include an identifier indicating which area of the
kernel tree you are modifying ("mv643xx" in this case), and a one-line
summary of the changeset. For example, when I check in net driver
changesets, they look like
[netdrvr 8139too] fix bugs, whitespace change
* fix RX error overflow case
* Update PCI initialization code to better use PCI API
* trim trailing whitespace (chomp)
For now, I have (with great patience) hand-edited all 30+ changesets to
fix this up.
See rule #1 of http://linux.yyz.us/patch-format.html. Even though that
URL applies to patches, not BitKeeper, the one-line-summary and
$subsystem portions are applicable to you.
> +void mv643xx_set_ethtool_ops(struct net_device *netdev)
> +{
> + SET_ETHTOOL_OPS(netdev, &mv643xx_ethtool_ops);
> +}
> +
2) This function should not exist.
Jeff
next prev parent reply other threads:[~2005-02-24 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 22:42 [PATCH] mv643xx enet update + ethtool support Dale Farnsworth
2005-02-24 5:02 ` Jeff Garzik [this message]
2005-03-01 0:07 ` [PATCH] mv643xx: permit VLAN tagged rx packets + minor cleanup Dale Farnsworth
2005-03-02 6:20 ` Jeff Garzik
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=421D5FD3.9020107@pobox.com \
--to=jgarzik@pobox.com \
--cc=benh@kernel.crashing.org \
--cc=brian@waitefamily.us \
--cc=dale@farnsworth.org \
--cc=mlachwani@mvista.com \
--cc=netdev@oss.sgi.com \
--cc=ralf@linux-mips.org \
--cc=sjhill@realitydiluted.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).