From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
Date: Sun, 2 Jul 2023 15:05:25 +0200 [thread overview]
Message-ID: <ae400e28-0cd4-cdf8-811d-843e62cd4a95@gmail.com> (raw)
In-Reply-To: <2023070254-embark-subplot-4dd4@gregkh>
Hi,
Le 02/07/2023 à 14:02, Greg Kroah-Hartman a écrit :
> On Sun, Jul 02, 2023 at 10:03:24AM +0200, Raphael Gallais-Pou wrote:
>> Using FBTFT_REGISTER_DRIVER resolves to a NULL struct spi_device_id. This
>> ultimately causes the module to an early exit at probe time.
>
> So this doesn't work at all today? Has it ever worked? What commit
> does thi fix?
I tested again with only a tweak in my device-tree. The early exit in
the driver's code is caused by a missing field. So regarding this
particular driver the macro works.
It resolves to set spi_driver.id_table = NULL, which yields a warning in
__spi_register_driver(). So I guess this patch only fixes a warning.
>
>> In addition the MODULE_ALIASes can be dropped.
>
> Why? When you say "also" or "in addition", that's a huge hint it should
> be a separate patch.
I did not find any reference to those aliases in the kernel, which led
me to remove those.
If you think they are still necessary, I'll split them in an upcoming v2.
Thanks for your insights,
Raphaël
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-07-02 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 8:03 [PATCH] staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER Raphael Gallais-Pou
2023-07-02 12:02 ` Greg Kroah-Hartman
2023-07-02 13:05 ` Raphaël Gallais-Pou [this message]
2023-07-03 13:25 ` Greg Kroah-Hartman
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=ae400e28-0cd4-cdf8-811d-843e62cd4a95@gmail.com \
--to=rgallaispou@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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).