Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/spike_riscv64: remove the no longer needed kernel fragment
Date: Thu, 11 Jul 2024 00:01:55 +0200	[thread overview]
Message-ID: <20240711000155.62e892f3@windsurf> (raw)
In-Reply-To: <20240624180519.434061-1-ju.o@free.fr>

On Mon, 24 Jun 2024 20:05:19 +0200
Julien Olivain <ju.o@free.fr> wrote:

> Buildroot commit [1] updated riscv-isa-sim (Spike), which now includes
> a NS16550 uart emulation. The Kernel config fragment was introduced to
> work with older HTIF interface from Spike.
> 
> For more information about the HTIF/NS16550 in Spike, see the commit
> log [2].
> 
> This commit removes this Kernel config fragment, since it is no longer
> needed.
> 
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/853b7661bf5ddca5d4b81964ef1a19a133beac85
> [2] https://gitlab.com/buildroot.org/buildroot/-/commit/38c581b05cd8e7967783410b36c14b9b561acd12
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Patch tested on branch master at commit 3f464c2 with commands:

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-10 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 18:05 [Buildroot] [PATCH 1/1] configs/spike_riscv64: remove the no longer needed kernel fragment Julien Olivain
2024-07-10 22:01 ` Thomas Petazzoni via buildroot [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=20240711000155.62e892f3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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