From: "Cédric Le Goater" <clg@kaod.org>
To: Karthikeyan Pasupathi <pkarthikeyan1509@gmail.com>,
<peter.maydell@linaro.org>, <andrew@aj.id.au>, <joel@jms.id.au>,
<qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v1] Added TMP421 type sensor's support in tiogapass
Date: Tue, 7 Mar 2023 11:28:20 +0100 [thread overview]
Message-ID: <ddf527c7-20e2-0eb8-0105-2b1c4ef653eb@kaod.org> (raw)
In-Reply-To: <20230307101913.3585785-1-pkarthikeyan1509@gmail.com>
Hello Karthikeyan,
On 3/7/23 11:19, Karthikeyan Pasupathi wrote:
> Added TMP421 type sensor support in tiogapass platform.
>
> Tested: Tested and verified in tiogapass platform.
>
> Signed-off-by: Karthikeyan Pasupathi <pkarthikeyan1509@gmail.com>
> ---
> hw/arm/aspeed.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/arm/aspeed.c b/hw/arm/aspeed.c
> index e985ce85e5..c1843693fa 100644
> --- a/hw/arm/aspeed.c
> +++ b/hw/arm/aspeed.c
> @@ -545,7 +545,7 @@ static void tiogapass_bmc_i2c_init(AspeedMachineState *bmc)
> /* TMP421 */
> i2c_slave_create_simple(aspeed_i2c_get_bus(&soc->i2c, 8), "tmp421", 0x1f);
> i2c_slave_create_simple(aspeed_i2c_get_bus(&soc->i2c, 6), "tmp421", 0x4f);
> - i2c_slave_create_simple(aspeed_i2c_get_bus(&soc->i2c, 6), "tmp421", 0x4e);
> + i2c_slave_create_simple(aspeed_i2c_get_bus(&soc->i2c, 6), "tmp421", 0x4e);
> }
>
> static void create_pca9552(AspeedSoCState *soc, int bus_id, int addr)
This patch is only removing a white space at the end of a line. Is that expected ?
If so, the commit log should be changed.
Thanks,
C.
next prev parent reply other threads:[~2023-03-07 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 10:19 [PATCH v1] Added TMP421 type sensor's support in tiogapass Karthikeyan Pasupathi
2023-03-07 10:28 ` karthikeyan Pasupathi
2023-03-07 10:28 ` Cédric Le Goater [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-07 10:33 Karthikeyan Pasupathi
2023-03-07 13:53 ` Cédric Le Goater
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=ddf527c7-20e2-0eb8-0105-2b1c4ef653eb@kaod.org \
--to=clg@kaod.org \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=pkarthikeyan1509@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).