From: Andrew Morton <akpm@linux-foundation.org>
To: Wan ZongShun <mcuos.com@gmail.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
LKML <linux-kernel@vger.kernel.org>,
rtc-linux <rtc-linux@googlegroups.com>
Subject: Re: [PATCH 3/3] RTC/nuc900: fix build warning
Date: Wed, 30 Jun 2010 12:42:42 -0700 [thread overview]
Message-ID: <20100630124242.fc966300.akpm@linux-foundation.org> (raw)
In-Reply-To: <4C231FF5.9090602@gmail.com>
On Thu, 24 Jun 2010 17:05:57 +0800
Wan ZongShun <mcuos.com@gmail.com> wrote:
> Firstly,I am sorry for this patch, because I omit the warning
> when I submit 'nuc900-rtc-change-the-waiting-for-device-ready-implement.patch'.
> so I have to send a patch to fix it.
When fixing a warning or build error, pelase quote the compiler
messages in the changelog so we can see what got fixed.
> It is reported by Nuvoton test guys, thanks.
I don't know who that is. Perhaps use the Reported-by: tag here?
> Signed-off-by: Wan ZongShun <mcuos.com@gmail.com>
>
> ---
> drivers/rtc/rtc-nuc900.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/rtc/rtc-nuc900.c b/drivers/rtc/rtc-nuc900.c
> index 0267ea3..62de66a 100644
> --- a/drivers/rtc/rtc-nuc900.c
> +++ b/drivers/rtc/rtc-nuc900.c
> @@ -85,7 +85,7 @@ static irqreturn_t nuc900_rtc_interrupt(int irq, void *_rtc)
>
> static int *check_rtc_access_enable(struct nuc900_rtc *nuc900_rtc)
> {
> - unsigned int i, timeout = 0x1000;
> + unsigned int timeout = 0x1000;
> __raw_writel(INIRRESET, nuc900_rtc->rtc_reg + REG_RTC_INIR);
Well it's pretty obvious what the warning was this time.
prev parent reply other threads:[~2010-06-30 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 9:05 [PATCH 3/3] RTC/nuc900: fix build warning Wan ZongShun
2010-06-30 19:42 ` Andrew Morton [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=20100630124242.fc966300.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mcuos.com@gmail.com \
--cc=rtc-linux@googlegroups.com \
/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.