All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu@kernel.org>
To: Stefan Eschenbacher <stefan.eschenbacher@fau.de>
Cc: Michael Kelley <mikelley@microsoft.com>,
	Max Stolze <max.stolze@fau.de>, KY Srinivasan <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH] drivers/hv: remove obsolete TODO and fix misleading typo in comment
Date: Mon, 7 Dec 2020 11:25:31 +0000	[thread overview]
Message-ID: <20201207112531.uyacqporhjk26hki@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20201206104850.24843-1-stefan.eschenbacher@fau.de>

On Sun, Dec 06, 2020 at 11:48:50AM +0100, Stefan Eschenbacher wrote:
> Removes an obsolete TODO in the VMBus module and fixes a misleading typo
> in the comment for the macro MAX_NUM_CHANNELS, where two digits have been
> twisted.
> 
> Signed-off-by: Stefan Eschenbacher <stefan.eschenbacher@fau.de>
> Co-developed-by: Max Stolze <max.stolze@fau.de>
> Signed-off-by: Max Stolze <max.stolze@fau.de>

Applied to hyperv-next. Thanks.

Wei.

      reply	other threads:[~2020-12-07 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 17:26 [PATCH 0/3] drivers/hv: make max_num_channels_supported configurable Stefan Eschenbacher
2020-12-05 17:30 ` [PATCH 1/3] " Stefan Eschenbacher
2020-12-05 17:30 ` [PATCH 2/3] drivers/hv: fix misleading typo in comment Stefan Eschenbacher
2020-12-05 17:30 ` [PATCH 3/3] drivers/hv: add default number of vmbus channels to Kconfig Stefan Eschenbacher
2020-12-05 18:27 ` [PATCH 0/3] drivers/hv: make max_num_channels_supported configurable Michael Kelley
2020-12-05 20:32   ` Max Stolze
2020-12-05 21:33     ` Michael Kelley
2020-12-06 10:48       ` [PATCH] drivers/hv: remove obsolete TODO and fix misleading typo in comment Stefan Eschenbacher
2020-12-07 11:25         ` 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=20201207112531.uyacqporhjk26hki@liuwe-devbox-debian-v2 \
    --to=wei.liu@kernel.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.stolze@fau.de \
    --cc=mikelley@microsoft.com \
    --cc=stefan.eschenbacher@fau.de \
    --cc=sthemmin@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 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.