> >
> > I am wondering if this is the correct tree to submit the patch for MFD?
> >
> > So to sum it up, the latest patch is my first version to this tree.
>
> Either MFD or -next is fine for MFD-only patches.
>
> Has the code changed at all in any of the patches?
>
> If so, please provide a cha
On Mon, 22 Mar 2021, Min Li wrote:
> >
> > I'm pretty confused. This has been sent ~6 times already. What is the v1
> > of?
> > Is this a different driver? If so, why does it have the same $SUBJECT line?
> >
> > If this is not actually v1. Please provide a change-log.
> >
>
>
> Hi Lee
>
>
> I'm pretty confused. This has been sent ~6 times already. What is the v1 of?
> Is this a different driver? If so, why does it have the same $SUBJECT line?
>
> If this is not actually v1. Please provide a change-log.
>
Hi Lee
Sorry for confusion. This is no version before v1. The reaso
On Sat, 20 Mar 2021, min.li...@renesas.com wrote:
> From: Min Li
>
> Add support for ClockMatrix(TM) and 82P33xxx families of timing
> and synchronization devices. The access interface can be either
> SPI or I2C. Currently, it will create 2 types of MFD devices,
> which are to be used by the cor
From: Min Li
Add support for ClockMatrix(TM) and 82P33xxx families of timing
and synchronization devices. The access interface can be either
SPI or I2C. Currently, it will create 2 types of MFD devices,
which are to be used by the corresponding rsmu character device
driver and the PTP hardware cl
From: Min Li
Add support for ClockMatrix(TM) and 82P33xxx families of timing
and synchronization devices. The access interface can be either
SPI or I2C. Currently, it will create 2 types of MFD devices,
which are to be used by the corresponding rsmu character device
driver and the PTP hardware cl
6 matches
Mail list logo
