public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	linux-security-module <linux-security-module@vger.kernel.org>,
	Serge Hallyn <serge.hallyn@canonical.com>
Subject: Re: Change in security maintainer for a few weeks
Date: Thu, 5 Jun 2014 15:54:24 -0700	[thread overview]
Message-ID: <20140605225424.GC32470@kroah.com> (raw)
In-Reply-To: <20140605185513.GA15591@mail.hallyn.com>

On Thu, Jun 05, 2014 at 08:55:13PM +0200, Serge E. Hallyn wrote:
> Quoting Greg KH (gregkh@linuxfoundation.org):
> > On Thu, Jun 05, 2014 at 02:38:25PM -0400, Josh Boyer wrote:
> > > On Thu, Jun 5, 2014 at 2:30 PM, Greg KH <gregkh@linuxfoundation.org> 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?
> > > 
> > > Serge seems to have already done this?
> > > 
> > > https://lkml.org/lkml/2014/6/4/350
> > 
> > Ah, that's good, but wasn't sent to the linux-security-module list where
> > I would have noticed it :(
> > 
> > The patches also don't seem to have ended up in Linus's tree either
> > yet...
> > 
> > Serge, are you going to be doing this in replacement of James for a
> > while?
> 
> I don't mind, but I definately don't mind if you do.  In the past with
> planned vacations James has asked me to babysit the tree, so I just
> wanted to make sure it didn't get neglected.  But he did not ask me,
> I'm just an interloper.

That's great, I wasn't aware of this.  Feel free to keep doing this and
taking over for now.  As you already have a kernel.org account, and have
done it in the past, it only makes sense for you to continue.

But next time, cc: the subsystem mailing list :)

thanks,

greg k-h

  reply	other threads:[~2014-06-05 22:50 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 [this message]
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

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=20140605225424.GC32470@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge.hallyn@canonical.com \
    --cc=serge@hallyn.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