Hi Greg,
On Sun, 29 Apr 2018 15:36:42 +0200
Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 07:56:46PM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Apr 23, 2018 at 07:38:14PM +0200, Boris Brezillon wrote:
> > > Hi,
> > >
> > > On Fri, 30 Mar 2018 09:47:41 +0200
> > > Boris Brezillon wrot
On Mon, Apr 23, 2018 at 07:56:46PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 07:38:14PM +0200, Boris Brezillon wrote:
> > Hi,
> >
> > On Fri, 30 Mar 2018 09:47:41 +0200
> > Boris Brezillon wrote:
> >
> > > This patch series is a proposal for a new I3C subsystem.
> >
> > This v4
On Mon, Apr 23, 2018 at 07:38:14PM +0200, Boris Brezillon wrote:
> Hi,
>
> On Fri, 30 Mar 2018 09:47:41 +0200
> Boris Brezillon wrote:
>
> > This patch series is a proposal for a new I3C subsystem.
>
> This v4 has been sent almost a month ago and I didn't get any feedback
> so far apart from Ro
Hi,
On Fri, 30 Mar 2018 09:47:41 +0200
Boris Brezillon wrote:
> This patch series is a proposal for a new I3C subsystem.
This v4 has been sent almost a month ago and I didn't get any feedback
so far apart from Rob's R-b. Greg, is there any chance we can get these
patches merged in 4.18? If not,
This patch series is a proposal for a new I3C subsystem.
This infrastructure is not complete yet and will be extended over
time.
There are a few design choices that are worth mentioning because they
impact the way I3C device drivers can interact with their devices:
- all functions used to send I
