All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem
Date: Thu, 28 Sep 2017 09:48:28 +0000	[thread overview]
Message-ID: <alpine.LRH.2.21.1709281946500.1903@namei.org> (raw)
In-Reply-To: <5855.1506590782@warthog.procyon.org.uk>

On Thu, 28 Sep 2017, David Howells wrote:

> James Morris <jmorris@namei.org> wrote:
> 
> > David, have you taken these into your tree?  I can apply them to mine if 
> > needed.
> 
> I was intending to add them to my next tree for security/next.

Ok, please add
Reviewed-by: James Morris <james.l.morris@oracle.com>

to these.

Also, please use the new next-general branch for tracking & pull requests 
for the next kernel.



-- 
James Morris
<jmorris@namei.org>


WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: Baolin Wang <baolin.wang@linaro.org>,
	james.l.morris@oracle.com, serge@hallyn.com, arnd@arndb.de,
	broonie@kernel.org, keyrings@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem
Date: Thu, 28 Sep 2017 19:48:28 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1709281946500.1903@namei.org> (raw)
In-Reply-To: <5855.1506590782@warthog.procyon.org.uk>

On Thu, 28 Sep 2017, David Howells wrote:

> James Morris <jmorris@namei.org> wrote:
> 
> > David, have you taken these into your tree?  I can apply them to mine if 
> > needed.
> 
> I was intending to add them to my next tree for security/next.

Ok, please add
Reviewed-by: James Morris <james.l.morris@oracle.com>

to these.

Also, please use the new next-general branch for tracking & pull requests 
for the next kernel.



-- 
James Morris
<jmorris@namei.org>

WARNING: multiple messages have this Message-ID (diff)
From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem
Date: Thu, 28 Sep 2017 19:48:28 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1709281946500.1903@namei.org> (raw)
In-Reply-To: <5855.1506590782@warthog.procyon.org.uk>

On Thu, 28 Sep 2017, David Howells wrote:

> James Morris <jmorris@namei.org> wrote:
> 
> > David, have you taken these into your tree?  I can apply them to mine if 
> > needed.
> 
> I was intending to add them to my next tree for security/next.

Ok, please add
Reviewed-by: James Morris <james.l.morris@oracle.com>

to these.

Also, please use the new next-general branch for tracking & pull requests 
for the next kernel.



-- 
James Morris
<jmorris@namei.org>

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-09-28  9:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  2:32 [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem Baolin Wang
2017-09-21  2:32 ` Baolin Wang
2017-09-21  2:32 ` Baolin Wang
2017-09-21  2:32 ` [PATCH v2 1/2] security: keys: Replace time_t/timespec with time64_t Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-21  2:32 ` [PATCH v2 2/2] security: keys: Replace time_t with time64_t for struct key_preparsed_payload Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-28  9:11 ` [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem James Morris
2017-09-28  9:11   ` James Morris
2017-09-28  9:11   ` James Morris
2017-09-28  9:26 ` David Howells
2017-09-28  9:26   ` David Howells
2017-09-28  9:26   ` David Howells
2017-09-28  9:48   ` James Morris [this message]
2017-09-28  9:48     ` James Morris
2017-09-28  9:48     ` James Morris
2017-09-28 22:05     ` Baolin Wang
2017-09-28 22:05       ` Baolin Wang
2017-09-28 22:05       ` Baolin Wang

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.1709281946500.1903@namei.org \
    --to=jmorris@namei.org \
    --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 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.