From: "Arnd Bergmann" <arnd@arndb.de>
To: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>, arm <arm@kernel.org>,
soc <soc@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org
Subject: Re: [GIT,PULL,1/2] MediaTek ARM64 Device Tree fixes for v6.9
Date: Tue, 30 Apr 2024 08:40:33 +0200 [thread overview]
Message-ID: <dc4975fa-82ae-4b2b-94f2-c518595f8694@app.fastmail.com> (raw)
In-Reply-To: <20240423102915.371782-1-angelogioacchino.delregno@collabora.com>
On Tue, Apr 23, 2024, at 12:28, AngeloGioacchino Del Regno wrote:
> The following changes since commit 4cece764965020c22cff7665b18a012006359095:
>
> Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
>
> are available in the Git repository at:
>
>
> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git/
> tags/mtk-dts64-fixes-for-v6.9
Just FYI, these were both merged into v6.9-rc6, but you got
no automated notification because I had to merge them manually
into the arm/fixes branch.
The problem here was the ssh://git@gitolite.k.o/ address, which
does not get picked up by the automated tooling, and I see your
later pull requests have the correct https:// address instead.
Arnd
_______________________________________________
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:[~2024-04-30 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:28 [GIT,PULL,1/2] MediaTek ARM64 Device Tree fixes for v6.9 AngeloGioacchino Del Regno
2024-04-23 10:28 ` [GIT,PULL,2/2] MediaTek driver " AngeloGioacchino Del Regno
2024-04-30 6:40 ` Arnd Bergmann [this message]
2024-04-30 7:55 ` [GIT,PULL,1/2] MediaTek ARM64 Device Tree " AngeloGioacchino Del Regno
2024-04-30 8:06 ` Arnd Bergmann
2024-04-30 8:12 ` AngeloGioacchino Del Regno
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=dc4975fa-82ae-4b2b-94f2-c518595f8694@app.fastmail.com \
--to=arnd@arndb.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@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