From: hayeswang <hayeswang@realtek.com>
To: "'Francois Romieu'" <romieu@fr.zoreil.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 3/5] r8169: fix the wrong parameter of point address
Date: Tue, 22 Feb 2011 16:46:02 +0800 [thread overview]
Message-ID: <F0C0A9D890424ECAAB19523FCC4A2FCC@realtek.com.tw> (raw)
In-Reply-To: <20110222082153.GA12463@electric-eye.fr.zoreil.com>
> -----Original Message-----
> From: Francois Romieu [mailto:romieu@fr.zoreil.com]
> Sent: Tuesday, February 22, 2011 4:22 PM
> To: Hayeswang
> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 3/5] r8169: fix the wrong parameter of
> point address
>
> Francois Romieu <romieu@fr.zoreil.com> :
> > Hayes Wang <hayeswang@realtek.com> :
> > > Correct the parameter of rtl8168_oob_notify. It results
> in the wrong
> > > point address and influences RTL8168DP.
> >
> > Please send this one separately as a patch against current
> kernel tree
> > as it is clearly a bugfix. The remaining patches are probably more
> > -next material.
>
> Correct me if I am wrong:
> - #3 and #1 are bugfixes
> - can you specify if #4 and #5 are either bugfixes,
> optimizations or cleanups ?
> - #2 adds support for a new chipset
#1, #3, #4 are bugfixes.
#2 adds support for a new chipset
#5 is cleanup.
I would separate them and send the patches again.
Best Regards,
Hayes
next prev parent reply other threads:[~2011-02-22 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 6:41 [PATCH 1/5] r8169: Correct settings of rtl8102e Hayes Wang
2011-02-22 6:41 ` [PATCH 2/5] r8169: Support RTL8105E Hayes Wang
2011-02-22 6:41 ` [PATCH 3/5] r8169: fix the wrong parameter of point address Hayes Wang
2011-02-22 8:00 ` Francois Romieu
2011-02-22 8:21 ` Francois Romieu
2011-02-22 8:46 ` hayeswang [this message]
2011-02-22 6:41 ` [PATCH 4/5] r8169: adjust the code of RTL8168DP Hayes Wang
2011-02-22 6:41 ` [PATCH 5/5] r8169: adjust rtl8169_set_speed_xmii function Hayes Wang
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=F0C0A9D890424ECAAB19523FCC4A2FCC@realtek.com.tw \
--to=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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®