From: David Howells <dhowells@redhat•com>
To: Or Gerlitz <or.gerlitz@gmail•com>
Cc: dhowells@redhat•com, Or Gerlitz <ogerlitz@mellanox•com>,
netdev <netdev@vger•kernel.org>
Subject: Re: private netdev flags into UAPI?
Date: Tue, 27 Nov 2012 02:03:09 +0000 [thread overview]
Message-ID: <990.1353981789@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAJZOPZLQSCNTfSm63z1P_S4ZmwL+9mbP7rOCH7yHgBFcjaz1UA@mail.gmail.com>
Or Gerlitz <or.gerlitz@gmail•com> wrote:
> On Mon, Nov 26, 2012 at 11:22 AM, David Howells <dhowells@redhat•com> wrote:
> > They were exposed to userspace already
>
> So the script carries the bug into a new directory... why? AFAIK,
> intentionally there's no way to read private flags from user space, so
> what's the point in defining them there?
How should the script know what's private and what's not? By the
encapsulation of code inside __KERNEL__ blocks. In their absence, everything
is assumed to be public - given it is already part of the UAPI. I don't know
that the code is private rather than the comment is wrong.
David
next prev parent reply other threads:[~2012-11-27 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 7:43 private netdev flags into UAPI? Or Gerlitz
2012-11-26 9:22 ` David Howells
2012-11-26 22:29 ` Or Gerlitz
2012-11-27 2:03 ` David Howells [this message]
2012-11-27 6:51 ` Or Gerlitz
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=990.1353981789@warthog.procyon.org.uk \
--to=dhowells@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ogerlitz@mellanox$(echo .)com \
--cc=or.gerlitz@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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