[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <FC41C24E35F18A40888AACA1A36F3E418ADD335B@fmsmsx115.amr.corp.intel.com>
Date: Thu, 15 Jan 2015 17:19:29 +0000
From: "Nelson, Shannon" <shannon.nelson@...el.com>
To: Or Gerlitz <gerlitz.or@...il.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
"nhorman@...hat.com" <nhorman@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"jogreene@...hat.com" <jogreene@...hat.com>,
"Krawczyk, Kamil" <kamil.krawczyk@...el.com>
Subject: RE: [net-next 13/17] i40e: AQ API updates for new commands
> From: Or Gerlitz [mailto:gerlitz.or@...il.com]
> Sent: Thursday, January 15, 2015 9:14 AM
>
> On Thu, Jan 15, 2015 at 2:19 PM, Jeff Kirsher
> <jeffrey.t.kirsher@...el.com> wrote:
> > From: Shannon Nelson <shannon.nelson@...el.com>
> >
> > Add lldp control commands, add oem ocsd and ocbb commands, and fix up
> > NVM config read and write data structs.
>
> Sounds to me like a proofed nightmare for someone doing future
> bisection and landing here... we want kernel patches to be made of
> basically one logical change, right?
Yes, but note that these are mostly API additions for transactions that aren't used in the code quite yet. There are a couple of defines that get changed as well, but they aren't used yet either else they'd be accompanied by related code changes.
sln
Powered by blists - more mailing lists