From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mediatek fixes for v4.17
Date: Tue, 29 May 2018 15:46:02 +0200 [thread overview]
Message-ID: <3c61a698-cc38-cb3d-78cc-62562872e8d4@gmail.com> (raw)
In-Reply-To: <b32962c3-2ede-b352-959d-cb0c5244307f@gmail.com>
On 29/05/18 13:29, Matthias Brugger wrote:
> Hi Olof, hi Arnd,
>
> We observe boot issues on mt7622 with v4.17
> The following fix addresses this. Could you please merge this so that we have
> working v4.17 on the mt7622 :)
Just FYI, I sent the very same commit via v4.17-next-defconfig pull request, but
it would be good if it could go into v4.17 already so we don't have to wait
until it is merged thorough the stable process.
Regards,
Matthias
>
> Thanks a lot,
> Matthias
>
> ---
>
> The following changes since commit b04e217704b7f879c6b91222b066983a44a7a09f:
>
> Linux 4.17-rc7 (2018-05-27 13:01:47 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
> tags/v4.17-next-fixes
>
> for you to fetch changes up to eac2e79a02a2c92c09600162d02167d8dfb63d66:
>
> arm64: defconfig: Enable CONFIG_PINCTRL_MT7622 by default (2018-05-29 13:19:49
> +0200)
>
> ----------------------------------------------------------------
> mt7622 enable pinctrl driver in defconfig to fix boot issue
>
> ----------------------------------------------------------------
> Sean Wang (1):
> arm64: defconfig: Enable CONFIG_PINCTRL_MT7622 by default
>
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
prev parent reply other threads:[~2018-05-29 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 11:29 [GIT PULL] ARM: mediatek fixes for v4.17 Matthias Brugger
2018-05-29 13:46 ` Matthias Brugger [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=3c61a698-cc38-cb3d-78cc-62562872e8d4@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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