All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chen Lin <chen45464546@163.com>
Cc: will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
	treding@nvidia.com, linux-arm-kernel@lists.infradead.org,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	Chen Lin <chen.lin5@zte.com.cn>
Subject: Re: [PATCH] iommu/arm-smmu: Warn once when the perfetcher errata patch fails to allpy
Date: Sun, 23 Oct 2022 16:36:49 +0200	[thread overview]
Message-ID: <Y1VRgf1wsng07cMT@kroah.com> (raw)
In-Reply-To: <20221022024559.4913-1-chen45464546@163.com>

On Sat, Oct 22, 2022 at 10:45:59AM +0800, Chen Lin wrote:
> From: Chen Lin <chen.lin5@zte.com.cn>
> 
> Default reset value of secure banked register SMMU_sACR.cache_lock is 1.
> If it is not been set to 0 by secure software(eg: atf), the non-secure 
> linux cannot clear ARM_MMU500_ACTLR_CPRE bit. In this situation,
> the prefetcher errata is not applied successfully, warn once.
> 
> Signed-off-by: Chen Lin <chen.lin5@zte.com.cn>
> ---
>  drivers/iommu/arm/arm-smmu/arm-smmu-impl.c | 3 +++
>  1 file changed, 3 insertions(+)

As has been stated many times before, please fix your email systems and
stop using personal accounts, if you wish for us to think that you
really are developing from a zte.com.cn account.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Chen Lin <chen45464546@163.com>
Cc: will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
	treding@nvidia.com, linux-arm-kernel@lists.infradead.org,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	Chen Lin <chen.lin5@zte.com.cn>
Subject: Re: [PATCH] iommu/arm-smmu: Warn once when the perfetcher errata patch fails to allpy
Date: Sun, 23 Oct 2022 16:36:49 +0200	[thread overview]
Message-ID: <Y1VRgf1wsng07cMT@kroah.com> (raw)
In-Reply-To: <20221022024559.4913-1-chen45464546@163.com>

On Sat, Oct 22, 2022 at 10:45:59AM +0800, Chen Lin wrote:
> From: Chen Lin <chen.lin5@zte.com.cn>
> 
> Default reset value of secure banked register SMMU_sACR.cache_lock is 1.
> If it is not been set to 0 by secure software(eg: atf), the non-secure 
> linux cannot clear ARM_MMU500_ACTLR_CPRE bit. In this situation,
> the prefetcher errata is not applied successfully, warn once.
> 
> Signed-off-by: Chen Lin <chen.lin5@zte.com.cn>
> ---
>  drivers/iommu/arm/arm-smmu/arm-smmu-impl.c | 3 +++
>  1 file changed, 3 insertions(+)

As has been stated many times before, please fix your email systems and
stop using personal accounts, if you wish for us to think that you
really are developing from a zte.com.cn account.

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-10-23 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22  2:45 [PATCH] iommu/arm-smmu: Warn once when the perfetcher errata patch fails to allpy Chen Lin
2022-10-22  2:45 ` Chen Lin
2022-10-23 14:36 ` Greg KH [this message]
2022-10-23 14:36   ` Greg KH

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=Y1VRgf1wsng07cMT@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chen.lin5@zte.com.cn \
    --cc=chen45464546@163.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=treding@nvidia.com \
    --cc=will@kernel.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.