From: Norihiko Hama <norihiko.hama@alpsalpine.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kernel test robot <lkp@intel.com>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [usb:usb-testing 17/35] drivers/usb/storage/usb.c:141:21: error: incompatible pointer types passing 'unsigned int *' to parameter of type 'uint64_t *' (aka 'unsigned long long *')
Date: Thu, 2 May 2024 08:04:14 +0000 [thread overview]
Message-ID: <TYVPR01MB1078177211401B245ED7150B290182@TYVPR01MB10781.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <3e2a7570-0704-4453-ad0b-68c5806157e5@rowland.harvard.edu>
On Wed, May 011, 2024 at 11:03 PM +0900, Alan Stern wrote:
> On Wed, May 01, 2024 at 08:50:36AM +0200, Greg Kroah-Hartman wrote:
> > On Wed, May 01, 2024 at 02:32:56PM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
> usb-testing
> > > head: ac6a205c5bef39d65ecd9f5dd2c1d75652c35405
> > > commit: 70d66b8e47e6fa031f541291e9dd3d7f0c44b41e [17/35]
> > > usb-storage: Optimize scan delay more precisely
> >
> Norihiko, another possibility is to use ordinary integers but have users add an
> "m" or "ms" suffix when they want the value to be interpreted in milliseconds.
> So "5" means 5 seconds, but "500ms" means
> 500 milliseconds.
Greg, I'm sorry for my problem.
Alan, thank you for your proposal.
I'll change the code based on it although I'm not sure if it's acceptable or not.
I'll use only suffix as "ms" so that it could be also shown as 'delay_use' with unique suffix.
prev parent reply other threads:[~2024-05-02 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 6:32 [usb:usb-testing 17/35] drivers/usb/storage/usb.c:141:21: error: incompatible pointer types passing 'unsigned int *' to parameter of type 'uint64_t *' (aka 'unsigned long long *') kernel test robot
2024-05-01 6:50 ` Greg Kroah-Hartman
2024-05-01 14:03 ` Alan Stern
2024-05-02 8:04 ` Norihiko Hama [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=TYVPR01MB1078177211401B245ED7150B290182@TYVPR01MB10781.jpnprd01.prod.outlook.com \
--to=norihiko.hama@alpsalpine.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).