All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Youling Tang <tangyouling@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	Xi Ruoyao <xry111@xry111.site>,
	 Huacai Chen <chenhuacai@loongson.cn>,
	Arnd Bergmann <arnd@arndb.de>,
	loongarch@lists.linux.dev,
	 linux-arch <linux-arch@vger.kernel.org>,
	Xuefeng Li <lixuefeng@loongson.cn>,  Guo Ren <guoren@kernel.org>,
	Xuerui Wang <kernel@xen0n.name>,
	 Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-efi <linux-efi@vger.kernel.org>,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] LoongArch: Add efistub booting support
Date: Mon, 5 Sep 2022 09:04:30 +0200	[thread overview]
Message-ID: <CAMj1kXEj_4amyccrHu40i6XTrSX9bxZdXL=8aY=AD9QT-2JmDw@mail.gmail.com> (raw)
In-Reply-To: <2772310e-a537-a733-c7c1-be3ff243d2fe@loongson.cn>

On Mon, 5 Sept 2022 at 08:29, Youling Tang <tangyouling@loongson.cn> wrote:
>
> Hi, Ard & Huacai
>
> While applying this patch [1] we need to add vmlinuz* (vmlinuz and
> vmlinuz.efi) to arch/loongarch/boot/.gitignore to ignore the generated
> binary (also required for arm64 and riscv).
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/commit/?h=efi-decompressor-v4&id=efcc03a013f2ddbed0ee782e5049b39432dc9db2
>

Good point. I'll add that.

  reply	other threads:[~2022-09-05  7:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 10:20 [PATCH V3] LoongArch: Add efistub booting support Huacai Chen
2022-08-22 10:44 ` Ard Biesheuvel
2022-08-22 18:03   ` Ard Biesheuvel
2022-08-23  3:11     ` Huacai Chen
     [not found]       ` <CAAhV-H7-JGGjcFBenpwUz1itZvFK9f1pH88b1dcRtPcGKToojA@mail.gmail.com>
     [not found]         ` <CAMj1kXFEaM7KULxygTABRXB2HHnmRbpSq4N3Q4bYaPOtJxEN2g@mail.gmail.com>
     [not found]           ` <CAAhV-H4CuCSTv8G+bBy52P7kWEc9mapatJ-83mrLYmozG+5SXA@mail.gmail.com>
     [not found]             ` <CAMj1kXF8u=M6R_9pCciY+5oWj6VbLcMEFFC=JYQm5aq1-c8eRg@mail.gmail.com>
2022-08-25  9:47               ` Huacai Chen
2022-08-25  9:51                 ` Ard Biesheuvel
2022-08-25 10:13                   ` Feiyang Chen
2022-08-25 10:22                     ` Ard Biesheuvel
2022-08-25 11:54                   ` Huacai Chen
2022-08-23  2:04   ` Huacai Chen
2022-08-27  4:41 ` Xi Ruoyao
2022-08-27  7:13   ` Ard Biesheuvel
2022-09-01 10:40     ` Huacai Chen
2022-09-04 13:24       ` Huacai Chen
2022-09-04 21:59         ` Ard Biesheuvel
2022-09-05  3:50           ` Huacai Chen
2022-09-05  4:34             ` Youling Tang
2022-09-05  6:28               ` Youling Tang
2022-09-05  7:04                 ` Ard Biesheuvel [this message]
2022-09-05  7:03               ` Ard Biesheuvel
2022-09-05  7:02             ` Ard Biesheuvel
2022-09-05  7:24               ` Huacai Chen
2022-09-05  7:28                 ` Ard Biesheuvel
2022-09-05 18:07                   ` WANG Xuerui
2022-09-05 18:35                     ` Ard Biesheuvel
2022-09-05  7:34                 ` Youling Tang

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='CAMj1kXEj_4amyccrHu40i6XTrSX9bxZdXL=8aY=AD9QT-2JmDw@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=chenhuacai@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=guoren@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=loongarch@lists.linux.dev \
    --cc=tangyouling@loongson.cn \
    --cc=xry111@xry111.site \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.