mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "liuyuntao (F)" <liuyuntao12@huawei.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Russell King <linux@armlinux.org.uk>,
	Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Fangrui Song <maskray@google.com>, <geert@linux-m68k.org>,
	<afd@ti.com>, <akpm@linux-foundation.org>,
	<kirill.shutemov@linux.intel.com>, <geert+renesas@glider.be>,
	<corbet@lwn.net>, <rppt@kernel.org>, <robh@kernel.org>,
	<tglx@linutronix.de>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-next v4] arm32: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION
Date: Mon, 3 Jun 2024 22:15:05 +0800	[thread overview]
Message-ID: <daeb2b80-98d6-44c1-9045-3a3fb087b858@huawei.com> (raw)
In-Reply-To: <CACRpkdYJkyqc5PkwTEdC=inqFHvZS4J9AoJOnBzxDB+wU6bZcg@mail.gmail.com>

OK.
Thanks~

On 2024/6/3 21:47, Linus Walleij wrote:
> Hi liuyuntao,
> 
> On Mon, Jun 3, 2024 at 2:55 PM liuyuntao (F) <liuyuntao12@huawei.com> wrote:
> 
>> Gentle ping
> 
> FWIW:
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> 
> I see you put versions into Russell's patch tracker, but please mark
> these as "superseded" (you can do this in the web UI) and put in this
> version of the patch based on v6.10-rc1 and tested. Basing on the
> -rc1 is usually best for development work.
> 
> Yours,
> Linus Walleij

  reply	other threads:[~2024-06-03 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16  2:39 Yuntao Liu
2024-03-19 17:12 ` Ard Biesheuvel
2024-06-03 12:55   ` liuyuntao (F)
2024-06-03 13:47     ` Linus Walleij
2024-06-03 14:15       ` liuyuntao (F) [this message]
2024-06-11 12:45 ` Geert Uytterhoeven
2024-06-12  1:54   ` liuyuntao (F)

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=daeb2b80-98d6-44c1-9045-3a3fb087b858@huawei.com \
    --to=liuyuntao12@huawei.com \
    --cc=afd@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maskray@google.com \
    --cc=robh@kernel.org \
    --cc=rppt@kernel.org \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®