linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Richter <rric@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Marek <mmarek@suse.cz>, Jan Beulich <JBeulich@suse.com>,
	dt.tangr@gmail.com, Geert Uytterhoeven <geert@linux-m68k.org>,
	James Hogan <james.hogan@imgtec.com>,
	Christian Kujau <lists@nerdbynature.de>,
	Mike Marciniszyn <mike.marciniszyn@intel.com>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	"Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>,
	zzs0213@gmail.com,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT] kbuild changes for v3.11-rc1
Date: Fri, 12 Jul 2013 11:57:21 +0100	[thread overview]
Message-ID: <20130712105721.GF8731@rric.localhost> (raw)
In-Reply-To: <CA+55aFyVjugxM7cUDWi0ASWttYthCxa6e7X3CADknBcSFxWgew@mail.gmail.com>

On 11.07.13 10:16:18, Linus Torvalds wrote:
> On Thu, Jul 11, 2013 at 6:54 AM, Michal Marek <mmarek@suse.cz> wrote:
> >
> > Yeah. It also reveals another bug that we rewrite the kernel.release
> > file each time.

The odd thing I have in a specific configuration is that depmod is
missing the kernelrelease when I only build install rules, though I
had built everything before and kernelrelease should be there:

 $ make <makeflags>
 $ make <makeflags> modules_install zinstall
 ...
   DEPMOD  
 Usage: .../scripts/depmod.sh /sbin/depmod <kernelrelease>

Note that makeflags include the -j option, INSTALL_MOD_PATH and
INSTALL_PATH variables set, so no root perms required in this case.

I agree, the fix to add a dependency to the kernelrelease file is
wrong here since it rewrites the object tree, which should be readonly
for install rules.

I could reproduce the error above in my setup and will look at it
again, hopefully fixing it more carefully.

Appologize the trouble this made.

Thanks,

-Robert

  reply	other threads:[~2013-07-12 10:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 13:37 [GIT] kbuild changes for v3.11-rc1 Michal Marek
2013-07-11  2:11 ` Linus Torvalds
2013-07-11  4:26   ` Greg KH
2013-07-11 13:54   ` Michal Marek
2013-07-11 17:16     ` Linus Torvalds
2013-07-12 10:57       ` Robert Richter [this message]
2013-07-17 16:05         ` [PATCH] arm, kbuild: make "make install" not depend on vmlinux Robert Richter
2013-07-17 16:36           ` Linus Torvalds
2013-07-17 16:57             ` Robert Richter
2013-07-17 17:03               ` Linus Torvalds
2013-07-18  9:22                 ` Michal Marek
2013-09-30  8:49                   ` Robert Richter
2013-09-30 16:31                     ` Yann E. MORIN
2013-10-09  7:18                       ` Geert Uytterhoeven
2013-10-09 10:28                         ` Michal Marek
2013-10-09 10:46                           ` Geert Uytterhoeven

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=20130712105721.GF8731@rric.localhost \
    --to=rric@kernel.org \
    --cc=JBeulich@suse.com \
    --cc=dt.tangr@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=mike.marciniszyn@intel.com \
    --cc=mmarek@suse.cz \
    --cc=nicolas.dichtel@6wind.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yselkowitz@users.sourceforge.net \
    --cc=zzs0213@gmail.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;
as well as URLs for NNTP newsgroup(s).