From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2 v2] Bugfixes for Tegra memory controllers.
Date: Tue, 11 Jun 2013 12:33:17 +0200 [thread overview]
Message-ID: <20130611103316.GC932@manwe> (raw)
In-Reply-To: <1370945479-2917-1-git-send-email-ttynkkynen@nvidia.com>
On Tue, Jun 11, 2013 at 01:11:17PM +0300, Tuomas Tynkkynen wrote:
> Hi,
>
> Here's two simple bugfixes for the Tegra memory controllers.
>
> v2: Fix a dumb bug in the bit masking.
>
> Tuomas Tynkkynen (2):
> memory: tegra20-mc: Fix hang in IRQ handler.
> memory: tegra30-mc: Fix IRQ handler.
>
> drivers/memory/tegra20-mc.c | 5 ++++-
> drivers/memory/tegra30-mc.c | 9 ++++++---
> 2 files changed, 10 insertions(+), 4 deletions(-)
Both patches:
Reviewed-by: Thierry Reding <thierry.reding@gmail.com>
On a side-note, the subject format looks a bit strange and my guess is
you had to manually edit it to insert "v2". git can do it for you when
you generate the patch series using:
git format-patch --subject-prefix='PATCH v2'
That'll also automatically add the v2 to all individual patches instead
of just the cover-letter.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130611/82711ac0/attachment.sig>
next prev parent reply other threads:[~2013-06-11 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 10:11 [PATCH 0/2 v2] Bugfixes for Tegra memory controllers Tuomas Tynkkynen
2013-06-11 10:11 ` [PATCH 1/2] memory: tegra20-mc: Fix hang in IRQ handler Tuomas Tynkkynen
2013-06-11 10:11 ` [PATCH 2/2] memory: tegra30-mc: Fix " Tuomas Tynkkynen
2013-06-11 10:33 ` Thierry Reding [this message]
2013-06-11 16:10 ` [PATCH 0/2 v2] Bugfixes for Tegra memory controllers Stephen Warren
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=20130611103316.GC932@manwe \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@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 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).