All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Nelson\, Shannon" <shannon.nelson@intel.com>, "Kirsher\,
	Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"e1000-devel\@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	"netdev\@vger.kernel.org" <netdev@vger.kernel.org>, "Brandeburg\,
	Jesse" <jesse.brandeburg@intel.com>,
	"gospo\@redhat.com" <gospo@redhat.com>,
	"davem\@davemloft.net" <davem@davemloft.net>,
	"sassmann\@redhat.com" <sassmann@redhat.com>
Subject: Re: [E1000-devel] [net-next v4 7/8] i40e: sysfs and debugfs interfaces
Date: Thu, 05 Sep 2013 13:10:19 +0200	[thread overview]
Message-ID: <8761uf5xt0.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAOaVG17stH4K=MOfB0-OfqerVOmXpGQtERD7kgCF97AOtpn18A@mail.gmail.com> (Stephen Hemminger's message of "Wed, 4 Sep 2013 21:55:39 -0700")

Stephen Hemminger <stephen@networkplumber.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

  reply	other threads:[~2013-09-05 11:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 23:17 [net-next v4 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 1/7] i40e: main driver core Jeff Kirsher
2013-09-05 16:26   ` Stephen Hemminger
2013-09-05 17:59     ` Nelson, Shannon
2013-09-04 23:17 ` [net-next v4 2/8] i40e: transmit, receive, and napi Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 3/8] i40e: driver ethtool core Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 4/8] i40e: driver core headers Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 5/8] i40e: implement virtual device interface Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 6/8] i40e: init code and hardware support Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 7/8] i40e: sysfs and debugfs interfaces Jeff Kirsher
2013-09-05  0:37   ` [E1000-devel] " Stephen Hemminger
2013-09-05  1:25     ` Nelson, Shannon
2013-09-05  3:19       ` David Miller
2013-09-05  4:08         ` Brandeburg, Jesse
2013-09-05  4:37           ` David Miller
2013-09-06  3:09             ` Nelson, Shannon
2013-09-05  4:55       ` Stephen Hemminger
2013-09-05 11:10         ` Bjørn Mork [this message]
2013-09-05 15:21           ` Stephen Hemminger
2013-09-05 17:53     ` Nelson, Shannon
2013-09-05 18:32       ` [E1000-devel] " Stephen Hemminger
2013-09-05 23:38         ` John Fastabend
2013-09-04 23:17 ` [net-next v4 8/8] i40e: include i40e in kernel proper Jeff Kirsher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761uf5xt0.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.com \
    --cc=shannon.nelson@intel.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.