From: philip.li@intel.com (Li, Philip)
To: linux-arm-kernel@lists.infradead.org
Subject: [rjarzmik:test/daniel 23/34] sound/arm/pxa2xx-ac97.c:27:10: fatal error: mach/regs-ac97.h: No such file or directory
Date: Thu, 24 May 2018 00:21:39 +0000 [thread overview]
Message-ID: <831EE4E5E37DCC428EB295A351E662494CB32366@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <87lgcaxxy4.fsf@belgarion.home>
> Subject: Re: [rjarzmik:test/daniel 23/34] sound/arm/pxa2xx-ac97.c:27:10: fatal
> error: mach/regs-ac97.h: No such file or directory
>
> "Li, Philip" <philip.li@intel.com> writes:
>
> >> On Wednesday, May 23, 2018 10:46 AM, kbuild test robot wrote:
> >> > tree: https://github.com/rjarzmik/linux test/daniel
> >> > head: f495e2dbc482d8f01a1ee20e86284ee9c0c8fa98
> >> > commit: 4cd654b13b9bcc0f206d414497b798ed42df573a [23/34] HACK:
> select
> >> SND_PXA_SOC_SSP for SND_SIMPLE_CARD
> >>
> >> This patch is just a local hack in one of my scratch-pad branches and is
> >> not meant for upstream inclusion. Could you remove the branch or make
> >> sure it isn't picked up by test robots?
> > thanks for info, we will exclude it from testing.
> Hi Li, Philip,
>
> Is it possible to exclude a pattern instead ?
> I mean would it be possible to exclude each branch of the form "test/*" ?
sure, we will use test/.* to match the branch to exclude.
>
> Cheers.
>
> --
> Robert
next prev parent reply other threads:[~2018-05-24 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 8:46 [rjarzmik:test/daniel 23/34] sound/arm/pxa2xx-ac97.c:27:10: fatal error: mach/regs-ac97.h: No such file or directory kbuild test robot
2018-05-23 9:00 ` Daniel Mack
2018-05-23 13:05 ` Li, Philip
2018-05-23 14:12 ` Robert Jarzmik
2018-05-24 0:21 ` Li, Philip [this message]
2018-05-24 6:48 ` Robert Jarzmik
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=831EE4E5E37DCC428EB295A351E662494CB32366@shsmsx102.ccr.corp.intel.com \
--to=philip.li@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.