All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com>
Cc: u-boot@lists.denx.de,
	Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>,
	Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH] fs: fat: do not mangle short filenames
Date: Mon, 20 Mar 2023 13:01:05 -0400	[thread overview]
Message-ID: <20230320170105.GA8135@bill-the-cat> (raw)
In-Reply-To: <20230317120413.11066-1-stefan.herbrechtsmeier-oss@weidmueller.com>

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

On Fri, Mar 17, 2023 at 01:04:13PM +0100, Stefan Herbrechtsmeier wrote:

> From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
> 
> Do not mangle lower or mixed case filenames which fit into the upper
> case 8.3 short filename. This ensures FAT standard compatible short
> filenames (SFN) to support systems without long filename (LFN) support
> like boot roms (ex. SFN BOOT.BIN instead of BOOT~1.BIN for LFN
> boot.bin).
> 
> Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
> 
> ---
> 
>  fs/fat/fat_write.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)

Can we update test/py/tests/test_fs/ somewhere to have a test for this
case? Thanks.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-03-20 17:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 12:04 [PATCH] fs: fat: do not mangle short filenames Stefan Herbrechtsmeier
2023-03-20 17:01 ` Tom Rini [this message]
2023-03-21  7:43   ` Stefan Herbrechtsmeier
2023-03-21 15:35     ` Tom Rini
2023-03-21 15:53       ` Stefan Herbrechtsmeier
2023-03-21 15:54         ` Tom Rini
2023-03-22  8:51           ` Stefan Herbrechtsmeier
2023-03-22 13:20             ` Tom Rini
2023-03-31 14:15 ` Tom Rini

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=20230320170105.GA8135@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=sjg@chromium.org \
    --cc=stefan.herbrechtsmeier-oss@weidmueller.com \
    --cc=stefan.herbrechtsmeier@weidmueller.com \
    --cc=u-boot@lists.denx.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 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.