public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: nathan.d.ciobanu@linux.intel.com
Cc: linux-kernel@vger.kernel.org, mika.westerberg@linux.intel.com,
	michael.jamet@intel.com, andreas.noever@gmail.com
Subject: Re: [PATCH] thunderbolt: fix small typo in variable name
Date: Sat, 7 Jul 2018 10:19:50 +0200	[thread overview]
Message-ID: <20180707081950.GA6660@wunner.de> (raw)
In-Reply-To: <1530056060-3612-1-git-send-email-nathan.d.ciobanu@linux.intel.com>

On Tue, Jun 26, 2018 at 04:34:20PM -0700, nathan.d.ciobanu@linux.intel.com wrot> Fixes small variable name typo and the associated
> checkpatch spelling warning
> 
> Signed-off-by: Nathan Ciobanu <nathan.d.ciobanu@linux.intel.com>
> ---
>  drivers/thunderbolt/tb_regs.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/thunderbolt/tb_regs.h b/drivers/thunderbolt/tb_regs.h
> index 5d94142afda6..693b0353c3fe 100644
> --- a/drivers/thunderbolt/tb_regs.h
> +++ b/drivers/thunderbolt/tb_regs.h
> @@ -202,7 +202,7 @@ struct tb_regs_port_header {
>  	/* DWORD 5 */
>  	u32 max_in_hop_id:11;
>  	u32 max_out_hop_id:11;
> -	u32 __unkown4:10;
> +	u32 __unknown4:10;
>  	/* DWORD 6 */
>  	u32 __unknown5;
>  	/* DWORD 7 */

This is not an improvement.  The bitfield is marked unknown because
its meaning hasn't been reverse-engineered yet.  But you work for
Intel, presumably you don't have to reverse-engineer the bitfield's
meaning because you know it or can find out about it.

So please submit a patch that changes the name to the bitfield's
actual meaning.

Thanks,

Lukas

  parent reply	other threads:[~2018-07-07  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 23:34 [PATCH] thunderbolt: fix small typo in variable name nathan.d.ciobanu
2018-06-27  9:41 ` Mika Westerberg
2018-07-07  8:19 ` Lukas Wunner [this message]
2018-07-07 11:09   ` 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=20180707081950.GA6660@wunner.de \
    --to=lukas@wunner.de \
    --cc=andreas.noever@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=nathan.d.ciobanu@linux.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