netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: oneukum@suse.com
Cc: netdev@vger.kernel.org, johan@kernel.org
Subject: Re: [PATCH] usb: hso: obey DMA rules in tiocmget
Date: Thu, 17 Oct 2019 14:19:55 -0400 (EDT)	[thread overview]
Message-ID: <20191017.141955.1615614075310331285.davem@davemloft.net> (raw)
In-Reply-To: <20191017095339.25034-1-oneukum@suse.com>

From: Oliver Neukum <oneukum@suse.com>
Date: Thu, 17 Oct 2019 11:53:38 +0200

> The serial state information must not be embedded into another
> data structure, as this interferes with cache handling for DMA
> on architectures without cache coherence..
> That would result in data corruption on some architectures
> Allocating it separately.
> 
> Signed-off-by: Oliver Neukum <oneukum@suse.com>

Applied, thanks Oliver.

  reply	other threads:[~2019-10-17 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  9:53 [PATCH] usb: hso: obey DMA rules in tiocmget Oliver Neukum
2019-10-17 18:19 ` David Miller [this message]
2019-10-17 18:20   ` David Miller
2019-10-17 20:35     ` Oliver Neukum

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=20191017.141955.1615614075310331285.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=johan@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.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;
as well as URLs for NNTP newsgroup(s).