From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Wolfram Sang <wsa@kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] i2c: mpc: use device managed APIs
Date: Tue, 13 Apr 2021 16:31:59 +0300 [thread overview]
Message-ID: <CAHp75VfTS8E3Rw-0c66KS5_OBeLMaxUph+d70FYVVmYkerUYhQ@mail.gmail.com> (raw)
In-Reply-To: <CAHp75Vc0F7zm47h94Pnh-dZJXG770UwR9za+GQP0eCr78qPgtg@mail.gmail.com>
On Tue, Apr 13, 2021 at 4:31 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Tue, Apr 13, 2021 at 3:21 PM Wolfram Sang <wsa@kernel.org> wrote:
> >
> >
> > > Yongjun[1] into the original patch. If Wei's patch is applied on top
> > > of whats already in i2c/for-next then this patch can be ignored.
> >
> > I applied Wei's patch instead. It was easier.
>
> Where is it? i2c/for-next shows the v2 of this series being applied.
Ah, I see it's a follow up.
I thought it was a replacement.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-04-13 13:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 5:09 [PATCH v3 0/4] i2c: mpc: Refactor to improve responsiveness Chris Packham
2021-04-13 5:09 ` [PATCH v3 1/4] i2c: mpc: use device managed APIs Chris Packham
2021-04-13 12:21 ` Wolfram Sang
2021-04-13 13:31 ` Andy Shevchenko
2021-04-13 13:31 ` Andy Shevchenko [this message]
2021-04-13 5:09 ` [PATCH v3 2/4] i2c: mpc: Interrupt driven transfer Chris Packham
2021-04-13 12:22 ` Wolfram Sang
2021-04-13 13:52 ` Andy Shevchenko
2021-04-13 22:28 ` Chris Packham
2021-04-13 23:23 ` Chris Packham
2021-04-13 5:09 ` [PATCH v3 3/4] i2c: mpc: Remove redundant NULL check Chris Packham
2021-04-13 12:27 ` Wolfram Sang
2021-04-13 5:09 ` [PATCH v3 3/3] MAINTAINERS: Add Chris Packham as FREESCALE MPC I2C maintainer Chris Packham
2021-04-13 5:14 ` Chris Packham
2021-04-13 11:19 ` Andy Shevchenko
2021-04-13 5:09 ` [PATCH v3 4/4] " Chris Packham
2021-04-13 12:27 ` Wolfram Sang
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=CAHp75VfTS8E3Rw-0c66KS5_OBeLMaxUph+d70FYVVmYkerUYhQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).