From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: outreachy@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] staging: axis-fifo: initialize timeouts in probe only
Date: Thu, 16 Mar 2023 21:17:52 +0100 [thread overview]
Message-ID: <3531852.LM0AJKV5NW@suse> (raw)
In-Reply-To: <ZBNhXc3sVVLdibUF@khadija-virtual-machine>
On giovedì 16 marzo 2023 19:35:09 CET Khadija Kamran wrote:
> On Thu, Mar 16, 2023 at 05:17:47PM +0100, Fabio M. De Francesco wrote:
[snip]
> > When you are done with build, install, and final reboot to test if your
> > module can "modprobe" or "insmod" (i.e. link with the running custom
kernel
> > you built, installed and boot), try to compare the output of the following
> > commands:
> >
> > # uname -a
> > Linux suse 6.2.2-1-default #1 SMP PREEMPT_DYNAMIC Thu Mar 9 06:06:13 UTC
> > 2023 (44ca817) x86_64 x86_64 x86_64 GNU/Linux
>
> The above command works
>
> > AND
> >
> > # modinfo <name of the module you are testing here>
>
> On running 'modinfo axis-fifo' I get error saying module axis-fifo not
> found.
I built axis-fifo with your changes and then I ran "make install
modules_install" in a QEMU/KVM x86_32 VM that I use on a Linux host for
testing my patches (Linux on Linux).
tweed32:~ # uname -a
Linux tweed32 6.3.0-rc2-x86-32-debug+ #32 SMP PREEMPT_DYNAMIC Thu Mar 16
18:09:49 CET 2023 i686 athlon i386 GNU/Linux
tweed32:~ # modinfo axis-fifo
filename: /lib/modules/6.3.0-rc2-x86-32-debug+/kernel/drivers/staging/
axis-fifo/axis-fifo.ko
description: Xilinx AXI-Stream FIFO v4.1 IP core driver
author: Jacob Feder <jacobsfeder@gmail.com>
license: GPL
srcversion: EBF46AD6851EAAE67D1000B
alias: of:N*T*Cxlnx,axi-fifo-mm-s-4.1C*
alias: of:N*T*Cxlnx,axi-fifo-mm-s-4.1
depends:
staging: Y
retpoline: Y
intree: Y
name: axis_fifo
vermagic: 6.3.0-rc2-x86-32-debug+ SMP preempt mod_unload modversions K7
parm: read_timeout:ms to wait before blocking read() timing out; set
to -1 for no timeout (long)
parm: write_timeout:ms to wait before blocking write() timing out;
set to -1 for no timeout (long)
Do you see the "parm" lines? What's the type of read and write_timeout?
Fabio
next prev parent reply other threads:[~2023-03-16 20:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 12:56 [PATCH v5] staging: axis-fifo: initialize timeouts in probe only Khadija Kamran
2023-03-16 13:02 ` Greg Kroah-Hartman
2023-03-16 13:04 ` Greg Kroah-Hartman
2023-03-16 15:12 ` Khadija Kamran
2023-03-16 14:07 ` kernel test robot
2023-03-16 14:38 ` Fabio M. De Francesco
2023-03-16 15:09 ` Khadija Kamran
2023-03-16 16:17 ` Fabio M. De Francesco
2023-03-16 18:17 ` Fabio M. De Francesco
2023-03-16 18:35 ` Khadija Kamran
2023-03-16 20:07 ` Fabio M. De Francesco
2023-03-20 6:00 ` Khadija Kamran
2023-03-20 14:09 ` Fabio M. De Francesco
2023-03-20 6:37 ` Khadija Kamran
2023-03-16 20:17 ` Fabio M. De Francesco [this message]
2023-03-20 6:04 ` Khadija Kamran
2023-03-17 6:59 ` 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=3531852.LM0AJKV5NW@suse \
--to=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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