From: Thomas Gleixner <tglx@linutronix.de>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Mark Brown <broonie@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Yijing Wang <wangyijing@huawei.com>,
Michal Simek <michal.simek@xilinx.com>,
kernel-build-reports@lists.linaro.org,
linaro-kernel <linaro-kernel@lists.linaro.org>,
linux-next list <linux-next@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: next-20150806 build: 2 failures 52 warnings (next-20150806)
Date: Tue, 18 Aug 2015 14:47:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1508181447480.3873@nanos> (raw)
In-Reply-To: <55CB0205.2020408@linux.intel.com>
On Wed, 12 Aug 2015, Jiang Liu wrote:
> On 2015/8/11 2:31, Bjorn Helgaas wrote:
> > On Fri, Aug 7, 2015 at 4:49 AM, Mark Brown <broonie@kernel.org> wrote:
> >> On Fri, Aug 07, 2015 at 07:39:54AM +1000, Stephen Rothwell wrote:
> >>> On Thu, 6 Aug 2015 18:53:22 +0100 Mark Brown <broonie@kernel.org> wrote:
> >>
> >>>> msi_desc_to_pci_sys_data doesn't appear to exist anywhere else in
> >>>> current -next, the usage was introduced by e39758e0ea769e632e (PCI: Use
> >>>> helper functions to access fields in struct msi_desc) at which time it
> >>>> looks like it did exist but I can't immediately see where it was removed.
> >>
> >>> Actually, it is a typo ... all other uses are spelt msi_desc_to_pci_sysdata.
> >
> > c179c9b978b9 ("PCI: Add helper function msi_desc_to_pci_sysdata()")
> > added msi_desc_to_pci_sysdata().
> >
> > e39758e0ea76 ("PCI: Use helper functions to access fields in struct
> > msi_desc") added calls to msi_desc_to_pci_sysdata() in
> > pci-keystone-dw.c and pcie-designware.c, but to
> > msi_desc_to_pci_sys_data() (note extra "_") in pcie-xilinx.c.
> >
> > These were both merged by Thomas, so I assume he and Jiang will sort this out.
> Hi Bjorn and Mark,
> Thomas is on vocation this two weeks, so I will send him a
> patch to fix this issue once Thomas is back.
I'm back :)
next prev parent reply other threads:[~2015-08-18 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:00 next-20150806 build: 2 failures 52 warnings (next-20150806) Build bot for Mark Brown
2015-08-06 17:19 ` Mark Brown
2015-08-06 18:50 ` Andy Gross
2015-08-06 17:27 ` Mark Brown
2015-08-06 21:52 ` James Hogan
2015-08-06 17:53 ` Mark Brown
2015-08-06 21:39 ` Stephen Rothwell
2015-08-07 1:56 ` Jiang Liu
2015-08-07 9:49 ` Mark Brown
2015-08-10 18:31 ` Bjorn Helgaas
2015-08-12 8:21 ` Jiang Liu
2015-08-18 12:47 ` Thomas Gleixner [this message]
2015-08-06 18:01 ` Mark Brown
2015-08-06 20:17 ` Joerg Roedel
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=alpine.DEB.2.11.1508181447480.3873@nanos \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=jiang.liu@linux.intel.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=sfr@canb.auug.org.au \
--cc=wangyijing@huawei.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