On Mon, Apr 25, 2011 at 7:43 AM, Randy Dunlap <rdunlap@xxxxxxxxxxxx> wrote: > > On Sat, April 23, 2011 11:29 pm, Arvind R wrote: >> On Sat, Apr 23, 2011 at 9:15 PM, Randy Dunlap <randy.dunlap@xxxxxxxxxx> >> wrote: >>> On 04/23/11 01:21, Arvind R wrote: >>>> On Thu, Apr 21, 2011 at 9:21 PM, Randy Dunlap <randy.dunlap@xxxxxxxxxx> >>>> 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@xxxxxxxxxxxxxxxxxxxxx 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? No, though CC'ed to. Arvind -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
