All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Sloat <KSloat@aampglobal.com>
To: "Eugen.Hristev@microchip.com" <Eugen.Hristev@microchip.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"Nicolas.Ferre@microchip.com" <Nicolas.Ferre@microchip.com>,
	"Ludovic.Desroches@microchip.com"
	<Ludovic.Desroches@microchip.com>
Subject: RE: MICROCHIP ISC DRIVER Bug: Possible NULL struct pointer dereference case
Date: Tue, 20 Nov 2018 14:50:30 +0000	[thread overview]
Message-ID: <DM5PR07MB4119530EBAEE458BF6CF112CADD90@DM5PR07MB4119.namprd07.prod.outlook.com> (raw)
In-Reply-To: <6d1f98c0-31be-9b89-db2e-c1813ed2975d@microchip.com>

> Hello Ken,
> 
> Indeed this is a bug, I saw it before as well, but so far, this has not appeared with the sensors we have connected. I have been trying to get around to fix it, but it's not a simple fix, much rather a rework of the driver part that handles the raw > formats.
>
> Feel free to submit patches if you find a good fix/rework and I will have a look and test it for the sensors which I currently have.
>
> Thanks again,
> Eugen

Hi Eugen,

Thanks for your quick reply. I will see what I can come up with. I may reply with additional questions.

Thanks,
Ken Sloat

  reply	other threads:[~2018-11-21  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 23:06 MICROCHIP ISC DRIVER Bug: Possible NULL struct pointer dereference case Ken Sloat
2018-11-20  7:07 ` Eugen.Hristev
2018-11-20 14:50   ` Ken Sloat [this message]
2018-11-20 20:43   ` [PATCH v1 1/1] media: atmel-isc: Add safety checks for NULL isc->raw_fmt struct Ken Sloat
2018-11-21  7:36     ` Eugen.Hristev
2018-11-21 14:50       ` Ken Sloat
2018-11-23 13:49         ` Eugen.Hristev
2018-11-26 13:35           ` Ken Sloat

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=DM5PR07MB4119530EBAEE458BF6CF112CADD90@DM5PR07MB4119.namprd07.prod.outlook.com \
    --to=ksloat@aampglobal.com \
    --cc=Eugen.Hristev@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=linux-media@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 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.