From: Rob Herring <robh@kernel.org>
To: Olivier Moysan <olivier.moysan@st.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
alsa-devel@alsa-project.org, alexandre.torgue@st.com,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
arnaud.pouliquen@st.com, tiwai@suse.com, perex@perex.cz,
broonie@kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] dt-bindings: stm32: dfsdm: remove stm32-adfsdm.txt binding
Date: Mon, 26 Oct 2020 09:34:23 -0500 [thread overview]
Message-ID: <20201026143423.GA118005@bogus> (raw)
In-Reply-To: <20201020155709.2621-3-olivier.moysan@st.com>
On Tue, 20 Oct 2020 17:57:09 +0200, Olivier Moysan wrote:
> Device tree audio configuration for STM32 DFSDM is already
> covered in the following binding:
> Documentation/devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml
> Remove stm32-adfsdm.txt obsolete binding.
>
> Signed-off-by: Olivier Moysan <olivier.moysan@st.com>
> ---
> .../bindings/sound/st,stm32-adfsdm.txt | 63 -------------------
> 1 file changed, 63 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/sound/st,stm32-adfsdm.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-26 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 15:57 [PATCH v2 0/2] dt-bindings: stm32: convert audio dfsdm to json-schema Olivier Moysan
2020-10-20 15:57 ` [PATCH v2 1/2] dt-bindings: stm32: dfsdm: update audio properties Olivier Moysan
2020-10-26 14:34 ` Rob Herring
2020-10-20 15:57 ` [PATCH v2 2/2] dt-bindings: stm32: dfsdm: remove stm32-adfsdm.txt binding Olivier Moysan
2020-10-26 14:34 ` Rob Herring [this message]
2020-10-26 16:57 ` Mark Brown
2020-10-26 23:45 ` [PATCH v2 0/2] dt-bindings: stm32: convert audio dfsdm to json-schema 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=20201026143423.GA118005@bogus \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=olivier.moysan@st.com \
--cc=perex@perex.cz \
--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).