From: Andrew Lunn <andrew@lunn.ch>
To: "Koteshwar Rao, Satha" <Satha.Rao@cavium.com>
Cc: Sunil Kovvuri <sunil.kovvuri@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Goutham, Sunil" <Sunil.Goutham@cavium.com>,
Robert Richter <rric@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Daney, David" <David.Daney@cavium.com>,
"Vatsavayi, Raghu" <Raghu.Vatsavayi@cavium.com>,
"Chickles, Derek" <Derek.Chickles@cavium.com>,
"Romanov, Philip" <Philip.Romanov@cavium.com>,
Linux Netdev List <netdev@vger.kernel.org>,
LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH 0/7] ThunderX Embedded switch support
Date: Mon, 26 Dec 2016 15:55:15 +0100 [thread overview]
Message-ID: <20161226145515.GD30335@lunn.ch> (raw)
In-Reply-To: <DM5PR07MB2842EC647393430BE559D5B78D960@DM5PR07MB2842.namprd07.prod.outlook.com>
On Mon, Dec 26, 2016 at 02:04:27PM +0000, Koteshwar Rao, Satha wrote:
> Hi Sunil,
>
> In RFC cover letter we explained the feature details, files organized based on their supporting functionality, let me know if you are interested in any specific details
Please don't top post. Also, please perform correct quoting of the
email you are replying to.
As for getting patches merged, you will find it easier to get reviews
if you have lots of small patches which are obviously correct, and
each has a good change log entry describing the why as well as what.
Andrew
prev parent reply other threads:[~2016-12-26 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 8:46 [RFC PATCH 0/7] ThunderX Embedded switch support Satha Koteswara Rao
2016-12-21 8:46 ` [RFC PATCH 1/7] PF driver modified to enable HW filter support, changes works in backward compatibility mode Enable required things in Makefile Enable LZ4 dependecy inside config file Satha Koteswara Rao
2016-12-21 13:05 ` Sunil Kovvuri
2016-12-26 14:20 ` Koteshwar Rao, Satha
2016-12-27 4:19 ` Sunil Kovvuri
2016-12-21 8:46 ` [RFC PATCH 2/7] VF driver changes to enable hooks to get kernel notifications Satha Koteswara Rao
2016-12-21 8:46 ` [RFC PATCH 3/7] Enable pause frame support Satha Koteswara Rao
[not found] ` <DM5PR07MB2889471E0668C95BD2A266709E930@DM5PR07MB2889.namprd07.prod.outlook.com>
2016-12-26 14:21 ` Koteshwar Rao, Satha
2016-12-21 8:46 ` [RFC PATCH 4/7] HW Filter Initialization code and register access APIs Satha Koteswara Rao
2016-12-21 12:36 ` Sunil Kovvuri
2016-12-26 14:13 ` Koteshwar Rao, Satha
2016-12-21 8:46 ` [RFC PATCH 5/7] Multiple VF's grouped together under single physical port called PF group PF Group maintainance API's Satha Koteswara Rao
2016-12-21 12:43 ` Sunil Kovvuri
2016-12-26 14:16 ` Koteshwar Rao, Satha
2016-12-21 8:46 ` [RFC PATCH 6/7] HW Filter Table access API's Satha Koteswara Rao
2016-12-21 8:46 ` [RFC PATCH 7/7] Get notifications from PF driver and configure filter block based on request data Satha Koteswara Rao
2016-12-21 12:03 ` [RFC PATCH 0/7] ThunderX Embedded switch support Sunil Kovvuri
2016-12-26 14:04 ` Koteshwar Rao, Satha
2016-12-26 14:55 ` Andrew Lunn [this message]
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=20161226145515.GD30335@lunn.ch \
--to=andrew@lunn.ch \
--cc=David.Daney@cavium.com \
--cc=Derek.Chickles@cavium.com \
--cc=Philip.Romanov@cavium.com \
--cc=Raghu.Vatsavayi@cavium.com \
--cc=Satha.Rao@cavium.com \
--cc=Sunil.Goutham@cavium.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rric@kernel.org \
--cc=sunil.kovvuri@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;
as well as URLs for NNTP newsgroup(s).