From: Paul Moore <paul.moore@hp.com>
To: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Subject: [PATCH] Small cleanup for 2.6.24 and a git tree test
Date: Wed, 12 Sep 2007 15:29:31 -0400 [thread overview]
Message-ID: <20070912192305.18318.11911.stgit@flek.americas.hpqcorp.net> (raw)
The cleanup patch is pretty trivial and is explained in it's own email, but
essentially it is just moving similar code into a new function and then
modifying the original functions to call the newly created function.
The new and exciting thing is that I actually decided I should probably know
how to do more than just clone git trees, which means you can get this patch
by pulling from the brand spankin' new labeled networking git tree. The tree
looks okay to me but it's possible I munged something, if that is the case let
me know and I'll try to fix it ... I'd like to get this working at some point.
* git://git.infradead.org/users/pcmoore/lblnet-2.6
Thanks.
--
paul moore
linux security @ hp
next reply other threads:[~2007-09-12 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 19:29 Paul Moore [this message]
2007-09-12 19:29 ` [PATCH] CIPSO: remove duplicated code in the cipso_v4_*_getattr() functions Paul Moore
2007-09-16 4:45 ` David Miller
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=20070912192305.18318.11911.stgit@flek.americas.hpqcorp.net \
--to=paul.moore@hp.com \
--cc=netdev@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
/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