public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Quan Nguyen <quan@os.amperecomputing.com>
To: corey@minyard.net
Cc: Cosmo Chou <chou.cosmo@gmail.com>,
	openipmi-developer@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, cosmo.chou@quantatw.com,
	potin.lai@quantatw.com, minyard@acm.org
Subject: Re: [PATCH] ipmi: ssif_bmc: Move smbus_cmd assignment after cleanup
Date: Mon, 6 Jan 2025 09:32:22 +0700	[thread overview]
Message-ID: <344a5d68-bcb5-46c1-ba58-8cd95c3ac4ee@os.amperecomputing.com> (raw)
In-Reply-To: <Z3ffxfF6eEtvqOxx@mail.minyard.net>



On 03/01/2025 20:01, Corey Minyard wrote:
> On Fri, Jan 03, 2025 at 10:44:46AM +0700, Quan Nguyen wrote:
>>
>>
>> On 01/01/2025 23:54, Cosmo Chou wrote:
>>> Move smbus_cmd assignment to the end of process_smbus_cmd() to ensure
>>> the new command is not lost when complete_response() is triggered.
>>>
>>
>> Thanks Cosmo for the catch.
>>
>> And, IMHO, the root cause is the memset() on part buffer called in
>> complete_response() is not quite correct. In the current implementation, the
>> complete_response() should only be called when the READ is completed, ie:
>> only on I2C_SLAVE_STOP of READ transaction, otherwise all the info of
>> current on-going request will be mistakenly cleared as in this case.
>>
>> This patch is good and I wonder if we can make this a bit further as below?
> 
> Yes, this is probably more future proof.
> 
> Can you send me a formal patch, with a "Found-by:" for Cosmo?  I'll
> replace Cosmo's patch.
> 

Thanks Corey,

Will send the formal patch later.

Thanks,
-- Quan

      reply	other threads:[~2025-01-06  2:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-01 16:54 [PATCH] ipmi: ssif_bmc: Move smbus_cmd assignment after cleanup Cosmo Chou
2025-01-03  3:20 ` Corey Minyard
2025-01-03  3:49   ` Quan Nguyen
2025-01-03  3:44 ` Quan Nguyen
2025-01-03 13:01   ` Corey Minyard
2025-01-06  2:32     ` Quan Nguyen [this message]

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=344a5d68-bcb5-46c1-ba58-8cd95c3ac4ee@os.amperecomputing.com \
    --to=quan@os.amperecomputing.com \
    --cc=chou.cosmo@gmail.com \
    --cc=corey@minyard.net \
    --cc=cosmo.chou@quantatw.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=potin.lai@quantatw.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