Please stay on the mailing list.

I'm not doing substantive review of the patch, so I don't need a new
repost.  It is possible that whoever does review the patch could request
one.

It is customary to describe the changes from one version of a patch to
another following the commit message, near the diffstat.

On Tue, Jun 24, 2014 at 04:04:19PM +0000, Polehn, Mike A wrote:
> Hi Ben!
> 
> This was a repost with no code changes but an additional performance change 
> comment.
> 
> Do you want a new repost?
> 
> Mike
> 
> -----Original Message-----
> From: Ben Pfaff [mailto:b...@nicira.com] 
> Sent: Tuesday, June 24, 2014 8:50 AM
> To: Polehn, Mike A
> Cc: dev@openvswitch.org
> Subject: Re: [ovs-dev] PATCH [1/1] High speed PMD physical NIC queue size, 
> resubmit
> 
> On Thu, Jun 19, 2014 at 10:58:26PM +0000, Polehn, Mike A wrote:
> > Large TX and RX queues are needed for high speed 10 GbE physical NICS.
> > Observed a 250% zero loss improvement over small NIC queue test for A 
> > port to port flow test.
> > 
> > Signed-off-by: Mike A. Polehn <mike.a.pol...@intel.com>
> 
> Please be more careful with subject lines.  The correct format would be:
> 
>         [PATCH v2] High speed PMD physical NIC queue size
> 
> or if you didn't actually change anything from the first posting (in which 
> case I'd discourage reposting it):
> 
>         [PATCH repost] High speed PMD physical NIC queue size
> 
> The reason that this is important is because "git am" automatically strips 
> anything in brackets in the subject from the commit message.  We don't want 
> PATCH or "resubmit" in the commit message.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to