From: Paul Bolle <pebolle@tiscali.nl>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: tegra: Fix comment typo 'CONFIG_SLEEP'
Date: Thu, 17 Jul 2014 12:06:58 +0200 [thread overview]
Message-ID: <1405591618.4808.26.camel@x220> (raw)
In-Reply-To: <20140717095409.GB17877@ulmo>
On Thu, 2014-07-17 at 11:54 +0200, Thierry Reding wrote:
> I don't have this typo in my local tree, so I guess I must have fixed it
> sometime late yesterday but then forgot push this for linux-next.
I see. I'll keep this patch in my local stash (which I constantly rebase
onto the latest linux-next). So either it disappears automagically or
I'll send you a reminder in a few weeks.
Thanks,
Paul Bolle
prev parent reply other threads:[~2014-07-17 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 9:45 [PATCH] ARM: tegra: Fix comment typo 'CONFIG_SLEEP' Paul Bolle
2014-07-17 9:54 ` Thierry Reding
2014-07-17 10:06 ` Paul Bolle [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=1405591618.4808.26.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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