[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1CCDC14B@AcuExch.aculab.com>
Date: Tue, 9 Feb 2016 16:10:13 +0000
From: David Laight <David.Laight@...LAB.COM>
To: "'Karicheri, Muralidharan'" <m-karicheri2@...com>,
"Strashko, Grygorii" <grygorii.strashko@...com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>,
"Arnd Bergmann" <arnd@...db.de>
CC: "Cooper Jr., Franklin" <fcooper@...com>,
"Nori, Sekhar" <nsekhar@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Kwok, WingMan" <w-kwok2@...com>,
"N, Mugunthan V" <mugunthanvnm@...com>
Subject: RE: [PATCH] net: ti: netcp: restore get/set_pad_info() functionality
From: Karicheri, Muralidharan
> Sent: 09 February 2016 16:10
...
> >In reality the 'pad' fields ought to be renamed - since they aren't pads.
> >Perhaps they should be a union?
> No. At the end of the descriptor, host software can add scratchpad which is
> not modified by the hardware, but is used by the driver. So please don't
> rename.
So comment in the definition that the hardware doesn't modify them.
The driver is defining these fields and they are definitely NOT padding.
David
Powered by blists - more mailing lists