From: Mark Brown <broonie@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org, linux-pci@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Keith Busch <keith.busch@intel.com>,
linux-next@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20181008 build: 2 failures 22 warnings (next-20181008)
Date: Mon, 8 Oct 2018 23:35:55 +0100 [thread overview]
Message-ID: <20181008223555.GC4440@sirena.org.uk> (raw)
In-Reply-To: <20181008213006.GP120535@bhelgaas-glaptop.roam.corp.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 390 bytes --]
On Mon, Oct 08, 2018 at 04:30:06PM -0500, Bjorn Helgaas wrote:
> On Mon, Oct 08, 2018 at 10:20:21PM +0100, Mark Brown wrote:
> > introduced in e3fbcc7c4b130(PCI/AER: Covertly inject errors with ftrace
> > hooks). This field is not present on arm.
> I dropped e3fbcc7c4b130 and related patches already, so this should be gone
> in my current "next" branch (18b4baa4d9fc).
Great, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-10-08 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1g9cV0-0008Sg-4U@optimist>
2018-10-08 21:11 ` next-20181008 build: 2 failures 22 warnings (next-20181008) Mark Brown
2018-10-08 21:30 ` Borislav Petkov
2018-10-10 4:27 ` Stephen Rothwell
2018-10-10 4:33 ` Borislav Petkov
2018-10-11 23:37 ` Stephen Rothwell
2018-10-12 2:43 ` Stephen Rothwell
2018-10-08 21:20 ` Mark Brown
2018-10-08 21:30 ` Bjorn Helgaas
2018-10-08 22:35 ` Mark Brown [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=20181008223555.GC4440@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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