From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: ep93xx: add dma_masks for the M2P and M2M DMA controllers
Date: Thu, 04 Dec 2014 17:08:13 +0100 [thread overview]
Message-ID: <8117546.fJoYSDGdY9@wuerfel> (raw)
In-Reply-To: <DC148C5AA1CEBA4E87973D432B1C2D8826070BCE@P3PWEX4MB008.ex4.secureserver.net>
On Monday 01 December 2014 21:14:36 Hartley Sweeten wrote:
> On Monday, December 01, 2014 10:59 AM, Arnd Bergmann wrote:
> > Is there any harm in applying the fix on older kernels? If not, I'd just
> > mark it as stable for 3.11, which will cause it to get backported to
> > 3.17, 3.14 and 3.12 but not 3.10 or older longerm releases.
>
> I don't see any harm with it. It just adds the dma_mask data that
> should have been there anyway.
>
Ok, I've applied it to the fixes branch now as a reminder, with the
Cc: <stable@vger.kernel.org> # v3.11+
line added. It's already in next/fixes-non-critical, so the patch will
make it into 3.19, but if this is the only patch left for 3.18, we probably
won't send it. If not, I'll send an email to the stable list so it gets
backported.
I just noticed that we didn't have arm at kernel.org on Cc and you had just
sent the patch to me personally. To ensure that something gets picked up,
please send it to the arm at kernel.org alias so it doesn't accidentally get
lost, thanks!
Arnd
next prev parent reply other threads:[~2014-12-04 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 17:23 [PATCH] arm: ep93xx: add dma_masks for the M2P and M2M DMA controllers H Hartley Sweeten
2014-11-28 11:35 ` Arnd Bergmann
2014-11-28 22:30 ` Hartley Sweeten
2014-12-01 17:16 ` Hartley Sweeten
2014-12-01 17:58 ` Arnd Bergmann
2014-12-01 21:14 ` Hartley Sweeten
2014-12-04 16:08 ` Arnd Bergmann [this message]
[not found] <1416415519-4903-1-git-send-email-hsweeten@visionengravers.com>
2014-11-19 17:55 ` Alexander Sverdlin
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=8117546.fJoYSDGdY9@wuerfel \
--to=arnd@arndb.de \
--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).