From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Kamal Dasu <kamal.dasu@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Andi Shyti <andi.shyti@kernel.org>, Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH] i2c: brcmstb: Add support for atomic transfers
Date: Mon, 9 Oct 2023 13:41:24 -0700 [thread overview]
Message-ID: <bec3b967-f287-4a99-9c79-3b949a31c296@broadcom.com> (raw)
In-Reply-To: <20231006144117.4079796-1-m.szyprowski@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On 10/6/23 07:41, Marek Szyprowski wrote:
> Add support for atomic transfers using polling mode with interrupts
> intentionally disabled to get rid of the warning introduced by commit
> 63b96983a5dd ("i2c: core: introduce callbacks for atomic transfers")
> during system reboot and power-off.
Is there an existing system that you have access to which needs atomic
transfer support, or is this a forward looking change?
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Kamal Dasu <kamal.dasu@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Andi Shyti <andi.shyti@kernel.org>, Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH] i2c: brcmstb: Add support for atomic transfers
Date: Mon, 9 Oct 2023 13:41:24 -0700 [thread overview]
Message-ID: <bec3b967-f287-4a99-9c79-3b949a31c296@broadcom.com> (raw)
In-Reply-To: <20231006144117.4079796-1-m.szyprowski@samsung.com>
[-- Attachment #1.1: Type: text/plain, Size: 562 bytes --]
On 10/6/23 07:41, Marek Szyprowski wrote:
> Add support for atomic transfers using polling mode with interrupts
> intentionally disabled to get rid of the warning introduced by commit
> 63b96983a5dd ("i2c: core: introduce callbacks for atomic transfers")
> during system reboot and power-off.
Is there an existing system that you have access to which needs atomic
transfer support, or is this a forward looking change?
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-09 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231006144123eucas1p111cbbdbd70927ffbd697f7edf6b7ae1c@eucas1p1.samsung.com>
2023-10-06 14:41 ` [PATCH] i2c: brcmstb: Add support for atomic transfers Marek Szyprowski
2023-10-06 14:41 ` Marek Szyprowski
2023-10-09 20:41 ` Florian Fainelli [this message]
2023-10-09 20:41 ` Florian Fainelli
2023-10-11 9:57 ` Marek Szyprowski
2023-10-11 9:57 ` Marek Szyprowski
2023-10-11 15:43 ` Florian Fainelli
2023-10-11 15:43 ` Florian Fainelli
2023-10-11 10:23 ` Gregor Riepl
2023-10-11 10:23 ` Gregor Riepl
2023-10-11 11:47 ` Marek Szyprowski
2023-10-11 11:47 ` Marek Szyprowski
2023-10-11 14:48 ` Wolfram Sang
2023-10-11 14:48 ` Wolfram Sang
2023-10-11 13:40 ` Andi Shyti
2023-10-11 13:40 ` Andi Shyti
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=bec3b967-f287-4a99-9c79-3b949a31c296@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andi.shyti@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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 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.