Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: arm-soc <arm@kernel.org>, soc <soc@kernel.org>,
	 linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com
Subject: Re: [GIT,PULL,1/2] MediaTek ARM64 Device Tree updates for v7.1
Date: Sat, 21 Mar 2026 12:07:56 +0100	[thread overview]
Message-ID: <20260321-aspiring-real-foxhound-4a18e7@quoll> (raw)
In-Reply-To: <20260320085641.15843-1-angelogioacchino.delregno@collabora.com>

On Fri, Mar 20, 2026 at 09:56:38AM +0100, AngeloGioacchino Del Regno wrote:
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git tags/mtk-dts64-for-v7.1
> 
> for you to fetch changes up to 820ed0c1a13c5fafb36232538d793f99a0986ef3:
> 
>   arm64: dts: mediatek: mt7986a: Fix gpio-ranges pin count (2026-03-12 13:32:17 +0100)

Days in linux-next:
----------------------------------------
 0 | +++ (3)

With 0 days in next, you cannot really react on any bug reports.

Please send pull requests for next releast with code being in the next
for at least few next releases.

Best regards,
Krzysztof



  parent reply	other threads:[~2026-03-21 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  8:56 [GIT,PULL,1/2] MediaTek ARM64 Device Tree updates for v7.1 AngeloGioacchino Del Regno
2026-03-20  8:56 ` [GIT,PULL,2/2] MediaTek ARM32 " AngeloGioacchino Del Regno
2026-03-21 11:07 ` Krzysztof Kozlowski [this message]
2026-03-24 13:52   ` [GIT,PULL,1/2] MediaTek ARM64 " AngeloGioacchino Del Regno
2026-03-24 13:54     ` Krzysztof Kozlowski
2026-03-27 11:48 ` Krzysztof Kozlowski

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=20260321-aspiring-real-foxhound-4a18e7@quoll \
    --to=krzk@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --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