mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, David Smith <dsmith@redhat.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	Wenji Huang <wenji.huang@oracle.com>,
	Takashi Nishiie <t-nishiie@np.css.fujitsu.com>
Subject: Re: [PATCH] Marker depmod fix core kernel list
Date: Mon,  6 Oct 2008 13:23:16 -0700 (PDT)	[thread overview]
Message-ID: <20081006202316.805C51541E4@magilla.localdomain> (raw)
In-Reply-To: Theodore Tso's message of  Saturday, 4 October 2008 11:24:56 -0400 <20081004152456.GB23398@mit.edu>

> Also, something we need to consider is getting distributions to ship
> Modules.markers, and where it should be installed.  I would argue that
> it belongs in /lib/modules/`uname -r`, so maybe "make modules_install"
> should put it there?

Fedora kernel RPMs put it in /lib/modules/`uname -r`/build/, which is where
Module.symvers is installed.  This lands it in the kernel-devel RPM, which
is needed to build modules (and hence by Systemtap).

Since new uses of markers won't necessarily require building modules,
your suggestion is probably better.


Thanks,
Roland

      parent reply	other threads:[~2008-10-06 20:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 19:16 Markers in (non-module) kernel code? Theodore Ts'o
2008-10-03 19:54 ` [PATCH] Marker depmod fix core kernel list Mathieu Desnoyers
2008-10-04 15:24   ` Theodore Tso
2008-10-06  4:08     ` Greg KH
2008-10-10  9:39       ` Ingo Molnar
2008-10-10  9:39         ` Ingo Molnar
2008-10-10 15:48           ` Greg KH
2008-10-10  9:46         ` [PATCH RESEND] early_ioremap has a fencepost error Alan Cox
2008-10-10 10:21           ` Ingo Molnar
2008-10-06 20:23     ` Roland McGrath [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=20081006202316.805C51541E4@magilla.localdomain \
    --to=roland@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dsmith@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=t-nishiie@np.css.fujitsu.com \
    --cc=tytso@mit.edu \
    --cc=wenji.huang@oracle.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
all inboxes | Powered by JetHome®