linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
Cc: Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v3] arm64: defconfig: Config that had RPMSG_CHAR now gets RPMSG_CTRL
Date: Wed, 1 Jun 2022 14:50:45 +0100	[thread overview]
Message-ID: <YpdutV3/jOsfPb5c@arm.com> (raw)
In-Reply-To: <c497e1ef-5a62-d956-4516-87e7b53a6001@foss.st.com>

On Wed, Jun 01, 2022 at 03:25:42PM +0200, Arnaud POULIQUEN wrote:
> Gentle reminder.
> Please notice that Mathieu replied with a "Reviewed-by".

We usually leave the defconfig updates to the SoC team. Cc'ing Arnd.

Catalin

> Thanks,
> Arnaud
> 
> On 4/5/22 18:11, Arnaud Pouliquen wrote:
> > In the commit 617d32938d1b ("rpmsg: Move the rpmsg control device
> > from rpmsg_char to rpmsg_ctrl"), we split the rpmsg_char driver in two.
> > By default give everyone who had the old driver enabled the rpmsg_ctrl
> > driver too.
> > 
> > Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
> > ---
> > 
> > This patch is extracted from the series [1] that has been partially
> > integrated in the Linux Kernel 5.18-rc1.
> > 
> > Update vs previous version:
> > - Add missing "---" separation marker after "Signed-off-by".
> > 
> > [1]https://lore.kernel.org/lkml/15be2f08-ba03-2b80-6f53-2056359d5c41@gmail.com/T/
> > [2]https://lore.kernel.org/linux-arm-kernel/CANLsYky1_b80qPbgOaLGVYD-GEr21V6C653iGEB7VCU=GbGvAQ@mail.gmail.com/T/
> > ---
> >  arch/arm64/configs/defconfig | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> > index 50aa3d75ab4f..3f8906b8a2ca 100644
> > --- a/arch/arm64/configs/defconfig
> > +++ b/arch/arm64/configs/defconfig
> > @@ -1053,6 +1053,7 @@ CONFIG_QCOM_Q6V5_PAS=m
> >  CONFIG_QCOM_SYSMON=m
> >  CONFIG_QCOM_WCNSS_PIL=m
> >  CONFIG_RPMSG_CHAR=m
> > +CONFIG_RPMSG_CTRL=m
> >  CONFIG_RPMSG_QCOM_GLINK_RPM=y
> >  CONFIG_RPMSG_QCOM_GLINK_SMEM=m
> >  CONFIG_RPMSG_QCOM_SMD=y

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-01 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 16:11 [PATCH v3] arm64: defconfig: Config that had RPMSG_CHAR now gets RPMSG_CTRL Arnaud Pouliquen
2022-04-06 14:48 ` Mathieu Poirier
2022-06-01 13:25 ` Arnaud POULIQUEN
2022-06-01 13:50   ` Catalin Marinas [this message]
2022-07-12  8:17     ` Arnaud POULIQUEN

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=YpdutV3/jOsfPb5c@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=will@kernel.org \
    /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).