From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org,
ubraun@linux.ibm.com, johannes.berg@intel.com
Subject: Re: [PATCH] smc: generic netlink family should be __ro_after_init
Date: Thu, 20 Sep 2018 07:50:16 -0700 (PDT) [thread overview]
Message-ID: <20180920.075016.2069698292089129165.davem@davemloft.net> (raw)
In-Reply-To: <20180920072730.17584-1-johannes@sipsolutions.net>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu, 20 Sep 2018 09:27:30 +0200
> From: Johannes Berg <johannes.berg@intel.com>
>
> The generic netlink family is only initialized during module init,
> so it should be __ro_after_init like all other generic netlink
> families.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Looks good, applied.
prev parent reply other threads:[~2018-09-20 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 7:27 [PATCH] smc: generic netlink family should be __ro_after_init Johannes Berg
2018-09-20 14:50 ` David Miller [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=20180920.075016.2069698292089129165.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ubraun@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).