From: Christoph Hellwig <hch@lst.de>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
kbusch@kernel.org, sagi@grimberg.me, linux@roeck-us.net,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-hwmon: don't return errors from nvme_hwmon_init
Date: Tue, 18 Oct 2022 17:16:25 +0200 [thread overview]
Message-ID: <20221018151625.GA22639@lst.de> (raw)
In-Reply-To: <20221018151421.jeqe2bi6nyj3afzi@mobilestation>
On Tue, Oct 18, 2022 at 06:14:21PM +0300, Serge Semin wrote:
> On Tue, Oct 18, 2022 at 04:58:08PM +0200, Christoph Hellwig wrote:
> > An NVMe controller works perfectly fine even when the hwmon
> > initialization fails. Stop returning errors from nvme_hwmon_init to
> > handle this case consistently.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> I was going to resubmit the series taking into account your resolution
> on this issue since patch #3 still needs to be resent. But you just
> submitted a fixup patch. Less worries to me. I'll resend patch #3
> separately then. Thanks.
I already have a locally rebased version, so don't bother.
next prev parent reply other threads:[~2022-10-18 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:58 [PATCH] nvme-hwmon: don't return errors from nvme_hwmon_init Christoph Hellwig
2022-10-18 15:14 ` Serge Semin
2022-10-18 15:16 ` Christoph Hellwig [this message]
2022-10-18 15:21 ` Serge Semin
2022-10-18 15:23 ` Christoph Hellwig
2022-10-18 15:25 ` Serge Semin
2022-10-18 15:15 ` Keith Busch
2022-10-18 15:23 ` Christoph Hellwig
2022-10-18 15:26 ` Keith Busch
2022-10-18 15:31 ` Christoph Hellwig
2022-10-18 15:31 ` Serge Semin
2022-10-18 15:38 ` Christoph Hellwig
2022-10-18 15:44 ` Serge Semin
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=20221018151625.GA22639@lst.de \
--to=hch@lst.de \
--cc=fancer.lancer@gmail.com \
--cc=kbusch@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 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.