From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Joel Stanley <joel@jms.id.au>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org
Subject: Re: Add bmc/linux for-next to linux-next
Date: Wed, 02 Jul 2025 11:28:06 +0930 [thread overview]
Message-ID: <8b035557ad025d31ab347349ebf9b91ff668498a.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250702114941.5bfe1e5a@canb.auug.org.au>
Hi Stephen,
On Wed, 2025-07-02 at 11:49 +1000, Stephen Rothwell wrote:
> Hi Andrew,
>
> On Wed, 02 Jul 2025 11:01:54 +0930 Andrew Jeffery <andrew@codeconstruct.com.au> wrote:
> >
> > Could you add the following to linux-next?
> >
> > Repo: https://git.kernel.org/pub/scm/linux/kernel/git/bmc/linux.git
> > Branch: for-next
> >
> > This aligns with the recent patch to MAINTAINERS for the ASPEED tree:
> >
> > https://lore.kernel.org/all/20250702-bmc-tree-update-v1-1-c270cd8af0ab@codeconstruct.com.au/
>
> So, does this replace the aspeed tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/joel/bmc.git branch
> for-next)? Or sit along side it?
It can replace joel/bmc.git, however, it should be fine to sit along-
side until Joel confirms removal of his tree with you. I've been doing
the BMC SoC patch wrangling recently, and he hasn't been updating his
tree with the branches I put together until I poke him about it. In
this case I'll just hassling him to update his tree, which should
remove any opportunity for conflicts or the like.
>
> Either way, who should be the contact(s) for this tree?
>
Both myself and Joel.
Cheers,
Andrew
next prev parent reply other threads:[~2025-07-02 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 1:31 Add bmc/linux for-next to linux-next Andrew Jeffery
2025-07-02 1:49 ` Stephen Rothwell
2025-07-02 1:58 ` Andrew Jeffery [this message]
2025-07-02 2:06 ` Stephen Rothwell
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=8b035557ad025d31ab347349ebf9b91ff668498a.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-next@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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