From: Quan Nguyen <quan@os.amperecomputing.com>
To: Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
Thang Nguyen <thang@os.amperecomputing.com>
Subject: Re: [PATCH] docs: i2c: slave-interface: return errno when handle I2C_SLAVE_WRITE_REQUESTED
Date: Thu, 29 Sep 2022 15:07:23 +0700 [thread overview]
Message-ID: <094d7641-daf3-dbda-3603-8b4f7f640e38@os.amperecomputing.com> (raw)
In-Reply-To: <YzSjaVQUm/B4Jtwf@shikoro>
Thank you, Wolfram, for the review and the wording fixes :-)
- Quan
On 29/09/2022 02:41, Wolfram Sang wrote:
> On Thu, Sep 15, 2022 at 10:54:40AM +0700, Quan Nguyen wrote:
>> In case backend is not ready, ie: fail to wakeup or initialization, on
>> the returning of the I2C_SLAVE_WRITE_REQUESTED event, bus driver should
>> aware the backend status and might auto sending NACK on the next
>> incoming bytes for I2C master to retry.
>>
>> Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
>> Links:https://lore.kernel.org/linux-arm-kernel/556fa9e1-c54b-8370-4de7-c2d3ec7d6906@os.amperecomputing.com/
>
> Sorry for the delay. I made some wording more precise and applied it to
> for-next. So, we can use it right for next merge window, if needed.
>
> Thank you for suggesting this and for your patience!
>
prev parent reply other threads:[~2022-09-29 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 3:54 [PATCH] docs: i2c: slave-interface: return errno when handle I2C_SLAVE_WRITE_REQUESTED Quan Nguyen
2022-09-28 19:41 ` Wolfram Sang
2022-09-29 8:07 ` 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=094d7641-daf3-dbda-3603-8b4f7f640e38@os.amperecomputing.com \
--to=quan@os.amperecomputing.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=thang@os.amperecomputing.com \
--cc=wsa@kernel.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