From: mark.rutland@arm.com (Mark Rutland)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/2] meson-sm: Fix issues when reading data from sm
Date: Thu, 23 Mar 2017 10:31:54 +0000 [thread overview]
Message-ID: <20170323103153.GA9287@leverpostej> (raw)
In-Reply-To: <m24lylnw5q.fsf@baylibre.com>
On Wed, Mar 22, 2017 at 08:55:29AM -0700, Kevin Hilman wrote:
> Carlo Caione <carlo@caione.org> writes:
>
> > From: Carlo Caione <carlo@endlessm.com>
> >
> > While working on a related driver I noticed a couple of problems in the
> > meson-sm driver. The problems are unrelated but since the fixes touch the same
> > codebase I decided to submit these in the same patchset.
>
> Applied to amlogic tree, branch: v4.12/drivers
>
> I'd prefer to have acks from Mark and Srini, but since this has been on
> the list for awhile, I'm guessing that isn't going to happen, so
> consider this a request.
>From a quick scan, this looks fine to me. FWIW:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] meson-sm: Fix issues when reading data from sm
Date: Thu, 23 Mar 2017 10:31:54 +0000 [thread overview]
Message-ID: <20170323103153.GA9287@leverpostej> (raw)
In-Reply-To: <m24lylnw5q.fsf@baylibre.com>
On Wed, Mar 22, 2017 at 08:55:29AM -0700, Kevin Hilman wrote:
> Carlo Caione <carlo@caione.org> writes:
>
> > From: Carlo Caione <carlo@endlessm.com>
> >
> > While working on a related driver I noticed a couple of problems in the
> > meson-sm driver. The problems are unrelated but since the fixes touch the same
> > codebase I decided to submit these in the same patchset.
>
> Applied to amlogic tree, branch: v4.12/drivers
>
> I'd prefer to have acks from Mark and Srini, but since this has been on
> the list for awhile, I'm guessing that isn't going to happen, so
> consider this a request.
>From a quick scan, this looks fine to me. FWIW:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
next prev parent reply other threads:[~2017-03-23 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 15:17 [PATCH 0/2] meson-sm: Fix issues when reading data from sm Carlo Caione
2017-03-03 15:17 ` Carlo Caione
2017-03-03 15:17 ` [PATCH 1/2] firmware: meson-sm: Check for buffer output size Carlo Caione
2017-03-03 15:17 ` Carlo Caione
2017-03-22 16:28 ` Srinivas Kandagatla
2017-03-22 16:28 ` Srinivas Kandagatla
2017-03-03 15:17 ` [PATCH 2/2] firmware: meson-sm: Allow 0 as valid return value Carlo Caione
2017-03-03 15:17 ` Carlo Caione
2017-03-22 15:55 ` [PATCH 0/2] meson-sm: Fix issues when reading data from sm Kevin Hilman
2017-03-22 15:55 ` Kevin Hilman
2017-03-23 10:31 ` Mark Rutland [this message]
2017-03-23 10:31 ` Mark Rutland
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=20170323103153.GA9287@leverpostej \
--to=mark.rutland@arm.com \
--cc=linus-amlogic@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.