From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Wolfram Sang <wsa@kernel.org>
Cc: "Andreas Färber" <afaerber@suse.de>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-actions@lists.infradead.org
Subject: Re: [PATCH v2 1/1] i2c: busses: Add support for atomic transfers in Actions Semi Owl driver
Date: Fri, 9 Oct 2020 01:17:01 +0300 [thread overview]
Message-ID: <20201008221701.GA72402@BV030612LT> (raw)
In-Reply-To: <20200929210010.GB35053@BV030612LT>
Hi Mani, Wolfram,
On Wed, Sep 30, 2020 at 12:00:10AM +0300, Cristian Ciocaltea wrote:
> Hi Wolfram,
>
> On Tue, Sep 29, 2020 at 09:45:23PM +0200, Wolfram Sang wrote:
> >
> > > Sure, I can handle this. I assume this should be a separate patch, to
> > > be applied before the current patch. Should I submit a patch series
> > > instead?
> >
> > Yes, just do it.
>
> Sure, I have already clarified this directly with Mani and I'm going
> to handle it soon.
I have just submitted a patch series that incorporates the current
feedback (patches 1 & 2) and an additional improvement (patch 3):
i2c: owl: Clear NACK and BUS error bits
i2c: owl: Add support for atomic transfers
i2c: owl: Enable asynchronous probing
https://lore.kernel.org/lkml/cover.1602190168.git.cristian.ciocaltea@gmail.com/
Thanks,
Cristi
WARNING: multiple messages have this Message-ID (diff)
From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Wolfram Sang <wsa@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-actions@lists.infradead.org,
"Andreas Färber" <afaerber@suse.de>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 1/1] i2c: busses: Add support for atomic transfers in Actions Semi Owl driver
Date: Fri, 9 Oct 2020 01:17:01 +0300 [thread overview]
Message-ID: <20201008221701.GA72402@BV030612LT> (raw)
In-Reply-To: <20200929210010.GB35053@BV030612LT>
Hi Mani, Wolfram,
On Wed, Sep 30, 2020 at 12:00:10AM +0300, Cristian Ciocaltea wrote:
> Hi Wolfram,
>
> On Tue, Sep 29, 2020 at 09:45:23PM +0200, Wolfram Sang wrote:
> >
> > > Sure, I can handle this. I assume this should be a separate patch, to
> > > be applied before the current patch. Should I submit a patch series
> > > instead?
> >
> > Yes, just do it.
>
> Sure, I have already clarified this directly with Mani and I'm going
> to handle it soon.
I have just submitted a patch series that incorporates the current
feedback (patches 1 & 2) and an additional improvement (patch 3):
i2c: owl: Clear NACK and BUS error bits
i2c: owl: Add support for atomic transfers
i2c: owl: Enable asynchronous probing
https://lore.kernel.org/lkml/cover.1602190168.git.cristian.ciocaltea@gmail.com/
Thanks,
Cristi
_______________________________________________
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:[~2020-10-08 22:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 10:52 [PATCH v2 1/1] i2c: busses: Add support for atomic transfers in Actions Semi Owl driver Cristian Ciocaltea
2020-09-08 10:52 ` Cristian Ciocaltea
2020-09-09 15:17 ` Manivannan Sadhasivam
2020-09-09 15:17 ` Manivannan Sadhasivam
2020-09-09 16:59 ` Cristian Ciocaltea
2020-09-09 16:59 ` Cristian Ciocaltea
2020-09-10 3:02 ` Manivannan Sadhasivam
2020-09-10 3:02 ` Manivannan Sadhasivam
2020-09-10 14:12 ` Cristian Ciocaltea
2020-09-10 14:12 ` Cristian Ciocaltea
2020-09-29 19:45 ` Wolfram Sang
2020-09-29 19:45 ` Wolfram Sang
2020-09-29 21:00 ` Cristian Ciocaltea
2020-09-29 21:00 ` Cristian Ciocaltea
2020-10-08 22:17 ` Cristian Ciocaltea [this message]
2020-10-08 22:17 ` Cristian Ciocaltea
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=20201008221701.GA72402@BV030612LT \
--to=cristian.ciocaltea@gmail.com \
--cc=afaerber@suse.de \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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 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.