From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: "Chalamarla,
Tirumalesh"
<Tirumalesh.Chalamarla-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
Cc: "mark.rutland-5wv7dgnIgG8@public.gmane.org"
<mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"Akula,
Geethasowjanya"
<Geethasowjanya.Akula-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>,
"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH V4] iommu/arm-smmu-v2: Workaround for ThunderX errata#27704
Date: Thu, 24 Mar 2016 17:51:37 +0000 [thread overview]
Message-ID: <20160324175127.GA29365@arm.com> (raw)
In-Reply-To: <44D97D2C-5114-4FCD-AE3E-9404391FD449-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
On Thu, Mar 24, 2016 at 05:36:39PM +0000, Chalamarla, Tirumalesh wrote:
> Do you want me to resend it with path version number change?
Shouldn't be any need. I've queued this locally, and will push out when
I update my repo after the merge window.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4] iommu/arm-smmu-v2: Workaround for ThunderX errata#27704
Date: Thu, 24 Mar 2016 17:51:37 +0000 [thread overview]
Message-ID: <20160324175127.GA29365@arm.com> (raw)
In-Reply-To: <44D97D2C-5114-4FCD-AE3E-9404391FD449@caviumnetworks.com>
On Thu, Mar 24, 2016 at 05:36:39PM +0000, Chalamarla, Tirumalesh wrote:
> Do you want me to resend it with path version number change?
Shouldn't be any need. I've queued this locally, and will push out when
I update my repo after the merge window.
Will
next prev parent reply other threads:[~2016-03-24 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 21:56 [PATCH V4] iommu/arm-smmu-v2: Workaround for ThunderX errata#27704 Tirumalesh Chalamarla
2016-03-04 21:56 ` Tirumalesh Chalamarla
[not found] ` <1457128569-13878-1-git-send-email-tchalamarla-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-03-24 17:36 ` Chalamarla, Tirumalesh
2016-03-24 17:36 ` Chalamarla, Tirumalesh
[not found] ` <44D97D2C-5114-4FCD-AE3E-9404391FD449-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-03-24 17:51 ` Will Deacon [this message]
2016-03-24 17:51 ` Will Deacon
[not found] ` <20160324175127.GA29365-5wv7dgnIgG8@public.gmane.org>
2016-03-24 18:29 ` Chalamarla, Tirumalesh
2016-03-24 18:29 ` Chalamarla, Tirumalesh
2016-03-28 18:57 ` Radha Mohan
2016-03-28 18:57 ` Radha Mohan
2016-03-28 19:25 ` Radha Mohan
2016-03-28 19:25 ` Radha Mohan
-- strict thread matches above, loose matches on Subject: below --
2016-03-04 18:39 Tirumalesh Chalamarla
2016-03-04 18:39 ` Tirumalesh Chalamarla
[not found] ` <1457116784-13287-1-git-send-email-tchalamarla-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-03-04 20:59 ` Will Deacon
2016-03-04 20:59 ` Will Deacon
[not found] ` <20160304205945.GG7886-5wv7dgnIgG8@public.gmane.org>
2016-03-04 21:35 ` Tirumalesh Chalamarla
2016-03-04 21:35 ` Tirumalesh Chalamarla
2016-03-04 3:44 Tirumalesh Chalamarla
2016-03-04 3:44 ` Tirumalesh Chalamarla
[not found] ` <1457063043-10623-1-git-send-email-tchalamarla-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-03-04 16:02 ` Will Deacon
2016-03-04 16:02 ` Will Deacon
[not found] ` <20160304160221.GC7886-5wv7dgnIgG8@public.gmane.org>
2016-03-04 18:09 ` Tirumalesh Chalamarla
2016-03-04 18:09 ` Tirumalesh Chalamarla
[not found] ` <56D9CF3E.7080607-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-03-04 18:16 ` Tirumalesh Chalamarla
2016-03-04 18:16 ` Tirumalesh Chalamarla
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=20160324175127.GA29365@arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=Geethasowjanya.Akula-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org \
--cc=Tirumalesh.Chalamarla-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.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.