public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	James Morris <jmorris@namei.org>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: Change in security maintainer for a few weeks
Date: Wed, 11 Jun 2014 04:49:43 +0200	[thread overview]
Message-ID: <20140611024943.GA25981@mail.hallyn.com> (raw)
In-Reply-To: <1402450480.612.18.camel@dhcp-9-2-203-236.watson.ibm.com>

Quoting Mimi Zohar (zohar@linux.vnet.ibm.com):
> On Tue, 2014-06-10 at 13:23 -0700, Greg KH wrote: 
> > On Tue, Jun 10, 2014 at 03:20:15PM +1000, James Morris wrote:
> > > On Thu, 5 Jun 2014, Greg KH wrote:
> > > 
> > > > Hi all,
> > > > 
> > > > James has had to step back from doing kernel work for a few weeks, so
> > > > I've offered to step up and handle the security patches to get shuttled
> > > > to Linus for merging for a while.
> > > > 
> > > > I'll take his git tree on kernel.org and push those to Linus for
> > > > 3.16-rc1, as those look like they have had proper testing in linux-next.
> > > > 
> > > > But there only seems to be 14 patches in there.  Are there pending
> > > > patches that people have been sending and need to get in besides those?
> > > > 
> > > 
> > > Thanks for stepping up.
> > > 
> > > I had to take urgent leave and was unable to access email until this week.
> > > 
> > > We really should have a co-maintainer for the security subsystem -- please 
> > > feel free to nominate someone.
> > > 
> > > There are several good candidates, including Serge, Kees and Paul Moore.
> > 
> > As Serge has done it in the past when you are on vacation, I suggest he
> > continue doing it.
> 
> As long as Serge agrees, that sounds good.

Sure, happy to do help however I can.

-serge

      reply	other threads:[~2014-06-11  2:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 18:30 Change in security maintainer for a few weeks Greg KH
2014-06-05 18:38 ` Josh Boyer
2014-06-05 18:47   ` Serge E. Hallyn
2014-06-05 18:52   ` Greg KH
2014-06-05 18:55     ` Serge E. Hallyn
2014-06-05 22:54       ` Greg KH
2014-06-05 19:52 ` Dmitry Kasatkin
2014-06-06  3:26   ` Mimi Zohar
2014-06-05 21:51 ` Tetsuo Handa
2014-06-05 21:59 ` Jiri Kosina
2014-06-05 22:39   ` Paul Moore
2014-06-05 22:53     ` Greg KH
2014-06-06  4:42       ` Serge Hallyn
2014-06-06 15:08         ` Casey Schaufler
2014-06-06 15:23           ` Serge E. Hallyn
2014-06-06 15:41             ` Casey Schaufler
2014-06-10  5:20 ` James Morris
2014-06-10 20:23   ` Greg KH
2014-06-11  1:34     ` Mimi Zohar
2014-06-11  2:49       ` Serge E. Hallyn [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=20140611024943.GA25981@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=zohar@linux.vnet.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