All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "André Moreira" <andrem.33333@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: core: hub: fix coding style and prefer unsigned int
Date: Wed, 24 Jun 2026 08:28:23 +0200	[thread overview]
Message-ID: <2026062445-reissue-calculus-baa3@gregkh> (raw)
In-Reply-To: <20260624061734.28479-1-andrem.33333@gmail.com>

On Wed, Jun 24, 2026 at 03:17:34AM -0300, André Moreira wrote:
> Fix indentation issues and clear checkpatch warnings by replacing
> bare uses of 'unsigned' with 'unsigned int' throughout the file.

There's no need to do coding style changes for existing kernel code that
isn't asking for it :)

Please stick to this in subsystems that explicitly ask for it, like
drivers/staging/

thanks,

greg k-h

      parent reply	other threads:[~2026-06-24  6:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24  6:17 [PATCH] usb: core: hub: fix coding style and prefer unsigned int André Moreira
2026-06-24  6:28 ` Andre Moreira
2026-06-24  6:28 ` Greg Kroah-Hartman [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=2026062445-reissue-calculus-baa3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andrem.33333@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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 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.