From: Olof Johansson <olof@lixom.net>
To: Maxime Ripard <mripard@kernel.org>
Cc: soc@kernel.org, arm@kernel.org, Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Allwinner arm64 Defconfig Changes for 5.6
Date: Fri, 10 Jan 2020 22:23:49 -0800 [thread overview]
Message-ID: <20200111062349.esn2rfeppbt4b5kv@localhost> (raw)
In-Reply-To: <3b09a9b4-9d46-4f05-9c4d-420b93f0f88b.lettre@localhost>
On Fri, Jan 10, 2020 at 06:13:57PM +0100, Maxime Ripard wrote:
> Hi,
>
> Please pull the following changes for the next release.
>
> Thanks!
> Maxime
>
> The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
>
> Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-config64-for-5.6
>
> for you to fetch changes up to cb4132672f76954ddc234aa343b4d2a1f1b8437a:
>
> arm64: defconfig: Enable DRM_SUN6I_DSI (2020-01-02 10:30:35 +0100)
>
> ----------------------------------------------------------------
> Two patches to enable the new thermal sensor driver found on newer
> Allwinner SoCs and to enable the MIPI-DSI controller.
This adds a SUN8I_THERMAL that I can't find in the tree? (this also goes for
the 32-bit branch)
Also, is there a reason to have it =y, or would =m suffice? I see that RCAR is
=y, but we should revisit that as well.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-11 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 17:13 [GIT PULL] Allwinner arm64 Defconfig Changes for 5.6 Maxime Ripard
2020-01-11 6:23 ` Olof Johansson [this message]
2020-01-11 9:09 ` Maxime Ripard
2020-01-11 22:58 ` Olof Johansson
2020-01-12 11:47 ` Maxime Ripard
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=20200111062349.esn2rfeppbt4b5kv@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=soc@kernel.org \
--cc=wens@csie.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.