From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH v2] backports: add spatch to handle IFF_NO_QUEUE
Date: Mon, 14 Sep 2015 10:27:33 +0200 [thread overview]
Message-ID: <1442219253.2075.4.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6VMH6Ket9CRni2KMiTaAgStUGqDtUoZw4buF0R=9TH_Aw@mail.gmail.com> (sfid-20150914_102534_238057_71CA5FF2)
On Mon, 2015-09-14 at 01:25 -0700, Luis R. Rodriguez wrote:
> > ++#if LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0)
> > + E->priv_flags |= IFF_NO_QUEUE;
> > ++#else
> > ++E->tx_queue_len = 0;
> > ++#endif
>
> Interesting so although priv_flags may be a member name prevalent in
> *many* data structures the SmPL rule here is very specific about the
> use of IFF_NO_QUEUE as a flag, and since we know that is unique to one
> use case we take the liberty over using expression here. Replying just
> to annotate this practice and Cc Julia on her thoughts.
>
Yeah I thought about this for a while - it doesn't even cover all cases
(there might be drivers that don't use |=, for example).
However, for now this seemed sufficient since very few places in the
code actually use this.
That said, there are cases where E really needs to be an expression
since it's not just "dev->..." but something like "foo->dev->...".
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2015-09-14 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 9:27 [PATCH v2] backports: add spatch to handle IFF_NO_QUEUE Johannes Berg
2015-09-14 8:25 ` Luis R. Rodriguez
2015-09-14 8:27 ` Johannes Berg [this message]
2015-09-14 9:33 ` Luis R. Rodriguez
2015-09-14 19:48 ` Julia Lawall
2015-09-30 19:10 ` Luis R. Rodriguez
2015-09-14 19:15 ` Julia Lawall
2015-09-22 21:41 ` Hauke Mehrtens
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=1442219253.2075.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=mcgrof@do-not-panic.com \
/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.