From: Christoph Hellwig <hch@lst.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] nvme: host: hwmon: constify pointers to hwmon_channel_info
Date: Tue, 11 Apr 2023 08:09:00 +0200 [thread overview]
Message-ID: <20230411060900.GD18527@lst.de> (raw)
In-Reply-To: <20230407145845.79557-1-krzysztof.kozlowski@linaro.org>
Thanks,
applied to nvme-6.4 with a trivial whitespace fix.
next prev parent reply other threads:[~2023-04-11 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 14:58 [PATCH] nvme: host: hwmon: constify pointers to hwmon_channel_info Krzysztof Kozlowski
2023-04-11 6:09 ` Christoph Hellwig [this message]
2023-04-11 6:10 ` Christoph Hellwig
2023-04-11 6:11 ` Krzysztof Kozlowski
2023-04-12 6:48 ` Christoph Hellwig
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=20230411060900.GD18527@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=jdelvare@suse.com \
--cc=kbusch@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=sagi@grimberg.me \
/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