From: Kevin Hilman <khilman@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
nm@ti.com, dianders@chromium.org, heiko@sntech.de
Subject: Re: [GIT PULL] PM / AVS changes for v3.18 - v2
Date: Fri, 26 Sep 2014 07:23:21 -0700 [thread overview]
Message-ID: <7hmw9m795y.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20140926081534.GA27755@sirena.org.uk> (Mark Brown's message of "Fri, 26 Sep 2014 09:15:34 +0100")
Mark Brown <broonie@kernel.org> writes:
> On Thu, Sep 25, 2014 at 12:05:42PM -0700, Kevin Hilman wrote:
>
>> The first pull request was missing a dependency on a feature that went
>> in through Mark Brown's regulator tree, so it wouldn't actually compile
>> properly by itself. This version pulls in that topic branch from Marks
>> tree (topic/voltage-ev branch, already part of -next), and now compiles fine.
>
> Please in future don't pull anything in from my tree without a signed
> tag (speak to me if there isn't one).
Sorry about that.
Had there been more than one patch in this topic branch, or it wasn't
based directly on an -rc tag, I would've waited for confirmation about
it being stable, but since it was a single patch, based directly on an
-rc tag, I assumed it was stable.
In the future, I'll be sure to request a signed tag.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] PM / AVS changes for v3.18 - v2
Date: Fri, 26 Sep 2014 07:23:21 -0700 [thread overview]
Message-ID: <7hmw9m795y.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20140926081534.GA27755@sirena.org.uk> (Mark Brown's message of "Fri, 26 Sep 2014 09:15:34 +0100")
Mark Brown <broonie@kernel.org> writes:
> On Thu, Sep 25, 2014 at 12:05:42PM -0700, Kevin Hilman wrote:
>
>> The first pull request was missing a dependency on a feature that went
>> in through Mark Brown's regulator tree, so it wouldn't actually compile
>> properly by itself. This version pulls in that topic branch from Marks
>> tree (topic/voltage-ev branch, already part of -next), and now compiles fine.
>
> Please in future don't pull anything in from my tree without a signed
> tag (speak to me if there isn't one).
Sorry about that.
Had there been more than one patch in this topic branch, or it wasn't
based directly on an -rc tag, I would've waited for confirmation about
it being stable, but since it was a single patch, based directly on an
-rc tag, I assumed it was stable.
In the future, I'll be sure to request a signed tag.
Kevin
next prev parent reply other threads:[~2014-09-26 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 19:05 [GIT PULL] PM / AVS changes for v3.18 - v2 Kevin Hilman
2014-09-25 19:05 ` Kevin Hilman
2014-09-25 20:42 ` Rafael J. Wysocki
2014-09-25 20:42 ` Rafael J. Wysocki
2014-09-26 8:15 ` Mark Brown
2014-09-26 8:15 ` Mark Brown
2014-09-26 13:40 ` Rafael J. Wysocki
2014-09-26 13:40 ` Rafael J. Wysocki
2014-09-26 14:23 ` Kevin Hilman [this message]
2014-09-26 14:23 ` Kevin Hilman
2014-09-26 15:42 ` Kevin Hilman
2014-09-26 15:42 ` Kevin Hilman
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=7hmw9m795y.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.