mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [GIT PULL] hwmon updates for 3.4
Date: Wed, 21 Mar 2012 11:07:23 -0700	[thread overview]
Message-ID: <1332353243.32717.207.camel@groeck-laptop> (raw)
In-Reply-To: <CA+55aFzEQ-undQpx_Q_5+scP5EN9KxJ9m-1O-8O0h+EbZE2mMw@mail.gmail.com>

On Wed, 2012-03-21 at 13:40 -0400, Linus Torvalds wrote:
> On Tue, Mar 20, 2012 at 9:23 AM, Guenter Roeck
> <guenter.roeck@ericsson.com> wrote:
> >
> > Please pull hwmon updates for Linux 3.4 from tag:
> >
> >    git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus
> >
> > Mostly cleanup. No new drivers this time around, but support for several chips
> > added to existing drivers: TPS40400, TPS40422, MTD040, MAX34446, ZL9101M,
> > ZL9117M, and LM96080. Also added watchdog support for SCH56xx, plus additional
> > sysfs attributes for a couple of drivers.
> 
> Btw, please don't put that "git log --oneline" generated data into the
> tag - there's no real point. It doesn't add anything human-readable to
> anything, and for any automation you can get the data better directly
> from git instead.
> 
> So the tag-message shouldn't contain anything auto-generated, since
> any auto-generated data is better just generated later on the fly.
> Just do the human-readable "this is the high-level overview of that
> the pull request contains" into the tag message.
> 
>                        Linus

Ok. Sorry for the noise, and thanks for pulling the changes.

Guenter



      reply	other threads:[~2012-03-21 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 16:23 Guenter Roeck
2012-03-21 17:40 ` Linus Torvalds
2012-03-21 18:07   ` Guenter Roeck [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=1332353243.32717.207.camel@groeck-laptop \
    --to=guenter.roeck@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --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

all inboxes | Powered by JetHome®