From: Shaun Ruffell <sruffell@digium.com>
To: Xie Shaohui-B21989 <B21989@freescale.com>
Cc: "avorontsov@mvista.com" <avorontsov@mvista.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH] edac/85xx: fix error handle of mpc85xx_mc_err_probe
Date: Tue, 18 Sep 2012 22:53:06 -0500 [thread overview]
Message-ID: <20120919035306.GF24873@digium.com> (raw)
In-Reply-To: <ED492CCEAF882048BC2237DE806547C9079E3F3D@039-SN2MPN1-012.039d.mgd.msft.net>
On Wed, Sep 19, 2012 at 03:43:35AM +0000, Xie Shaohui-B21989 wrote:
> > On Mon, Sep 17, 2012 at 10:32:59AM +0000, Xie Shaohui-B21989 wrote:
> > >
> > > BTW: seems you are using a different kernel tree with mine.
> >
> > On the chance that I missing something important: Why do you say
> > I was running a different kernel tree? I was against 3.6-rc2
> > when I original hit the problem.
>
> [S.H] I'm using 3.6-rc4, and some codes in your patch I did not
> find them in 3.6-rc4.
Is it because there were three patches in the series?
[1/3] https://lkml.org/lkml/2012/9/14/473
[2/3] https://lkml.org/lkml/2012/9/14/469
[3/3] https://lkml.org/lkml/2012/9/14/474
They are also the last three commits on my edac_debug_v2 branch
here, which is on top of 3.6-rc6:
https://github.com/sruffell/linux/commits/edac_debug_v2/
Cheers,
Shaun
next prev parent reply other threads:[~2012-09-19 4:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 10:55 [PATCH] edac/85xx: fix error handle of mpc85xx_mc_err_probe Shaohui Xie
2012-09-14 0:04 ` Kim Phillips
2012-09-14 18:21 ` Shaun Ruffell
2012-09-17 10:32 ` Xie Shaohui-B21989
2012-09-19 3:04 ` Shaun Ruffell
2012-09-19 3:43 ` Xie Shaohui-B21989
2012-09-19 3:53 ` Shaun Ruffell [this message]
2012-09-19 4:51 ` Xie Shaohui-B21989
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=20120919035306.GF24873@digium.com \
--to=sruffell@digium.com \
--cc=B21989@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=avorontsov@mvista.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).