From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org
Subject: : drop kirkwood from nightly build coverage.
Date: Sat, 30 Aug 2014 23:58:43 -0400 [thread overview]
Message-ID: <20140831035843.GA26632@windriver.com> (raw)
Hi Stephen,
When you restart build coverage after vacation, the kirkwood should be
dropped. Log summary here:
http://kisskb.ellerman.id.au/kisskb/target/8110/
shows failures since July because it was removed from mainline.
commit ee39028df14ca3220c8af08a5230a0a910900b41
Author: Andrew Lunn <andrew@lunn.ch>
Date: Thu Jul 10 23:36:22 2014 +0200
ARM: Kirkwood: Remove kirkwood_defconfig
This is no longer needed now that kirkwood lives inside mach-mvebu.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Link: https://lkml.kernel.org/r/1405028192-9623-3-git-send-email-andrew@lunn.ch
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
:100644 000000 b9e480c... 0000000... D arch/arm/configs/kirkwood_defconfig
Thanks,
Paul.
next reply other threads:[~2014-08-31 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 3:58 Paul Gortmaker [this message]
2014-09-17 7:53 ` : drop kirkwood from nightly build coverage Stephen Rothwell
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=20140831035843.GA26632@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).