mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: Dealing with complex patch series in linux-next
Date: Tue, 26 Jan 2021 11:26:29 +0100	[thread overview]
Message-ID: <20210126102629.cde4k436hvz3cibg@wittgenstein> (raw)
In-Reply-To: <20210126190030.109f24d7@canb.auug.org.au>

On Tue, Jan 26, 2021 at 07:00:30PM +1100, Stephen Rothwell wrote:
> Hi Christian,
> 
> On Mon, 25 Jan 2021 10:43:23 +0100 Christian Brauner <christian.brauner@ubuntu.com> wrote:
> >
> > After having received another round of acks on the idmapped mounts
> > series and other fses about to move forward with porting I moved forward
> > with merging [1] into my for-next branch which is tracked by sfr in
> > linux-next.
> > Given the nature of the series I expected there to be a good chunk of
> > merge conflicts including some non-trivial ones. But there proved to be
> > too many conflicts or at least a few ones that sfr couldn't handle
> > without more insight into the series. So after talking to sfr this
> > morning we decided to drop the tree for today.
> 
> OK, so tomorrow, I will try merging your tree really early.  This will,
> at least, spread the conflict pain out for me (yesterday it hit all at
> once at 4pm and added an hour to my day before I gave up).  Lets see
> how that goes.
> 
> Unless someone comes up with a better suggestion, of course :-)

I'm happy to help you if you want me to apply it to somewhere specific,
rebase or whatever. I have no problem doing it on a daily basis if that
makes it easier for you.

(Btw, I'm not sure this mail has made it to everyone here. It's
definitely not on lkml (as of now) seemingly because vger is having some
issues.)

Christian

      reply	other threads:[~2021-01-26 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  9:43 Christian Brauner
2021-01-26  8:00 ` Stephen Rothwell
2021-01-26 10:26   ` Christian Brauner [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=20210126102629.cde4k436hvz3cibg@wittgenstein \
    --to=christian.brauner@ubuntu.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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®