From: Tommy Lin <tommy.lin.1101@gmail.com>
To: "'Anton Vorontsov'" <cbouatmailru@gmail.com>
Cc: "'Tommy Lin'" <tommy.lin.1101@gmail.com>,
"'Wim Van Sebroeck'" <wim@iguana.be>,
<linux-watchdog@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Lin, Mac" <Mac.Lin@caviumnetworks.com>
Subject: RE: [PATCH 2/2] watchdog: mpcore_wdt Add reload value setting for CNS3xxx hardware
Date: Fri, 8 Jul 2011 15:28:05 +0800 [thread overview]
Message-ID: <CE02B12FB1A04C32A691217E8DA7B69E@starsemi.com> (raw)
In-Reply-To: <20110706193457.GA20378@oksana.dev.rtsoft.ru>
I submit another patch that can solve the warning.
[PATCH 1/2] arch: arm: Correct the dependency of HAVE_ARM_TWD
This patch should after above one.
Should I submit another patch or just attach it in this thread?
Best regards,
Tommy Lin
-----Original Message-----
From: Anton Vorontsov [mailto:cbouatmailru@gmail.com]
Sent: Thursday, July 07, 2011 3:35 AM
To: Lin, Tommy
Cc: Tommy Lin; Wim Van Sebroeck; linux-watchdog@vger.kernel.org;
linux-kernel@vger.kernel.org; Lin, Mac
Subject: Re: [PATCH 2/2] watchdog: mpcore_wdt Add reload value setting for
CNS3xxx hardware
On Wed, Jul 06, 2011 at 07:54:49AM -0700, Lin, Tommy wrote:
> I am thinking that mpcore_wdt should work even SMP is not turned on. Did
the dependency
> is neccesarry between mpcore_wdt and SMP? If CPU1 is turned off the
mpcore_wdt worked
> well with CPU0 only.
No doubt that the watchdog itself works fine. :-) But the point is
that the patch yields a warning, so it should be fixed before merging.
Thanks,
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
prev parent reply other threads:[~2011-07-08 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 12:05 Tommy Lin
2011-07-05 14:05 ` Anton Vorontsov
2011-07-06 10:05 ` Tommy Lin
2011-07-06 11:16 ` Anton Vorontsov
2011-07-06 11:28 ` Anton Vorontsov
2011-07-06 11:46 ` Anton Vorontsov
2011-07-06 14:54 ` Lin, Tommy
2011-07-06 19:34 ` Anton Vorontsov
2011-07-08 7:28 ` Tommy Lin [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=CE02B12FB1A04C32A691217E8DA7B69E@starsemi.com \
--to=tommy.lin.1101@gmail.com \
--cc=Mac.Lin@caviumnetworks.com \
--cc=cbouatmailru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=tommy.lin@caviumnetworks.com \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®