Linux backports project
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: Possible to build-in backports modules into kernel
Date: Fri, 17 Apr 2015 23:42:32 +0200	[thread overview]
Message-ID: <20150417214231.GA3800@t61> (raw)
In-Reply-To: <1429295166.1885.6.camel@sipsolutions.net>

Hi there,

> > > https://backports.wiki.kernel.org/index.php/Documentation/integration
thanks for your comments and the link. I skip that before as I thought it's actually for
backports developers, not users. I'll read it more carefully.

> > Just to clarify, the entire kernel will need to be built from some tree. In my 
> > reading of the original post, I got the impression that Petr wanted to use a 
> > pre-built kernel.

> Yes, indeed, that's not possible - and doesn't really make sense anyway,
> since if you have access to the kernel image and sources to build
> against, you might as well rebuild the whole kernel.

I'm stack with very old kernel (2.6.37 for arm TI's DM365). No pre-built kernel , I've
built the kernel as well, everything is working nice. But as I use embedded device, it
would be nice to have the drivers build-in (performance).

For some of modules I get message: "This feature depends on another which has been
configured as a module. As a result, this feature will be built as a module.". I'll try to
find the dependency, but is there any hint, how to search?

Thanks a lot for backports, it helped me already :-).

Kind regards,
Petr

      reply	other threads:[~2015-04-17 21:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 13:30 Possible to build-in backports modules into kernel Petr Vorel
2015-04-17 16:14 ` Larry Finger
2015-04-17 17:28   ` Johannes Berg
2015-04-17 18:03     ` Luis R. Rodriguez
2015-04-17 18:22       ` Larry Finger
2015-04-17 18:26         ` Johannes Berg
2015-04-17 21:42           ` Petr Vorel [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=20150417214231.GA3800@t61 \
    --to=petr.vorel@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=backports@vger.kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=mcgrof@do-not-panic.com \
    /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