From: Jonathan Cameron <jic23@kernel.org>
To: Nicolas Iooss <nicolas.iooss_linux@m4x.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: iio: initialize data pointer before using it
Date: Sun, 19 Jun 2016 12:58:57 +0100 [thread overview]
Message-ID: <afe789eb-0a01-cee9-7203-6e720f8c8c6a@kernel.org> (raw)
In-Reply-To: <19e60ec0-87cc-e79e-89a2-39857119640a@m4x.org>
On 19/06/16 11:03, Nicolas Iooss wrote:
> On 06/19/2016 11:41 AM, Lars-Peter Clausen wrote:
>> On 06/18/2016 11:12 PM, Nicolas Iooss wrote:
>>> ad7606_spi_read_block() reads SPI big-endian data into a buffer which is
>>> then converted to CPU byte-order with a second variable. This variable,
>>> data, has been left unitialized after commit 87787e5ef727 ("Staging:
>>> iio: Fix sparse endian warning").
>>
>> Hi,
>>
>> Thanks for the patch. A similar patch was already merged last week.
>
> Nice :) Actually I sent this patch because the bug is still present in
> linux-next tree [1] and I failed to see a reference to a dedicated
> development tree in MAINTAINERS.
>
This is just me being slow at sending a pull request.
Good point of the lack of a listed development tree. Will fix that so
no one else wastes their time as you have.
Sorry about that!
Jonathan
> Thanks for your quick reply!
>
> -- Nicolas
>
> [1]
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/drivers/staging/iio/adc/ad7606_spi.c
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-06-19 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 21:12 Nicolas Iooss
2016-06-19 9:41 ` Lars-Peter Clausen
2016-06-19 10:03 ` Nicolas Iooss
2016-06-19 11:58 ` Jonathan Cameron [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=afe789eb-0a01-cee9-7203-6e720f8c8c6a@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=ksenija.stanojevic@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.iooss_linux@m4x.org \
--cc=pmeerw@pmeerw.net \
/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
all inboxes | Powered by JetHome®