From: Bjorn Helgaas <helgaas@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/3] PCI: tegra: Remove unused field
Date: Tue, 8 Mar 2016 15:44:42 -0600 [thread overview]
Message-ID: <20160308214442.GE27132@localhost> (raw)
In-Reply-To: <1455029553-9460-1-git-send-email-thierry.reding@gmail.com>
On Tue, Feb 09, 2016 at 03:52:31PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The num_ports field of the tegra_pcie structure is never used so it can
> be safely removed.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
Applied all three of these to pci/host-tegra for v4.6, thanks!
> ---
> drivers/pci/host/pci-tegra.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/pci/host/pci-tegra.c b/drivers/pci/host/pci-tegra.c
> index 4cb8157a4678..82d7ad3a1c3a 100644
> --- a/drivers/pci/host/pci-tegra.c
> +++ b/drivers/pci/host/pci-tegra.c
> @@ -295,7 +295,6 @@ struct tegra_pcie {
> struct tegra_msi msi;
>
> struct list_head ports;
> - unsigned int num_ports;
> u32 xbar_config;
>
> struct regulator_bulk_data *supplies;
> --
> 2.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-08 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 14:52 [PATCH 1/3] PCI: tegra: Remove unused field Thierry Reding
2016-02-09 14:52 ` [PATCH 2/3] PCI: tegra: Track bus -> CPU mapping Thierry Reding
2016-02-09 14:52 ` [PATCH 3/3] PCI: tegra: Remove misleading PHYS_OFFSET Thierry Reding
2016-03-08 21:44 ` Bjorn Helgaas [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=20160308214442.GE27132@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gnurou@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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).