From: Rob Herring <robherring2@gmail.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <cbouatmailru@gmail.com>,
Colin Cross <ccross@android.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] pstore/ram for 3.11
Date: Fri, 14 Jun 2013 17:32:16 -0500 [thread overview]
Message-ID: <51BB99F0.6030607@gmail.com> (raw)
In-Reply-To: <CA+8MBbKPr_y4rTBArcmz315y0f2-07Qu6DsM2cj-XW7-U=L56Q@mail.gmail.com>
On 06/14/2013 05:18 PM, Tony Luck wrote:
> On Wed, Jun 12, 2013 at 8:44 PM, Rob Herring <robherring2@gmail.com> wrote:
>> Not sure who takes this, but please pull these 2 changes for pstore for
>> 3.11. These are necessary to get pstore to work with on-chip RAM on
>> Calxeda highbank platform.
>
> Were these posted for discussion and review? Is there anyone who should
> be providing {Acked,Reviewed,Tested}-by: tags for them? I haven't ever had
> a sub-maintained tree to pull from - so I'm being double-extra cautious before
> doing something with this as it all feels new and strange.
Yes, here:
https://lkml.org/lkml/2013/4/9/831
The main discussion was around the write-combining change which I
dropped. You can pick patches 2 and 3 off the mail list if you prefer. I
would assume they only require an ack from one of the 4 of you which
pulling the tree implicitly does.
Rob
next prev parent reply other threads:[~2013-06-14 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 3:44 [GIT PULL] pstore/ram for 3.11 Rob Herring
2013-06-14 22:18 ` Tony Luck
2013-06-14 22:32 ` Rob Herring [this message]
2013-06-14 22:47 ` Anton Vorontsov
2013-06-14 22:57 ` Tony Luck
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=51BB99F0.6030607@gmail.com \
--to=robherring2@gmail.com \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).