All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Jon Masters <jcm@redhat.com>,
	linux-kernel@vger.kernel.org,
	Lucas De Marchi <lucas.demarchi@profusion.mobi>
Subject: Re: [PATCH] modules: sysfs - export: taint, address, size
Date: Wed, 11 Jan 2012 10:24:26 +1030	[thread overview]
Message-ID: <878vlf6rm5.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1326214063.1038.1.camel@mop>

On Tue, 10 Jan 2012 17:47:43 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> From: Kay Sievers <kay.sievers@vrfy.org>
> Subject: modules: sysfs - export: taint, coresize, initsize
> 
> Recent tools do not want to use /proc to retrieve module information. A few
> values are currently missing from sysfs to replace the information available
> in /proc/modules.
> 
> This adds /sys/module/*/{coresize,initsize,taint} attributes.
> 
> TAINT_PROPRIETARY_MODULE (P) and TAINT_OOT_MODULE (O) flags are both always
> shown now, and do no longer exclude each other, also in /proc/modules.
> 
> Replace the open-coded sysfs attribute initializers with the __ATTR() macro.
> 
> Add the new attributes to Documentation/ABI.
> 
> Cc: Lucas De Marchi <lucas.demarchi@profusion.mobi>
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>

Thanks, applied.

Cheers,
Rusty.
PS.  You could have split this into four separate patches, like the
     pedants wanted, and got more gititude!
PPS.  I'm so glad you didn't.

  reply	other threads:[~2012-01-11  1:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 15:44 [PATCH] modules: sysfs - export: taint, address, size Kay Sievers
2012-01-09  7:27 ` Rusty Russell
2012-01-09 12:44   ` Kay Sievers
2012-01-09 18:40     ` Randy Dunlap
2012-01-09 22:44     ` Rusty Russell
2012-01-10 16:47       ` Kay Sievers
2012-01-10 23:54         ` Rusty Russell [this message]
2012-01-11  1:56           ` Lucas De Marchi
2012-01-09 15:52 ` Nick Bowler
2012-01-09 23:07 ` Greg KH

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=878vlf6rm5.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=jcm@redhat.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    /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.