All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
	Leif Lindholm <leif@nuviainc.com>,
	Grant Likely <grant.likely@arm.com>,
	grub-devel@gnu.org, Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ard Biesheuvel <ardb@kernel.org>,
	Nikita Ermakov <arei@altlinux.org>
Subject: Re: [PATCH 0/2] efi: device tree fix-up
Date: Fri, 13 Aug 2021 18:22:49 +0200	[thread overview]
Message-ID: <67c43f0c-ff15-26d3-06a1-e00a553c0a07@canonical.com> (raw)
In-Reply-To: <20210802151842.2ycunjvbuulvwb34@tomti.i.net-space.pl>

On 8/2/21 5:18 PM, Daniel Kiper wrote:
> Hi Heinrich,
> 
> On Mon, Aug 02, 2021 at 03:00:55PM +0200, Heinrich Schuchardt wrote:
>> Hello Daniel,
>>
>> I sent this series when you were in the middle of getting GRUB-2.06 out.
>> Unfortunately I did not see any feedback yet. Could you, please, share your
>> thoughts.
> 
> Sure, I will try to do that next week.
> 
> Daniel
> 

The series conflicts with the RISC-V series patch
"linux: ignore FDT unless we need to modify it"
https://lists.gnu.org/archive/html/grub-devel/2021-06/msg00010.html

My priority would be to have the RISC-V series merged first. Then I can 
rebase my series upon it.

But anyhow feedback for the concept of devicetree fixups will be helpful.

Best regards

Heinrich





  reply	other threads:[~2021-08-13 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 13:15 [PATCH 0/2] efi: device tree fix-up Heinrich Schuchardt
2021-02-04 13:15 ` [PATCH 1/2] efi: EFI Device Tree Fixup Protocol Heinrich Schuchardt
2021-02-04 13:15 ` [PATCH 2/2] 10_linux: support loading device trees Heinrich Schuchardt
2021-08-02 13:00 ` [PATCH 0/2] efi: device tree fix-up Heinrich Schuchardt
2021-08-02 15:18   ` Daniel Kiper
2021-08-13 16:22     ` Heinrich Schuchardt [this message]
2021-08-13 20:22       ` Daniel Kiper
2021-08-13 22:38         ` Heinrich Schuchardt
2021-08-16  7:04           ` Ard Biesheuvel
2021-08-16  8:58             ` Heinrich Schuchardt
2021-08-16  9:26               ` Ard Biesheuvel

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=67c43f0c-ff15-26d3-06a1-e00a553c0a07@canonical.com \
    --to=heinrich.schuchardt@canonical.com \
    --cc=ardb@kernel.org \
    --cc=arei@altlinux.org \
    --cc=daniel.kiper@oracle.com \
    --cc=dkiper@net-space.pl \
    --cc=grant.likely@arm.com \
    --cc=grub-devel@gnu.org \
    --cc=leif@nuviainc.com \
    --cc=xypron.glpk@gmx.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 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.