[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49FCCD093EDAFE45B73804AC3C1112E52E5CFF@ORSMSX116.amr.corp.intel.com>
Date: Fri, 19 Feb 2016 19:51:39 +0000
From: "Underwood, JohnX" <johnx.underwood@...el.com>
To: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"nhorman@...hat.com" <nhorman@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"jogreene@...hat.com" <jogreene@...hat.com>
Subject: RE: [net-next 10/16] i40e: add check for null VSI
Sorry, folks. I was confused. The patch looked familiar, but I wasn't able to find the email where I originally sent it out.
-----Original Message-----
From: Kirsher, Jeffrey T
Sent: Friday, February 19, 2016 11:49 AM
To: David Miller; Underwood, JohnX
Cc: netdev@...r.kernel.org; nhorman@...hat.com; sassmann@...hat.com; jogreene@...hat.com
Subject: Re: [net-next 10/16] i40e: add check for null VSI
On Fri, 2016-02-19 at 14:41 -0500, David Miller wrote:
> From: "Underwood, JohnX" <johnx.underwood@...el.com>
> Date: Fri, 19 Feb 2016 19:15:53 +0000
>
> > ACK
>
> You should never top-post on this mailing list.
>
> But in this specific case it is even more important.
>
> So just in case it is not clear:
>
> Please, pretty please, DO NOT top-post ACKs to patches like
> this.
>
> It looks like a new, fresh, patch submission to patchwork therefore
> you are creating a significant burdon for me.
Not to mention he was ACK'ing his own patch that he authored. :-(
Sorry Dave, I will work with him offline.
Powered by blists - more mailing lists