From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Asmaa Mnebhi <asmaa@nvidia.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/9] i2c-mlxbf.c: bug fixes and new feature support
Date: Wed, 7 Sep 2022 23:37:46 +0200 [thread overview]
Message-ID: <YxkPKpPNXg8wEIDf@shikoro> (raw)
In-Reply-To: <CH2PR12MB38951B9B8F189E1B991A7950D7769@CH2PR12MB3895.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
> What did change since v1 and where did Khalil's Rev-by tags go?
>
> Khalil told me to remove the rev-by : ) since it is supposed to be reserved for the reviewers.
But he reviewed the patches, or? Which makes him a reviewer? I mean he
is the maintainer of the driver, so I basically a Rev-by from him.
> I will add it back and describe what has changed in my next set of patches.
So, you are planning a v3 already?
> As a note , this is what changed from v1->v2:
Cool, thank you for doing that.
> I think this is a bug fix because we have an i2c driver also in UEFI
> so we need this lock mechanism to avoid race conditions over acquiring
> the i2c bus. Not using this lock resulted in unexpected behavior.
OK, thank you!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-07 21:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 19:57 [PATCH v2 0/9] i2c-mlxbf.c: bug fixes and new feature support Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 1/9] i2c-mlxbf.c: Fix frequency calculation Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 2/9] i2c-mlxbf.c: remove IRQF_ONESHOT Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 3/9] i2c-mlxbf.c: incorrect base address passed during io write Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 4/9] i2c-mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 5/9] i2c-mlxbf.c: support lock mechanism Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 6/9] i2c-mlxbf.c: Update SPDX license Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 7/9] i2c-mlxbf: add multi slave functionality Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 8/9] i2c-mlxbf.c: support BlueField-3 SoC Asmaa Mnebhi
2022-08-22 19:57 ` [PATCH v2 9/9] i2c-mlxbf.c: Update binding devicetree Asmaa Mnebhi
2022-08-29 20:19 ` [PATCH v2 0/9] i2c-mlxbf.c: bug fixes and new feature support Wolfram Sang
2022-08-29 20:46 ` Asmaa Mnebhi
2022-09-07 21:37 ` Wolfram Sang [this message]
2022-09-07 21:42 ` Asmaa Mnebhi
2022-09-07 21:56 ` Wolfram Sang
2022-09-08 17:38 ` Asmaa Mnebhi
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=YxkPKpPNXg8wEIDf@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=asmaa@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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