public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Askar Safin <safinaskar@gmail.com>
To: nfraprado@collabora.com
Cc: Tim.Bird@sony.com, bhelgaas@google.com, dan.carpenter@linaro.org,
	davidgow@google.com, devicetree@vger.kernel.org,
	dianders@chromium.org, gregkh@linuxfoundation.org,
	groeck@chromium.org, kernel@collabora.com,
	kernelci@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-usb@vger.kernel.org, robh+dt@kernel.org,
	saravanak@google.com, shuah@kernel.org
Subject: Re: [PATCH v4 3/3] kselftest: devices: Add sample board file for XPS 13 9300
Date: Sun, 28 Dec 2025 08:47:42 +0300	[thread overview]
Message-ID: <20251228054804.2515185-1-safinaskar@gmail.com> (raw)
In-Reply-To: <20240122-discoverable-devs-ksft-v4-3-d602e1df4aa2@collabora.com>

"Nícolas F. R. A. Prado" <nfraprado@collabora.com>:
> Add a sample board file describing the file's format and with the list
> of devices expected to be probed on the XPS 13 9300 machine as an
> example x86 platform.

And now "Dell Inc.,XPS 13 9300.yaml" became the only file in the repository,
which has space in its name:

$ find . -name '* *'
./tools/testing/selftests/devices/probe/boards/Dell Inc.,XPS 13 9300.yaml

I kindly ask you to rename file. New name should not contain space or comma
in it.

The file name in its current form breaks tools. For example, it breaks
"xargs".

For example, the following will work in "fs" directory:

stable/fs$ find . | xargs chmod -w

But it will not work in root of source tree because of this
"Dell Inc.,XPS 13 9300.yaml" file:

stable$ find . | xargs chmod -w
chmod: cannot access './tools/testing/selftests/devices/probe/boards/Dell': No such file or directory
chmod: cannot access 'Inc.,XPS': No such file or directory
chmod: cannot access '13': No such file or directory
chmod: cannot access '9300.yaml': No such file or directory

-- 
Askar Safin

  parent reply	other threads:[~2025-12-28  5:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 18:53 [PATCH v4 0/3] Add test to verify probe of devices from discoverable buses Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 1/3] kselftest: " Nícolas F. R. A. Prado
2025-12-29 13:57   ` Thomas Weißschuh
2025-12-29 14:14     ` Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 2/3] kselftest: devices: Add sample board file for google,spherion Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 3/3] kselftest: devices: Add sample board file for XPS 13 9300 Nícolas F. R. A. Prado
2024-01-23 11:08   ` AngeloGioacchino Del Regno
2024-01-23 14:50     ` Nícolas F. R. A. Prado
2025-12-28  5:47   ` Askar Safin [this message]
2025-12-29 13:42     ` Nícolas F. R. A. Prado
2025-12-30 11:36       ` Askar Safin

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=20251228054804.2515185-1-safinaskar@gmail.com \
    --to=safinaskar@gmail.com \
    --cc=Tim.Bird@sony.com \
    --cc=bhelgaas@google.com \
    --cc=dan.carpenter@linaro.org \
    --cc=davidgow@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=kernel@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=robh+dt@kernel.org \
    --cc=saravanak@google.com \
    --cc=shuah@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