From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH 3/3] backports: empty define for __ro_after_init
Date: Sat, 12 Nov 2016 22:07:22 +0100 [thread overview]
Message-ID: <1478984842.4226.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1478981923-12298-3-git-send-email-arend.vanspriel@broadcom.com> (sfid-20161112_212539_146779_9220B565)
On Sat, 2016-11-12 at 20:18 +0000, Arend van Spriel wrote:
> nl80211 now uses section qualifier __ro_after_init. However, this
> is not available in kernels before v4.6. Neither is the section
> itself hence adding an empty define in backports.
> +#if (LINUX_VERSION_CODE < KERNEL_VERSION(4,6,0))
> +#define __ro_after_init
> +#endif
Due to how __ro_after_init works, it *has* to be a macro originally, so
you could just ifndef on itself:
#ifndef __ro_after_init
#define __ro_after_init
#endif
and be slightly more compatible in case somebody ever backports it.
Don't think it really matters much, but why not.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2016-11-12 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 20:18 [PATCH 1/3] backports: add backport for nla_memdup() Arend van Spriel
2016-11-12 20:18 ` [PATCH 2/3] backports: add backport for genl_family_attrbuf() function Arend van Spriel
2016-11-12 20:18 ` [PATCH 3/3] backports: empty define for __ro_after_init Arend van Spriel
2016-11-12 21:07 ` Johannes Berg [this message]
2016-11-14 18:59 ` Luis R. Rodriguez
2016-11-14 19:26 ` Arend Van Spriel
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=1478984842.4226.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=mcgrof@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.