From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Pervushin <dpervushin@embeddedalley.com>
Subject: Re: linux-next: ubi tree build failure
Date: Fri, 05 Jun 2009 08:54:44 +0300 [thread overview]
Message-ID: <4A28B324.2090806@nokia.com> (raw)
In-Reply-To: <20090605105842.de948d0b.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Always directly include the header files for APIs you use ...
Yes, right, those were forgotten.
> I see that this particular problem is now fixed, thanks.
Good, thanks!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2009-06-05 5:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 8:44 linux-next: ubi tree build failure Stephen Rothwell
2009-06-03 8:46 ` Artem Bityutskiy
2009-06-03 11:26 ` Artem Bityutskiy
2009-06-03 12:55 ` Artem Bityutskiy
2009-06-03 13:05 ` dmitry pervushin
2009-06-03 13:07 ` Artem Bityutskiy
2009-06-05 0:58 ` Stephen Rothwell
2009-06-05 5:54 ` Artem Bityutskiy [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=4A28B324.2090806@nokia.com \
--to=artem.bityutskiy@nokia.com \
--cc=dpervushin@embeddedalley.com \
--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;
as well as URLs for NNTP newsgroup(s).