Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Helge Deller <deller@gmx.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Matthew Wilcox <Matthew.Wilcox@genedata.com>,
	adevries@thepuffingroup.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 715/33]
Date: Wed, 30 Jun 1999 17:14:49 +0200	[thread overview]
Message-ID: <19990630171449.V30362@mencheca.ch.genedata.com> (raw)
In-Reply-To: <377A21E9.C22A6F25@gmx.de>; from Helge Deller on Wed, Jun 30, 1999 at 03:55:53PM +0200

On Wed, Jun 30, 1999 at 03:55:53PM +0200, Helge Deller wrote:
> Alan Cox wrote:
> 
> > > printk("-3\n");
> > > printk("%p\n", *cmdline_p);
> > > printk("%s\n", *cmdline_p);
> > >         strcpy(*cmdline_p,saved_command_line);  // copy the command-line
> > > printk("-2\n");
> > >
> > > I get the following printout:
> > >
> > > setup_arch(000a0860, 000767e0, 000767e4)
> > > -3
> > > f000013c
> > >  zC
> >
> > f000013c is in I/O space. Is the command line really meant to point into
> > I/O space..
> 
> It was completely wrong to use strcpy() !
> Sorry, my fault !!!!!
> It is now corrected in CVS.

So it is.  Thank you very much.

Has the price of beef gone up?
[if you've not booted the kernel, there's no way you'll understand this :-)]

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

  parent reply	other threads:[~1999-06-30 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-30  2:31 [parisc-linux] 715/33] Alex deVries
1999-06-30  7:49 ` Matthew Wilcox
1999-06-30 10:41   ` Alan Cox
     [not found]     ` <377A21E9.C22A6F25@gmx.de>
1999-06-30 15:14       ` Matthew Wilcox [this message]
1999-06-30 15:40         ` Philipp Rumpf

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=19990630171449.V30362@mencheca.ch.genedata.com \
    --to=matthew.wilcox@genedata.com \
    --cc=adevries@thepuffingroup.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=deller@gmx.de \
    --cc=parisc-linux@thepuffingroup.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