From: Erik Kline <ekline@ekline.com>
To: linux-kernel@vger.kernel.org
Subject: [module/patch] optional /proc/patches ??
Date: Mon, 11 Mar 2002 13:24:15 -0800 [thread overview]
Message-ID: <200203112124.g2BLOFP01544@minerva.ekline.com> (raw)
All,
I was wondering whether something like a /proc/patches might be useful. This
could help list patches applied to a kernel such that "uname -a" and "cat
/proc/patches" provides some good information about the kernel, especially
stock kernels from distributions. I was able to work up a quick module
available at the link below. NOTE: I couldn't solve how to add entries fo a
patchlist structure using regular context diffs, but ed diffs work just
great. More information in the README attached. I'd very much appreciate any
feedback on whether this is useful and how it should actually be implemented,
if at all. Please note that my only access to lkml traffic is via Kernel
Traffic so I would appreciate being Cc'ed.
Thanks all,
-Erik (humble linux aficionado)
[patchlist module]
http://ekline.com/linux/patchlist-0.0.1.tar.gz
next reply other threads:[~2002-03-11 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 21:24 Erik Kline [this message]
2002-03-12 11:42 ` Ville Herva
2002-03-14 0:46 David Oleszkiewicz
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=200203112124.g2BLOFP01544@minerva.ekline.com \
--to=ekline@ekline.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®