From: Jean Delvare <khali@linux-fr.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [GIT PATCH] hwmon updates against v2.6.26
Date: Wed, 6 Aug 2008 20:03:01 +0200 [thread overview]
Message-ID: <20080806200301.6597e42d@hyperion.delvare> (raw)
In-Reply-To: <20080806085324.58d65849.akpm@linux-foundation.org>
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@linux-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.
--
Jean Delvare
next prev parent reply other threads:[~2008-08-06 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 4:10 [GIT PATCH] hwmon updates against v2.6.26 Mark M. Hoffman
2008-08-01 4:32 ` Andrew Morton
2008-08-06 8:39 ` Jean Delvare
2008-08-06 8:59 ` [lm-sensors] " Hans de Goede
2008-08-06 9:41 ` Jean Delvare
2008-08-06 11:15 ` Jean Delvare
2008-08-06 15:53 ` Andrew Morton
2008-08-06 18:03 ` Jean Delvare [this message]
2008-08-06 20:43 ` Andrew Morton
2008-08-06 21:09 ` Jean Delvare
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=20080806200301.6597e42d@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=torvalds@linux-foundation.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