From: Julia Lawall <julia.lawall@inria.fr>
To: Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
outreachy@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] staging: axis-fifo: initialize timeouts in probe only
Date: Thu, 16 Mar 2023 11:51:23 +0100 (CET) [thread overview]
Message-ID: <d4e16b4-c296-8130-eddd-4de05e426e2@inria.fr> (raw)
In-Reply-To: <ZBLxHyiFnOwEdPYf@khadija-virtual-machine>
On Thu, 16 Mar 2023, Khadija Kamran wrote:
> On Wed, Mar 15, 2023 at 09:09:16AM -0700, Alison Schofield wrote:
> > On Wed, Mar 15, 2023 at 07:22:39PM +0500, Khadija Kamran wrote:
> > > On Wed, Mar 15, 2023 at 02:34:31PM +0100, Fabio M. De Francesco wrote:
> > > > Aside from what I said and asked for with the other message of this same
> > > > thread, please take note that you can build a specific module if you prefer
> > > > not to re-build the whole kernel and other modules at the same time.
> > > >
> > > > I'm pretty sure that the instructions to do so are in the OutreachyFirstPatch
> > > > tutorial.
> > > >
> > > > If they are not there, please let us know.
> > > >
> > > > Fabio
> > >
> > > Hey Fabio!
> > >
> > > In the Outreachy FirstPatchTutorial under the 'Compiling only part of
> > > the kernel' section there are ways to compile only some part of the
> > > kernel.
> > >
> > > I have tried using "make W=1 drivers/staging/axis-fifo/" and it says
> > > 'nothing to be done for'.
> > >
> > > Should I start with the steps to reproduce? :'(
> >
> > Khadija,
> >
> > I've applied your patch and it fails to compile with the warnings
> > that LKP reports.
> >
> > If you are doing: $ make drivers/staging/axis-fifo/
> >
> > and it is saying 'nothing to be done...'
> >
> > You either have not changed anything since the last compile, or you
> > do not have the module configured.
> >
>
> Hey Alison!
> I might've written the statement wrong. Actually, here is the output of
> make drivers/staging/axis-fifo
>
> YACC scripts/genksyms/parse.tab.[ch]
> HOSTCC scripts/genksyms/parse.tab.o
> HOSTCC scripts/genksyms/lex.lex.o
> HOSTLD scripts/genksyms/genksyms
> CC scripts/mod/empty.o
> MKELF scripts/mod/elfconfig.h
> HOSTCC scripts/mod/modpost.o
> CC scripts/mod/devicetable-offsets.s
> HOSTCC scripts/mod/file2alias.o
> HOSTCC scripts/mod/sumversion.o
> HOSTLD scripts/mod/modpost
> CC kernel/bounds.s
> CC arch/x86/kernel/asm-offsets.s
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> INSTALL libsubcmd_headers
> DESCEND bpf/resolve_btfids
> INSTALL libsubcmd_headers
> make[3]: Nothing to be done for 'drivers/staging/axis-fifo/'.
Did you try make allyesconfig and make drivers/staging/axis-fifo/axis-fifo.o
I get no warnings with W=1, but I do get a .o file. I also tried
make drivers/staging/axis-fifo/axis-fifo.i
which just expands macros and simplifies ifdefs, and I see the various
code from the file. So I don't have the impression that it is getting
ifdef'd away in some obscure way. Perhaps I am missing something. Or
perhaps the warning in question only comres from LLVM?
julia
>
>
> > I suspect it has never compiled for you and you need to look at
> > the direction in the tutorial for 'Recompiling the driver' section
> > and learn how to use make menuconfig.
> >
> > This driver has a couple of dependencies described in the Kconfig
> > file. You will not even see the 'XIL_AXIS_FIFO' option until you
> > turn on 'OF' and HAS_'IOMEM'.
> >
> > See the drivers/staging/axis-fifo/Kconfig
> >
> > Please confirm that you have compiled the driver before chasing
> > after the build env that lkp reports.
> >
> > Thanks,
> > Alison
>
> Sorry, I made a mistake here.
>
> I did not change the driver 'Xilinx AXI-Stream FIFO IP core driver' to
> being compiled as a module by typing 'm'.
> Is that the problem here?
>
> Also, now when I try to change it by pressing 'm', it is not working.
> And I have tried many times but I cannot change the driver from '*' to
> 'm'.
>
> Kindly help me with this.
>
> Regards,
> Khadija
>
>
>
>
prev parent reply other threads:[~2023-03-16 10:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 18:07 Khadija Kamran
2023-03-13 19:00 ` kernel test robot
2023-03-14 3:45 ` kernel test robot
2023-03-14 14:08 ` Khadija Kamran
2023-03-14 14:42 ` Nathan Chancellor
2023-03-14 15:13 ` Alison Schofield
2023-03-14 19:07 ` Fabio M. De Francesco
2023-03-14 20:43 ` Alison Schofield
2023-03-14 21:31 ` Fabio M. De Francesco
2023-03-14 23:57 ` Alison Schofield
2023-03-15 12:32 ` Khadija Kamran
2023-03-15 13:13 ` Fabio M. De Francesco
2023-03-15 13:56 ` Khadija Kamran
2023-03-15 16:44 ` Fabio M. De Francesco
2023-03-16 9:50 ` Khadija Kamran
2023-03-16 11:13 ` Fabio M. De Francesco
2023-03-16 12:03 ` Khadija Kamran
2023-03-15 13:34 ` Fabio M. De Francesco
2023-03-15 14:22 ` Khadija Kamran
2023-03-15 15:06 ` Nathan Chancellor
2023-03-15 16:24 ` Fabio M. De Francesco
2023-03-16 10:17 ` Khadija Kamran
2023-03-16 11:39 ` Fabio M. De Francesco
2023-03-16 11:55 ` Khadija Kamran
2023-03-16 7:40 ` Julia Lawall
2023-03-16 10:47 ` Khadija Kamran
2023-03-16 11:41 ` Khadija Kamran
2023-03-15 16:09 ` Alison Schofield
2023-03-15 16:42 ` Khadija Kamran
2023-03-16 10:36 ` Khadija Kamran
2023-03-16 10:51 ` Julia Lawall [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=d4e16b4-c296-8130-eddd-4de05e426e2@inria.fr \
--to=julia.lawall@inria.fr \
--cc=alison.schofield@intel.com \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nathan@kernel.org \
--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
all inboxes | Powered by JetHome®