From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Thomas Körper" <thomas.koerper@esd.eu>, linux-can@vger.kernel.org
Subject: Re: [PATCH 1/1] can: esd_usb2: Fix sparse warnings
Date: Mon, 16 Mar 2015 14:24:41 +0100 [thread overview]
Message-ID: <5506D999.8000609@pengutronix.de> (raw)
In-Reply-To: <1426495709-10810-1-git-send-email-thomas.koerper@esd.eu>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
On 03/16/2015 09:48 AM, Thomas Körper wrote:
> The hnd field of the structs does not need to be __le32: the
> device just returns the value without using it itself.
>
> Signed-off-by: Thomas Körper <thomas.koerper@esd.eu>
Applied to can-next.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-16 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 8:48 [PATCH 1/1] can: esd_usb2: Fix sparse warnings Thomas Körper
2015-03-16 10:53 ` Marc Kleine-Budde
2015-03-16 13:24 ` Marc Kleine-Budde [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=5506D999.8000609@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=thomas.koerper@esd.eu \
/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;
as well as URLs for NNTP newsgroup(s).