From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: guoren@kernel.org
Cc: Guo Ren <ren_guo@c-sky.com>,
linux-csky@vger.kernel.org, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH V2] configs/csky_gx6605s: bump kernel to 5.0 and use buildroot toolchain
Date: Fri, 2 Aug 2019 23:46:19 +0200 [thread overview]
Message-ID: <20190802234619.0342bfe5@windsurf.home> (raw)
In-Reply-To: <1561376581-19568-1-git-send-email-guoren@kernel.org>
Hello Guo,
On Mon, 24 Jun 2019 19:43:01 +0800
guoren@kernel.org wrote:
> +BR2_ROOTFS_DEVICE_CREATION_STATIC=y
I dropped this option to keep the default behavior of using devtmpfs,
and applied.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-08-02 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 11:43 [PATCH V2] configs/csky_gx6605s: bump kernel to 5.0 and use buildroot toolchain guoren
2019-08-02 21:46 ` Thomas Petazzoni [this message]
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=20190802234619.0342bfe5@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=ren_guo@c-sky.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).