From: Greg KH <gregkh@linuxfoundation.org>
To: Peng Hao <peng.hao2@zte.com.cn>
Cc: arnd@arndb.de, andy.shevchenko@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/6] misc/pvpanic: preparing for pvpanic driver framework
Date: Wed, 23 Jan 2019 07:37:40 +0100 [thread overview]
Message-ID: <20190123063740.GA26046@kroah.com> (raw)
In-Reply-To: <1548243477-60654-2-git-send-email-peng.hao2@zte.com.cn>
On Wed, Jan 23, 2019 at 07:37:52PM +0800, Peng Hao wrote:
> Preparing for pvpanic driver framework. Create a pvpanic driver
> directory and move current driver file to new directory.
>
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> ---
> drivers/misc/Kconfig | 9 +--------
> drivers/misc/Makefile | 2 +-
> drivers/misc/pvpanic/Kconfig | 7 +++++++
> drivers/misc/pvpanic/Makefile | 5 +++++
> drivers/misc/{ => pvpanic}/pvpanic.c | 0
> 5 files changed, 14 insertions(+), 9 deletions(-)
> create mode 100644 drivers/misc/pvpanic/Kconfig
> create mode 100644 drivers/misc/pvpanic/Makefile
> rename drivers/misc/{ => pvpanic}/pvpanic.c (100%)
In none of these patches do you say what changed from v1 :(
Please fix up as the documentation says to, and resend as v3.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-23 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 11:37 [PATCH V2 0/6] add pvpanic driver framework Peng Hao
2019-01-23 11:37 ` [PATCH V2 1/6] misc/pvpanic: preparing for " Peng Hao
2019-01-23 6:37 ` Greg KH [this message]
2019-01-23 11:37 ` [PATCH V2 2/6] misc/pvpanic: Add " Peng Hao
2019-01-23 11:37 ` [PATCH V2 3/6] misc/pvpanic: add API for " Peng Hao
2019-01-23 11:37 ` [PATCH V2 4/6] misc/pvpanic: add pvpanic acpi driver Peng Hao
2019-01-23 11:37 ` [PATCH V2 5/6] misc/pvpanic: add pvpanic mmio driver Peng Hao
2019-01-23 11:37 ` [PATCH V2 6/6] misc/pvpanic: add new pvpanic pci driver Peng Hao
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=20190123063740.GA26046@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.hao2@zte.com.cn \
/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.