From: Merlijn Wajer <merlijn@wizzup.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Dev Null <devnull@uvos.xyz>, Pavel Machek <pavel@ucw.cz>,
Tony Lindgren <tony@atomide.com>
Subject: Re: Nokia N900 increased power draw with panel-sony-acx565akm loaded v5.9 and v5.10
Date: Fri, 10 Dec 2021 21:30:37 +0100 [thread overview]
Message-ID: <9fcbdb66-4183-7431-267b-d0836b6b8cc6@wizzup.org> (raw)
In-Reply-To: <20211210205945.747b2f97@aktux>
Hi Andreas,
On 10/12/2021 20:59, Andreas Kemnade wrote:
> Hi,
>
> On Fri, 10 Dec 2021 20:18:35 +0100
> Merlijn Wajer <merlijn@wizzup.org> wrote:
>
> [...]
>> * 21b2cec61c04bd175f0860d9411a472d5a0e7ba1 (mmc: Set
>> PROBE_PREFER_ASYNCHRONOUS for drivers that existed in v4.4)
>>
> just for the records, I have a fix for that commit which also went into
> stable, so this is not an additional contruction site:
>
> commit ec76c2eea903947202098090bbe07a739b5246e9
> Author: Andreas Kemnade <andreas@kemnade.info>
> Date: Fri Dec 4 10:55:39 2020 +0100
>
> ARM: OMAP2+: omap_device: fix idling of devices during probe
Right - thanks, I was aware of this commit, but for bisect purposes I
decided to just revert offending commits because they weren't relevant
(or so I think at least) to the problem I was trying to debug. So I
wasn't able to use a stable branch for bisecting because the first thing
the bisect would do was throw out the stable fixes.
Regards,
Merlijn
next prev parent reply other threads:[~2021-12-10 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 19:18 Nokia N900 increased power draw with panel-sony-acx565akm loaded v5.9 and v5.10 Merlijn Wajer
2021-12-10 19:59 ` Andreas Kemnade
2021-12-10 20:30 ` Merlijn Wajer [this message]
2021-12-13 13:10 ` Sebastian Reichel
2021-12-16 13:06 ` Merlijn Wajer
2022-01-06 12:53 ` Merlijn Wajer
2022-01-06 16:36 ` Ivaylo Dimitrov
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=9fcbdb66-4183-7431-267b-d0836b6b8cc6@wizzup.org \
--to=merlijn@wizzup.org \
--cc=andreas@kemnade.info \
--cc=devnull@uvos.xyz \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.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 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.