mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Martino Dell'Ambrogio <tillo@tillo.ch>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kees@kernel.org,
	tony.luck@intel.com, gpiccoli@igalia.com
Subject: Re: [PATCH v5] arm64: dts: mediatek: mt7986a-bananapi-bpi-r3: add ramoops region
Date: Tue, 15 Sep 2026 16:20:07 +0200	[thread overview]
Message-ID: <2203bb2b-9490-4d2b-8ec0-bebaaa9148b6@collabora.com> (raw)
In-Reply-To: <20260915155333.821189-1-tillo@tillo.ch>

On 9/15/26 15:53, Martino Dell'Ambrogio wrote:
> On 9/15/26 15:27, AngeloGioacchino Del Regno wrote:
>> You forgot to send the 7988a bpi-r4 patch :-)
> 
> It did go out - as v4 rather than v5, which is probably what threw the search
> off. Only the BPI-R3 needed the v5 respin, because its v4 accidentally carried
> the BPI-R4's values. The BPI-R4 patch was already correct at v4, so it stands
> as sent, and it does carry the plain reserved-memory node you asked for:
> 
>    https://lore.kernel.org/all/20260915135722.566918-1-tillo@tillo.ch/
> 
> Same To/Cc as this one, sent 13:57 CEST, five seconds before the R3 v4.
> Patchwork picked it up as 14818166 in the Linux-Mediatek project.
> 
> Happy to resend it if that is easier than fishing it out of the archive.
> 
> And thank you for applying the BPI-R3 one.
> 
> Martino

You're right. For whatever reason, it didn't reach my inbox.. go figure.

I applied the other one as well, thanks for sending!

Cheers,
Angelo

      reply	other threads:[~2026-09-15 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 12:12 Martino Dell'Ambrogio
2026-09-15 13:25 ` AngeloGioacchino Del Regno
2026-09-15 13:27 ` AngeloGioacchino Del Regno
2026-09-15 13:53   ` Martino Dell'Ambrogio
2026-09-15 14:20     ` AngeloGioacchino Del Regno [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=2203bb2b-9490-4d2b-8ec0-bebaaa9148b6@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gpiccoli@igalia.com \
    --cc=kees@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=tillo@tillo.ch \
    --cc=tony.luck@intel.com \
    /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

all inboxes | Powered by JetHome®