public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	Andy Whitcroft <apw@shadowen.org>, Andrew Morton <akpm@osdl.org>,
	Olaf Hering <olaf@aepfle.de>,
	linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Jean Delvare <khali@linux-fr.org>,
	Herbert Poetzl <herbert@13thfloor.at>,
	Andrey Borzenkov <arvidjaar@mail.ru>
Subject: Re: .version keeps being updated
Date: Thu, 11 Jan 2007 14:55:08 +0100	[thread overview]
Message-ID: <jeejq1is77.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0701111424390.29801@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Thu, 11 Jan 2007 14:27:59 +0100 (MET)")

Jan Engelhardt <jengelh@linux01.gwdg.de> writes:

>   ../drivers/char$ objcopy -j .modinfo -O binary sonypi.ko 
>   objcopy: stvfMiji: Permission denied
>
> Why does it want to create a file there? This one works better:

objcopy works in-place when only one file argument is passed.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2007-01-11 13:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  9:20 .version keeps being updated Jean Delvare
2007-01-09  9:32 ` Gene Heskett
2007-01-09 17:05 ` Andrey Borzenkov
2007-01-09 20:44   ` Jean Delvare
2007-01-09 21:31     ` Andrew Morton
2007-01-09 23:21       ` Linus Torvalds
2007-01-09 23:25         ` Andrew Morton
2007-01-09 23:33           ` David Miller
2007-01-09 23:39           ` Andi Kleen
2007-01-10  1:43           ` Herbert Poetzl
2007-01-10  8:53           ` Jean Delvare
2007-01-10 16:52           ` Martin J. Bligh
2007-01-10 17:05             ` Jean Delvare
2007-01-10 11:31         ` Jan Engelhardt
2007-01-10 13:45     ` Roman Zippel
2007-01-10 16:01       ` Olaf Hering
2007-01-10 17:10       ` Jean Delvare
2007-01-10 19:02         ` Linus Torvalds
2007-01-10 19:31           ` Olaf Hering
2007-01-10 20:02             ` Olaf Hering
2007-01-10 22:56               ` Jan Engelhardt
2007-01-10 23:35                 ` Segher Boessenkool
2007-01-11 13:27                   ` Jan Engelhardt
2007-01-11 13:55                     ` Andreas Schwab [this message]
2007-01-11 17:39                       ` Segher Boessenkool
2007-01-11 18:01                         ` Jan Engelhardt
2007-01-10 21:33             ` Linus Torvalds
2007-01-10 19:32           ` Linus Torvalds
2007-01-10 21:20             ` Andy Whitcroft
2007-01-11 10:56             ` Andy Whitcroft
2007-01-11 12:38           ` Roman Zippel
2007-01-11 13:05             ` Andy Whitcroft
2007-01-11 16:47             ` Linus Torvalds
2007-01-09 21:55 ` Luca Tettamanti
2007-01-10  7:34   ` Jean Delvare
2007-01-09 23:25 ` Willy Tarreau

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=jeejq1is77.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=arvidjaar@mail.ru \
    --cc=herbert@13thfloor.at \
    --cc=jengelh@linux01.gwdg.de \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=segher@kernel.crashing.org \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.org \
    /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