Linux SOC development
 help / color / mirror / Atom feed
From: Carsten Haitzler <carsten.haitzler@foss.arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: defconfig: Enable modules for arm displays
Date: Tue, 10 May 2022 13:42:35 +0100	[thread overview]
Message-ID: <199b8faf-71a7-e954-cec0-229d46d4cef0@foss.arm.com> (raw)
In-Reply-To: <CAK8P3a2dx+qV_LmbtveD8kEi9LhRSXBvgQ-a63bRcXB=niGOfg@mail.gmail.com>



On 5/9/22 15:34, Arnd Bergmann wrote:
> On Wed, Apr 27, 2022 at 1:42 PM <carsten.haitzler@foss.arm.com> wrote:
>>
>> Key devices that support displays on SoCs like the Komeda DRM driver, the
>> older HDLCD were not enabled by default and should be so displays can work
>> out of the box on defconfig. Also Candence I2C support should be enabled so
>> the PHY and thus displays can work too.
>>
>> Signed-off-by: Carsten Haitzler <carsten.haitzler@arm.com>
> 
> I applied this patch on Apr 27 after you first sent it. There is normally an
> automated confirmation email after it gets uploaded, but I think this did not
> happen here because there was a small context mismatch -- the patch
> still applied but patchwork did not detect it.

Aaaah cool. Sorry - I was hunting it down in git trees and didn't find 
it... never mind the follow-on mails then. :)

  reply	other threads:[~2022-05-10 12:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 11:42 [PATCH] arm64: defconfig: Enable modules for arm displays carsten.haitzler
2022-05-09 14:34 ` Arnd Bergmann
2022-05-10 12:42   ` Carsten Haitzler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-09 12:55 carsten.haitzler
2022-05-10 11:15 ` Sudeep Holla
2022-05-10 11:27   ` Mark Brown
2022-05-10 11:56     ` Robin Murphy
2022-05-10 12:01       ` Sudeep Holla
2022-05-10 12:07     ` Sudeep Holla
2022-05-10 12:34       ` Carsten Haitzler
2022-05-10 14:51         ` Sudeep Holla
2022-05-10 14:53           ` Carsten Haitzler
2022-05-10 12:55   ` Liviu Dudau
2022-05-10 13:05     ` Mark Brown
2022-05-10 14:05       ` Carsten Haitzler
2022-05-10 16:19         ` Liviu Dudau
2022-05-10 16:31           ` Mark Brown
2022-05-10 20:06             ` Liviu Dudau
2022-05-11 13:13               ` Mark Brown
2022-05-11 13:15                 ` Carsten Haitzler
2022-05-11 11:00             ` Carsten Haitzler

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=199b8faf-71a7-e954-cec0-229d46d4cef0@foss.arm.com \
    --to=carsten.haitzler@foss.arm.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox