From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Reset controller fixes for v3.15
Date: Tue, 27 May 2014 08:46:36 +0200 [thread overview]
Message-ID: <1401173196.4090.1.camel@paszta.hi.pengutronix.de> (raw)
In-Reply-To: <20140526191744.GD27093@quad.lixom.net>
Hi Olof,
Am Montag, den 26.05.2014, 12:17 -0700 schrieb Olof Johansson:
> Hi,
>
> Please use signed tags on pull requests. It gives you a good location to
> document what is in it, as well as us a chance to verify that it actually comes
> from you (if/once your key is signed by people).
Alright, I'll do so in the future.
> In this case, I don't see any in-tree users of the function in 3.15, and we're
> very late in the merge window, so I've added this to the fixes-non-critical
> branch for 3.16.
Just as well, thank you.
Philipp
prev parent reply other threads:[~2014-05-27 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 15:01 [GIT PULL] Reset controller fixes for v3.15 Philipp Zabel
2014-05-26 19:17 ` Olof Johansson
2014-05-27 6:46 ` Philipp Zabel [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=1401173196.4090.1.camel@paszta.hi.pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).