From: Krzysztof Halasa <khc@pm•waw.pl>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: hdlc tree build failure
Date: Thu, 14 Aug 2008 20:45:34 +0200 [thread overview]
Message-ID: <m34p5nmo4x.fsf@maximus.localdomain> (raw)
In-Reply-To: <20080814153732.63307d0e.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Thu\, 14 Aug 2008 15\:37\:32 +1000")
Hi,
Stephen Rothwell <sfr@canb•auug.org.au> writes:
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/net/wan/hdlc_ppp.c: In function 'ppp_cp_parse_cr':
> drivers/net/wan/hdlc_ppp.c:384: error: 'struct hdlc_device' has no
> member named 'stats'
Oops, sorry about that, my fault, already fixed it.
> I have to wonder if this was even build tested ...
It was, without the dev->stats patch which I made later. Then
I rebased, and even saw the problem while doing so :-(
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-08-14 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 5:37 linux-next: hdlc tree build failure Stephen Rothwell
2008-08-14 18:45 ` Krzysztof Halasa [this message]
2008-08-15 0:27 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 8:37 Stephen Rothwell
2008-07-08 9:28 ` Pierre Ossman
2008-07-08 9:30 ` Pierre Ossman
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=m34p5nmo4x.fsf@maximus.localdomain \
--to=khc@pm$(echo .)waw.pl \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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