From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Krystian Garbaciak <krystian.garbaciak@diasemi.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Anthony Olech <Anthony.Olech@diasemi.com>
Subject: Re: [PATCH 1/4] regmap: Reorganise internal read/write functions.
Date: Thu, 31 May 2012 17:41:49 +0100 [thread overview]
Message-ID: <20120531164148.GK2666@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201205311607.q4VG7avr012901@sw-eng-lt-dc-vm2>
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
On Thu, May 31, 2012 at 04:11:12PM +0200, Krystian Garbaciak wrote:
> +static int _regmap_raw_write(struct regmap *map, unsigned int reg,
> + const void *val, size_t val_len)
> +{
> + void *_val = (void *)val;
This is scary... why are we casting away const here?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-31 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 14:11 [PATCH 1/4] regmap: Reorganise internal read/write functions Krystian Garbaciak
2012-05-31 16:41 ` Mark Brown [this message]
2012-05-31 17:53 ` Krystian Garbaciak
2012-05-31 17:57 ` Mark Brown
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=20120531164148.GK2666@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Anthony.Olech@diasemi.com \
--cc=gregkh@linuxfoundation.org \
--cc=krystian.garbaciak@diasemi.com \
--cc=linux-kernel@vger.kernel.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