From: Joe Perches <joe@perches.com>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [210/2many] MAINTAINERS - HARDWARE MONITORING
Date: Mon, 13 Aug 2007 20:13:07 -0700 [thread overview]
Message-ID: <1187061187.10249.376.camel@localhost> (raw)
In-Reply-To: <20070814015945.GC7748@jupiter.solarsys.private>
On Mon, 2007-08-13 at 21:59 -0400, Mark M. Hoffman wrote:
> If you collect the hwmon stuff into one (1) patch, I'll take it.
I suspect that someone will either take or reject the
whole thing.
I'll send a batch of 10 or so patches to MAINTAINERS
with all the collected changes tomorrow along with
the modified script.
Thanks, Joe
prev parent reply other threads:[~2007-08-14 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:28 [PATCH] [210/2many] MAINTAINERS - HARDWARE MONITORING joe
2007-08-14 1:59 ` Mark M. Hoffman
2007-08-14 3:13 ` Joe Perches [this message]
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=1187061187.10249.376.camel@localhost \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
/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