From: Paul Moore <pmoore@redhat.com>
To: Waiman Long <waiman.long@hp.com>, Eric Paris <eparis@redhat.com>
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: Follow-up on the lblnet-next tree
Date: Tue, 10 Sep 2013 10:14:46 -0400 [thread overview]
Message-ID: <3166714.Qb6aJAv2jX@sifl> (raw)
In-Reply-To: <522E5B41.9090003@hp.com>
On Monday, September 09, 2013 07:35:29 PM Waiman Long wrote:
> On 07/23/2013 06:05 PM, Paul Moore wrote:
> > Just a quick follow-up to let you know that I've rebased the lblnet-next
> > tree to Linus' post -rc2 tree from earlier today. I did a quick
> > build/boot/test cycle and everything looked sane to me, but additional
> > testing is always welcome.
> >
> > * git://git.infradead.org/users/pcmoore/lblnet-2.6_next
> > * http://git.infradead.org/users/pcmoore/lblnet-2.6_next
>
> Just want to know if you are planning to push those patches into v3.12.
You and me both.
Your patches, as well as a number of others, should go in via Eric's SELinux
tree, not my labeled networking tree; I was simply hosting the patches to get
them some exposure in linux-next. A few weeks back Eric merged the patches
into his SELinux tree so I dropped them from lblnet-next to prevent conflicts.
Eric, push them patches up to James already. It is absolutely ridiculous that
we've got bug fixes that have missed *several* kernel releases because you
aren't pushing fixes upstream. This is *extremely* frustrating.
--
paul moore
security and virtualization @ redhat
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2013-09-10 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 22:05 Follow-up on the lblnet-next tree Paul Moore
[not found] ` <522E5B41.9090003@hp.com>
2013-09-10 14:14 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-08 19:28 Paul Moore
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=3166714.Qb6aJAv2jX@sifl \
--to=pmoore@redhat.com \
--cc=eparis@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=waiman.long@hp.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 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.