From: Heiner Kallweit <hkallweit1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
"linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] spi: fsl-espi: avoid processing uninitalized data on error
Date: Thu, 27 Oct 2016 20:11:35 +0200 [thread overview]
Message-ID: <7456def3-64e4-e679-b38a-2edc4b4072b0@gmail.com> (raw)
In-Reply-To: <20161027101417.GG25322-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
Am 27.10.2016 um 12:14 schrieb Mark Brown:
> On Thu, Oct 27, 2016 at 07:55:30AM +0200, Heiner Kallweit wrote:
>> When we get a spurious interrupt in fsl_espi_irq, we end up
>> processing four uninitalized bytes of data, as shown in this
>> warning message:
>
> This doesn't apply against current code, please check and resend.
>
OK, I'll provide an updated one. I thought it was intended to
replace Arnd's patch for next.
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-10-27 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 5:55 [PATCH] spi: fsl-espi: avoid processing uninitalized data on error Heiner Kallweit
[not found] ` <b5d3b5f3-034e-28c4-e616-69de4bf7cb8f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-10-27 10:14 ` Mark Brown
[not found] ` <20161027101417.GG25322-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-10-27 18:11 ` Heiner Kallweit [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=7456def3-64e4-e679-b38a-2edc4b4072b0@gmail.com \
--to=hkallweit1-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).