From: Greg Ungerer <gerg@snapgear.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: geert@linux-m68k.org, gerg@uclinux.org, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] m68k: fix compiler warning by properly inlining flat_set_persistent()
Date: Mon, 30 Apr 2012 13:42:56 +1000 [thread overview]
Message-ID: <4F9E0A40.40602@snapgear.com> (raw)
In-Reply-To: <1335622384-4806-1-git-send-email-elezegarcia@gmail.com>
Hi Ezequiel,
On 29/04/12 00:13, Ezequiel Garcia wrote:
> This patch removes the following warning:
> fs/binfmt_flat.c:752: warning: unused variable 'persistent'.
> There is neither functionality change, nor extra code generated.
>
> Signed-off-by: Ezequiel Garcia<elezegarcia@gmail.com>
Looks good, thanks. I'll push that into the for-next branch
of the m68knommu git tree.
Regards
Greg
> arch/m68k/include/asm/flat.h | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/arch/m68k/include/asm/flat.h b/arch/m68k/include/asm/flat.h
> index a0e2907..f9454b8 100644
> --- a/arch/m68k/include/asm/flat.h
> +++ b/arch/m68k/include/asm/flat.h
> @@ -11,6 +11,11 @@
> #define flat_get_addr_from_rp(rp, relval, flags, p) get_unaligned(rp)
> #define flat_put_addr_at_rp(rp, val, relval) put_unaligned(val,rp)
> #define flat_get_relocate_addr(rel) (rel)
> -#define flat_set_persistent(relval, p) 0
> +
> +static inline int flat_set_persistent(unsigned long relval,
> + unsigned long *persistent)
> +{
> + return 0;
> +}
>
> #endif /* __M68KNOMMU_FLAT_H__ */
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2012-04-30 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 14:13 [PATCH] m68k: fix compiler warning by properly inlining flat_set_persistent() Ezequiel Garcia
2012-04-30 3:42 ` Greg Ungerer [this message]
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=4F9E0A40.40602@snapgear.com \
--to=gerg@snapgear.com \
--cc=elezegarcia@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@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