From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: yexingchen116@gmail.com
Cc: pmladek@suse.com, rostedt@goodmis.org, senozhatsky@chromium.org,
andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
linux-kernel@vger.kernel.org,
ye xingchen <ye.xingchen@zte.com.cn>
Subject: Re: [PATCH linux-next] vsprintf: replace in_irq() with in_hardirq()
Date: Tue, 11 Oct 2022 12:07:57 +0900 [thread overview]
Message-ID: <Y0TeDdI9ncrFnqgr@google.com> (raw)
In-Reply-To: <20221011024831.322799-1-ye.xingchen@zte.com.cn>
On (22/10/11 02:48), yexingchen116@gmail.com wrote:
> Replace the obsolete and ambiguos macro in_irq() with new
> macro in_hardirq().
>
> Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
Per 15115830c8875 in_irq() is "obsolete".
FWIW,
Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
next prev parent reply other threads:[~2022-10-11 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 2:48 [PATCH linux-next] vsprintf: replace in_irq() with in_hardirq() yexingchen116
2022-10-11 3:07 ` Sergey Senozhatsky [this message]
2022-10-11 9:02 ` Petr Mladek
2022-10-18 14:31 ` Petr Mladek
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=Y0TeDdI9ncrFnqgr@google.com \
--to=senozhatsky@chromium.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=ye.xingchen@zte.com.cn \
--cc=yexingchen116@gmail.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.