From: Peter Chen <peter.chen@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: please clean up the usb-chipidea-fixes/next trees
Date: Sat, 9 Apr 2022 09:47:02 +0800 [thread overview]
Message-ID: <20220409014702.GA3421@Peter> (raw)
In-Reply-To: <20220406113242.3d7aefbd@canb.auug.org.au>
On 22-04-06 11:32:42, Stephen Rothwell wrote:
> Hi all,
>
> [Try again to an address that may work ...]
>
> The usb-chipidea-fixes and -next trees have not been updated since Oct,
> 2021 and the -fixes tree is generating a conflict when merged. Please
> clean them it up WRT Linus' tree as the only patches in them have been
> merged as other commits.
>
Hi Stephen,
Sorry about that. I have a little busy these years, the USB patches
which went to my tree will go to the Greg's USB tree directly, I only
review these patches now. Would you please also delete my tree from
your merge list? Thanks.
--
Thanks,
Peter Chen
next prev parent reply other threads:[~2022-04-09 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 1:32 linux-next: please clean up the usb-chipidea-fixes/next trees Stephen Rothwell
2022-04-09 1:47 ` Peter Chen [this message]
2022-04-09 5:38 ` 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=20220409014702.GA3421@Peter \
--to=peter.chen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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.