From: Nick Bowler <nbowler@elliptictech.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
Lucas De Marchi <lucas.demarchi@profusion.mobi>
Subject: Re: [PATCH] modules: sysfs - export: taint, address, size
Date: Mon, 9 Jan 2012 10:52:56 -0500 [thread overview]
Message-ID: <20120109155256.GA2288@elliptictech.com> (raw)
In-Reply-To: <1325951076.860.2.camel@mop>
On 2012-01-07 16:44 +0100, Kay Sievers wrote:
> From: Kay Sievers <kay.sievers@vrfy.org>
> Subject: modules: sysfs - export taint, address, size
>
> Recent tools do not use /proc to retrieve module information. A few values
> are currently missing from sysfs.
[...]
> @@ -907,10 +927,8 @@ static ssize_t show_refcnt(struct module
> return sprintf(buffer, "%u\n", module_refcount(mk->mod));
> }
>
> -static struct module_attribute refcnt = {
> - .attr = { .name = "refcnt", .mode = 0444 },
> - .show = show_refcnt,
> -};
> +static struct module_attribute refcnt =
> + __ATTR(refcnt, 0444, show_refcnt, NULL);
This change seems unrelated to the patch description, and is not
mentioned in the changelog. Several instances of this.
[...]
> static struct module_attribute *modinfo_attrs[] = {
> &modinfo_version,
> &modinfo_srcversion,
> - &initstate,
> + &module_initstate,
Another unrelated change?
> &module_uevent,
> + &module_address,
> + &module_size,
> + &module_taint,
You've forgotten to update Documentation/ABI to describe these new
attributes.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2012-01-09 16:02 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
2012-01-11 1:56 ` Lucas De Marchi
2012-01-09 15:52 ` Nick Bowler [this message]
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=20120109155256.GA2288@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=rusty@rustcorp.com.au \
/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.