From: Shane Chien <shane.chien@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, wsd_upstream@mediatek.com,
linux-kernel@vger.kernel.org, jiaxin.yu@mediatek.com,
shane.chien@mediatek.com, linux-mediatek@lists.infradead.org,
eason.yen@mediatek.com
Subject: [PATCH 0/1] Use memset_io to access I/O memory
Date: Fri, 18 Sep 2020 18:00:18 +0800 [thread overview]
Message-ID: <1600423219-29058-1-git-send-email-shane.chien@mediatek.com> (raw)
From: "Shane.Chien" <shane.chien@mediatek.com>
Use memset_io to access I/O memory, instead of
memset.
Shane.Chien (1):
ASoC: Use memset_io to access I/O memory
sound/core/pcm_native.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.7.9.5
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Shane Chien <shane.chien@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <wsd_upstream@mediatek.com>,
<jiaxin.yu@mediatek.com>, <eason.yen@mediatek.com>,
<shane.chien@mediatek.com>
Subject: [PATCH 0/1] Use memset_io to access I/O memory
Date: Fri, 18 Sep 2020 18:00:18 +0800 [thread overview]
Message-ID: <1600423219-29058-1-git-send-email-shane.chien@mediatek.com> (raw)
From: "Shane.Chien" <shane.chien@mediatek.com>
Use memset_io to access I/O memory, instead of
memset.
Shane.Chien (1):
ASoC: Use memset_io to access I/O memory
sound/core/pcm_native.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2020-09-18 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 10:00 Shane Chien [this message]
2020-09-18 10:00 ` [PATCH 0/1] Use memset_io to access I/O memory Shane Chien
2020-09-18 10:00 ` [PATCH] ASoC: " Shane Chien
2020-09-18 10:00 ` Shane Chien
2020-09-18 11:01 ` Mark Brown
2020-09-18 11:01 ` Mark Brown
2020-09-18 10:05 ` [PATCH 0/1] " Mark Brown
2020-09-18 10:05 ` Mark Brown
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=1600423219-29058-1-git-send-email-shane.chien@mediatek.com \
--to=shane.chien@mediatek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eason.yen@mediatek.com \
--cc=jiaxin.yu@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=wsd_upstream@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.