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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080806230932.73d78593@hyperion.delvare>
Date:	Wed, 6 Aug 2008 23:09:32 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	mhoffman@...htlink.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org
Subject: Re: [GIT PATCH] hwmon updates against v2.6.26

On Wed, 6 Aug 2008 13:43:14 -0700, Andrew Morton wrote:
> On Wed, 6 Aug 2008 20:03:01 +0200
> Jean Delvare <khali@...ux-fr.org> wrote:
> 
> > Hi Andrew,
> > 
> > On Wed, 6 Aug 2008 08:53:24 -0700, Andrew Morton wrote:
> > > On Wed, 6 Aug 2008 10:39:03 +0200 Jean Delvare <khali@...ux-fr.org> wrote:
> > > > I have a number of hwmon patches in my local kernel tree which I wrote
> > > > and that have been reviewed by a trusted developer, or that have been
> > > > posted to the lm-sensors list and that I have reviewed. I consider
> > > > these ready to go upstream. I plan to gather these into a public tree
> > > > and push them to Linus today or tomorrow. In the future, I will
> > > > probably have such a tree available to be included in linux-next.
> > > > 
> > > > Don't get me wrong, I am _not_ volunteering to become the new hwmon
> > > > subsystem maintainer. Remember, I've been there before and you know how
> > > > it ended. But in the absence of a subsystem maintainer, I don't want
> > > > hwmon patches to be lost (and especially not mine) and I don't think
> > > > that pushing everything to Andrew is a good solution either. So I'm
> > > > just proposing to do my part of the work. But if Andrew really prefers
> > > > to pick all the patches, I am not insisting either.
> > > 
> > > That would be great, thanks.
> > > 
> > > But it does mean that I'd prefer that any hwmon patches which I pick up
> > > are merged via that tree if that's OK.  Which all does end up making
> > > you look awfully like an hwmon maintainer..
> > 
> > No, that's not OK, sorry. This goes beyond what I can offer at this
> > point in time.
> > 
> > I offered to push selected patches to Linus, with no other guarantee
> > than the fact that said patches have been carefully reviewed and are
> > believed to be correct. I do not have the time to do more than that.
> > 
> > If this isn't OK with you, then I will have to withdraw my proposal.
> > It's up to you.
> 
> <rereads>
> 
> Ah, I see, this tree is only things-which-Jean-wrote.  No probs here.

Things that I wrote or reviewed, yes. Put in short, things I am already
involved in, so there is no extra cost for me to push them to Linus.

-- 
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