From: Bjorn Helgaas <bhelgaas@google.com>
To: Minghuan Lian <Minghuan.Lian@freescale.com>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Zang Roy-R61911 <r61911@freescale.com>,
Hu Mingkai-B21284 <B21284@freescale.com>,
Scott Wood <scottwood@freescale.com>,
Yoder Stuart-B08248 <stuart.yoder@freescale.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v4] PCI: Layerscape: Add Layerscape PCIe driver
Date: Mon, 29 Sep 2014 14:11:44 -0600 [thread overview]
Message-ID: <20140929201144.GB15712@google.com> (raw)
In-Reply-To: <1411888107-27640-1-git-send-email-Minghuan.Lian@freescale.com>
On Sun, Sep 28, 2014 at 03:08:27PM +0800, Minghuan Lian wrote:
> Add support for Freescale Layerscape PCIe controller. This driver
> re-uses the designware core code.
> ...
This looks pretty good to me. I have a couple trivial comments below.
Anybody else have any suggestions? I'd like to get this merged in the next
day or two so we can get this into v3.18.
I'd like a MAINTAINERS update, too, so I know who to expect patches and
acks from.
> +static irqreturn_t ls_pcie_msi_irq_handler(int irq, void *data)
> +{
> + struct pcie_port *pp = data;
> + struct ls_pcie *pcie = to_ls_pcie(pp);
> + unsigned int msi_irq;
> +
> + /* clear the interrupt */
> + regmap_write(pcie->scfg, SCFG_SPIMSICLRCR,
> + MSI_LS1021A_DATA(pcie->index));
> +
> + msi_irq = irq_find_mapping(pp->irq_domain, 0);
> + if (!msi_irq) {
> + /*
> + * that's weird who triggered this?
> + * just clear it
> + */
> + dev_err(pcie->dev, "unexpected MSI\n");
Scott suggested either using dev_dbg or rate-limiting this dev_err.
> +static int ls_add_pcie_port(struct ls_pcie *pcie)
> +{
> + struct pcie_port *pp;
> + int ret;
> +
> + if (!pcie)
> + return -EINVAL;
Unnecessary NULL pointer check (we already checked it below).
Bjorn
next prev parent reply other threads:[~2014-09-29 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 7:08 [PATCH v4] PCI: Layerscape: Add Layerscape PCIe driver Minghuan Lian
2014-09-29 20:11 ` Bjorn Helgaas [this message]
2014-09-30 9:18 ` Arnd Bergmann
2014-10-13 6:51 ` Lian Minghuan-B31939
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=20140929201144.GB15712@google.com \
--to=bhelgaas@google.com \
--cc=B21284@freescale.com \
--cc=Minghuan.Lian@freescale.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=r61911@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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).