From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Milan Zamazal <mzamazal@redhat.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Nuno Sá" <noname.nuno@gmail.com>
Subject: Re: [PATCH v3] iio: core: Prevent invalid memory access when there is no parent
Date: Wed, 19 Jul 2023 18:27:45 +0300 [thread overview]
Message-ID: <ZLgA8QG67QGROzwW@smile.fi.intel.com> (raw)
In-Reply-To: <20230719083208.88149-1-mzamazal@redhat.com>
On Wed, Jul 19, 2023 at 10:32:08AM +0200, Milan Zamazal wrote:
> Changes in v3:
> - The call trace in the commit message reduced to the minimum lines
> needed to explain the problem.
Precisely, that deserves my tag which I already had given :-)
Thank you!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-07-19 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 8:32 [PATCH v3] iio: core: Prevent invalid memory access when there is no parent Milan Zamazal
2023-07-19 15:27 ` Andy Shevchenko [this message]
2023-07-22 16:53 ` Jonathan Cameron
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=ZLgA8QG67QGROzwW@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mzamazal@redhat.com \
--cc=noname.nuno@gmail.com \
/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