All of lore.kernel.org
 help / color / mirror / Atom feed
From: trix@redhat.com
To: mdf@kernel.org, robh+dt@kernel.org, hao.wu@intel.com,
	corbet@lwn.net, fbarrat@linux.ibm.com, ajd@linux.ibm.com,
	bbrezillon@kernel.org, arno@natisbad.org, schalla@marvell.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	gregkh@linuxfoundation.org, Sven.Auhagen@voleatech.de,
	grandmaster@al2klimov.de
Cc: linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org,
	linux-staging@lists.linux.dev, Tom Rix <trix@redhat.com>
Subject: [PATCH 04/11] crypto: marvell: cesa: change FPGA indirect article to an
Date: Tue,  8 Jun 2021 14:23:43 -0700	[thread overview]
Message-ID: <20210608212350.3029742-6-trix@redhat.com> (raw)
In-Reply-To: <20210608212350.3029742-1-trix@redhat.com>

From: Tom Rix <trix@redhat.com>

Change use of 'a fpga' to 'an fpga'

Signed-off-by: Tom Rix <trix@redhat.com>
---
 drivers/crypto/marvell/cesa/cesa.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/crypto/marvell/cesa/cesa.h b/drivers/crypto/marvell/cesa/cesa.h
index c1007f2ba79c8..d215a6bed6bc7 100644
--- a/drivers/crypto/marvell/cesa/cesa.h
+++ b/drivers/crypto/marvell/cesa/cesa.h
@@ -66,7 +66,7 @@
 #define CESA_SA_ST_ACT_1			BIT(1)
 
 /*
- * CESA_SA_FPGA_INT_STATUS looks like a FPGA leftover and is documented only
+ * CESA_SA_FPGA_INT_STATUS looks like an FPGA leftover and is documented only
  * in Errata 4.12. It looks like that it was part of an IRQ-controller in FPGA
  * and someone forgot to remove  it while switching to the core and moving to
  * CESA_SA_INT_STATUS.
-- 
2.26.3


WARNING: multiple messages have this Message-ID (diff)
From: trix@redhat.com
To: mdf@kernel.org, robh+dt@kernel.org, hao.wu@intel.com,
	corbet@lwn.net, fbarrat@linux.ibm.com, ajd@linux.ibm.com,
	bbrezillon@kernel.org, arno@natisbad.org, schalla@marvell.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	gregkh@linuxfoundation.org, Sven.Auhagen@voleatech.de,
	grandmaster@al2klimov.de
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	Tom Rix <trix@redhat.com>,
	linux-fpga@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 04/11] crypto: marvell: cesa: change FPGA indirect article to an
Date: Tue,  8 Jun 2021 14:23:43 -0700	[thread overview]
Message-ID: <20210608212350.3029742-6-trix@redhat.com> (raw)
In-Reply-To: <20210608212350.3029742-1-trix@redhat.com>

From: Tom Rix <trix@redhat.com>

Change use of 'a fpga' to 'an fpga'

Signed-off-by: Tom Rix <trix@redhat.com>
---
 drivers/crypto/marvell/cesa/cesa.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/crypto/marvell/cesa/cesa.h b/drivers/crypto/marvell/cesa/cesa.h
index c1007f2ba79c8..d215a6bed6bc7 100644
--- a/drivers/crypto/marvell/cesa/cesa.h
+++ b/drivers/crypto/marvell/cesa/cesa.h
@@ -66,7 +66,7 @@
 #define CESA_SA_ST_ACT_1			BIT(1)
 
 /*
- * CESA_SA_FPGA_INT_STATUS looks like a FPGA leftover and is documented only
+ * CESA_SA_FPGA_INT_STATUS looks like an FPGA leftover and is documented only
  * in Errata 4.12. It looks like that it was part of an IRQ-controller in FPGA
  * and someone forgot to remove  it while switching to the core and moving to
  * CESA_SA_INT_STATUS.
-- 
2.26.3


  parent reply	other threads:[~2021-06-08 21:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 21:23 [PATCH 00/11] fpga: change FPGA indirect article to an trix
2021-06-08 21:23 ` trix
2021-06-08 21:23 ` trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 01/11] dt-bindings: fpga: fpga-region: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 02/11] Documentation: fpga: dfl: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 03/11] Documentation: ocxl.rst: " trix
2021-06-08 21:23   ` trix
2021-06-09  3:10   ` Andrew Donnellan
2021-06-09  3:10     ` Andrew Donnellan
2021-06-08 21:23 ` trix [this message]
2021-06-08 21:23   ` [PATCH 04/11] crypto: marvell: cesa: " trix
2021-06-17  8:00   ` Herbert Xu
2021-06-17  8:00     ` Herbert Xu
2021-06-08 21:23 ` [PATCH 05/11] fpga: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 06/11] fpga: bridge: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 07/11] fpga-mgr: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 08/11] fpga: region: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 09/11] fpga: of-fpga-region: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 10/11] fpga: stratix10-soc: " trix
2021-06-08 21:23   ` trix
2021-06-08 21:23 ` [PATCH 11/11] staging: fpgaboot: " trix
2021-06-08 21:23   ` trix

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=20210608212350.3029742-6-trix@redhat.com \
    --to=trix@redhat.com \
    --cc=Sven.Auhagen@voleatech.de \
    --cc=ajd@linux.ibm.com \
    --cc=arno@natisbad.org \
    --cc=bbrezillon@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=fbarrat@linux.ibm.com \
    --cc=grandmaster@al2klimov.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mdf@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=schalla@marvell.com \
    /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.