public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Khadija Kamran <kamrankhadijadj@gmail.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
	Alison Schofield <alison.schofield@intel.com>,
	outreachy@lists.linux.dev,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: axis-fifo: initialize timeouts in probe only
Date: Thu, 16 Mar 2023 15:17:05 +0500	[thread overview]
Message-ID: <ZBLsoTBeKbuYbhCi@khadija-virtual-machine> (raw)
In-Reply-To: <279821116.9N5E1g01tA@suse>

On Wed, Mar 15, 2023 at 05:24:23PM +0100, Fabio M. De Francesco wrote:
> On mercoledì 15 marzo 2023 16:06:56 CET Nathan Chancellor wrote:
> > Hi Khadija,
> > 
> > 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'.
> > 
> > Is CONFIG_XIL_AXIS_FIFO enabled in your configuration?
> 
> @Khadija:
> 
> Maybe that you won't find CONFIG_XIL_AXIS_FIFO among the staging drivers 
> entries while using "make menuconfig" (or the other similar commands for 
> working with the configuration). 
> 
> In that case, first enable the CONFIG_OF option if disabled. 
> CONFIG_XIL_AXIS_FIFO depends on the former. 
> 
> For "CONFIG_XIL_AXIS_FIFO depends on CONFIG_OF" we mean that you can the 
> former if and only if the latter is already enabled. 
> 
> Actually, CONFIG_XIL_AXIS_FIFO depends also on two other options. However you 
> shouldn't worry about those others because they are commonly enabled in more 
> than 99% of PC distributions.
>

Hey Fabio!

I have checked in my .config file and both options are enabled. The file
says,
CONFIG_OF=y
CONFIG_HAS_IOMEM=y

The "make menuconfig" shows 'Xilinx AXI-Stream FIFO IP core driver' with
built-in selection [*].
The problem I am having here is that in the OutreachyFIrstPatch
tutorial, it asks you to change [*] -> [m], but I cannot change it.

Kindly help me with this!

Thank you!
Regards,
Khadija



> > > Should I start with the steps to reproduce? :'(
> > 
> > I did see a report of this same warning occurring with GCC but the
> > report I commented on cane from clang/LLVM; using that toolchain may
> > make it easier for you to reproduce this issue. The robot's reproduction
> > instructions are fine but I think doing it manually is actually simpler.
> > 
> > Ubuntu 22.04 should have a pretty modern version of clang/LLVM, which
> > you can install via 'sudo apt install clang lld llvm'.
> > https://apt.llvm.org is another resource.
> 
> @Nathan: Congratulations, you now have another clang/LLVM adept!
> (Obviously, I'm just kidding :-))
> 
> Fabio
> 
> 
> 

  reply	other threads:[~2023-03-16 10:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 18:07 [PATCH] staging: axis-fifo: initialize timeouts in probe only 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 [this message]
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

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=ZBLsoTBeKbuYbhCi@khadija-virtual-machine \
    --to=kamrankhadijadj@gmail.com \
    --cc=alison.schofield@intel.com \
    --cc=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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