From: Greg KH <gregkh@linuxfoundation.org>
To: peng.hao2@zte.com.cn
Cc: arnd@arndb.de, andy.shevchenko@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5 1/3] misc/pvpanic: return 0 for empty body registerfunction
Date: Wed, 19 Dec 2018 10:46:01 +0100 [thread overview]
Message-ID: <20181219094601.GB11441@kroah.com> (raw)
In-Reply-To: <201812191703216682499@zte.com.cn>
On Wed, Dec 19, 2018 at 05:03:21PM +0800, peng.hao2@zte.com.cn wrote:
> >> Return 0 for empty body register function normally.
> >>
> >> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> >> ---
> >> v4 --> v5 : handle all typo "drvier/driver" in funtion name.
> >>
> >> v3 --> v4 : use pcim* function instead of pci* function.
> >> handle typo "drvier/driver" in funtion name.
> >>
> >> v2 --> v3 : handle a uninitialized variable in some path.
> >>
> >> v2 --> v1 : arch=sh don't support pci, adjust CONFIG_PCI macro.
> >>
> >> v1 : QEMU community requires additional PCI devices to simulate PVPANIC devices
> >> so that some architectures can not occupy precious less than 4G of memory
> >> space.
> >
> >Have you also fixed the kbuild issues that keep getting reported?
> >
>
> yes. v2--> v1 fixed the first kbuild issue.
> v2--> v3 fixed the second kbuild issue.
> v4 -->v5 fixed the last two kbuild issues.
And why did you not list all of this? Am I supposed to just guess it?
:(
prev parent reply other threads:[~2018-12-19 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 8:04 [PATCH V5 1/3] misc/pvpanic: return 0 for empty body register function Peng Hao
2018-12-19 8:04 ` [PATCH V5 2/3] misc/pvpanic : add pci interface for pvpanic Peng Hao
2018-12-19 8:04 ` [PATCH V5 3/3] misc/pvpanic : add pci dependency in Kconfig Peng Hao
2018-12-19 8:28 ` [PATCH V5 1/3] misc/pvpanic: return 0 for empty body register function Greg KH
[not found] ` <201812191703216682499@zte.com.cn>
2018-12-19 9:46 ` Greg KH [this message]
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=20181219094601.GB11441@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome