From: Jeff Garzik <jgarzik@pobox.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH] gianfar driver: eliminate compiler warnings and unnecessary macros
Date: Tue, 04 Dec 2007 15:15:08 -0500 [thread overview]
Message-ID: <4755B54C.60504@pobox.com> (raw)
In-Reply-To: <20071202051245.8918.24063.stgit@trillian.secretlab.ca>
Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
>
> This patch eliminates the warning of unused return values when the driver
> registers it sysfs files. Now the driver will print an error if it is
> unable to register the sysfs files.
>
> It also eliminates the macros used to wrap the DEVICE_ATTR macro and the
> device_create_file function call. The macros don't reduce the number of
> lines of source code in the file and the name munging makes is so that
> cscope and friends don't see the references to the functions. It's better
> to just call the kernel API directly.
>
> While we're at it, the DEVICE_ATTR instances have been moved down to
> be grouped with the functions they depend on.
>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
>
> drivers/net/gianfar_sysfs.c | 50 ++++++++++++++++++++++---------------------
> 1 files changed, 25 insertions(+), 25 deletions(-)
applied #upstream
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
galak@kernel.crashing.org, afleming@freescale.com
Subject: Re: [PATCH] gianfar driver: eliminate compiler warnings and unnecessary macros
Date: Tue, 04 Dec 2007 15:15:08 -0500 [thread overview]
Message-ID: <4755B54C.60504@pobox.com> (raw)
In-Reply-To: <20071202051245.8918.24063.stgit@trillian.secretlab.ca>
Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
>
> This patch eliminates the warning of unused return values when the driver
> registers it sysfs files. Now the driver will print an error if it is
> unable to register the sysfs files.
>
> It also eliminates the macros used to wrap the DEVICE_ATTR macro and the
> device_create_file function call. The macros don't reduce the number of
> lines of source code in the file and the name munging makes is so that
> cscope and friends don't see the references to the functions. It's better
> to just call the kernel API directly.
>
> While we're at it, the DEVICE_ATTR instances have been moved down to
> be grouped with the functions they depend on.
>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
>
> drivers/net/gianfar_sysfs.c | 50 ++++++++++++++++++++++---------------------
> 1 files changed, 25 insertions(+), 25 deletions(-)
applied #upstream
next prev parent reply other threads:[~2007-12-04 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 5:12 [PATCH] gianfar driver: eliminate compiler warnings and unnecessary macros Grant Likely
2007-12-04 20:15 ` Jeff Garzik [this message]
2007-12-04 20:15 ` Jeff Garzik
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=4755B54C.60504@pobox.com \
--to=jgarzik@pobox.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@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 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.