From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Silence sparse warning
Date: Tue, 20 Mar 2012 10:34:10 +0200 [thread overview]
Message-ID: <20120320083407.GC27063@aemeltch-MOBL1> (raw)
In-Reply-To: <1332178760.14217.213.camel@aeonflux>
Hi Marcel,
On Mon, Mar 19, 2012 at 10:39:20AM -0700, Marcel Holtmann wrote:
> > - memcpy(&val, &uuid128[12], 4);
> > + memcpy(&tmp, &uuid128[12], 4);
> >
> > - val = le32_to_cpu(val);
> > + val = le32_to_cpu(tmp);
>
> why aren't we using get_unaligned_le32?
You are right here, just sent new version.
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-03-20 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 11:26 [PATCH] Bluetooth: Silence sparse warning Andrei Emeltchenko
2012-03-19 17:39 ` Marcel Holtmann
2012-03-20 8:34 ` Andrei Emeltchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-20 8:32 Andrei Emeltchenko
2012-03-20 13:19 ` Gustavo Padovan
2012-03-20 15:49 ` Marcel Holtmann
2012-03-20 16:08 Andrei Emeltchenko
2012-03-20 16:18 ` Marcel Holtmann
2012-03-20 16:24 ` Andrei Emeltchenko
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=20120320083407.GC27063@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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