From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: davej@redhat.com, cpufreq@www.linux.org.uk
Subject: Re: [PATCH] fix cpufreq_update_policy
Date: Wed, 28 Jan 2004 19:24:27 -0500 [thread overview]
Message-ID: <200401281924.27484.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040128221636.GA5390@dominikbrodowski.de>
On Wednesday 28 January 2004 05:16 pm, Dominik Brodowski wrote:
> On Wed, Jan 28, 2004 at 05:12:30PM -0500, Dmitry Torokhov wrote:
> > Why not change it to:
> >
> > policy = *data;
> >
> > ?
>
> Because I doubt this works for whole structs. Or am I totally wrong
> (again)?
>
> Dominik
The assignment does not work only for arrays because really arrays are
constant pointers:
char a[] == char * const a
With structures everything is clear, size, etc. I think that K&R did not
support structure assignment but I believe that it appeared at least in
C89.
--
Dmitry
prev parent reply other threads:[~2004-01-29 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 21:52 [PATCH] fix cpufreq_update_policy Dominik Brodowski
2004-01-28 22:12 ` Dmitry Torokhov
2004-01-28 22:16 ` Dominik Brodowski
2004-01-29 0:24 ` Dmitry Torokhov [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=200401281924.27484.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux@dominikbrodowski.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.