[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8761uf5xt0.fsf@nemi.mork.no>
Date: Thu, 05 Sep 2013 13:10:19 +0200
From: Bjørn Mork <bjorn@...k.no>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: "Nelson\, Shannon" <shannon.nelson@...el.com>,
"Kirsher\, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"e1000-devel\@lists.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
"Brandeburg\, Jesse" <jesse.brandeburg@...el.com>,
"gospo\@redhat.com" <gospo@...hat.com>,
"davem\@davemloft.net" <davem@...emloft.net>,
"sassmann\@redhat.com" <sassmann@...hat.com>
Subject: Re: [E1000-devel] [net-next v4 7/8] i40e: sysfs and debugfs interfaces
Stephen Hemminger <stephen@...workplumber.org> writes:
> More surprising is that others did not see the same things.
If I were to guess the 3 primary reasons for that:
1) the series is too large for anyone to actually read it all without
being paid to do so
2) the sysfs code is at the end of a huge debugfs patch, which
probably noone cares about whether they are paid or not
3) the small sysfs patch is so full of minor issues to nit about that
it seems pointless to even start
But since I looked at it, I can name a few other obvious issues with the
sysfs patch:
- mix of macro and octal mode values
- no documentation (required for all new sysfs attributes according to
Documentation/filesystems/sysfs.txt)
- extremely dubious kboject usage and attribute creation/deletion (How
does this fit into the driver model? How will userspace race with
these attributes being added and removed?)
I am sure there are plenty more.
Bjørn
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists