From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-edac <linux-edac@vger.kernel.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] EDAC updates for 4.2
Date: Wed, 24 Jun 2015 10:23:07 +0200 [thread overview]
Message-ID: <20150624082306.GB23842@gmail.com> (raw)
In-Reply-To: <20150624074029.GA32642@pd.tnic>
* Borislav Petkov <bp@suse.de> wrote:
> > If it doesn't work or compile without the tip pile, then I'm not pulling it at
> > all, since that means that any problems are not bisectable.
>
> Ok, how would you prefer this solved - should I merge the relevant tip branches
> into it?
So the broken commit is 1862c7c3483c. Given that only a handful of commits follow
it, I'd suggest the following resolution, to preserve half of your tree:
git checkout -b tmp.tmp your/edac/tree
git reset --hard 1862c7c3483c^1
git merge linus # where 'linus' is 407a2c720556e - your DEFERRED_ERROR_VECTOR dependency
git checkout -b tmp.tmp2 your/edac/tree
git rebase --onto tmp.tmp 1862c7c3483c^1
Then re-test and re-submit the result to Linus as -v2.
Note that 407a2c720556e is very early in the v4.2 merge window, with only -tip
(and some VFS) bits in it, which I have tested and which is looking pretty robust.
In the future we can do such dependencies in -tip as well, so that they don't
reach Linus - I didn't realize your tree had this dependency.
Thanks,
Ingo
next prev parent reply other threads:[~2015-06-24 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 9:11 [GIT PULL] EDAC updates for 4.2 Borislav Petkov
2015-06-23 22:49 ` Linus Torvalds
2015-06-24 7:40 ` Borislav Petkov
2015-06-24 8:23 ` Ingo Molnar [this message]
2015-06-24 8:50 ` Thomas Gleixner
2015-06-24 8:54 ` Borislav Petkov
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=20150624082306.GB23842@gmail.com \
--to=mingo@kernel.org \
--cc=bp@suse.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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