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 16:55:21 +0500 [thread overview]
Message-ID: <ZBMDqXMWpjNzsf4p@khadija-virtual-machine> (raw)
In-Reply-To: <1902746.IobQ9Gjlxr@suse>
On Thu, Mar 16, 2023 at 12:39:31PM +0100, Fabio M. De Francesco wrote:
> Hi Khadija,
>
> Sorry for being here so late.
>
> I just saw also your other messages with further help requests.
> Please do other work while waiting for help on a specific issue.
>
> If I understand you correctly, you are saying that you can only build axis-
> fifo in-kernel because you cannot change the '*' to 'm'. Correct?
>
Yes, corect.
> If so, you have probably touched other configuration options in a way that
> forces that driver to work only if compiled in-kernel). Therefore, I'd restart
> from scratch.
>
> Please delete your current .config and make a copy of the one from your
> running kernel. Then check the three options Alison and I were talking about.
>
> Remember that you cannot see the axis-fifo module entry (CONFIG_XIL_AXIS_FIFO)
> in "Device Drivers" -> "Staging Drivers" section if you have not yet enabled
> (either with 'm' or 'y') CONFIG_OF and CONFIG_HAS_IOMEM.
>
> Now you should end up with a visible CONFIG_XIL_AXIS_FIFO that can be enabled
> as a module with 'm'.
>
Hey Fabio!
I am on it. I have undertood the steps. I will let you know if this
works.
Also, with the help of Nathan's feedback I was able to reproduce the
warnings. I have changed the files to remove the warnings and it works.
I will submit another [PATCH v5].
Thank you!
Regards,
Khadija Kamran
> Let me know if this procedure works.
>
> Fabio
>
>
next prev parent reply other threads:[~2023-03-16 11:55 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 [this message]
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=ZBMDqXMWpjNzsf4p@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
all inboxes | Powered by JetHome®