From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bruno <codeagain@codeagain.dev>
Cc: Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: vme: Adjusted VME_USER in Kconfig
Date: Sun, 3 Apr 2022 13:05:44 +0200 [thread overview]
Message-ID: <Ykl/iBR+pDaaLImA@kroah.com> (raw)
In-Reply-To: <37e5203d1efd310ea82cf91c18c6a07eea743ac7.camel@codeagain.dev>
You sent this twice?
Anyway...
On Fri, Apr 01, 2022 at 03:21:50PM -0300, Bruno wrote:
> With my tests in my, I have found two other things that I think are
> remarkable to mention. First one is a missing `depends on` line for
> `VME_BRIDGE` in drivers/staging/vme/devices/Kconfig, not visible
> because they were in the same tree, but now unveiled. I'm fixing it,
> do you think it's best to add it in the same patch?
Make that a second patch, and resend it as part of a patch series since
your first patch here is gone from my queue.
> Finally, not directly related with the patch, yet remarkable, I
> happened to notice something. When probing the vme_user module
> (compiled with CONFIG_VME_USER=m), I naturally get the following
> messages on my log and command output for `modprobe vme_user`:
> | [177666.590400] vme_user: module is from the staging directory, the
> quality is unknown, you have been warned.
That is expected.
> While this is completely expected, the message about the code from
> staging directory does not appear when compiled with
> CONFIG_VME_USER=y, as shows a `grep -i vme` on the console log:
That is because you built the driver into the tree, so there is nothing
to cause the taint code to run as there is no module loader involved.
It's expected and works the same for all staging drivers. Try it
yourself with a different one to verify this.
> | [0.000000] Linux version 5.17.0lsa-t-vme_user=y-13483-gfeb94431c35c-
> dirty (bruno@AN5Bruno) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.38)
> #7 SMP PREEMPT_DYNAMIC Fri Apr 1 14:33:16 -03 2022
> | [1.974450] vme_user: VME User Space Access Driver
> | [ 1.975405] vme_user: No cards, skipping registration
>
> Do you think it would be interesting for a future patch to provide
> some output when drivers from the staging tree are present in the
> running kernel image?
If you can figure out how to do so, that would be interesting to see.
thanks,
greg k-h
next prev parent reply other threads:[~2022-04-03 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 5:00 [PATCH] staging: vme: Adjusted VME_USER in Kconfig Bruno Moreira-Guedes
2022-04-01 6:08 ` reg Kroah-Hartman
2022-04-01 6:10 ` reg Kroah-Hartman
2022-04-01 18:21 ` Bruno
2022-04-03 11:05 ` Greg Kroah-Hartman [this message]
2022-04-12 15:14 ` Bruno Moreira-Guedes
2022-04-12 15:54 ` Greg Kroah-Hartman
2022-04-01 19:26 ` Bruno Moreira-Guedes
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=Ykl/iBR+pDaaLImA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=codeagain@codeagain.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--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;
as well as URLs for NNTP newsgroup(s).