From: Pavel Machek <pavel@ucw.cz>
To: Arnd Bergmann <arnd@kernel.org>, rafael.j.wysocki@intel.com
Cc: Amireddy Mallikarjuna reddy <mallikarjunax.reddy@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>, Dan Murphy <dmurphy@ti.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Intel, please maintain your drivers was Re: [PATCH] leds: lgm: fix gpiolib dependency
Date: Tue, 9 Mar 2021 19:08:51 +0100 [thread overview]
Message-ID: <20210309180851.GA4669@duo.ucw.cz> (raw)
In-Reply-To: <20210308153052.2353885-1-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
Hi!
> From: Arnd Bergmann <arnd@arndb.de>
>
> Without gpiolib, the driver fails to build:
>
> drivers/leds/blink/leds-lgm-sso.c:123:19: error: field has incomplete type 'struct gpio_chip'
> struct gpio_chip chip;
> ^
Thanks, applied.
I'd like people from Intel to contact me. There's more to fix there,
and AFAICT original author went away.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-03-09 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 15:30 [PATCH] leds: lgm: fix gpiolib dependency Arnd Bergmann
2021-03-09 18:08 ` Pavel Machek [this message]
2021-03-09 19:39 ` Intel, please maintain your drivers was " Pavel Machek
2021-03-10 1:19 ` MaxLinear, " Adam Borowski
2021-03-10 7:28 ` Pavel Machek
2021-03-10 16:57 ` Arnd Bergmann
2021-03-10 20:17 ` Hauke Mehrtens
[not found] ` <MN2PR19MB3486B88ADF5BE557BEE168AEAF909@MN2PR19MB3486.namprd19.prod.outlook.com>
[not found] ` <MW2PR1901MB2187816296E1B03F91EB972BD0909@MW2PR1901MB2187.namprd19.prod.outlook.com>
[not found] ` <MN2PR19MB3693B7620DABED199AA304B5B1909@MN2PR19MB3693.namprd19.prod.outlook.com>
2021-03-11 10:00 ` Arnd Bergmann
2021-03-16 9:19 ` Rahul Tanwar
2021-03-13 10:24 ` Pavel Machek
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=20210309180851.GA4669@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mallikarjunax.reddy@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
/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).