From: Andra Danciu <andradanciu1997@gmail.com>
To: timur@kernel.org, nicoleotsuka@gmail.com, Xiubo.Lee@gmail.com,
festevam@gmail.com, lgirdwood@gmail.com, broonie@kernel.org,
perex@perex.cz, tiwai@suse.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de, linux-imx@nxp.com,
alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, daniel.baluta@gmail.com
Subject: [PATCH 0/2] Fix invalid license IDS
Date: Sun, 14 Apr 2019 22:14:48 +0300 [thread overview]
Message-ID: <20190414191450.18377-1-andradanciu1997@gmail.com> (raw)
This series of patches solves two issues reported by Thomas Gleixner
Andra Danciu (2):
ASoC: mpc5200_dma: Fix invalid license ID
ASoC: mpc5200_psc_i2s: Fix invalid license ID
sound/soc/fsl/mpc5200_dma.c | 2 +-
sound/soc/fsl/mpc5200_psc_i2s.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.11.0
next reply other threads:[~2019-04-14 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 19:14 Andra Danciu [this message]
2019-04-14 19:14 ` [PATCH 1/2] ASoC: mpc5200_dma: Fix invalid license ID Andra Danciu
2019-04-14 21:53 ` Fabio Estevam
2019-04-15 7:23 ` Thomas Gleixner
2019-04-15 7:26 ` Daniel Baluta
2019-04-15 7:29 ` Daniel Baluta
2019-04-15 7:33 ` Thomas Gleixner
2019-04-15 8:53 ` Applied "ASoC: mpc5200_dma: Fix invalid license ID" to the asoc tree Mark Brown
2019-05-02 2:18 ` Mark Brown
2019-04-14 19:14 ` [PATCH 2/2] ASoC: mpc5200_psc_i2s: Fix invalid license ID Andra Danciu
2019-04-15 8:53 ` Applied "ASoC: mpc5200_psc_i2s: Fix invalid license ID" to the asoc tree Mark Brown
2019-05-02 2:18 ` 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=20190414191450.18377-1-andradanciu1997@gmail.com \
--to=andradanciu1997@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
--cc=timur@kernel.org \
--cc=tiwai@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).