From: Lee Jones <lee.jones@linaro.org>
To: Min Li <min.li.xe@renesas.com>
Cc: "derek.kiernan@xilinx.com" <derek.kiernan@xilinx.com>,
"dragan.cvetic@xilinx.com" <dragan.cvetic@xilinx.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v3 1/2] mfd: Add Renesas Synchronization Management Unit (SMU) support
Date: Fri, 9 Apr 2021 11:02:20 +0100 [thread overview]
Message-ID: <20210409100220.GE2961413@dell> (raw)
In-Reply-To: <OSBPR01MB4773DF588214D8B9E613E074BA749@OSBPR01MB4773.jpnprd01.prod.outlook.com>
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 identical to v2
Then you need to mention that in the change log.
What changed from v1 => v2?
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-04-09 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 1:50 [PATCH net-next v3 1/2] mfd: Add Renesas Synchronization Management Unit (SMU) support min.li.xe
2021-04-08 1:50 ` [PATCH net-next v3 2/2] misc: " min.li.xe
2021-04-08 6:22 ` Greg KH
2021-04-08 17:26 ` Min Li
2021-04-08 17:54 ` Greg KH
2021-04-08 18:01 ` Min Li
2021-04-08 18:10 ` Greg KH
2021-04-08 18:59 ` Min Li
2021-04-09 6:44 ` Greg KH
2021-04-08 7:08 ` [PATCH net-next v3 1/2] mfd: " Lee Jones
2021-04-08 17:38 ` Min Li
2021-04-09 10:02 ` Lee Jones [this message]
2021-04-09 13:57 ` Min Li
2021-04-11 14:10 ` Min Li
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=20210409100220.GE2961413@dell \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li.xe@renesas.com \
/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.