From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Linux Security Module list
<linux-security-module@vger.kernel.org>
Subject: Re: [PULL] Smack: Repair for 5.2 build issue.
Date: Mon, 6 May 2019 08:53:29 -0700 [thread overview]
Message-ID: <c028ab99-c042-191c-8a18-d34b8ecfc3bd@schaufler-ca.com> (raw)
In-Reply-To: <b1d1d0b8-51cb-657b-c8be-aa365a29c8a5@schaufler-ca.com>
On 4/30/2019 2:29 PM, Casey Schaufler wrote:
> James, please pull this repair for a build problem with the last change.
James, did you get this request? It's an important build fix.
> The following changes since commit b9ef5513c99bf9c8bfd9c9e8051b67f52b2dee1e:
> smack: Check address length before reading address family (2019-04-29 17:32:27 -0700)
> are available in the git repository at:
> https://github.com/cschaufler/next-smack.git smack-for-5.2-b
> for you to fetch changes up to 619ae03e922b65a1a5d4269ceae1e9e13a058d6b:
> Smack: Fix kbuild reported build error (2019-04-30 14:13:32 -0700)
> ----------------------------------------------------------------
> Casey Schaufler (1):
> Smack: Fix kbuild reported build error
> security/smack/smack_lsm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
next prev parent reply other threads:[~2019-05-06 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 21:29 [PULL] Smack: Repair for 5.2 build issue Casey Schaufler
2019-05-06 15:53 ` Casey Schaufler [this message]
2019-05-06 21:31 ` James Morris
2019-05-06 23:45 ` Casey Schaufler
2019-05-07 3:29 ` James Morris
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=c028ab99-c042-191c-8a18-d34b8ecfc3bd@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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