lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 14 Apr 2012 09:12:18 +0000
From:	"Huang, Xiong" <>
To:	David Miller <>
CC:	"" <>,
	"" <>,
	qca-linux-team <>,
	nic-devel <>
Subject: RE: [PATCH 04/37] atl1c: remove VPD register

> -----Original Message-----
> From: David Miller []
> Sent: Saturday, April 14, 2012 8:46
> To: Huang, Xiong
> Cc:;; qca-linux-team; nic-
> devel
> Subject: Re: [PATCH 04/37] atl1c: remove VPD register
> From: xiong <>
> Date: Fri, 13 Apr 2012 08:14:29 +0800
> > VPD register is only used for L1(devid=PCI_DEVICE_ID_ATTANSIC_L1) to
> > access external NV-memory.
> > l1c & later chip doesn't use it any more.
> >
> > Signed-off-by: xiong <>
> > Tested-by: Liu David <>
> You just broke ethtool register dumps with this change.
> Now, all the initial registers are reported offset by one entry, yet the last two are
> still reported in their original spots.
> This layout is exposed to userspace, and interpreted by tools, and you cannot
> change it.
> If this register always reports some value, you should just keep it there in the
> dumps.
The VPD register doesn't report anything :(, just a dummy register now.
we don't have any special tools in userspace to explain the dumped registers.
Actually the purpose of dumping these registers via ethtool is just for debug.

> I think you guys are way too aggressively removing things from the driver.
> You are also posting way too many patches at one time.
> If you post so many patches at once, if one of the early patches have a problem
> (as already is the case here) it means all the rest of your patches will not apply
> without offsets or rejects and therefore will all need to be redone and
> resubmitted.
> Posting too many patches at once also creates a large burdon for those who will
> choose to help review your changes.
> Send a small, reasonable, number of patches at one time.  Say, for example, 10
> or 15 maximum.

Completely agree.


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists