From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Mark Brown <broonie@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the imx-mxs tree
Date: Fri, 27 Jan 2023 15:58:28 +0800 [thread overview]
Message-ID: <20230127075827.GN20713@T480> (raw)
In-Reply-To: <20230127110833.6cb7f4c8@canb.auug.org.au>
On Fri, Jan 27, 2023 at 11:08:33AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in arm-soc tree as a different commit
> (but the same patch):
>
> b82765d04e37 ("ARM: multi_v7_defconfig: Enable wm896x audio CODECs")
Dropped it from imx-mxs tree.
Shawn
>
> This is commit
>
> 74ab23d5a7fc ("ARM: multi_v7_defconfig: Enable wm896x audio CODECs")
>
> in the arm-soc tree.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Mark Brown <broonie@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the imx-mxs tree
Date: Fri, 27 Jan 2023 15:58:28 +0800 [thread overview]
Message-ID: <20230127075827.GN20713@T480> (raw)
In-Reply-To: <20230127110833.6cb7f4c8@canb.auug.org.au>
On Fri, Jan 27, 2023 at 11:08:33AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in arm-soc tree as a different commit
> (but the same patch):
>
> b82765d04e37 ("ARM: multi_v7_defconfig: Enable wm896x audio CODECs")
Dropped it from imx-mxs tree.
Shawn
>
> This is commit
>
> 74ab23d5a7fc ("ARM: multi_v7_defconfig: Enable wm896x audio CODECs")
>
> in the arm-soc tree.
_______________________________________________
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:[~2023-01-27 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 0:08 linux-next: duplicate patch in the imx-mxs tree Stephen Rothwell
2023-01-27 0:08 ` Stephen Rothwell
2023-01-27 7:58 ` Shawn Guo [this message]
2023-01-27 7:58 ` Shawn Guo
-- strict thread matches above, loose matches on Subject: below --
2024-07-10 1:53 Stephen Rothwell
2024-07-10 2:31 ` Shawn Guo
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=20230127075827.GN20713@T480 \
--to=shawnguo@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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.