All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 0/2] selftests/vm: fix a rename typo, fix executable issues
Date: Fri, 2 Oct 2020 17:21:40 -0700	[thread overview]
Message-ID: <20201003002142.32671-1-jhubbard@nvidia.com> (raw)

Here's v3, which treats the executable permissions of the two scripts here as
optional nice-to-have features.

It fixes the rename as well.

Again, I've put in commit hashes that are only valid in linux-next, so those
will need adjustment if these patches remain as distinct patches.


John Hubbard (2):
  selftests/vm: fix an improper dependency upon executable script
    permissions
  selftests/vm: fix a rename typo: run_vmtest.sh --> run_vmtests.sh

 tools/testing/selftests/vm/Makefile                          | 2 +-
 tools/testing/selftests/vm/check_config.sh                   | 0
 tools/testing/selftests/vm/{run_vmtest.sh => run_vmtests.sh} | 0
 3 files changed, 1 insertion(+), 1 deletion(-)
 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


             reply	other threads:[~2020-10-03  0:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03  0:21 John Hubbard [this message]
2020-10-03  0:21 ` [PATCH v3 1/2] selftests/vm: fix an improper dependency upon executable script permissions John Hubbard
2020-10-03  0:21 ` [PATCH v3 2/2] selftests/vm: fix a rename typo: run_vmtest.sh --> run_vmtests.sh 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=20201003002142.32671-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.