From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Jiang Liu <jiang.liu@linux•intel.com>,
Yijing Wang <wangyijing@huawei•com>,
Thomas Gleixner <tglx@linutronix•de>,
Bjorn Helgaas <bhelgaas@google•com>,
Michal Simek <michal.simek@xilinx•com>,
kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-pci@vger•kernel.org
Subject: Re: next-20150806 build: 2 failures 52 warnings (next-20150806)
Date: Fri, 7 Aug 2015 10:49:57 +0100 [thread overview]
Message-ID: <20150807094957.GK20873@sirena.org.uk> (raw)
In-Reply-To: <20150807073954.3d19fc69@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
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.
Oh, that explains why it was so difficult to see where it was broken.
All the spinlock breakage for the past week masked other things so it
looked like it'd been added then later broken :/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-08-07 9:50 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 [this message]
2015-08-10 18:31 ` Bjorn Helgaas
2015-08-12 8:21 ` Jiang Liu
2015-08-18 12:47 ` Thomas Gleixner
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=20150807094957.GK20873@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=bhelgaas@google$(echo .)com \
--cc=jiang.liu@linux$(echo .)intel.com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=michal.simek@xilinx$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=wangyijing@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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