From: Guenter Roeck <linux@roeck-us.net>
To: "andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"Sanil, Shruthi" <shruthi.sanil@intel.com>
Cc: "wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kris.pan@linux.intel.com" <kris.pan@linux.intel.com>,
"mgross@linux.intel.com" <mgross@linux.intel.com>,
"Thokala, Srikanth" <srikanth.thokala@intel.com>,
"Raja Subramanian,
Lakshmi Bai" <lakshmi.bai.raja.subramanian@intel.com>,
"Sangannavar,
Mallikarjunappa" <mallikarjunappa.sangannavar@intel.com>
Subject: Re: [PATCH v2 0/9] Intel Keem Bay WDT bug fixes
Date: Mon, 24 May 2021 06:42:57 -0700 [thread overview]
Message-ID: <88c07283-981c-b998-59a1-315f94f10f3e@roeck-us.net> (raw)
In-Reply-To: <YKuBppIuUHqkiMg4@smile.fi.intel.com>
On 5/24/21 3:36 AM, andriy.shevchenko@linux.intel.com wrote:
> On Mon, May 24, 2021 at 06:06:35AM +0000, Sanil, Shruthi wrote:
>> Hi Roeck,
>>
>> I have addressed your review comments in the v2 version of this patch series.
>> Could you please review?
>>
>> If no comments, can I get an Acked-by tag?
>> Thanks!
>
> First of all, do not top post!
>
>>> From: Sanil, Shruthi <shruthi.sanil@intel.com>
>>> Sent: Monday, May 17, 2021 11:20 PM
>
> AFAICS Guenter had reviewed (as you put his tags into commits). It means that
> maintainer will pickup patches when they feel it's a good time.
>
Yes, and the patches are queued in my own watchdog-next branch.
At this point we'll have to wait for the Wim to pick up the series.
Guenter
prev parent reply other threads:[~2021-05-24 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 17:49 [PATCH v2 0/9] Intel Keem Bay WDT bug fixes shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 1/9] watchdog: keembay: Update WDT pre-timeout during the initialization shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 2/9] watchdog: keembay: Upadate WDT pretimeout for every update in timeout shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 3/9] watchdog: keembay: Update pretimeout to zero in the TH ISR shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 4/9] watchdog: keembay: Clear either the TO or TH interrupt bit shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 5/9] watchdog: keembay: Remove timeout update in the WDT start function shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 6/9] watchdog: keembay: Removed timeout update in the TO ISR shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 7/9] watchdog: keembay: MACRO for WDT enable and disable values shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 8/9] watchdog: keembay: WDT SMC handler MACRO name update shruthi.sanil
2021-05-17 17:49 ` [PATCH v2 9/9] watchdog: keembay: Typo corrections and other blank operations shruthi.sanil
2021-05-24 6:06 ` [PATCH v2 0/9] Intel Keem Bay WDT bug fixes Sanil, Shruthi
2021-05-24 10:36 ` andriy.shevchenko
2021-05-24 13:42 ` Guenter Roeck [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=88c07283-981c-b998-59a1-315f94f10f3e@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=kris.pan@linux.intel.com \
--cc=lakshmi.bai.raja.subramanian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mgross@linux.intel.com \
--cc=shruthi.sanil@intel.com \
--cc=srikanth.thokala@intel.com \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).