netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: David Miller <davem@davemloft.net>,
	Ben Hutchings <ben@decadent.org.uk>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: kdoc struct net_device flags and priv_flags
Date: Tue, 25 Feb 2014 14:39:28 -0800	[thread overview]
Message-ID: <CAGVrzcaaViC10TvnSVBJsKRF3pSOvbP7Z+Kh4Qcu0RS_RY5GBA@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6WAmHqAYsh6rwyHdvZy3J6ck-uD_Kavk3qqy02vML359g@mail.gmail.com>

2014-02-25 14:19 GMT-08:00 Luis R. Rodriguez <mcgrof@do-not-panic.com>:
> On Mon, Feb 24, 2014 at 9:37 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> Le lundi 24 février 2014, 23:53:43 David Miller a écrit :
>>> They are visible to userspace via sysfs.
>>
>> In /sys/class/net/*/flags, although we are lacking quite a lot of documentation
>> for the exported attributes there.
>
> I only see dev->flags there, I don't see any toggle capability for
> priv_flags. Let me know if you find anywhere that userspace lets a
> user toggle private flags, I just don't see it.

You are right, those are dev->flags, not priv_flags, sorry about that.

>
> I'll extend the documentation for a v2 with the sysfs attribute stuff.

Thanks!
-- 
Florian

  reply	other threads:[~2014-02-25 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25  0:14 [PATCH] net: kdoc struct net_device flags and priv_flags Luis R. Rodriguez
2014-02-25  2:11 ` Ben Hutchings
2014-02-25  4:53   ` David Miller
2014-02-25  5:37     ` Florian Fainelli
2014-02-25  6:09       ` Luis R. Rodriguez
2014-02-25 22:19       ` Luis R. Rodriguez
2014-02-25 22:39         ` Florian Fainelli [this message]
2014-02-25 23:08           ` Luis R. Rodriguez
2014-02-25 13:47     ` Ben Hutchings

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=CAGVrzcaaViC10TvnSVBJsKRF3pSOvbP7Z+Kh4Qcu0RS_RY5GBA@mail.gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).