All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: linux-next: manual merge of the cputime tree
Date: Mon, 10 Nov 2008 09:45:26 +0100	[thread overview]
Message-ID: <1226306726.23046.14.camel@localhost> (raw)
In-Reply-To: <20081110170943.114a7786.sfr@canb.auug.org.au>

Hi Stephen,

On Mon, 2008-11-10 at 17:09 +1100, Stephen Rothwell wrote:
> Today's linux-next merge of the cputime tree got a conflict in
> arch/s390/kernel/process.c between commit
> 2933aa2758dc5e520f83a5f4c3f255aea297bd3f ("[S390] ftrace: disable tracing
> on idle psw") from the s390 tree and commit
> bbda3e73a200e966955b15a08a8be05a7c1d430e ("[PATCH] improve precision of
> idle accounting") from the cputime tree.
> 
> I attempted a fix (see below) but please either provide me with a better
> patch or fix this conflict in one or the other tree.  You could do this
> by merging the s390 tree into the cputime tree (but you would need to be
> careful to keep the consistent) and fixing this in the merge commit.

You are pulling the s390 tree first and then the cputime tree, no? Then
I could simply rebase the cputime tree off the s390 tree. You'll find
new features/cputime branches on git390.

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.

  reply	other threads:[~2008-11-10  8:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  6:09 linux-next: manual merge of the cputime tree Stephen Rothwell
2008-11-10  8:45 ` Martin Schwidefsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-11  6:56 Stephen Rothwell
2008-11-25  9:21 Stephen Rothwell
2008-11-25 10:06 ` Peter Zijlstra
2008-11-25 10:15   ` Martin Schwidefsky
2008-11-25 10:28     ` Peter Zijlstra
2008-11-25 10:32       ` Paul Mackerras
2008-11-25 11:00       ` Martin Schwidefsky

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=1226306726.23046.14.camel@localhost \
    --to=schwidefsky@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --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.