From: John Hubbard <jhubbard@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH v2 0/2] selftests/vm: fix up executable bits, and a file name
Date: Fri, 2 Oct 2020 01:40:47 -0700 [thread overview]
Message-ID: <20201002084049.556824-1-jhubbard@nvidia.com> (raw)
Hi,
Here's v2. I can't use $(CONFIG_SHELL) from the Makefile, because
unfortunately this is not kbuild. So this is my proposed fix for these
two glitches.
(Actually, the "Fixes:" tags in each refer to linux-next commits, so
those commit hashes would ultimately need changing. But I suspect these
patches will actually be merged back into Andrew's tree?)
thanks,
John Hubbard
NVIDIA
John Hubbard (2):
selftests/vm: fix: make check_config.sh executable
selftests/vm: fix run_vmtest.sh: restore executable bits, and "s" in
name
tools/testing/selftests/vm/check_config.sh | 0
tools/testing/selftests/vm/{run_vmtest.sh => run_vmtests.sh} | 0
2 files changed, 0 insertions(+), 0 deletions(-)
mode change 100644 => 100755 tools/testing/selftests/vm/check_config.sh
rename tools/testing/selftests/vm/{run_vmtest.sh => run_vmtests.sh} (100%)
mode change 100644 => 100755
--
2.28.0
next reply other threads:[~2020-10-02 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 8:40 John Hubbard [this message]
2020-10-02 8:40 ` [PATCH v2 1/2] selftests/vm: fix: make check_config.sh executable John Hubbard
2020-10-02 8:40 ` [PATCH v2 2/2] selftests/vm: fix run_vmtest.sh: restore executable bits, and "s" in name John Hubbard
2020-10-02 21:59 ` Andrew Morton
2020-10-02 22:04 ` John Hubbard
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=20201002084049.556824-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.