linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Rich Felker <dalias@libc.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Christoph Hellwig <hch@infradead.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>, Rob Landley <rob@landley.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Mon, 1 Jun 2020 23:12:17 +0200	[thread overview]
Message-ID: <CAK8P3a3=XjLvQYz2xB_1=XHFb34Q6zhAJbpJEDRUPX_r=kEBRg@mail.gmail.com> (raw)
In-Reply-To: <20200601181259.GV1079@brightrain.aerifal.cx>

On Mon, Jun 1, 2020 at 8:13 PM Rich Felker <dalias@libc.org> wrote:
> On Sat, May 30, 2020 at 10:08:09AM +0200, John Paul Adrian Glaubitz wrote:
> > On 5/29/20 7:53 PM, Rich Felker wrote:
> > > [PATCH next] sh: remove call to memset after dma_alloc_coherent
> > > https://marc.info/?l=linux-sh&m=157793031102356&w=2
>
> Can anyone confirm that this is correct/safe?

Yes, this is safe, I checked both the API definition and the sh
implementation in arch_dma_alloc(), which passes __GFP_ZERO.

       Arnd

  reply	other threads:[~2020-06-01 21:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 22:19 [GIT PULL] sh: remove sh5 support Arnd Bergmann
2020-04-24 22:19 ` [PATCH 1/1] " Arnd Bergmann
2020-05-07 14:35 ` [GIT PULL] " Christoph Hellwig
2020-05-28  5:46   ` Christoph Hellwig
2020-05-28  5:55     ` John Paul Adrian Glaubitz
2020-05-28  9:40       ` Rob Landley
2020-05-28 16:14     ` Rich Felker
2020-05-28 22:14       ` Rich Felker
2020-05-28 22:28         ` Rob Landley
2020-05-28 22:32         ` John Paul Adrian Glaubitz
2020-05-28 22:37           ` Rich Felker
2020-05-29 14:35         ` Christoph Hellwig
2020-05-29 14:30       ` Christoph Hellwig
2020-05-29 17:53         ` Rich Felker
2020-05-29 18:22           ` Christoph Hellwig
2020-05-30  8:08           ` John Paul Adrian Glaubitz
2020-05-30  8:47             ` Geert Uytterhoeven
2020-05-31  3:20             ` Rob Landley
2020-05-31  8:03               ` John Paul Adrian Glaubitz
2020-06-01  2:55                 ` Rich Felker
2020-06-01  8:16                   ` John Paul Adrian Glaubitz
2020-06-01 18:13             ` Rich Felker
2020-06-01 21:12               ` Arnd Bergmann [this message]
2020-06-02  1:33               ` Rich Felker
2020-06-02  2:49                 ` Andrew Morton
2020-06-02  2:53                   ` Rich Felker
2020-06-03  7:27                 ` John Paul Adrian Glaubitz
2020-06-03  7:31                   ` John Paul Adrian Glaubitz
2020-06-05 15:38                 ` John Paul Adrian Glaubitz
2020-06-05 15:43                   ` Rich Felker
2020-06-05 15:47                     ` John Paul Adrian Glaubitz
2020-06-05 15:59                       ` Rich Felker
2020-06-05 17:58                         ` John Paul Adrian Glaubitz
2020-06-05 18:23                           ` Geert Uytterhoeven
2020-06-06  0:50                             ` Andrew Morton

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='CAK8P3a3=XjLvQYz2xB_1=XHFb34Q6zhAJbpJEDRUPX_r=kEBRg@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ysato@users.sourceforge.jp \
    /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).