From: Steffen Klassert <steffen.klassert@secunet.com>
To: Cong Wang <amwang@redhat.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, herbert@gondor.hengli.com.au
Subject: Re: [Patch net-next] xfrm: add missing xfrm message types to selinux perm table
Date: Wed, 5 Dec 2012 08:39:41 +0100 [thread overview]
Message-ID: <20121205073941.GA18940@secunet.com> (raw)
In-Reply-To: <1354690585.28951.10.camel@cr0>
On Wed, Dec 05, 2012 at 02:56:25PM +0800, Cong Wang wrote:
> On Wed, 2012-12-05 at 06:41 +0100, Steffen Klassert wrote:
> > On Tue, Dec 04, 2012 at 01:02:57PM -0500, David Miller wrote:
> > > From: Cong Wang <amwang@redhat.com>
> > > Date: Tue, 4 Dec 2012 13:39:31 +0800
> > >
> > > > Cc: Steffen Klassert <steffen.klassert@secunet.com>
> > > > Cc: Herbert Xu <herbert@gondor.apana.org.au>
> > > > Cc: "David S. Miller" <davem@davemloft.net>
> > > > Signed-off-by: Cong Wang <amwang@redhat.com>
> > >
> > > Steffen will you take this into your IPSEC tree?
> > >
> >
> > I would do so, but I have not seen this patch by now.
> > Was it really send to me? I have not even seen it on the
> > netdev list.
> >
> > Anyway, I don't have it, please resend.
> >
>
> Weird, you are already Cc'ed in the original patch, Cc: Steffen Klassert
> <steffen.klassert@secunet.com>.
>
Even patchwork does not list this patch, I can only guess that
something went wrong with your submission.
Please resend it,
Thanks.
next prev parent reply other threads:[~2012-12-05 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1354599571-6181-1-git-send-email-amwang@redhat.com>
2012-12-04 18:02 ` [Patch net-next] xfrm: add missing xfrm message types to selinux perm table David Miller
2012-12-05 5:41 ` Steffen Klassert
2012-12-05 6:56 ` Cong Wang
2012-12-05 7:39 ` Steffen Klassert [this message]
2012-12-05 7:42 Cong Wang
2012-12-05 8:14 ` Steffen Klassert
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=20121205073941.GA18940@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).