From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Miller <davem@davemloft.net>
Cc: kxie@chelsio.com, linux-scsi@vger.kernel.org,
netdev@vger.kernel.org, hariprasad@chelsio.com,
anish@chelsio.com, hch@infradead.org, michaelc@cs.wisc.edu
Subject: Re: [PATCH net v7 3/7] cxgb4/cxgb4i: set the max. pdu length in firmware
Date: Wed, 10 Dec 2014 23:41:29 +0300 [thread overview]
Message-ID: <1418244089.8310.15.camel@HansenPartnership.com> (raw)
In-Reply-To: <20141210.153159.617405179156473446.davem@davemloft.net>
On Wed, 2014-12-10 at 15:31 -0500, David Miller wrote:
> From: Karen Xie <kxie@chelsio.com>
> Date: Wed, 10 Dec 2014 12:24:09 -0800
>
> > [PATCH net v7 3/7] cxgb4/cxgb4i: set the max. pdu length in firmware.
>
> Please listen to the feedback you have been given.
>
> Again, you should not duplicate the Subject line in your message
> body, that makes more work for the people integrating your patches
> as we have to remove all of these things by hand.
While we're on the subject of making life easier for maintainers, could
I put in a plea for threading your patch set? It really does make it
easier to find and apply all the patches, especially on a high traffic
list where they otherwise get interspersed with other messages. If you
don't use git-send-email, which threads automatically, you can thread
manually by just making all the other patches a reply to your [PATCH
0/N],
James
next prev parent reply other threads:[~2014-12-10 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 20:24 [PATCH net v7 3/7] cxgb4/cxgb4i: set the max. pdu length in firmware Karen Xie
2014-12-10 20:31 ` David Miller
2014-12-10 20:41 ` James Bottomley [this message]
2014-12-10 20:44 ` David Miller
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=1418244089.8310.15.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=anish@chelsio.com \
--cc=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=hch@infradead.org \
--cc=kxie@chelsio.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=netdev@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 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.