public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Du Huanpeng <dhu@hodcarrier.org>
Cc: u-boot@lists.denx.de, u74147@gmail.com
Subject: Re: [PATCH v5 3/6] mips: add a ls1c300 based board
Date: Thu, 27 Jul 2023 15:05:28 -0400	[thread overview]
Message-ID: <20230727190528.GL3630934@bill-the-cat> (raw)
In-Reply-To: <20230726123027.1536-4-dhu@hodcarrier.org>

[-- Attachment #1: Type: text/plain, Size: 359 bytes --]

On Wed, Jul 26, 2023 at 08:30:24PM +0800, Du Huanpeng wrote:

> - devicetree for ls1c300 SoC and board

What linux kernel release is this from?

[snip]
> +			u-boot,dm-pre-reloc;

Here and elsewhere, these are "bootph-" now and also upstreamable.

[snip]
> +LS1C300_EVAL BOARD
> +M:	Du Huanpeng<dhu@hodcarrier.org>

Missing space.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-07-27 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 12:30 [PATCH v5 0/6] add loongson mips ls1c300 initial support Du Huanpeng
2023-07-26 12:30 ` [PATCH v5 1/6] mips: initial build infrastructure for loongson SoCs Du Huanpeng
2023-07-27 19:05   ` Tom Rini
2023-07-26 12:30 ` [PATCH v5 2/6] mips: ls1c300: add base support Du Huanpeng
2023-07-27 20:46   ` Tom Rini
2023-07-26 12:30 ` [PATCH v5 3/6] mips: add a ls1c300 based board Du Huanpeng
2023-07-27 19:05   ` Tom Rini [this message]
2023-07-28  2:59     ` Du Huanpeng
2023-07-28 14:35       ` Tom Rini
2023-07-29  9:02         ` Du Huanpeng
2023-07-26 12:30 ` [PATCH v5 4/6] mips: ls1c300: add clock driver Du Huanpeng
2023-07-26 12:30 ` [PATCH v5 5/6] mips: ls1c300: add watchdog support Du Huanpeng
2023-07-26 12:30 ` [PATCH v5 6/6] mips: ls1c300: add reset support based on watchdog driver Du Huanpeng
2023-07-27 20:46 ` [PATCH v5 0/6] add loongson mips ls1c300 initial support 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=20230727190528.GL3630934@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=dhu@hodcarrier.org \
    --cc=u-boot@lists.denx.de \
    --cc=u74147@gmail.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