From: Corey Minyard <minyard@acm.org>
To: Yuchen Zhang <zhangyuchen.lcr@bytedance.com>
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, qi.zheng@linux.dev
Subject: Re: [PATCH 1/3] ipmi: fix msg stack when IPMI is disconnected
Date: Sat, 8 Oct 2022 06:49:02 -0500 [thread overview]
Message-ID: <Y0FjriRusk0H4Fxp@minyard.net> (raw)
In-Reply-To: <28367829-10e1-1a74-5572-ba01b8f8b716@bytedance.com>
On Sat, Oct 08, 2022 at 09:36:16AM +0800, Yuchen Zhang wrote:
> > Also, the following is in start_kcs_transaction():
> >
> > if ((kcs->state != KCS_IDLE) && (kcs->state != KCS_HOSED)) {
> > dev_warn(kcs->io->dev, "KCS in invalid state %d\n", kcs->state);
> > return IPMI_NOT_IN_MY_STATE_ERR;
> > }
> >
> > You probably need to remove the (kcs->state != KCS_HOSED) part of this
> > now. Would you agree?
> >
> > -corey
> >
> I agree. KCS_HOSED state should be an invalid state.
Can you make this change, run a quick test, and re-submit this one
patch? With that, I can include this.
Thanks,
-corey
next prev parent reply other threads:[~2022-10-08 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 9:26 [PATCH 0/3] ipmi: fix ipmi memleak and unload bug Zhang Yuchen
2022-10-07 9:26 ` [PATCH 1/3] ipmi: fix msg stack when IPMI is disconnected Zhang Yuchen
2022-10-07 19:43 ` Corey Minyard
2022-10-08 1:36 ` Yuchen Zhang
2022-10-08 11:49 ` Corey Minyard [this message]
2022-10-09 0:53 ` Yuchen Zhang
2022-10-07 9:26 ` [PATCH 2/3] ipmi: fix long wait in unload when IPMI disconnect Zhang Yuchen
2022-10-07 19:48 ` Corey Minyard
2022-10-07 9:26 ` [PATCH 3/3] ipmi: fix memleak when unload ipmi driver Zhang Yuchen
2022-10-07 19:51 ` Corey Minyard
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=Y0FjriRusk0H4Fxp@minyard.net \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=qi.zheng@linux.dev \
--cc=zhangyuchen.lcr@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome