From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, arm@kernel.org,
soc@kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH v2 1/2] arm64: defconfig: Enable USB gadget with configfs
Date: Sun, 23 Aug 2020 10:42:41 +0200 [thread overview]
Message-ID: <20200823084241.GA2886@kozik-lap> (raw)
In-Reply-To: <20200823014600.GH30094@dragon>
On Sun, Aug 23, 2020 at 09:46:01AM +0800, Shawn Guo wrote:
> On Mon, Aug 17, 2020 at 08:56:53AM +0200, Krzysztof Kozlowski wrote:
> > USB OTG connections are pretty common for embedded and development
> > boards, for example to have networking or serial access to the device.
> > Build as a module the USB gadget configfs options so the defconfig can
> > be used in such development configurations.
> >
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
>
> Applied both, thanks.
Thanks, although few days ago I got confirmation from patchwork that
Olof already applied them to arm-soc. I cannot find them in arm-soc
or next trees, though.
Dear Olof,
Did you pick these up already?
Best regards,
Krzysztof
next parent reply other threads:[~2020-08-23 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200817065654.4419-1-krzk@kernel.org>
[not found] ` <20200823014600.GH30094@dragon>
2020-08-23 8:42 ` Krzysztof Kozlowski [this message]
2020-08-23 22:58 ` [PATCH v2 1/2] arm64: defconfig: Enable USB gadget with configfs Olof Johansson
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=20200823084241.GA2886@kozik-lap \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.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).