From: Petr Vorel <petr.vorel@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] pinctrl: aspeed: fix null dereference in debug
Date: Thu, 3 Mar 2022 06:52:01 +0100 [thread overview]
Message-ID: <YiBXgV4mVYiJ2MxQ@pevik> (raw)
In-Reply-To: <tencent_BBDF8D2C89ECC450F3349D6E46F8EAF87F0A@qq.com>
Hi Weiguo,
LGTM.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
prev parent reply other threads:[~2022-03-03 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 19:30 [PATCH] pinctrl: aspeed: fix null dereference in debug Weiguo Li
2022-03-02 0:09 ` Andrew Jeffery
2022-03-02 7:12 ` [PATCH v2] " Weiguo Li
2022-03-04 9:04 ` Weiguo Li
2022-03-03 5:52 ` Petr Vorel [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=YiBXgV4mVYiJ2MxQ@pevik \
--to=petr.vorel@gmail.com \
--cc=linux-aspeed@lists.ozlabs.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