From: yjin <yanjiang.jin@windriver.com>
To: Guenter Roeck <linux@roeck-us.net>, <wim@iguana.be>
Cc: <jinyanjiang@gmail.com>, <linux-watchdog@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] watchdog: imx2_wdt: use new_timeout value to override the old
Date: Thu, 20 Jul 2017 11:22:16 +0800 [thread overview]
Message-ID: <72fd5906-49f3-9e87-f6a9-2757103e7535@windriver.com> (raw)
In-Reply-To: <b433d1ff-0d89-fbd9-3e2d-04bd278371fb@roeck-us.net>
On 2017年07月20日 11:18, Guenter Roeck wrote:
> On 07/19/2017 07:45 PM, yanjiang.jin@windriver.com wrote:
>> From: Yanjiang Jin <yanjiang.jin@windriver.com>
>>
>> Without this patch we couldn't change the timeout value of imx2_wdt.
>>
>> Signed-off-by: Yanjiang Jin <yanjiang.jin@windriver.com>
>> ---
>> drivers/watchdog/imx2_wdt.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c
>> index 4874b0f..6cfeee6 100644
>> --- a/drivers/watchdog/imx2_wdt.c
>> +++ b/drivers/watchdog/imx2_wdt.c
>> @@ -178,6 +178,9 @@ static int imx2_wdt_set_timeout(struct
>> watchdog_device *wdog,
>> regmap_update_bits(wdev->regmap, IMX2_WDT_WCR, IMX2_WDT_WCR_WT,
>> WDOG_SEC_TO_COUNT(new_timeout));
>> +
>> + wdog->timeout = new_timeout;
>> +
>
> I must be missing something. That very same code is already in line 177,
> added with commit 30dd4a8f08b57 ("watchdog: imx2_wdt: also set
> wdog->timeout
> to new_timeout") back in 2015.
>
> Did you see this in an older kernel, maybe ?
Oh, I missed this. I did use the older kernel to validate it. Thanks for
your reminder, please ignore my patch.
Thanks again!
Regards!
Yanjiang
>
> Guenter
prev parent reply other threads:[~2017-07-20 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 2:45 yanjiang.jin
2017-07-20 3:18 ` Guenter Roeck
2017-07-20 3:22 ` yjin [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=72fd5906-49f3-9e87-f6a9-2757103e7535@windriver.com \
--to=yanjiang.jin@windriver.com \
--cc=jinyanjiang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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®