From: Florian Fainelli <florian.fainelli@broadcom.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Linus Walleij <linus.walleij@linaro.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org (open list:PIN CONTROL SUBSYSTEM),
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
IPROC ARM ARCHITECTURE)
Subject: [PATCH 0/2 v2] pinctrl: bcm: Use dev_err_probe()
Date: Tue, 8 Aug 2023 11:07:31 -0700 [thread overview]
Message-ID: <20230808180733.2081353-1-florian.fainelli@broadcom.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 496 bytes --]
These two drivers were giving "unable to add GPIO chip data" which
was slightly concerning but did not have any functional impact.
Changes in v2:
- return from dev_err_probe() directly (Andy)
Florian Fainelli (2):
pinctrl: iproc-gpio: Silence probe deferral messages
pinctrl: nsp-gpio: Silence probe deferral messages
drivers/pinctrl/bcm/pinctrl-iproc-gpio.c | 6 ++----
drivers/pinctrl/bcm/pinctrl-nsp-gpio.c | 6 ++----
2 files changed, 4 insertions(+), 8 deletions(-)
--
2.34.1
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-08-08 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 18:07 Florian Fainelli [this message]
2023-08-08 18:07 ` [PATCH 1/2 v2] pinctrl: iproc-gpio: Silence probe deferral messages Florian Fainelli
2023-08-10 8:41 ` Linus Walleij
2023-08-08 18:07 ` [PATCH 2/2 v2] pinctrl: nsp-gpio: " Florian Fainelli
2023-08-10 8:41 ` Linus Walleij
2023-08-09 5:45 ` [PATCH 0/2 v2] pinctrl: bcm: Use dev_err_probe() Dhruva Gole
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=20230808180733.2081353-1-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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