From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Gavin Schenk <g.schenk@eckelmann.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] rootfs: Fix creation of the /media directory
Date: Thu, 8 Oct 2020 09:49:29 +0200 [thread overview]
Message-ID: <20201008074929.kehjhuacpfj3lmhi@pengutronix.de> (raw)
In-Reply-To: <20201008073253.20055-1-g.schenk@eckelmann.de>
[-- Attachment #1.1: Type: text/plain, Size: 971 bytes --]
On Thu, Oct 08, 2020 at 09:32:53AM +0200, Gavin Schenk wrote:
> Ensure that with PTXCONF_ROOTFS_MEDIA set directory '/media' is created
> even if none of PTXCONF_ROOTFS_MEDIA[1-6] is set.
>
> On our read-only system we mount a tmpfs on directory '/media' in order
> to dynamically create additional mount points there.
>
> Fixes: 63e2d8696 (rootfs: don't create empty /media subdirs)
> Signed-off-by: Gavin Schenk <g.schenk@eckelmann.de>
> ---
> Hi,
>
> the "messed whitespaces" of changes in our mail server software.
> Our IT department implemented a workaround, I hope this
> mail looks better.
It seems the workaround worked fine. I didn't try to apply, but at least
now there are tabs in your patch.
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-10-08 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 7:32 Gavin Schenk
2020-10-08 7:49 ` Uwe Kleine-König [this message]
2020-10-09 12:18 ` Michael Olbrich
2020-10-14 10:30 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20201008074929.kehjhuacpfj3lmhi@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=g.schenk@eckelmann.de \
--cc=ptxdist@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