From: Florian Fainelli <f.fainelli@gmail.com>
To: Wolfram Sang <wsa@kernel.org>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
Cc: Ray Jui <ray.jui@broadcom.com>,
Dhananjay Phadke <dphadke@linux.microsoft.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Brendan Higgins <brendanhiggins@google.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lori Hikichi <lori.hikichi@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Subject: Re: [PATCH v3 5/6] i2c: iproc: handle master read request
Date: Tue, 5 Jan 2021 09:46:52 -0800 [thread overview]
Message-ID: <b5e38606-6ca8-b52c-65cd-5f24411661d0@gmail.com> (raw)
In-Reply-To: <20210105162145.GG1842@ninjato>
On 1/5/21 8:21 AM, Wolfram Sang wrote:
>
>>> I think that makes sense, and I'm okay with these patches going in as
>>> they are now.
>>>
>>> Acked-by: Ray Jui <ray.jui@broadcom.com>
>>
>> Thank you.
>
> Yes, thank you everyone.
>
> All applied to for-next, thanks!
>
>> --
>> This electronic communication and the information and any files transmitted
>> with it, or attached to it, are confidential and are intended solely for
> ...
>
> Please remove this paragraph for mailing lists.
We are working on it, but as you may expect with any large corporations
it is "complicated".
--
Florian
next prev parent reply other threads:[~2021-01-05 17:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 3:54 [PATCH v3 0/6] fix iproc driver to handle master read request Rayagonda Kokatanur
2020-11-02 3:54 ` [PATCH v3 1/6] i2c: iproc: handle Master aborted error Rayagonda Kokatanur
2020-11-02 3:54 ` [PATCH v3 2/6] i2c: iproc: handle only slave interrupts which are enabled Rayagonda Kokatanur
2020-11-02 3:54 ` [PATCH v3 3/6] i2c: iproc: update slave isr mask (ISR_MASK_SLAVE) Rayagonda Kokatanur
2020-11-02 3:54 ` [PATCH v3 4/6] i2c: iproc: fix typo in slave_isr function Rayagonda Kokatanur
2020-11-02 3:54 ` [PATCH v3 5/6] i2c: iproc: handle master read request Rayagonda Kokatanur
2020-11-03 6:19 ` Dhananjay Phadke
2020-11-04 3:35 ` Florian Fainelli
2020-11-04 3:57 ` Rayagonda Kokatanur
2020-11-04 18:01 ` Ray Jui
2020-11-05 7:46 ` Dhananjay Phadke
2020-11-05 9:43 ` Rayagonda Kokatanur
2020-11-06 17:41 ` Dhananjay Phadke
2020-11-10 4:23 ` Rayagonda Kokatanur
2020-11-10 19:24 ` Ray Jui
2020-11-14 1:17 ` Dhananjay Phadke
[not found] ` <CAHO=5PFzd9KTR93ntUvAX5dqzxqJQpVXEirs5uoXdvcnZ7hL4g@mail.gmail.com>
2020-12-02 14:35 ` Wolfram Sang
2020-12-02 17:44 ` Ray Jui
2020-12-17 4:08 ` Rayagonda Kokatanur
2020-12-17 19:11 ` Ray Jui
2020-12-20 7:13 ` Rayagonda Kokatanur
2021-01-05 16:21 ` Wolfram Sang
2021-01-05 17:46 ` Florian Fainelli [this message]
2021-01-05 20:50 ` Wolfram Sang
2020-12-02 17:43 ` Ray Jui
2020-11-02 3:54 ` [PATCH v3 6/6] i2c: iproc: handle rx fifo full interrupt Rayagonda Kokatanur
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=b5e38606-6ca8-b52c-65cd-5f24411661d0@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brendanhiggins@google.com \
--cc=dphadke@linux.microsoft.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lori.hikichi@broadcom.com \
--cc=ray.jui@broadcom.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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;
as well as URLs for NNTP newsgroup(s).