public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Peter Chen <peter.chen@kernel.org>
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 15:38:48 +1000	[thread overview]
Message-ID: <20220409153848.4974ed6f@canb.auug.org.au> (raw)
In-Reply-To: <20220409014702.GA3421@Peter>

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

Hi Peter,

On Sat, 9 Apr 2022 09:47:02 +0800 Peter Chen <peter.chen@kernel.org> wrote:
>
> On 22-04-06 11:32:42, Stephen Rothwell wrote:
> > 
> > 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.
> 
> 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.

No worries, done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2022-04-09  5:38 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
2022-04-09  5:38   ` 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=20220409153848.4974ed6f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peter.chen@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