From: David Miller <davem@davemloft.net>
To: vyekkirala@trustedcs.com
Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov, eparis@redhat.com,
sgrubb@redhat.com, sds@tycho.nsa.gov, jmorris@namei.org,
chanson@trustedcs.com, michal.k.k.piotrowski@gmail.com
Subject: Re: [PATCH 1/1] selinux: fix 2.6.20-rc6 build when no xfrm
Date: Fri, 26 Jan 2007 19:04:07 -0800 (PST) [thread overview]
Message-ID: <20070126.190407.126764080.davem@davemloft.net> (raw)
In-Reply-To: <45BA331B.9090701@trustedcs.com>
From: Venkat Yekkirala <vyekkirala@trustedcs.com>
Date: Fri, 26 Jan 2007 10:58:03 -0600
> This patch is an incremental fix to the flow_cache_genid
> patch for selinux that breaks the build of 2.6.20-rc6 when
> xfrm is not configured.
>
> Signed-off-by: Venkat Yekkirala <vyekkirala@TrustedCS.com>
Applied, thanks for taking care of this.
prev parent reply other threads:[~2007-01-27 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 16:58 [PATCH 1/1] selinux: fix 2.6.20-rc6 build when no xfrm Venkat Yekkirala
2007-01-26 16:58 ` Venkat Yekkirala
2007-01-27 3:04 ` David Miller [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=20070126.190407.126764080.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chanson@trustedcs.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=sgrubb@redhat.com \
--cc=vyekkirala@trustedcs.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.