From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: James Hogan <james.hogan@imgtec.com>,
Guenter Roeck <linux@roeck-us.net>, <linux-next@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
<linux-metag@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 16
Date: Wed, 17 Dec 2014 11:23:16 +1100 [thread overview]
Message-ID: <20141217112316.3018b44e@canb.auug.org.au> (raw)
In-Reply-To: <20141216160857.4a9d55ecbff0d67c1c6e38fd@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
Hi Andrew,
On Tue, 16 Dec 2014 16:08:57 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Wed, 17 Dec 2014 10:57:22 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > So should I just dump that patch into my copy of your tree? (it seems
> > harmless and lets people get onto other stuff)
>
> yep, thanks. I forgot to cc you on my merge of it, as usual.
OK, added.
--
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:[~2014-12-17 0:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 4:46 Stephen Rothwell
2014-12-16 6:35 ` Guenter Roeck
2014-12-16 6:44 ` Andrew Morton
2014-12-16 6:55 ` Guenter Roeck
2014-12-16 9:42 ` James Hogan
2014-12-16 10:45 ` James Hogan
2014-12-16 23:57 ` Stephen Rothwell
2014-12-17 0:08 ` Andrew Morton
2014-12-17 0:23 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 1:47 Stephen Rothwell
2024-12-16 6:25 Stephen Rothwell
2022-12-16 1:46 Stephen Rothwell
2020-12-16 9:40 Stephen Rothwell
2019-12-16 5:22 Stephen Rothwell
2016-12-16 3:49 Stephen Rothwell
2015-12-16 5:43 Stephen Rothwell
2013-12-16 5:59 Stephen Rothwell
2011-12-16 6:00 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=20141217112316.3018b44e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luto@amacapital.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®