Linux USB
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Adam Simonelli" <adamsimonelli@gmail.com>, linux-usb@vger.kernel.org
Subject: Re: [[PATCH v3]] USB: visor add vendor/device IDs for PalmSource devices from the PalmUSBD.inf file in Palm Desktop 6.2
Date: Tue, 10 Nov 2026 02:30:55 +0000	[thread overview]
Message-ID: <sashiko-outbox-206047@kernel.org> (raw)
In-Reply-To: <20261110022351.302989-1-adamsimonelli@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] USB: serial: visor: malformed commit subject with stray leading
  bracket
--

commit cb84cb0d86c345eb88e5efd1e32db221810d4087
Author: Adam Simonelli <adamsimonelli@gmail.com>

> ] USB: visor add vendor/device IDs for PalmSource devices from the PalmUSBD.inf file in Palm Desktop 6.2
>
> PalmUSBD.inf from Palm Desktop 6.2's driver defines two PalmSource
> devices. While PalmSource only developed the PalmOS, and never made
> actualy hardware, as it was Palm Inc. made the Palm hardware, there
> is a bootable ROM containing PalmOS 6.1 that can be booted into RAM
> on the Tungsten T3. When this ROM is running, when plugged in, the
> device will then present the PalmSource vendorid that is defined in
> the INI filem and the deviceid then becomes PALMSOURCE_DEVICE_1_ID
> the PALMSOURCE_DEVICE_2_ID is also defined for completeness.
>
> Signed-off-by: Adam Simonelli <adamsimonelli@gmail.com>

[Severity: Low]
This isn't a bug, but the commit subject begins with a stray "] " character,
exceeds standard length, and does not use the "USB: serial: visor: " prefix.
The commit message body also has several typos and unpunctuated run-on
clauses ("never made actualy hardware, as it was Palm Inc. made the Palm
hardware" and "defined in the INI filem and the deviceid then becomes
PALMSOURCE_DEVICE_1_ID the PALMSOURCE_DEVICE_2_ID is also defined for
completeness") that make the explanation hard to follow.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261110022351.302989-1-adamsimonelli@gmail.com?part=1

      reply	other threads:[~2026-11-10  2:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  2:23 [[PATCH v3]] USB: visor add vendor/device IDs for PalmSource devices from the PalmUSBD.inf file in Palm Desktop 6.2 Adam Simonelli
2026-11-10  2:30 ` sashiko-bot [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=sashiko-outbox-206047@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=adamsimonelli@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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