From: Thierry Reding <thierry.reding@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-pwm@vger.kernel.org
Subject: Re: [PATCH] pwm: Fix compile error in pwm_get()
Date: Fri, 10 Feb 2017 15:23:12 +0100 [thread overview]
Message-ID: <20170210142312.GA10204@ulmo.ba.sec> (raw)
In-Reply-To: <20170210114430.21512-1-hdegoede@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On Fri, Feb 10, 2017 at 12:44:30PM +0100, Hans de Goede wrote:
> commit bf71f4e8fb95 ("pwm: Try to load modules during pwm_get()") had
> error checking added to the request_module call it adds, before merging
> it. But the "err" variable the error checking uses was never declared,
> this commit fixes this.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> Feel free to squash this into the original commit
> ---
> drivers/pwm/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
You had me really confused there for a little bit. Turns out I had two
versions of that patch in my tree, one with the missing variable
declaration and another where I had already added it after build tests
had failed. The old patch stuck around because it was part of a branch
that I had created in case anyone wanted to pull this into the ACPI
tree to resolve dependencies and I had forgotten to rebase that branch
onto the fixed patch.
I've pushed a new set of branches, so this confusion should be gone by
tomorrow. It's a little odd that you even saw this failing to build,
since none of the farms seemed to have noticed, and the file in
linux-next is actually the correct one.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-02-10 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 11:44 [PATCH] pwm: Fix compile error in pwm_get() Hans de Goede
2017-02-10 14:23 ` Thierry Reding [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=20170210142312.GA10204@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-pwm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.