From: Max Filippov <jcmvbkbc@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Chris Zankel <chris@zankel.net>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@linux-xtensa.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xtensa/PCI: Remove unused variable
Date: Mon, 17 Jun 2019 09:34:28 -0700 [thread overview]
Message-ID: <CAMo8BfJMUOmF_Py1wtWCKHG=S=ckrq0-K8DFHFmaDr22BUU6QA@mail.gmail.com> (raw)
In-Reply-To: <1560694321-31380-1-git-send-email-linux@roeck-us.net>
On Sun, Jun 16, 2019 at 7:12 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> gcc reports:
>
> arch/xtensa/kernel/pci.c:40:32: warning:
> 'pci_ctrl_tail' defined but not used
>
> which is indeed the case.
>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> arch/xtensa/kernel/pci.c | 1 -
> 1 file changed, 1 deletion(-)
Applied to my xtensa tree.
--
Thanks.
-- Max
prev parent reply other threads:[~2019-06-17 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 14:12 [PATCH] xtensa/PCI: Remove unused variable Guenter Roeck
2019-06-17 16:34 ` Max Filippov [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='CAMo8BfJMUOmF_Py1wtWCKHG=S=ckrq0-K8DFHFmaDr22BUU6QA@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linux@roeck-us.net \
/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).