From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Linux Security Module list <linux-security-module@vger.kernel.org>
Subject: Re: [PULL] Smack: Changes for 5.2
Date: Tue, 16 Apr 2019 10:33:42 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1904161033280.7992@namei.org> (raw)
In-Reply-To: <9a7f3da5-a80c-0fa6-c66d-70a1ef61af6f@schaufler-ca.com>
On Mon, 15 Apr 2019, Casey Schaufler wrote:
> James, please take these updates for 5.2. There's one bug fix for
> IPv6 handling and two memory use improvements.
>
> The following changes since commit 9d7b7bfbafba5e6cad609f1188243a7f0cd0d293:
>
> Merge tag 'v5.1-rc2' into next-general (2019-03-26 16:28:01 -0700)
>
> are available in the Git repository at:
>
> https://github.com/cschaufler/next-smack smack-for-5.2
>
> for you to fetch changes up to f7450bc6e76860564f3842a41892f9b74313cc23:
>
> Smack: Fix IPv6 handling of 0 secmark (2019-04-03 14:28:38 -0700)
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-smack
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2019-04-16 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 16:27 [PULL] Smack: Changes for 5.2 Casey Schaufler
2019-04-16 0:33 ` James Morris [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=alpine.LRH.2.21.1904161033280.7992@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox