From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@redhat.com" <gospo@redhat.com>
Subject: Re: [net-next v2 07/14] i40evf: remove double space after return
Date: Mon, 31 Mar 2014 11:24:45 -0700 [thread overview]
Message-ID: <1396290285.2158.2.camel@jtkirshe-mobl.jf.intel.com> (raw)
In-Reply-To: <CAJZOPZKSowPH4fB_QS3eXh2e9QFESKGaFfo9=x9gncE9bL8xAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Mon, 2014-03-31 at 21:18 +0300, Or Gerlitz wrote:
> On Mon, Mar 31, 2014 at 8:48 PM, Jesse Brandeburg
> <jesse.brandeburg@intel.com> wrote:
> > On Fri, 28 Mar 2014 22:58:31 +0300
> > Or Gerlitz <or.gerlitz@gmail.com> wrote:
> >> Just out of curiosity, any special reason for four of the maintainers
> >> to sign on a patch that remove a space?
> >
> > Yeah, seems like lots of overkill, in this case it is just an artifact
> > of all the people that handled the patch as it exited our process.
> >
> > Thanks for the review.
>
> So beinh curios again, are you planning to change something based on
> this feedback and your overkill comment?
Yeah, I will ensure that patches I send out won't have an overkill of
signatures. I saw this when I went to push it upstream and thought
twice about trimming down the list. I plan on keeping the author,
tested-by and my signatures on the patch for sure.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-31 18:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 14:08 [net-next v2 00/14][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 01/14] i40e: Delete ATR filter on RST Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 02/14] i40evf: fix oops in watchdog handler Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 03/14] i40e: Make the alloc and free queue vector calls orthogonal Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 04/14] i40e: eeprom integrity check on load and empr Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 05/14] i40e: Cleanup in FDIR SB ethtool code Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 06/14] i40e: Add functionality for FD SB to drop packets Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 07/14] i40evf: remove double space after return Jeff Kirsher
2014-03-28 19:58 ` Or Gerlitz
2014-03-31 17:48 ` Jesse Brandeburg
2014-03-31 18:18 ` Or Gerlitz
2014-03-31 18:24 ` Jeff Kirsher [this message]
2014-03-28 14:08 ` [net-next v2 08/14] i40e: check for netdev before debugfs use Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 09/14] i40e/i40evf: Add an FD message level Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 10/14] i40e: Use DEBUG_FD message level for an FD message Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 11/14] e1000e: add timeout for TX HW time stamping work Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 12/14] e1000e: remove redundant if clause from PTP work Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 13/14] igb: never generate both software and hardware timestamps Jeff Kirsher
2014-03-28 14:08 ` [net-next v2 14/14] igb: fix race conditions on queuing skb for HW time stamp Jeff Kirsher
2014-03-28 18:45 ` [net-next v2 00/14][pull request] Intel Wired LAN Driver Updates 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=1396290285.2158.2.camel@jtkirshe-mobl.jf.intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@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).