From: Markus Elfring <Markus.Elfring@web.de>
To: Liao Chang <liaochang1@huawei.com>,
linux-i2c@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com, kernel@pengutronix.de,
linux-imx@nxp.com, Andi Shyti <andi.shyti@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>, Asmaa Mnebhi <asmaa@nvidia.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
George Cherian <gcherian@marvell.com>,
Khalil Blaiech <kblaiech@nvidia.com>,
Loic Poulain <loic.poulain@linaro.org>,
Ray Jui <rjui@broadcom.com>, Robert Foss <rfoss@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Scott Branden <sbranden@broadcom.com>,
Shawn Guo <shawnguo@kernel.org>,
Yicong Yang <yangyicong@hisilicon.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/9] i2c: mlxbf: Use dev_err_probe in probe function
Date: Tue, 8 Aug 2023 12:32:48 +0200 [thread overview]
Message-ID: <10af2aad-e55d-47bf-bd6b-2bf45eb90eef@web.de> (raw)
In-Reply-To: <20230808012954.1643834-3-liaochang1@huawei.com>
…
> so that the printed messge includes …
How do you think about to avoid another typo in similar wordings?
Regards,
Markus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-08 10:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 1:29 [PATCH v3 0/9] Use dev_err_probe in i2c probe function Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 1:29 ` [PATCH v3 1/9] i2c: bcm2835: Use dev_err_probe in " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 9:37 ` Markus Elfring
2023-08-08 11:31 ` Andi Shyti
2023-08-08 11:31 ` Andi Shyti
2023-08-08 1:29 ` [PATCH v3 2/9] i2c: mlxbf: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 8:36 ` Krzysztof Kozlowski
2023-08-08 8:36 ` Krzysztof Kozlowski
2023-08-08 11:29 ` Andi Shyti
2023-08-08 11:29 ` Andi Shyti
2023-08-08 11:31 ` Krzysztof Kozlowski
2023-08-08 11:31 ` Krzysztof Kozlowski
2023-08-08 11:47 ` Andi Shyti
2023-08-08 11:47 ` Andi Shyti
2023-08-08 15:55 ` Krzysztof Kozlowski
2023-08-08 15:55 ` Krzysztof Kozlowski
2023-08-09 8:02 ` Andi Shyti
2023-08-09 8:02 ` Andi Shyti
2023-08-08 10:32 ` Markus Elfring [this message]
2023-08-08 1:29 ` [PATCH v3 3/9] i2c: xlp9xx: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 8:36 ` Krzysztof Kozlowski
2023-08-08 8:36 ` Krzysztof Kozlowski
2023-08-08 1:29 ` [PATCH v3 4/9] i2c: hisi: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 8:36 ` Krzysztof Kozlowski
2023-08-08 8:36 ` Krzysztof Kozlowski
2023-08-08 1:29 ` [PATCH v3 5/9] i2c: qcom-cci: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-10 15:06 ` Bjorn Andersson
2023-08-10 15:06 ` Bjorn Andersson
2023-08-08 1:29 ` [PATCH v3 6/9] i2c: pxa: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 1:29 ` [PATCH v3 7/9] i2c: dln2: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 1:29 ` [PATCH v3 8/9] i2c: imx-lpi2c: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 8:37 ` Krzysztof Kozlowski
2023-08-08 8:37 ` Krzysztof Kozlowski
2023-08-08 1:29 ` [PATCH v3 9/9] i2c: synquacer: " Liao Chang
2023-08-08 1:29 ` Liao Chang
2023-08-08 8:37 ` Krzysztof Kozlowski
2023-08-08 8:37 ` Krzysztof Kozlowski
2023-08-09 19:21 ` Andi Shyti
2023-08-09 19:21 ` Andi Shyti
2023-08-10 2:33 ` Liao, Chang
2023-08-10 2:33 ` Liao, Chang
2023-08-10 8:10 ` Andi Shyti
2023-08-10 8:10 ` Andi Shyti
2023-08-10 8:19 ` [PATCH v3 0/9] Use dev_err_probe in i2c " Andi Shyti
2023-08-10 8:19 ` Andi Shyti
2023-08-14 15:16 ` Wolfram Sang
2023-08-14 15:16 ` Wolfram Sang
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=10af2aad-e55d-47bf-bd6b-2bf45eb90eef@web.de \
--to=markus.elfring@web.de \
--cc=aisheng.dong@nxp.com \
--cc=andi.shyti@kernel.org \
--cc=ardb@kernel.org \
--cc=asmaa@nvidia.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=festevam@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=gcherian@marvell.com \
--cc=kblaiech@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=loic.poulain@linaro.org \
--cc=rfoss@kernel.org \
--cc=rjui@broadcom.com \
--cc=s.hauer@pengutronix.de \
--cc=sbranden@broadcom.com \
--cc=shawnguo@kernel.org \
--cc=yangyicong@hisilicon.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.