linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matheus Castello <matheus@castello.eng.br>
To: Wei Liu <wei.liu@kernel.org>, mikelley@microsoft.com
Cc: kys@microsoft.com, haiyangz@microsoft.com,
	sthemmin@microsoft.com, sashal@kernel.org,
	Tianyu.Lan@microsoft.com, decui@microsoft.com,
	sunilmut@microsoft.com, linux-hyperv@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Add improvements suggested by checkpatch for vmbus_drv
Date: Tue, 24 Nov 2020 21:53:02 -0300	[thread overview]
Message-ID: <0870858d-7f92-28f0-e9ca-a2e6f23bcc2a@castello.eng.br> (raw)
In-Reply-To: <20201117105843.ijvulc7cx3ac2zng@liuwe-devbox-debian-v2>

Hi Wei,

Em 11/17/2020 7:58 AM, Wei Liu escreveu:
> On Sun, Nov 15, 2020 at 04:57:28PM -0300, Matheus Castello wrote:
>> This series fixes some warnings edmited by the checkpatch in the file
>> vmbus_drv.c. I thought it would be good to split each fix into a commit to
>> help with the review.
>>
>> Matheus Castello (6):
>>    drivers: hv: Fix hyperv_record_panic_msg path on comment
>>    drivers: hv: vmbus: Replace symbolic permissions by octal permissions
>>    drivers: hv: vmbus: Fix checkpatch LINE_SPACING
>>    drivers: hv: vmbus: Fix checkpatch SPLIT_STRING
>>    drivers: hv: vmbus: Fix unnecessary OOM_MESSAGE
>>    drivers: hv: vmbus: Fix call msleep using < 20ms
> 
> I've pushed patch 1-3 and 6 to hyperv-next.
> 
> Patch 4 has a pending comment from Michael. Patch 5 can be dropped.
>

Thanks for the review, got it and I agree with the drop of patch 5 
thanks to point it. I will send the v2 for the patch 4.

> Wei.
> 

      reply	other threads:[~2020-11-25  1:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 19:57 [PATCH 0/6] Add improvements suggested by checkpatch for vmbus_drv Matheus Castello
2020-11-15 19:57 ` [PATCH 1/6] drivers: hv: Fix hyperv_record_panic_msg path on comment Matheus Castello
2020-11-15 22:11   ` Michael Kelley
2020-11-15 19:57 ` [PATCH 2/6] drivers: hv: vmbus: Replace symbolic permissions by octal permissions Matheus Castello
2020-11-15 22:15   ` Michael Kelley
2020-11-15 19:57 ` [PATCH 3/6] drivers: hv: vmbus: Fix checkpatch LINE_SPACING Matheus Castello
2020-11-15 22:16   ` Michael Kelley
2020-11-15 19:57 ` [PATCH 4/6] drivers: hv: vmbus: Fix checkpatch SPLIT_STRING Matheus Castello
2020-11-15 22:25   ` Michael Kelley
2020-11-25  0:54     ` Matheus Castello
2020-11-25  2:56       ` Joe Perches
2020-11-25  3:14         ` Matheus Castello
2020-11-15 19:57 ` [PATCH 5/6] drivers: hv: vmbus: Fix unnecessary OOM_MESSAGE Matheus Castello
2020-11-16 11:21   ` Wei Liu
2020-11-16 15:58     ` Wei Liu
2020-11-15 19:57 ` [PATCH 6/6] drivers: hv: vmbus: Fix call msleep using < 20ms Matheus Castello
2020-11-15 22:32   ` Michael Kelley
2020-11-17 10:58 ` [PATCH 0/6] Add improvements suggested by checkpatch for vmbus_drv Wei Liu
2020-11-25  0:53   ` Matheus Castello [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=0870858d-7f92-28f0-e9ca-a2e6f23bcc2a@castello.eng.br \
    --to=matheus@castello.eng.br \
    --cc=Tianyu.Lan@microsoft.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=sashal@kernel.org \
    --cc=sthemmin@microsoft.com \
    --cc=sunilmut@microsoft.com \
    --cc=wei.liu@kernel.org \
    /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).