From: Wolfram Sang <wsa@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
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 21:50:17 +0100 [thread overview]
Message-ID: <20210105205017.GA1824@ninjato> (raw)
In-Reply-To: <b5e38606-6ca8-b52c-65cd-5f24411661d0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
> We are working on it, but as you may expect with any large corporations
> it is "complicated".
I understand. Good luck, then!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Lori Hikichi <lori.hikichi@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Brendan Higgins <brendanhiggins@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Dhananjay Phadke <dphadke@linux.microsoft.com>,
Ray Jui <ray.jui@broadcom.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
linux-i2c <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v3 5/6] i2c: iproc: handle master read request
Date: Tue, 5 Jan 2021 21:50:17 +0100 [thread overview]
Message-ID: <20210105205017.GA1824@ninjato> (raw)
In-Reply-To: <b5e38606-6ca8-b52c-65cd-5f24411661d0@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 131 bytes --]
> We are working on it, but as you may expect with any large corporations
> it is "complicated".
I understand. Good luck, then!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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:[~2021-01-05 20:52 UTC|newest]
Thread overview: 52+ 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 ` Rayagonda Kokatanur
2020-11-02 3:54 ` [PATCH v3 1/6] i2c: iproc: handle Master aborted error Rayagonda Kokatanur
2020-11-02 3:54 ` 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 ` 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 ` 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 ` 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-03 6:19 ` Dhananjay Phadke
2020-11-02 3:54 ` Rayagonda Kokatanur
2020-11-04 3:35 ` Florian Fainelli
2020-11-04 3:35 ` Florian Fainelli
2020-11-04 3:57 ` Rayagonda Kokatanur
2020-11-04 3:57 ` Rayagonda Kokatanur
2020-11-04 18:01 ` Ray Jui
2020-11-04 18:01 ` Ray Jui
2020-11-05 7:46 ` Dhananjay Phadke
2020-11-05 7:46 ` Dhananjay Phadke
2020-11-05 9:43 ` Rayagonda Kokatanur
2020-11-05 9:43 ` Rayagonda Kokatanur
2020-11-06 17:41 ` Dhananjay Phadke
2020-11-06 17:41 ` Dhananjay Phadke
2020-11-10 4:23 ` Rayagonda Kokatanur
2020-11-10 4:23 ` Rayagonda Kokatanur
2020-11-10 19:24 ` Ray Jui
2020-11-10 19:24 ` Ray Jui
2020-11-14 1:17 ` Dhananjay Phadke
2020-11-14 1:17 ` Dhananjay Phadke
[not found] ` <CAHO=5PFzd9KTR93ntUvAX5dqzxqJQpVXEirs5uoXdvcnZ7hL4g@mail.gmail.com>
2020-12-02 14:35 ` Wolfram Sang
2020-12-02 14:35 ` Wolfram Sang
2020-12-02 17:44 ` Ray Jui
2020-12-02 17:44 ` Ray Jui
2020-12-17 4:08 ` Rayagonda Kokatanur
2020-12-17 4:08 ` Rayagonda Kokatanur
2020-12-17 19:11 ` Ray Jui
2020-12-17 19:11 ` Ray Jui
2020-12-20 7:13 ` Rayagonda Kokatanur
2020-12-20 7:13 ` Rayagonda Kokatanur
2021-01-05 16:21 ` Wolfram Sang
2021-01-05 16:21 ` Wolfram Sang
2021-01-05 17:46 ` Florian Fainelli
2021-01-05 17:46 ` Florian Fainelli
2021-01-05 20:50 ` Wolfram Sang [this message]
2021-01-05 20:50 ` Wolfram Sang
2020-12-02 17:43 ` Ray Jui
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
2020-11-02 3:54 ` 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=20210105205017.GA1824@ninjato \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brendanhiggins@google.com \
--cc=dphadke@linux.microsoft.com \
--cc=f.fainelli@gmail.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 \
/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.