From: Michael Rubin <matchstick@neverthere.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: dpenkler@gmail.com, dan.carpenter@linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 00/23] staging: gpib: u8 over uint8_t and u64 over uint64_t
Date: Thu, 17 Apr 2025 00:46:34 +0000 [thread overview]
Message-ID: <aABPat7WxeVBIOQ5@tiamat> (raw)
In-Reply-To: <2025041519-drier-decimal-8a7f@gregkh>
On Tue, Apr 15, 2025 at 04:45:58PM +0200, Greg KH wrote:
> On Wed, Apr 09, 2025 at 06:09:30PM +0000, Michael Rubin wrote:
> > Preferring u8 over uint8_t and preferring u64 over uint64_t to adhere to
> > Linux code style.
> >
> > * Patch 1 - Patch 22:
> > Reported by checkpatch.pl.
> > CHECK: Prefer kernel type 'u8' over 'uint8_t'
> >
> > * Patch 23:
> > Reported by checkpatch.pl.
> > CHECK: Prefer kernel type 'u64' over 'uint64_t'
> >
>
> Only a portion of this series could be applied, as I hit some patch
> errors that I couldn't resolve easily. Odds are we are out of sync
> somehow, can you rebase and resend the remaining ones?
Done. Hope these are the right ones.
Thanks for your patience.
Michael Rubin
prev parent reply other threads:[~2025-04-17 0:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 18:09 [PATCH v1 00/23] staging: gpib: u8 over uint8_t and u64 over uint64_t Michael Rubin
2025-04-09 18:09 ` [PATCH v1 01/23] staging: gpib: cb7210: u8 over uint8_t Michael Rubin
2025-04-09 18:09 ` [PATCH v1 02/23] staging: gpib: ibsys: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 03/23] staging: gpib: fluke_gpib: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 04/23] staging: gpib: fmh_gpib: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 05/23] staging: gpib: gpib_proto: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 06/23] staging: gpib: gpib_types: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 07/23] staging: gpib: nec7210: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 08/23] staging: gpib: tms9914: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 09/23] staging: gpib: ines: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 10/23] staging: gpib: gpib_ioctl: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 11/23] staging: gpib: gpib_user: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 12/23] staging: gpib: agilent_82350b: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 13/23] staging: gpib: agilent_82357a: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 14/23] staging: gpib: cec: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 15/23] staging: gpib: gpib_os: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 16/23] staging: gpib: gpib_bitbang: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 17/23] staging: gpib: hp_82335: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 18/23] staging: gpib: hp_82341: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 19/23] staging: gpib: lpvo_usb_gpib: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 20/23] staging: gpib: ni_usb: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 21/23] staging: gpib: pc2: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 22/23] staging: gpib: tnt4882: " Michael Rubin
2025-04-09 18:09 ` [PATCH v1 23/23] staging: gpib: gpib_ioctl: u64 over uint64_t Michael Rubin
2025-04-15 14:45 ` [PATCH v1 00/23] staging: gpib: u8 over uint8_t and " Greg KH
2025-04-17 0:46 ` Michael Rubin [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=aABPat7WxeVBIOQ5@tiamat \
--to=matchstick@neverthere.org \
--cc=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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