From: "Randy Dunlap" <rdunlap@xenotime.net>
To: "Arvind R" <arvino55@gmail.com>
Cc: "Randy Dunlap" <randy.dunlap@oracle.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Ranganathan Desikan" <ravi@jetztechnologies.com>,
linux-next@vger.kernel.org, "LKML" <linux-kernel@vger.kernel.org>,
bluesmoke-devel@lists.sourceforge.net,
linux-edac@vger.kernel.org,
"Doug Thompson" <dougthompson@xmission.com>,
"Jason Uhlenkott" <juhlenko@akamai.com>
Subject: Re: linux-next: Tree for April 21 (i82975x_edac)
Date: Sun, 24 Apr 2011 19:13:16 -0700 [thread overview]
Message-ID: <4ac1d916ddc0ab9e7e94b81bc77880be.squirrel@xenotime.net> (raw)
In-Reply-To: <BANLkTikWa7wZYonWLHMqWkBRHfi7tLiyuA@mail.gmail.com>
On Sat, April 23, 2011 11:29 pm, Arvind R wrote:
> On Sat, Apr 23, 2011 at 9:15 PM, Randy Dunlap <randy.dunlap@oracle.com>
> wrote:
>> On 04/23/11 01:21, Arvind R wrote:
>>> On Thu, Apr 21, 2011 at 9:21 PM, Randy Dunlap <randy.dunlap@oracle.com>
>>> wrote:
>>>> On Thu, 21 Apr 2011 13:20:45 +1000 Stephen Rothwell wrote:
>>>>
>>>>> Changes since 20110420:
>>>>
>>>>
>>>> on i386:
>>>>
>>>> drivers/edac/i82975x_edac.c:298: warning: integer constant is too
>>>> large for 'unsigned long' type
>
>> I think that the goal should be to get your 4-patch series merged.
>>
>>> That would still not fix the wrong error-info reported by the driver -
>>> this is
>>> fixed by the patch-set titled '[RFC PATCH 2.6.37 0/4] i3000_edac :
>>> merge
>>> i82975x support' dated 2011-02-14 in the linux-edac archives.
>>>
>>> Please advise on getting the patch into main-stream. The I3000 is a
>>> re-labeled
>>> i82975x (or vice-versa). Hence the patch-set to merge the drivers. If
>>> separate
>>> i82975x driver is needed - I can provide the patch. The reported bug is
>>> not
>>> present in the merge-patched driver.
>>
>> Doug, any plans to merge this 4-patch series from Arvind?
>>
>> Arvind, was bluesmoke-devel@lists.sourceforge.net copied on this patch
>> series?
> No - thought that the bluesmoke-list had moved to linux-edac.
>
If bluesmoke-devel is obsolete, the MAINTAINERS file
needs to be updated.
>>
>> and was the I3000 driver maintainer copied? (added)
>> I can't tell this from the marc.info archives.
> Added myself to the driver maintainer in the i3000_edac.c file. The
> patch-set adds support for i82975x in the i3000 driver, which is
> better structured.
> TODO:
> 1. Change Kconfig file - select I3000 for i82975x support
> 2. Delete i82975x_edac.c file
> 3. Update MAINTAINERS file
Did the other EDAC-I3000 maintainer respond?
thanks,
--
~Randy
next prev parent reply other threads:[~2011-04-25 2:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 3:20 linux-next: Tree for April 21 Stephen Rothwell
2011-04-21 14:41 ` linux-next: Tree for April 21 (md/raid456) Randy Dunlap
2011-04-21 15:51 ` linux-next: Tree for April 21 (i82975x_edac) Randy Dunlap
2011-04-23 8:21 ` Arvind R
2011-04-23 15:45 ` Randy Dunlap
2011-04-24 6:29 ` Arvind R
2011-04-25 2:13 ` Randy Dunlap [this message]
2011-04-25 5:51 ` Arvind R
2011-04-25 7:00 ` Jason Uhlenkott
2011-04-21 16:09 ` [PATCH -next] kvm: fix const value warning on i386 Randy Dunlap
2011-04-24 7:12 ` Avi Kivity
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=4ac1d916ddc0ab9e7e94b81bc77880be.squirrel@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=arvino55@gmail.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dougthompson@xmission.com \
--cc=juhlenko@akamai.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=ravi@jetztechnologies.com \
--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
all inboxes | Powered by JetHome®