From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Paul Fox <pgf@laptop.org>,
linux-kernel@vger.kernel.org,
Andres Salomon <dilinger@queued.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v1] OLPC: use %*ph specifier instead of passing direct values
Date: Tue, 6 Oct 2015 23:18:13 +0100 [thread overview]
Message-ID: <20151006221813.GA43526@vmdeb7> (raw)
In-Reply-To: <1443625184.8361.310.camel@linux.intel.com>
On Wed, Sep 30, 2015 at 05:59:44PM +0300, Andy Shevchenko wrote:
> On Mon, 2014-12-29 at 09:32 -0500, Paul Fox wrote:
> > change looks okay to me.
> > Acked-by: Paul Fox <pgf@laptop.org>
> >
>
> Darren, maybe you can apply this one? Seems OLPC is x86-based.
Change is good, and olpc appears to be orphaned per MAINTAINERS. I'm OK
including it in my pull request along with an update to MAINTAINERS.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2015-10-06 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 12:26 [PATCH v1] OLPC: use %*ph specifier instead of passing direct values Andy Shevchenko
2014-12-29 14:32 ` Paul Fox
2015-09-30 14:59 ` Andy Shevchenko
2015-10-06 22:18 ` Darren Hart [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=20151006221813.GA43526@vmdeb7 \
--to=dvhart@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dilinger@queued.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pgf@laptop.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