From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
backports@vger.kernel.org
Subject: Re: [PATCH 2/2] backports: add the necessary backports for netlink extack
Date: Fri, 21 Apr 2017 20:54:20 +0200 [thread overview]
Message-ID: <1492800860.19290.3.camel@sipsolutions.net> (raw)
In-Reply-To: <d79056c4-ff9d-0e16-ed84-03fae4cdee83@broadcom.com> (sfid-20170421_205053_447231_D19084FD)
On Fri, 2017-04-21 at 20:50 +0200, Arend Van Spriel wrote:
> On 21-4-2017 12:47, Johannes Berg wrote:
> > From: Johannes Berg <johannes.berg@intel.com>
>
> I did not follow everything about this extack thing, but does it
> impose a version requirement on the libnl used in user-space?
No. It turns out that libnl doesn't care at all about the ack message
contents, so you can use any version.
Here's a sample iw patch:
https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/commit/?h=bpf&id=7105f7614c13680306cf3b91ad8711eccfa70df3
> > +/* this is for patches we apply */
>
> Guess the comment is inspired by the one below ;-) but would it not
> be a bit more clear to say:
>
> /* this is for files patched using 0078-genl-extack.cocci */
Yeah I guess that'd make some sense :)
Though realistically none of it is really all that necessary since one
can always grep ;-)
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2017-04-21 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:47 [PATCH 1/2] backports: extend magic to 6 possible arguments Johannes Berg
2017-04-21 10:47 ` [PATCH 2/2] backports: add the necessary backports for netlink extack Johannes Berg
2017-04-21 18:50 ` Arend Van Spriel
2017-04-21 18:54 ` Johannes Berg [this message]
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=1492800860.19290.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@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 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.