From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joel Stanley <joel@jms.id.au>
Cc: Andrew Jeffery <andrew@codeconstruct.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the bmc tree
Date: Thu, 3 Jul 2025 14:05:38 +1000 [thread overview]
Message-ID: <20250703140538.1d48c8d3@canb.auug.org.au> (raw)
In-Reply-To: <CACPK8XeQyZA0OgF_o1vujgu9AdR3aXKjNPGQ1djUSyk6RVhh6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Hi Joel,
On Thu, 3 Jul 2025 12:47:29 +0930 Joel Stanley <joel@jms.id.au> wrote:
>
> Please remove the joel/bmc.git from next. Andrew has added a new shared
> tree that will take it's place for BMC patches.
No worries, I will remove it tomorrow.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-07-03 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 7:40 Stephen Rothwell
[not found] ` <CACPK8XeQyZA0OgF_o1vujgu9AdR3aXKjNPGQ1djUSyk6RVhh6Q@mail.gmail.com>
2025-07-03 4:05 ` Stephen Rothwell [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=20250703140538.1d48c8d3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®