All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Stripping kernel modules for ARC
Date: Thu, 15 Sep 2016 10:53:37 +0000	[thread overview]
Message-ID: <1473936815.4481.2.camel@synopsys.com> (raw)
In-Reply-To: <8760pxfuun.fsf@dell.be.48ers.dk>

Hi all,

On Thu, 2016-09-15 at 10:08 +0200, Peter Korsgaard wrote:
> > 
> > > 
> > > > 
> > > > > 
> > > > > > 
> > > > > > "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
> ?> Hello,
> ?> On Thu, 15 Sep 2016 09:18:58 +0200, Peter Korsgaard wrote:
> 
> ?>> Sounds good. When was this introduced and what about external kernel modules?
> 
> ?> Introduced in commit ac031f26e89cc04fc7504f31ae137857eb83a051, appeared
> ?> first in 2.6.18.
> 
> Ok, good!
> 
> ?> External kernel modules: the one using kbuild will do fine, as long as
> ?> we use the modules_install target of the kbuild build system and not
> ?> manually install/copy the .ko files.
> 
> ?> External kernel modules not using kbuild would obviously no longer be
> ?> stripped. Not sure how many of these we have today, and how to handle
> ?> them. They could be problematic :-/
> 
> I guess we'll just have to handle those explictly whenever we find them.

Let me cook up a patch which uses?INSTALL_MOD_STRIP=1 then.

-Alexey

      reply	other threads:[~2016-09-15 10:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 11:29 [Buildroot] Stripping kernel modules for ARC Alexey Brodkin
2016-09-14 19:00 ` Arnout Vandecappelle
2016-09-14 19:18 ` Vineet Gupta
2016-09-14 19:57   ` Peter Korsgaard
2016-09-14 20:00     ` Alexey Brodkin
2016-09-14 20:18     ` Vineet Gupta
2016-09-14 20:21       ` Peter Korsgaard
     [not found] ` <CAE2F3rCBwysRFrMf4CD6uLevvfw0TNaZGyptOj6MLDQvGPPwFg@mail.gmail.com>
2016-09-15  6:47   ` Thomas Petazzoni
2016-09-15  7:18     ` Peter Korsgaard
2016-09-15  7:49       ` Thomas Petazzoni
2016-09-15  8:08         ` Peter Korsgaard
2016-09-15 10:53           ` Alexey Brodkin [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=1473936815.4481.2.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.