From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Jean Delvare <khali@linux-fr.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: [lm-sensors] [GIT PATCH] hwmon updates against v2.6.26
Date: Wed, 06 Aug 2008 10:59:16 +0200 [thread overview]
Message-ID: <489967E4.9060002@hhs.nl> (raw)
In-Reply-To: <20080806103903.6b9eec76@hyperion.delvare>
Jean Delvare wrote:
> Hi Mark, Andrew,
>
> On Fri, 1 Aug 2008 00:10:27 -0400, Mark M. Hoffman wrote:
>> Hi Linus:
>>
>> Please pull from:
>> git://lm-sensors.org/kernel/mhoffman/hwmon-2.6.git release
>>
>> You'll get what few patches I've managed to look at in the last few months,
>> including a patch to MAINTAINERS which makes it official. I'm sorry I was
>> not able to keep up - I should have admitted defeat much sooner.
>
> I'm sad to see you go (and can only hope that you won't leave the
> project entirely). But I would also like to thank you for the good work
> you've done. Even if it was short, everything you did is done and
> that's something you can be proud of. Especially given the conditions
> in which you started in this new role - please forgive me for that.
>
All I can see really is +1, sad to see you go and thanks for all the work done!
>> To all lm-sensors/hwmon developers: please resend/CC patches to Andrew.
>
> 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.
>
I too don't want to see any patches get dropped, so I'll try to step up a
little with regards to reviewing hwmon patches, I would be grateful if you
could incorporate any patches Acked by me in said tree. Esp since my git-fu
isn't all that good.
> Don't get me wrong, I am _not_ volunteering to become the new hwmon
> subsystem maintainer.
Don't get me wrong either, I will try to step up my reviewing but I am _not_
volunteering to become the new hwmon subsystem maintainer either. I'm just
starting a new job and with that combined with that I'm doing a lot of v4l work
lately, I simply don't have the time for this.
> In the future, I would like to suggest to have 2 hwmon subsystem
> maintainers instead of 1. Apparently none of us has the time to do all
> the work, but maybe some of us would have the time to do half of it.
> This is the path I took for the i2c subsystem, and while the change is
> still fairly recent, it seems to be working well enough.
>
+1
Regards,
Hans
next prev parent reply other threads:[~2008-08-06 8:57 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 ` Hans de Goede [this message]
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
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=489967E4.9060002@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=khali@linux-fr.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