From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pcmcia: sa1111: fix propagation of lowlevel board init return code
Date: Fri, 02 Sep 2016 19:58:04 +0200 [thread overview]
Message-ID: <87eg52kwur.fsf@belgarion.home> (raw)
In-Reply-To: <E1bfnCj-0006HT-12@rmk-PC.armlinux.org.uk> (Russell King's message of "Fri, 02 Sep 2016 13:04:17 +0100")
Russell King <rmk+kernel@armlinux.org.uk> writes:
> When testing Lubbock, it was noticed that the sa1111 pcmcia driver bound
> but was not functional due to no sockets being registered. This is
> because the return code from the lowlevel board initialisation was not
> being propagated out of the probe function. Fix this.
>
> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> ---
> Robert,
>
> I'd prefer this solution. Please check that it resolves your issue,
> thanks.
Excellent, tested it without the clock fix on lubbock, and the error message is
there.
Tested-by: Robert Jarzmik <robert.jarzmik@free.fr>
Cheers.
--
Robert
prev parent reply other threads:[~2016-09-02 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 12:04 [PATCH] pcmcia: sa1111: fix propagation of lowlevel board init return code Russell King
2016-09-02 17:58 ` Robert Jarzmik [this message]
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=87eg52kwur.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/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