linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ohaugan@codeaurora.org (Olav Haugan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/1] iommu/arm-smmu: Do not access non-existing S2CR registers
Date: Sat, 13 Sep 2014 08:36:53 -0700	[thread overview]
Message-ID: <54146495.8020609@codeaurora.org> (raw)
In-Reply-To: <20140828105552.GI22580@arm.com>

On 8/28/2014 3:55 AM, Will Deacon wrote:
> On Tue, Aug 26, 2014 at 11:37:30AM +0100, Will Deacon wrote:
>> On Sat, Aug 23, 2014 at 01:12:32AM +0100, Olav Haugan wrote:
>>> The number of S2CR registers is not properly set when stream
>>> matching is not supported. Fix this and add check that we do not try to
>>> access outside of the number of S2CR regisrers.
>>
>> Sorry for the bother, but could you base this on either iommu/devel or
>> iommu/staging please? Now that the merge window is well and truly over, I
>> moved those branches forward, so you needn't worry about iommu/pci anymore
>> (which, as you pointed out, contains a bunch of WIP patches which should
>> hold-up useful fixes like this one).
> 
> Actually, it looks like this was eaten by our sorry excuse for an email
> service. I've managed to apply a version from the archive, thanks.
> 

Thanks Will. Sorry for the late reply. I have been OoO.

Thanks,

Olav

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

      reply	other threads:[~2014-09-13 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23  0:12 [PATCH v4 1/1] iommu/arm-smmu: Do not access non-existing S2CR registers Olav Haugan
2014-08-26 10:37 ` Will Deacon
2014-08-28 10:55   ` Will Deacon
2014-09-13 15:36     ` Olav Haugan [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=54146495.8020609@codeaurora.org \
    --to=ohaugan@codeaurora.org \
    --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).