From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Lad Prabhakar <prabhakar.csengg@gmail.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH] misc: pci_endpoint_test: remove duplicate macro PCI_ENDPOINT_TEST_STATUS
Date: Thu, 26 Mar 2020 17:51:31 +0000 [thread overview]
Message-ID: <20200326175131.GA13622@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200321112139.17184-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Sat, Mar 21, 2020 at 11:21:39AM +0000, Lad Prabhakar wrote:
> PCI_ENDPOINT_TEST_STATUS is already defined in pci_endpoint_test.c along
> with the status bits, so this patch drops duplicate definition.
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> ---
> This patch applies on top of pci/endpoint branch [1].
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git
>
> drivers/misc/pci_endpoint_test.c | 1 -
> 1 file changed, 1 deletion(-)
Applied to pci/endpoint, thanks.
Lorenzo
> diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
> index b536ca4b14ca..a1bb94902b5a 100644
> --- a/drivers/misc/pci_endpoint_test.c
> +++ b/drivers/misc/pci_endpoint_test.c
> @@ -53,7 +53,6 @@
> #define STATUS_SRC_ADDR_INVALID BIT(7)
> #define STATUS_DST_ADDR_INVALID BIT(8)
>
> -#define PCI_ENDPOINT_TEST_STATUS 0x8
> #define PCI_ENDPOINT_TEST_LOWER_SRC_ADDR 0x0c
> #define PCI_ENDPOINT_TEST_UPPER_SRC_ADDR 0x10
>
> --
> 2.20.1
>
prev parent reply other threads:[~2020-03-26 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 11:21 [PATCH] misc: pci_endpoint_test: remove duplicate macro PCI_ENDPOINT_TEST_STATUS Lad Prabhakar
2020-03-26 17:51 ` Lorenzo Pieralisi [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=20200326175131.GA13622@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=arnd@arndb.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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 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).