From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>
Cc: jeffrey.t.kirsher@intel.com, shemminger@vyatta.com,
netdev@vger.kernel.org, gospo@redhat.com,
peter.p.waskiewicz.jr@intel.com
Subject: Re: [ethtool PATCH] ethtool: Add Direct Attach to the available connector ports
Date: Sun, 29 Nov 2009 05:42:28 -0500 [thread overview]
Message-ID: <4B125014.9080507@garzik.org> (raw)
In-Reply-To: <20091129.003601.253425360.davem@davemloft.net>
On 11/29/2009 03:36 AM, David Miller wrote:
> From: Jeff Kirsher<jeffrey.t.kirsher@intel.com>
> Date: Wed, 25 Nov 2009 02:13:15 -0800
>
>> From: PJ Waskiewicz<peter.p.waskiewicz.jr@intel.com>
>>
>> This adds Direct Attach SFP+ types to the connector ports
>> for the GSET mode.
>>
>> Signed-off-by: Peter P Waskiewicz Jr<peter.p.waskiewicz.jr@intel.com>
>> Signed-off-by: Jeff Kirsher<jeffrey.t.kirsher@intel.com>
>
> Jeff Garzik, ping?
These days, unless I have some massive objection, I merge stuff into
ethtool when the kernel bits hit net-next. ethtool should be current as
of net-next 24 hrs ago.
I queued the ethtool patch in $subject, and was waiting on your kernel
merge verdict.
> Also, do you plan on doing any ethtool releases this century? :-)
I've been trying to think of what would be a good versioning scheme for
ethtool. Even though it is [essentially] a user-friendly kernel
interface, its releases have never really been closely synchronized with
the kernel releases. And unlike a lot of other software, ethtool is so
simple it does not really go through any release-candidate or beta period.
The current scheme just increments a release number: 5->6, 6->7, etc.
But with so few kernel releases (and thus ethtool releases), I was
leaning towards either yearly release naming ("ethtool-2009"), kernel
release naming ("ethtool-2.6.33"), or the release scheme proposed for
glibc: snapshot directly from the git repository.
If people want one, I could do a release right now. Or, we could move
to an alternate scheme like git snapshots. I think git snapshots are
viable because ethtool has historically had next to zero bugs in the
actual userland utility. Fedora already imports git snapshots, for example.
Preferences?
Jeff
next prev parent reply other threads:[~2009-11-29 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 10:13 [ethtool PATCH] ethtool: Add Direct Attach to the available connector ports Jeff Kirsher
2009-11-29 8:36 ` David Miller
2009-11-29 10:42 ` Jeff Garzik [this message]
2009-11-29 18:35 ` Peter P Waskiewicz Jr
2009-11-30 12:35 ` Ben Hutchings
2009-12-23 22:52 ` Jeff Garzik
2009-11-29 11:03 ` 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=4B125014.9080507@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@vyatta.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).