All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Shi Hao <i.shihao.999@gmail.com>
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu
Subject: Re: [PATCH v6] usb-storage: Fix comment indentation level
Date: Wed, 8 Oct 2025 13:21:56 +0200	[thread overview]
Message-ID: <2025100802-sedan-security-3529@gregkh> (raw)
In-Reply-To: <20251008110910.33833-1-i.shihao.999@gmail.com>

On Wed, Oct 08, 2025 at 04:39:10PM +0530, Shi Hao wrote:
> Fix comment  indentation level .
> 
> The previous comment was indented at the wrong level, breaking
> kernel coding style consistency. The indentation has been corrected
> to align with the relevant code block.

This does not describe what this patch does.

Please take a break, relax, and come back in a day or so and start from
a "clean" tree to implement this after taking a look at the kernel
documentation for how to submit patches again.

You are making patches on top of patches, all of which will not work
here.

thanks,

greg k-h

  reply	other threads:[~2025-10-08 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 10:46 [PATCH] usb: fix protocol translation in drivers/usb/storage/transport.c Shi Hao
2025-10-03 11:39 ` Greg KH
2025-10-03 11:40 ` Greg KH
2025-10-06 12:31 ` [PATCH v3] usb-storage: Protocol translation for scsi opcode Shi Hao
2025-10-06 13:47   ` Alan Stern
2025-10-07 11:37     ` [PATCH v4] usb-storage v4: Simplify protocol translation Shi Hao
2025-10-07 14:35       ` Alan Stern
2025-10-08  7:04         ` [PATCH v5] usb-storage: " Shi Hao
2025-10-08  7:31           ` Greg KH
2025-10-08  9:18             ` ShiHao
2025-10-08 10:04               ` Greg KH
2025-10-08 11:09                 ` [PATCH v6] usb-storage: Fix comment indentation level Shi Hao
2025-10-08 11:21                   ` Greg KH [this message]
2025-10-09 21:15 ` [PATCH] usb: fix protocol translation in drivers/usb/storage/transport.c kernel test robot

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=2025100802-sedan-security-3529@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=i.shihao.999@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.