From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>, backports@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 2/2] backports: add the necessary backports for netlink extack
Date: Fri, 21 Apr 2017 20:50:51 +0200 [thread overview]
Message-ID: <d79056c4-ff9d-0e16-ed84-03fae4cdee83@broadcom.com> (raw)
In-Reply-To: <20170421104722.21538-2-johannes@sipsolutions.net>
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?
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> backport/backport-include/linux/netlink.h | 17 ++++++++
> backport/backport-include/net/genetlink.h | 24 +++++++++++
> backport/backport-include/net/netlink.h | 69 +++++++++++++++++++++++++++++++
> patches/0078-genl-extack.cocci | 5 +++
> 4 files changed, 115 insertions(+)
> create mode 100644 patches/0078-genl-extack.cocci
[...]
> +/* 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 */
> +static inline struct netlink_ext_ack *genl_info_extack(struct genl_info *info)
> +{
> +#if LINUX_VERSION_IS_GEQ(4,12,0)
> + return info->extack;
> +#else
> + return NULL;
> +#endif
> +}
> +
> /* this is for patches we apply */
> #if LINUX_VERSION_IS_LESS(3,7,0)
> #define genl_info_snd_portid(__genl_info) (__genl_info->snd_pid)
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-04-21 18:50 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 [this message]
2017-04-21 18:54 ` Johannes Berg
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=d79056c4-ff9d-0e16-ed84-03fae4cdee83@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
/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