mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Linux v2.6.27-rc1: problem with firmware stuff
Date: Tue, 29 Jul 2008 14:01:00 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807291359110.3334@nehalem.linux-foundation.org> (raw)
In-Reply-To: <200807292301.36987.rjw@sisk.pl>



On Tue, 29 Jul 2008, Rafael J. Wysocki wrote:
> 
> Actually, this happened due to some firmware files being created as root during
> installations of pre-rc -git kernels from the O= directory.  So, not a real
> problem, but somewhat confusing.

Yeah, I've had that happen myself. It used to be that "make 
modules_install" (as root, obviously) would try build a new version of the 
kernel, and as a result subsequent build attempts would fail horribly 
because of various random files being now owned-by-root.

I don't know if there is a whole lot we can do about it in general..

			Linus

  reply	other threads:[~2008-07-29 21:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  3:23 Linux v2.6.27-rc1 Linus Torvalds
2008-07-29  4:01 ` Nick Piggin
2008-07-29  9:49 ` 2.6.27-rc1: zd1211rw association fails Alistair John Strachan
2008-07-29 10:09   ` Johannes Berg
2008-07-29 11:25     ` Alistair John Strachan
2008-07-29 11:26       ` Johannes Berg
2008-07-29 11:37         ` Hugh Dickins
2008-07-29 11:46         ` Kalle Valo
2008-07-29 11:55         ` Alistair John Strachan
2008-07-29 12:04     ` Theodore Tso
2008-07-29 12:09       ` Johannes Berg
2008-07-29 12:15         ` Johannes Berg
2008-07-29 15:18           ` Theodore Tso
2008-07-29 17:52           ` John W. Linville
2008-07-30  4:48             ` David Miller
2008-07-29 13:57 ` Oops in microcode sysfs registration, Alistair John Strachan
2008-07-29 16:22   ` Pekka Paalanen
2008-07-29 16:50     ` Alistair John Strachan
2008-07-30  9:07       ` Dmitry Adamushko
2008-07-30 10:35         ` Dmitry Adamushko
2008-07-30 13:28           ` Peter Oruba
2008-07-31 12:49           ` Alistair John Strachan
2008-07-31 16:56           ` Ingo Molnar
2008-07-31 19:52             ` Dmitry Adamushko
2008-07-31 19:55               ` Dmitry Adamushko
2008-07-29 16:27 ` Linux v2.6.27-rc1 Jesse Barnes
2008-07-29 16:59   ` Linus Torvalds
2008-07-29 17:31     ` Roland Dreier
2008-07-30  9:03     ` Andrew Morton
2008-07-31 22:22       ` Linux v2.6.27-rc1: linux-next Rafael J. Wysocki
2008-07-29 20:49 ` Linux v2.6.27-rc1: problem with firmware stuff Rafael J. Wysocki
2008-07-29 21:01   ` Rafael J. Wysocki
2008-07-29 21:01     ` Linus Torvalds [this message]
2008-07-29 22:26       ` David Woodhouse
2008-07-29 21:37 ` Linux v2.6.27-rc1 Sam Ravnborg
2008-07-29 21:42   ` Linus Torvalds
2008-07-29 21:59     ` Sam Ravnborg
2008-07-29 22:03       ` Linus Torvalds
2008-07-29 22:30         ` Sam Ravnborg
2008-07-29 22:03 ` Linux v2.6.27-rc1: fails to compile Grant Coady
2008-07-29 22:40   ` Frederik Deweerdt
2008-07-29 23:46     ` Grant Coady

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=alpine.LFD.1.10.0807291359110.3334@nehalem.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

Powered by JetHome