From: Sean Young <sean@mess.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Ravi Kumar V <kumarrav@codeaurora.org>,
"open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB)"
<linux-media@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Matthew Lear <matthew.lear@broadcom.com>
Subject: Re: [PATCH v2 0/2] Correct gpio-ir-recv wakeup capability
Date: Tue, 4 Apr 2023 08:57:10 +0100 [thread overview]
Message-ID: <ZCvYVoH96pINE+4I@gofer.mess.org> (raw)
In-Reply-To: <4cea1e91-f0d4-291f-813d-353f8b9d2a5e@gmail.com>
On Mon, Apr 03, 2023 at 03:06:44PM -0700, Florian Fainelli wrote:
> On 3/24/23 13:38, Florian Fainelli wrote:
> > This small patch series fixes the gpio-ir-recv binding and driver to
> > first indicate that it can be a wake-up source for the system, and
> > second actually make that happen.
> >
> > Changes in v2:
> > - corrected the indentation of the description for "wakeup-source"
> >
> > Florian Fainelli (2):
> > dt-bindings: media: gpio-ir-receiver: Document wakeup-souce property
> > media: rc: gpio-ir-recv: Fix support for wake-up
>
> Ping? Someone maintaining this driver?
That's me :) Applied, thanks for the reminder.
Sean
prev parent reply other threads:[~2023-04-04 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 20:38 Florian Fainelli
2023-03-24 20:38 ` [PATCH v2 1/2] dt-bindings: media: gpio-ir-receiver: Document wakeup-souce property Florian Fainelli
2023-03-25 11:18 ` Krzysztof Kozlowski
2023-03-24 20:38 ` [PATCH v2 2/2] media: rc: gpio-ir-recv: Fix support for wake-up Florian Fainelli
2023-04-03 22:06 ` [PATCH v2 0/2] Correct gpio-ir-recv wakeup capability Florian Fainelli
2023-04-04 7:57 ` Sean Young [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=ZCvYVoH96pINE+4I@gofer.mess.org \
--to=sean@mess.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kumarrav@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.lear@broadcom.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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
all inboxes | Powered by JetHome®