linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: Fix IR on Beelink A1
Date: Mon, 06 Jan 2020 15:23:04 +0100	[thread overview]
Message-ID: <12698221.yjhRjYoh56@diego> (raw)
In-Reply-To: <3d0f69d5-739a-0566-b1d7-bc3c2f0c8045@arm.com>

Hi Robin,

Am Mittwoch, 1. Januar 2020, 14:01:32 CET schrieb Robin Murphy:
> On 2019-12-31 11:50 am, Heiko Stuebner wrote:
> > Am Sonntag, 29. Dezember 2019, 18:48:05 CET schrieb Robin Murphy:
> >> Apparently I wasn't paying enough attention... And nor is the lazy
> >> test of `cat /dev/lirc0` sufficiently blunder-proof. Oh well, with
> >> the correct polarity, let's also hook up a keymap now that one for
> >> the standard Beelink remote has handily appeared.
> >>
> >> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> >> ---
> > 
> > applied for 5.6
> 
> Thanks Heiko - although if you have any other fixes to send for 5.5 do 
> you think this might be able to sneak in too? Someone mentioned on IRC 
> that unlike mine, their box wouldn't even generate interrupts with the 
> polarity backwards.

I've moved the patch over to a shiny new fixes branch for 5.5 now :-)

Heiko



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-01-06 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-29 17:48 [PATCH] arm64: dts: rockchip: Fix IR on Beelink A1 Robin Murphy
2019-12-31 11:50 ` Heiko Stuebner
2020-01-01 13:01   ` Robin Murphy
2020-01-06 14:23     ` Heiko Stübner [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=12698221.yjhRjYoh56@diego \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robin.murphy@arm.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).