From: "John W. Linville" <linville@tuxdriver.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <lrodriguez@qca.qualcomm.com>
Subject: Re: [PATCH 2/2] compat: implement dummy security_sk_clone
Date: Fri, 18 Nov 2011 15:53:28 -0500 [thread overview]
Message-ID: <20111118205327.GB2663@tuxdriver.com> (raw)
In-Reply-To: <4EC6B3FA.90502@hauke-m.de>
On Fri, Nov 18, 2011 at 08:37:30PM +0100, Hauke Mehrtens wrote:
> On 11/17/2011 01:39 AM, John W. Linville wrote:
> > This has been defined in include/linux/security.h for some time, but was
> > only given an EXPORT_SYMBOL for 3.2. Add a compat_* definition to avoid
> > breaking the module load with an undefined symbol.
> >
> > Signed-off-by: John W. Linville <linville@tuxdriver.com>
<snip>
> Hi,
>
> security_sk_clone gets also exported in Linux-3.1 so this should move to
> include/linux/compat-3.1.h. 3.1-rcX did not contain this fix, but I hope
> nobody is using this any more.
>
> Hauke
>
> $ git tag --contains 6230c9b4f8957c8938ee4cf2d03166d3c2dc89de
> v3.1
> v3.1.1
> v3.2-rc1
> v3.2-rc2
My bad -- must have misread it! Sending a new one now...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-11-18 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 0:39 [PATCH 1/2] compat: avoid warning in compat_system_workqueue_create John W. Linville
2011-11-17 0:39 ` [PATCH 2/2] compat: implement dummy security_sk_clone John W. Linville
2011-11-18 19:37 ` Hauke Mehrtens
2011-11-18 20:53 ` John W. Linville [this message]
2011-11-18 19:24 ` [PATCH 1/2] compat: avoid warning in compat_system_workqueue_create Hauke Mehrtens
2011-11-18 19:32 ` Luis R. Rodriguez
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=20111118205327.GB2663@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@qca.qualcomm.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