From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 01/14] sh: add a temporary macro to define fixed voltage regulators
Date: Wed, 20 Jun 2012 15:20:06 +0000 [thread overview]
Message-ID: <20120620152005.GA8008@linux-sh.org> (raw)
In-Reply-To: <1340205142-32606-2-git-send-email-g.liakhovetski@gmx.de>
On Wed, Jun 20, 2012 at 05:12:09PM +0200, Guennadi Liakhovetski wrote:
> Until the regulator_register_fixed_volt() function becomes available add a
> macro to define fixed-voltage always on regulators.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Uh, no. If you have a dependency on something in another tree then we
pull that dependency in to a topic branch and layer on top of that.
Contrary to popular belief, a couple of changes in a topic branch in
someone else's tree is hardly a rare occurence, nor does it make you
special.
I can't even begin to imagine at what point making this header started to
look like a good idea, you must really go out of your way to avoid using
git in your workflow.
next prev parent reply other threads:[~2012-06-20 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 15:12 [PATCH 01/14] sh: add a temporary macro to define fixed voltage regulators Guennadi Liakhovetski
2012-06-20 15:20 ` Paul Mundt [this message]
2012-06-20 15:30 ` Guennadi Liakhovetski
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=20120620152005.GA8008@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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