>
> Then you need to mention that in the change log.
>
> What changed from v1 => v2?
>
Please see my latest [PATCH next v2] and it has the following change log
Signed-off-by: Min Li
---
-rebase change to linux-next tree
-add log to inform driver loading success
>
> Then you need to mention that in the change log.
>
> What changed from v1 => v2?
>
Please look it up by the latest patch I sent over yesterday. It is under the
Signed-off-by
---
-rebase change to linux-next tree
-add log to inform driver loading success
On Thu, 08 Apr 2021, Min Li wrote:
> >
> > If this is v3, there should be a changelog here.
> >
> Hi Lee
>
> There is no change in v3 for MFD part of code, v3 is only for misc part.
> But I have to format 2 patches together and that is why mfd part got v3 as
> well.
> But it is actually ident
>
> If this is v3, there should be a changelog here.
>
Hi Lee
There is no change in v3 for MFD part of code, v3 is only for misc part.
But I have to format 2 patches together and that is why mfd part got v3 as well.
But it is actually identical to v2
On Wed, 07 Apr 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
6 matches
Mail list logo
