From: Borislav Petkov <petkovbb@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Borislav Petkov <borislav.petkov@amd.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Doug Thompson <dougthompson@xmission.com>
Subject: Re: linux-next: manual merge of the edac-amd tree with Linus' tree
Date: Wed, 5 Aug 2009 08:22:15 +0200 [thread overview]
Message-ID: <20090805062215.GA7732@liondog.tnic> (raw)
In-Reply-To: <20090805150933.103de233.sfr@canb.auug.org.au>
Hi Stephen,
On Wed, Aug 05, 2009 at 03:09:33PM +1000, Stephen Rothwell wrote:
> Today's linux-next merge of the edac-amd tree got a conflict in
> drivers/edac/amd64_edac.c between commit
> 126b67b8d26f6623d199aa59279f2e3243f2144c ("amd64_edac: fix ECC checking")
> from Linus' tree and commit 793a2a12b43aba669c8b2604a45f000a394f142d
> ("amd64_edac: cleanup amd64_check_ecc_enabled") from the edac-amd tree.
>
> I don't think the fix in the former patch is required, so I just used the
> latter version.
thanks and yes, you're right. The former patch is less intrusive
and we opted for that one since it is really late in the -rc cycle
but the latter cleans up stuff so that code flow becomes much more
understandable. I'll rediff later and sorry for the inconvenience.
By the way, I see that you're merging edac-amd before tip and I'm going
to need to rebase my tree against tip in the next couple of days since
it depends on a bunch of stuff in it, so could you please switch the
merge order of the two trees so that edac-amd goes after tip?
Thanks.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2009-08-05 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 5:09 linux-next: manual merge of the edac-amd tree with Linus' tree Stephen Rothwell
2009-08-05 6:22 ` Borislav Petkov [this message]
2009-08-05 6:40 ` Rebasing the edac-amd tree (Was: Re: linux-next: manual merge of the edac-amd tree with Linus' tree) Stephen Rothwell
2009-08-05 7:42 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2015-06-26 7:08 linux-next: manual merge of the edac-amd tree with Linus' tree Stephen Rothwell
2015-06-26 7:27 ` Borislav Petkov
2015-06-26 8:22 ` Stephen Rothwell
2015-06-26 8:34 ` Borislav Petkov
2015-06-26 8:37 ` 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=20090805062215.GA7732@liondog.tnic \
--to=petkovbb@googlemail.com \
--cc=borislav.petkov@amd.com \
--cc=dougthompson@xmission.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox