From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 17
Date: Thu, 18 Jul 2013 10:33:22 +0100 [thread overview]
Message-ID: <20130718093322.GC22506@sirena.org.uk> (raw)
In-Reply-To: <20130718120916.3bfd1ccdefdbc9e4fe907927@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Thu, Jul 18, 2013 at 12:09:16PM +1000, Stephen Rothwell wrote:
> On Thu, 18 Jul 2013 09:38:24 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > So these are the errors I got yesterday:
> > sound/soc/fsl/imx-mc13783.c:23:28: fatal error: asm/mach-types.h: No such file or directory
> > #include <asm/mach-types.h>
> > I didn't look closely enough, because this is the same error that I got
> > the previous day, but in a different file.
> I got this again today.
OK, thanks - this is the first report I've seen of this, I'm really
surprised the zero day tester hasn't been spottinng any of this stuff as
it's definitely running on the tree and sending me other things (mostly
warnings).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-18 9:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 4:13 linux-next: Tree for Jul 17 Stephen Rothwell
2013-07-17 8:31 ` Mark Brown
2013-07-17 23:38 ` Stephen Rothwell
2013-07-18 2:09 ` Stephen Rothwell
2013-07-18 9:33 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-17 8:53 Stephen Rothwell
2015-07-17 5:26 Stephen Rothwell
2015-07-18 19:41 ` Paul Gortmaker
2015-07-20 3:00 ` Stephen Rothwell
2017-07-17 3:19 Stephen Rothwell
2018-07-17 9:05 Stephen Rothwell
2019-07-17 4:29 Stephen Rothwell
2019-07-17 15:30 ` Sedat Dilek
2019-07-17 15:33 ` Darrick J. Wong
2019-07-17 15:44 ` Sedat Dilek
2020-07-17 11:40 Stephen Rothwell
2023-07-17 3:46 Stephen Rothwell
2024-07-17 6:34 Stephen Rothwell
2025-07-17 9:36 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=20130718093322.GC22506@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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