From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Markos Chandras <markos.chandras@imgtec.com>,
linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
baspeters93@gmail.com
Subject: Re: linux-next: Tree for Feb 16
Date: Tue, 17 Feb 2015 07:36:19 +1100 [thread overview]
Message-ID: <20150217073619.4c972211@canb.auug.org.au> (raw)
In-Reply-To: <20150216171213.GA2804@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
Hi Guenter,
On Mon, 16 Feb 2015 09:12:13 -0800 Guenter Roeck <linux@roeck-us.net> wrote:
>
> On Thu, Feb 16, 2012 at 04:41:44PM +1100, Stephen Rothwell wrote:
> >
> > Changes since 20120215:
> ---
> [ Trying again, this time hopefully replying to the correct e-mail.
> Sorry for the earlier noise. ]
Did you really mean to reply to a release from 3 years ago?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-16 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 5:41 linux-next: Tree for Feb 16 Stephen Rothwell
2012-02-16 15:58 ` linux-next: Tree for Feb 16 (selinux) Randy Dunlap
2012-02-16 19:24 ` Eric Paris
2015-02-16 17:12 ` linux-next: Tree for Feb 16 Guenter Roeck
2015-02-16 20:36 ` Stephen Rothwell [this message]
2015-02-16 20:52 ` Guenter Roeck
2015-02-16 4:39 Stephen Rothwell
2016-02-16 5:53 Stephen Rothwell
2017-02-16 4:46 Stephen Rothwell
2018-02-16 3:25 Stephen Rothwell
2021-02-16 11:08 Stephen Rothwell
2022-02-16 8:42 Stephen Rothwell
2023-02-16 3:57 Stephen Rothwell
2024-02-16 3:32 Stephen Rothwell
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=20150217073619.4c972211@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=baspeters93@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.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).