From: Roman Suvorov <4rvs19@gmail.com>
To: Pascal Klein <p.p.k@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Builds
Date: Wed, 18 Apr 2012 16:16:10 -0400 [thread overview]
Message-ID: <2A68BAC5-6AAD-4AC6-B841-1A88F16ECEFB@gmail.com> (raw)
In-Reply-To: <4F8E77B7.1030201@web.de>
Hi Pascal,
Thanks for your reply!
Correct me if I'm wrong, but don't patches modify just the source code (.c/.h files)? You would still need to compile it to binary code to see the changes in action, right?
What I'm looking into is how much time a typical kernel developer spends with the build system every day.
Regards,
Roman.
On 18-Apr-2012, at 4:13 , Pascal Klein wrote:
> Hello Roman,
>
> Mostly there is no need of building a new kernel - as in most cases new developments can be added as a patch without building the kernel.
>
> For normal users there is also no need as new kernel versions are provided by the distro teams.
>
> What are you looking for?
>
> Sincerely,
>
> Pascal
> from Germany
>
next parent reply other threads:[~2012-04-18 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F8E77B7.1030201@web.de>
2012-04-18 20:16 ` Roman Suvorov [this message]
2012-04-18 5:13 kernel builds Roman Suvorov
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=2A68BAC5-6AAD-4AC6-B841-1A88F16ECEFB@gmail.com \
--to=4rvs19@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.p.k@web.de \
/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
all inboxes | Powered by JetHome®