From: Greg KH <gregkh@linuxfoundation.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>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH next 2/2] misc: Add Renesas Synchronization Management Unit (SMU) support
Date: Fri, 2 Apr 2021 16:22:48 +0200 [thread overview]
Message-ID: <YGcouOYV/FlROZJv@kroah.com> (raw)
In-Reply-To: <OSBPR01MB4773E0C511E724307E7A2C0DBA7E9@OSBPR01MB4773.jpnprd01.prod.outlook.com>
On Mon, Mar 29, 2021 at 05:03:53PM +0000, Min Li wrote:
> >
> > Where is patch 1/2 of this series?
> >
> > Also, please fix up the errors that the testing bot found, and properly version
> > your patch submission so I know which one is the "latest" one to look at.
> >
>
> Hi Greg
>
> The first patch is mfd so I was not sure if I should send that to you guys in the first place.
Then the patches are independant and they should be sent as such,
otherwise it causes confusion and our tools get messed up when trying to
grab the whole "series" of patches.
Can you please fix this up and just send two independant patches?
thanks,
greg k-h
next prev parent reply other threads:[~2021-04-02 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 15:34 [PATCH next 2/2] misc: Add Renesas Synchronization Management Unit (SMU) support min.li.xe
2021-03-27 7:58 ` kernel test robot
2021-03-27 9:53 ` kernel test robot
2021-03-28 12:13 ` Greg KH
2021-03-29 17:03 ` Min Li
2021-04-02 14:22 ` Greg KH [this message]
2021-04-03 22:06 ` Min Li
-- strict thread matches above, loose matches on Subject: below --
2021-04-03 22:08 [PATCH next 1/2] mfd: " min.li.xe
2021-04-03 22:08 ` [PATCH next 2/2] misc: " min.li.xe
2021-04-04 10:08 ` Greg KH
2021-04-05 1:52 ` Min Li
2021-04-05 6:37 ` Greg KH
2021-04-05 13:53 ` Min Li
2021-03-23 16:40 min.li.xe
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=YGcouOYV/FlROZJv@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=dragan.cvetic@xilinx.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox