From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Yang Chen <yangchen.openbmc@gmail.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
patrick@stwcx.xyz, amithash@meta.com
Cc: Jerry.Lin@quantatw.com, yang.chen@quantatw.com
Subject: Re: [PATCH v1 0/4] Revise Meta (Facebook) Minerva BMC
Date: Fri, 13 Dec 2024 12:13:00 +0100 [thread overview]
Message-ID: <17435684-a1f5-44cd-ac25-7e8efe88c754@linaro.org> (raw)
In-Reply-To: <20241212133226.342937-1-yangchen.openbmc@gmail.com>
On 12/12/2024 14:32, Yang Chen wrote:
> Revise the linux device tree entry related to Meta (Facebook) Minerva
> specific devices connected to BMC (AST2600) SoC.
>
> Base on:
> https://lore.kernel.org/all/172722509817.374662.7338401100529556748.b4-ty@codeconstruct.com.au/
>
I don't believe. You are working on some old kernel. There is no way you
can get my address like this. It's impossible.
Form letter:
You CC-ed an address, which suggests you do not work on mainline kernel
or you do not use get_maintainers.pl/b4/patman. Please rebase and always
work on mainline or start using mentioned tools, so correct addresses
will be used.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-12-13 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 13:32 Yang Chen
2024-12-12 13:32 ` [PATCH v1 1/4] ARM: dts: aspeed: minerva: add i/o expanders on bus 0 Yang Chen
2024-12-12 13:32 ` [PATCH v1 2/4] ARM: dts: aspeed: minerva: add i/o expanders on each FCB Yang Chen
2024-12-12 13:32 ` [PATCH v1 3/4] ARM: dts: aspeed: minerva: add bmc ready led setting Yang Chen
2024-12-12 13:32 ` [PATCH v1 4/4] ARM: dts: aspeed: minerva: add second source RTC Yang Chen
2024-12-13 5:28 ` [PATCH v1 0/4] Revise Meta (Facebook) Minerva BMC Andrew Jeffery
2024-12-13 11:13 ` Krzysztof Kozlowski [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=17435684-a1f5-44cd-ac25-7e8efe88c754@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Jerry.Lin@quantatw.com \
--cc=amithash@meta.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=robh+dt@kernel.org \
--cc=yang.chen@quantatw.com \
--cc=yangchen.openbmc@gmail.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®