From: Francois Romieu <romieu@fr.zoreil.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12?
Date: Sat, 4 Jun 2005 13:33:16 +0200 [thread overview]
Message-ID: <20050604113316.GA3883@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <42A167FE.2020008@pobox.com>
Jeff Garzik <jgarzik@pobox.com> :
[...]
> >Any chance the r8169 queue could be merged in mainline before ?
>
> I'll push the length check.
Cool.
> Everything else is a new feature.
Hmmmm... Ok, let's have some r8169 handwaving/advocacy/explanation to
tell what is going on.
- From a usability viewpoint, the PCI ID for the USRobotics adapter
should be included. It has been reported around 10/04/2005.
Consider the usual july/LKS/conf period and it will not be available
in a stable serie before september (it is not a bugfix, it will not
be in 2.6.12.x either). USR has cut the price: it will have some
effect.
- The new features are not really new:
o 03/2005 for Stephen Hemminger's stats + other changes
-> it does not collide with existing functions.
o 03/2005 for the message level support
-> not new but it will be noticed, yes.
- Some of the usual suspects on netdev know the code and even if your
favorite r8169 maintainer has a real day job like everyone, I usually
manage to dig the issues when something hits the fan (no engagement in
sight, it helps :o) ).
Of course, you are free to ignore these points if you already took them
into consideration.
--
Ueimor
next prev parent reply other threads:[~2005-06-04 11:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 22:24 2.6.12? Jeff Garzik
2005-06-03 23:37 ` 2.6.12? Francois Romieu
2005-06-04 8:36 ` 2.6.12? Jeff Garzik
2005-06-04 11:33 ` Francois Romieu [this message]
2005-06-04 20:59 ` 2.6.12? Jeff Garzik
2005-06-03 23:38 ` 2.6.12? Andrew Morton
2005-06-03 23:55 ` 2.6.12? Jeff Garzik
2005-06-04 0:05 ` 2.6.12? Andrew Morton
2005-06-06 10:56 ` 2.6.12? Takashi Iwai
2005-06-04 0:01 ` 2.6.12? Wakko Warner
2005-06-04 0:51 ` 2.6.12? Andrew Morton
2005-06-04 0:03 ` 2.6.12? Benjamin Herrenschmidt
2005-06-04 1:19 ` 2.6.12? Andrew Morton
2005-06-04 0:05 ` 2.6.12? Brice Goglin
2005-06-04 1:21 ` 2.6.12? Andrew Morton
2005-06-07 14:43 ` 2.6.12? Brice Goglin
2005-06-07 15:53 ` 2.6.12? Sylvain Meyer
2005-06-08 8:02 ` 2.6.12? Brice Goglin
2005-06-04 0:34 ` 2.6.12? Dave Jones
2005-06-04 1:50 ` 2.6.12? Dmitry Torokhov
2005-06-04 8:15 ` 2.6.12? Russell King
2005-06-04 9:25 ` 2.6.12? Johannes Stezenbach
2005-06-04 12:25 ` 2.6.12? Michael Krufky
2005-06-04 14:23 ` 2.6.12? Martin J. Bligh
2005-06-04 14:35 ` 2.6.12? Martin J. Bligh
2005-06-04 15:24 ` 2.6.12? Rafael J. Wysocki
2005-06-04 22:11 ` 2.6.12? Andrew Morton
2005-06-05 15:02 ` 2.6.12? Martin J. Bligh
2005-06-07 18:16 ` 2.6.12? Martin J. Bligh
2005-06-07 19:24 ` 2.6.12? Andrew Morton
2005-06-08 12:56 ` 2.6.12? Andi Kleen
2005-06-08 19:47 ` 2.6.12? Martin J. Bligh
2005-06-08 23:04 ` 2.6.12? Martin J. Bligh
2005-06-09 4:44 ` 2.6.12? Martin J. Bligh
2005-06-09 19:45 ` 2.6.12? Martin J. Bligh
2005-06-09 13:41 ` 2.6.12? Andi Kleen
2005-06-06 22:06 ` 2.6.12? Adam Belay
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=20050604113316.GA3883@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®