LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.18.4
Date: Tue, 27 Jan 2015 21:26:50 +0000 [thread overview]
Message-ID: <54C8029A.5080500@linicks.net> (raw)
Wow.
On my amd64 it usually takes about 19 minutes to build my bespoke
kernel. After I downloaded/untarball/setup issued 'make' and then
watched TV for a bit. Bloody hell, next time I looked it was built...
in about 13 minutes. I suspected something was wrong, as I added new
ipsets classes tonight prior to this and had to double check.
Nope, all hunky dory :)
So, I just updated my lowly Samsung notebook bespoke build - normal
build time on this is about 57 minutes - 3.18.4 is now < 45 minutes.
Great stuff - I dunno what you guys changed, but it's good.
Many thanks,
Nick
P.S. also the Intel driver is fixed toboot too :)
--
Q. What's the difference between a duck and an elephant?
A. You can't get down off an elephant.
next reply other threads:[~2015-01-27 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 21:26 Nick Warne [this message]
2015-01-27 22:06 ` Linux 3.18.4 Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2015-01-27 17:13 Greg KH
2015-01-27 17:14 ` Greg KH
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=54C8029A.5080500@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.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 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).