lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101020184515.38512719@endymion.delvare>
Date:	Wed, 20 Oct 2010 18:45:15 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Guenter Roeck <guenter.roeck@...csson.com>,
	Hans de Goede <j.w.r.degoede@....nl>,
	Alistair John Strachan <alistair@...zero.co.uk>,
	Henrik Rydberg <rydberg@...omail.se>,
	"Mark M. Hoffman" <mhoffman@...htlink.com>,
	Luca Tettamanti <kronos.it@...il.com>,
	Fenghua Yu <fenghua.yu@...el.com>,
	Juerg Haefliger <juergh@...il.com>,
	Eric Piel <eric.piel@...mplin-utc.net>,
	Jim Cromie <jim.cromie@...il.com>,
	Roger Lucas <vt8231@...denengine.co.uk>,
	"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drivers/hwmon: Use pr_fmt and pr_<level>

Hi Joe,

On Wed, 20 Oct 2010 09:08:10 -0700, Joe Perches wrote:
> On Wed, 2010-10-20 at 07:46 -0700, Guenter Roeck wrote:
> > > * That being said, now that the hwmon subsystem maintainer is a shared
> > >   duty between Guenter and myself, there's no single place where we can
> > >   keep a patch touching many drivers and ensure it doesn't conflict
> > >   with the changes in the other tree. But I would think   this is
> > >   something for Gunter and myself to sort out, not patch contributors.
> 
> Perhaps allow both maintainers read/write access to hwmon-next?

Guenter and myself are collaborating on the hwmon tree since a
relatively recent date. We still have to find the best method. For now
we have separate trees because it seemed easier that way, but we may
change our minds later.

> > > I currently have pending patches to the following hwmon drivers in my
> > > tree: adt7475, ams, asc7621, hdaps, it87, k8temp, lm75, lm85, lm90,
> > > pcf8591, s3c-hwmon, w83795. Two of these are affected by Joe's
> > > patch(es). Guenter, what about you?
> >
> > coretemp, pkgtemp, via-cputemp, ltc4261 (new), lis3, hp_accel
> 
> I did these against next which includes 'hwmon-staging/hwmon-next'.
> 
> Shouldn't these patches apply without modification or do I need
> to do something else?

If you based your patches on linux-next then you're all set. I was
asking Guenter about his affected drivers only to decide who, of him and
me, should take which patch.

-- 
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ