From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jkosina@suse.cz>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Bolle <pebolle@tiscali.nl>
Subject: Re: linux-next: manual merge of the trivial tree with the pm tree
Date: Wed, 3 Dec 2014 15:13:02 +1100 [thread overview]
Message-ID: <20141203151302.6e273bd4@canb.auug.org.au> (raw)
In-Reply-To: <20141203150153.7bbf3eb1@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
Hi,
On Wed, 3 Dec 2014 15:01:53 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> I fixed it up (the pm tree change was a subset of the trivial tree one)
^^^^^^
superset
--
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-03 4:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 4:01 linux-next: manual merge of the trivial tree with the pm tree Stephen Rothwell
2014-12-03 4:13 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 3:09 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=20141203151302.6e273bd4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rjw@rjwysocki.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