From: Greg KH <gregkh@linuxfoundation.org>
To: Mario_Limonciello@Dell.com
Cc: hayeswang@realtek.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
pali.rohar@gmail.com, anthony.wong@canonical.com
Subject: Re: [PATCH v3] r8152: Add support for setting pass through MAC address on RTL8153-AD
Date: Mon, 6 Jun 2016 07:50:21 -0700 [thread overview]
Message-ID: <20160606145021.GA6433@kroah.com> (raw)
In-Reply-To: <fa640d6998d8477b8ed43b70ddf6c0a8@ausx13mpc124.AMER.DELL.COM>
On Mon, Jun 06, 2016 at 02:43:37PM +0000, Mario_Limonciello@Dell.com wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Monday, June 6, 2016 9:40 AM
> > To: Limonciello, Mario <Mario_Limonciello@Dell.com>
> > Cc: hayeswang@realtek.com; LKML <linux-kernel@vger.kernel.org>; Netdev
> > <netdev@vger.kernel.org>; Linux USB <linux-usb@vger.kernel.org>;
> > pali.rohar@gmail.com; anthony.wong@canonical.com
> > Subject: Re: [PATCH v3] r8152: Add support for setting pass through MAC
> > address on RTL8153-AD
> >
> > On Mon, Jun 06, 2016 at 09:15:20AM -0500, Mario Limonciello wrote:
> > > Since this is a Realtek feature, I feel this shouldn't be moved into a platform
> > > MAC address lookup. The code should only be run when the correct
> > Realtek device
> > > is plugged in.
> > >
> > > Changes from v2:
> > > * Only apply to RTL8153-AD w/ eFuse pass through mac address pass thru
> > > bit set.
> > > * Drop matching DMI information on Dell. Although this is implemented
> > on
> > > Dell, this is a Realtek feature that may may be implemented on other
> > > OEMs as well.
> > > * Test that pass through MAC address is valid, fall back to HW address if
> > > invalid.
> > > * Don't track status of which device has MAC pass through activated.
> > > - Expected experience is that if two docks (RTL8153-AD's w/ mac pass thru
> > > bit set) were plugged in both should have MAC pass through activated.
> >
> > cover letters for single-patch submissions is overkill and confusing,
> > please don't.
>
> I was trying to convey differences between versions of this patch, I'll avoid
> that in the future and let the audience find them themselves.
No, put them in the patch itself, under the --- line, like is documented
to do so. Don't make people "find them themselves", if you do that,
your patch will just be ignored.
greg k-h
next prev parent reply other threads:[~2016-06-06 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 14:15 [PATCH v3] r8152: Add support for setting pass through MAC address on RTL8153-AD Mario Limonciello
2016-06-06 14:15 ` Mario Limonciello
2016-06-06 14:39 ` Greg KH
2016-06-06 14:56 ` Mario_Limonciello
2016-06-06 16:12 ` Greg KH
2016-06-06 17:24 ` Mario_Limonciello
2016-06-06 17:38 ` Greg KH
2016-06-06 14:40 ` Andrew Lunn
2016-06-06 14:57 ` Mario_Limonciello
2016-06-06 14:40 ` Greg KH
2016-06-06 14:43 ` Mario_Limonciello
2016-06-06 14:50 ` Greg KH [this message]
2016-06-06 14:51 ` Mario_Limonciello
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=20160606145021.GA6433@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Mario_Limonciello@Dell.com \
--cc=anthony.wong@canonical.com \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pali.rohar@gmail.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