From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] minicom: don't build after rootfs
Date: Tue, 29 Jun 2021 07:09:06 +0200 [thread overview]
Message-ID: <20210629050906.2523267-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20210612203817.26185-1-rhi@pengutronix.de>
Thanks, applied as e1f0f2abd3116fdcb5e3e3211321aef801e959ff.
Michael
[sent from post-receive hook]
On Tue, 29 Jun 2021 07:09:05 +0200, Roland Hieber <rhi@pengutronix.de> wrote:
> minicom only needs /var/lock to be present. ROOTFS should always be
> enabled anyways, so no need to depend on it – otherwise, minicom will
> always be rebuilt after the rootfs is rebuild, which often happens e.g.
> when the Git hash changes.
>
> Fixes: 8f259a6e887248160a01 (2021-05-24, "minicom: version bump 2.6.2. -> 2.8")
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20210612203817.26185-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/minicom.in b/rules/minicom.in
> index d3580bda069a..abbb15252822 100644
> --- a/rules/minicom.in
> +++ b/rules/minicom.in
> @@ -4,7 +4,6 @@ menuconfig MINICOM
> tristate
> prompt "minicom "
> select NCURSES
> - select ROOTFS
> select ROOTFS_VAR_LOCK
> select CKERMIT if MINICOM_KERMIT
> help
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-06-29 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 20:38 [ptxdist] [PATCH] " Roland Hieber
2021-06-29 5:09 ` Michael Olbrich [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=20210629050906.2523267-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.de \
/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