public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: linux-usb@vger.kernel.org,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Andreas Noever <andreas.noever@gmail.com>
Subject: Re: [PATCH 2/2] thunderbolt: Add missing kernel-doc comment to tb_tunnel_maximum_bandwidth()
Date: Tue, 24 Jan 2023 12:33:44 +0200	[thread overview]
Message-ID: <Y8+0CJYuuYxomwXg@black.fi.intel.com> (raw)
In-Reply-To: <20230124102626.GA32238@wunner.de>

On Tue, Jan 24, 2023 at 11:26:26AM +0100, Lukas Wunner wrote:
> On Tue, Jan 24, 2023 at 11:09:38AM +0200, Mika Westerberg wrote:
> > +/**
> > + * tb_tunnel_maximum_bandwidth() - Return maximum possible bandwidth
> > + * @tunnel: Tunnel to check
> > + * @max_up: Maximum upstream bandwidth in Mb/s
> > + * @max_down: Maximum upstream bandwidth in Mb/s
>                          ^^^^^^^^
> 			 downstream?
> 
> I'm sure you're just testing whether anyone is reading your patches ;)

Hehe, thanks for reading them ;-) Fixed it now.

  reply	other threads:[~2023-01-24 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  9:09 [PATCH 1/2] thunderbolt: Handle bandwidth allocation mode enablement notification Mika Westerberg
2023-01-24  9:09 ` [PATCH 2/2] thunderbolt: Add missing kernel-doc comment to tb_tunnel_maximum_bandwidth() Mika Westerberg
2023-01-24 10:26   ` Lukas Wunner
2023-01-24 10:33     ` Mika Westerberg [this message]
2023-01-27  6:28 ` [PATCH 1/2] thunderbolt: Handle bandwidth allocation mode enablement notification Mika Westerberg

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=Y8+0CJYuuYxomwXg@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.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