u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: "Csókás Bence" <csokas.bence@prolan.hu>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Dan Carpenter <dan.carpenter@linaro.org>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
	"Andrew Davis" <afd@ti.com>,
	Andre Przywara <andre.przywara@arm.com>,
	Bin Meng <bmeng@tinylab.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Fabio Estevam <festevam@denx.de>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	Yang Xiwen <forbidden405@outlook.com>,
	Peng Fan <peng.fan@nxp.com>, <u-boot@lists.denx.de>,
	Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
Subject: Re: [PATCH v2 2/2] arm64: Enable CONFIG_64BIT for static analysis
Date: Mon, 4 Mar 2024 15:11:04 +0100	[thread overview]
Message-ID: <007f1c98-4871-49d6-b601-4766ff45e20c@prolan.hu> (raw)
In-Reply-To: <6907b26a-9eb2-4ffd-8337-50ee96155c05@canonical.com>

2024. 03. 04. 14:44 keltezéssel, Heinrich Schuchardt írta> How about 
other 64bit architectures (sandbox64, x86_64)?

I think that could be its own patchset.

> Best regards
> 
> Heinrich

Bence

P.S., does anyone know why I'm being CC'ed here? Did I participate in 
this thread at some point? I only remember contributing to lib/rsa and 
also a small patch to arch/arm/lib/vectors.S. Maybe because the latter 
touched arch/arm/Kconfig as well, so now I should expect to get loads of 
mail for a month or two?


  reply	other threads:[~2024-03-04 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  7:03 [PATCH v2 0/2] arm64: Enable CONFIG_64BIT for static analysis Dan Carpenter
2024-03-04  7:04 ` [PATCH v2 1/2] Kconfig: move CONFIG_32/64BIT to arch/Kconfig Dan Carpenter
2024-03-04 14:16   ` Tom Rini
2024-03-14  0:38   ` Tom Rini
2024-03-04  7:04 ` [PATCH v2 2/2] arm64: Enable CONFIG_64BIT for static analysis Dan Carpenter
2024-03-04 13:44   ` Heinrich Schuchardt
2024-03-04 14:11     ` Csókás Bence [this message]
2024-03-04 14:16       ` Tom Rini
2024-03-04 14:27     ` Dan Carpenter
2024-03-14  0:38   ` Tom Rini

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=007f1c98-4871-49d6-b601-4766ff45e20c@prolan.hu \
    --to=csokas.bence@prolan.hu \
    --cc=afd@ti.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=bmeng@tinylab.org \
    --cc=dan.carpenter@linaro.org \
    --cc=festevam@denx.de \
    --cc=forbidden405@outlook.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=linus.walleij@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=rayagonda.kokatanur@broadcom.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).