From: Kalle Valo <kvalo@codeaurora.org>
To: "Michael Büsch" <m@bues.ch>
Cc: linux-wireless@vger.kernel.org, Albert Herranz <albert_herranz@yahoo.es>
Subject: Re: ssb: sdio: Don't overwrite const buffer if block_write fails
Date: Tue, 15 Jun 2021 10:11:21 +0000 (UTC) [thread overview]
Message-ID: <20210615101121.D987DC4338A@smtp.codeaurora.org> (raw)
In-Reply-To: <20210515210252.318be2ba@wiggum>
Michael Büsch <m@bues.ch> wrote:
> It doesn't make sense to clobber the const driver-side buffer, if a
> write-to-device attempt failed. All other SSB variants (PCI, PCMCIA and SoC)
> also don't corrupt the buffer on any failure in block_write.
> Therefore, remove this memset from the SDIO variant.
>
> Signed-off-by: Michael Büsch <m@bues.ch>
> Cc: stable@vger.kernel.org
Patch applied to wireless-drivers-next.git, thanks.
47ec636f7a25 ssb: sdio: Don't overwrite const buffer if block_write fails
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210515210252.318be2ba@wiggum/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-06-15 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 19:02 [PATCH] drivers/ssb/sdio: Don't overwrite const buffer if block_write fails Michael Büsch
2021-06-15 10:11 ` Kalle Valo [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=20210615101121.D987DC4338A@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=albert_herranz@yahoo.es \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
/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).