From: Jon Mason <jdmason@us.ibm.com>
To: Richard Dawe <rich@phekda.gotadsl.co.uk>
Cc: Francois Romieu <romieu@fr.zoreil.com>, netdev@oss.sgi.com
Subject: Re: [PATCH 2/3] r8169: code clean-up
Date: Sun, 20 Feb 2005 12:14:15 -0600 [thread overview]
Message-ID: <200502201214.15884.jdmason@us.ibm.com> (raw)
In-Reply-To: <4218CE73.6010206@phekda.gotadsl.co.uk>
On Sunday 20 February 2005 11:52 am, Richard Dawe wrote:
> Hello.
>
> Francois Romieu wrote:
> > Jon Mason <jdmason@us.ibm.com> :
>
> [snip]
>
> >>adds a link down notification, and cleans up
> >
> > Ok. I'll netif_msg it before someone else complains that the driver
> > is too verbose.
>
> [snip]
>
> I started working on adding netif_msg checks to the printks. How far
> have you got? I don't want to duplicate your work.
>
> Incidentally, is there a to-do list somewhere for the r8169 driver?
Not to my knowledge. It would be nice if there was a wiki out there which
lists all of the drivers and areas to work on (features enablement, open
bugs, etc.)
> Maybe I can help out with some of the things.
I know Francois likes it when people test his patches. :-)
> Thanks, bye, Rich =]
next prev parent reply other threads:[~2005-02-20 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 0:23 [PATCH 2/3] r8169: code clean-up Jon Mason
2005-02-17 23:28 ` Francois Romieu
2005-02-18 4:00 ` Jon Mason
2005-02-20 17:52 ` Richard Dawe
2005-02-20 18:14 ` Jon Mason [this message]
2005-02-21 0:28 ` Francois Romieu
2005-02-21 3:40 ` Jon Mason
[not found] ` <200502181918.07859.jdmason@us.ibm.com>
[not found] ` <20050219104640.GA31035@electric-eye.fr.zoreil.com>
2005-02-19 17:47 ` Jon Mason
2005-02-19 22:30 ` Francois Romieu
2005-02-20 18:04 ` Jon Mason
2005-02-20 23:34 ` Francois Romieu
2005-02-21 4:54 ` Jon Mason
2005-02-21 8:16 ` Francois Romieu
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=200502201214.15884.jdmason@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=rich@phekda.gotadsl.co.uk \
--cc=romieu@fr.zoreil.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.