All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: Tom Rini <trini@konsulko.com>, u-boot@lists.u-boot-project.org
Subject: Re: [GIT PULL] Please pull U-Boot spacemit-main-20261010
Date: Sat, 10 Oct 2026 23:55:43 +0000	[thread overview]
Message-ID: <20261010235543-GKE26088@kernel.org> (raw)
In-Reply-To: <62a524d6-4693-413a-a704-da8e83a98ed9@freeshell.de>

Hi E Shattow,

On 15:57 Sat 10 Oct     , E Shattow wrote:
> On 10/10/26 14:46, Tom Rini wrote:
> > On Sat, 10 Oct 2026 04:30:56 +0000, Yixun Lan wrote:
> > 
> >> Please pull from u-boot-spacemit into main, thanks.
> >>
> >> CI for this pull request is available here:
> >>   https://git.u-boot-project.org/u-boot/custodians/u-boot-spacemit/-/pipelines/1535
> >>
> >>
> >> The following changes since commit 0a55b098d6f5f6bafa84fc2f18b433dd167bf729:
> >>
> >> [...]
> > 
> > Merged into u-boot/main, thanks!
> > 
> 
> FYI to any future versions of ourselves wondering why non-existent
> symbol CONFIG_DWC_ETH_QOS_SPACEMIT is enabled in this PR, this was
> applied out-of-sequence due to a delay with the networking custodian
> tree PR for the merge window [1].
> 
Right, I thought about this before sending this PR, but didn't consider
it's a problem.. for building and testing, there is no error with this
single PR, yes, will result with no network. Besides, I also trust net
maintainer whom will send the PR eventually..

> 1: https://lore.kernel.org/u-boot/20261009172150.GD769217@bill-the-cat/
> 
> -E

-- 
Yixun Lan (dlan)

      reply	other threads:[~2026-10-10 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10  4:30 [GIT PULL] Please pull U-Boot spacemit-main-20261010 Yixun Lan
2026-10-10 21:46 ` Tom Rini
2026-10-10 22:57   ` E Shattow
2026-10-10 23:55     ` Yixun Lan [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=20261010235543-GKE26088@kernel.org \
    --to=dlan@kernel.org \
    --cc=e@freeshell.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    /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.