From: Wei Liu <wei.liu@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Michael Kelley <mikelley@microsoft.com>,
Matheus Castello <matheus@castello.eng.br>,
wei.liu@kernel.org, joe@perches.com,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
sashal@kernel.org, Tianyu Lan <Tianyu.Lan@microsoft.com>,
Dexuan Cui <decui@microsoft.com>,
Sunil Muthuswamy <sunilmut@microsoft.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/6] drivers: hv: vmbus: Fix checkpatch SPLIT_STRING
Date: Wed, 2 Dec 2020 11:55:04 +0000 [thread overview]
Message-ID: <20201202115504.w52yeixpg7nbzw2v@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20201129214328.254372dd@hermes.local>
On Sun, Nov 29, 2020 at 09:43:28PM -0800, Stephen Hemminger wrote:
> On Sun, 29 Nov 2020 08:51:47 -0800
> "Michael Kelley" <mikelley@microsoft.com> wrote:
>
> > From: Matheus Castello <matheus@castello.eng.br> Sent: Tuesday, November
> > 24, 2020 7:29 PM
> > >
> > > Checkpatch emits WARNING: quoted string split across lines.
> > > To keep the code clean and with the 80 column length indentation the
> > > check and registration code for kmsg_dump_register has been transferred
> > > to a new function hv_kmsg_dump_register.
> > >
> > > Signed-off-by: Matheus Castello <matheus@castello.eng.br>
> > > ---
> > > This is the V3 of patch 4 of the series "Add improvements suggested by
> > > checkpatch for vmbus_drv" with the changes suggested by Michael Kelley
> > and
> > > Joe Perches. Thanks!
> > > ---
> > > drivers/hv/vmbus_drv.c | 35 ++++++++++++++++++++---------------
> > > 1 file changed, 20 insertions(+), 15 deletions(-)
> > >
> > > diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> > > index 61d28c743263..edcc419ba328 100644
> > > --- a/drivers/hv/vmbus_drv.c
> > > +++ b/drivers/hv/vmbus_drv.c
> > > @@ -1387,6 +1387,24 @@ static struct kmsg_dumper hv_kmsg_dumper = {
> > > .dump = hv_kmsg_dump,
> > > };
> > >
> > > +static void hv_kmsg_dump_register(void)
> > > +{
> > > + int ret;
> > > +
> > > + hv_panic_page = (void *)hv_alloc_hyperv_zeroed_page();
>
> I know you just copy/pasted the original code, but one other thing.
>
> Doesn't it already return void *?
> arch/x86/include/asm/mshyperv.h:void *hv_alloc_hyperv_zeroed_page(void);
Good catch.
I have amended this patch and applied it to hyperv-next.
Wei.
prev parent reply other threads:[~2020-12-02 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 3:29 [PATCH v3 4/6] drivers: hv: vmbus: Fix checkpatch SPLIT_STRING Matheus Castello
2020-11-29 16:51 ` Michael Kelley
2020-11-30 5:43 ` Stephen Hemminger
2020-12-02 11:55 ` Wei Liu [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=20201202115504.w52yeixpg7nbzw2v@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=joe@perches.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matheus@castello.eng.br \
--cc=mikelley@microsoft.com \
--cc=sashal@kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=sunilmut@microsoft.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;
as well as URLs for NNTP newsgroup(s).