From: Guenter Roeck <linux@roeck-us.net>
To: "liuxp11@chinatelecom.cn" <liuxp11@chinatelecom.cn>,
wim <wim@linux-watchdog.org>, Tzung-Bi Shih <tzungbi@kernel.org>
Cc: linux-watchdog <linux-watchdog@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] watchdog: iTCO_wdg: Make code more clearly with macro definition
Date: Tue, 26 Apr 2022 01:35:18 -0700 [thread overview]
Message-ID: <275d7e40-a4bf-624a-6072-9750c6cb1ff0@roeck-us.net> (raw)
In-Reply-To: <2022042616273282549226@chinatelecom.cn>
On 4/26/22 01:27, liuxp11@chinatelecom.cn wrote:
> On 4/26/22 00:10, Liu Xinpeng wrote:
> > Using SET_NOIRQ_SYSTEM_SLEEP_PM_OPS reduces redundant code.
> >
> > Signed-off-by: Liu Xinpeng <liuxp11@chinatelecom.cn>
> > Reviewed-by: Tzung-Bi Shih <tzungbi@kernel.org>
> Also, Tzung-Bi never sent a Reviewed-by: tag. As with the other patches,
> this is completely inappropriate. Really, who gave you that idea ?
> You adding such tags without receiving them means we can never trust
> your patches again since you are making things up.
> Guenter
> -->Very sorry about this. I am not clearly when need to add "Reviewed-by: tag",
> Just expressing thanks.
>
If you get a Reviewed-by: tag for a patch, you keep it in the next version of
that patch unless there are substantial changes. You _never_ add one yourself.
Guenter
next prev parent reply other threads:[~2022-04-26 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 7:10 [PATCH v4 0/4] Some impovements about watchdog Liu Xinpeng
2022-04-26 7:10 ` [PATCH v4 1/4] watchdog: wdat_wdg: Using the existed function to check parameter timeout Liu Xinpeng
2022-04-26 8:05 ` Guenter Roeck
2022-04-26 7:10 ` [PATCH v4 2/4] watchdog: wdat_wdg: Stop watchdog when rebooting the system Liu Xinpeng
2022-04-26 7:10 ` [PATCH v4 3/4] watchdog: wdat_wdg: Stop watchdog when uninstalling module Liu Xinpeng
2022-04-26 7:10 ` [PATCH v4 4/4] watchdog: iTCO_wdg: Make code more clearly with macro definition Liu Xinpeng
2022-04-26 8:01 ` Guenter Roeck
[not found] ` <2022042616173226700718@chinatelecom.cn>
2022-04-26 8:27 ` Guenter Roeck
2022-04-26 8:12 ` Guenter Roeck
[not found] ` <2022042616273282549226@chinatelecom.cn>
2022-04-26 8:35 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 7:03 [PATCH v3 0/4] Some impovements about watchdog Liu Xinpeng
2022-04-26 7:03 ` [PATCH v4 4/4] watchdog: iTCO_wdg: Make code more clearly with macro definition Liu Xinpeng
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=275d7e40-a4bf-624a-6072-9750c6cb1ff0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=liuxp11@chinatelecom.cn \
--cc=tzungbi@kernel.org \
--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
all inboxes | Powered by JetHome®