mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John B. Wyatt IV" <jbwyatt4@gmail.com>
To: "' Joel Fernandes (Google)" <joel@joelfernandes.org>,
	Nishanth Aravamudan <naravamudan@digitalocean.com>,
	Julien Desfossez <jdesfossez@digitalocean.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	Vineeth Pillai <viremana@linux.microsoft.com>,
	Aaron Lu <aaron.lwe@gmail.com>,
	Aubrey Li <aubrey.intel@gmail.com>,
	tglx@linutronix.de, linux-kernel@vger.kernel.org,
	mingo@kernel.org, torvalds@linux-foundation.org,
	fweisbec@gmail.com, keescook@chromium.org, kerrnel@google.com,
	Phil Auld <pauld@redhat.com>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	vineeth@bitbyteword.org, Chen Yu <yu.c.chen@intel.com>,
	Christian Brauner <christian.brauner@ubuntu.com>,
	Agata Gruza <agata.gruza@intel.com>,
	Antonio Gomez Iglesias <antonio.gomez.iglesias@intel.com>,
	graf@amazon.com, konrad.wilk@oracle.com, dfaggioli@suse.com,
	pjt@google.com, rostedt@goodmis.org, derkling@google.com,
	benbjiang@tencent.com,
	Alexandre Chartre <alexandre.chartre@oracle.com>,
	James.Bottomley@hansenpartnership.com, OWeisse@umich.edu,
	Dhaval Giani <dhaval.giani@oracle.com>,
	Junaid Shahid <junaids@google.com>,
	jsbarnes@google.com, chris.hyser@oracle.com,
	Aubrey Li <aubrey.li@linux.intel.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Tim Chen ' <tim.c.chen@intel.com>
Cc: "John B. Wyatt IV" <jbwyatt4@gmail.com>
Subject: [PATCH 0/8] Style and small fixes for core-scheduling
Date: Wed, 28 Oct 2020 05:19:09 -0700	[thread overview]
Message-ID: <20201028121917.635203-1-jbwyatt4@gmail.com> (raw)

Patchset of style and small fixes for the 8th iteration of the
Core-Scheduling feature.

Style fixes include changing spaces to tabs, inserting new lines before
declarations, removing unused braces, and spelling.

Two small fixes involving changing a main() to main(void) and removing an
unused 'else'.

All issues were reported by checkpatch.

I am a new Linux kernel developer interning with the Outreachy project.

Please feel free to advise on any corrections or improvements that can be
made.

John B. Wyatt IV (8):
  sched: Correct misspellings in core-scheduling.rst
  sched: Fix bad function definition
  sched: Fix some style issues in test_coresched.c
  sched: Remove unused else
  sched: Add newline after declaration
  sched: Remove unneeded braces
  sched: Replace spaces with tabs
  sched: Add newlines after declarations

 Documentation/admin-guide/hw-vuln/core-scheduling.rst | 8 ++++----
 arch/x86/include/asm/thread_info.h                    | 4 ++--
 kernel/sched/core.c                                   | 6 ++++--
 kernel/sched/coretag.c                                | 3 ++-
 tools/testing/selftests/sched/test_coresched.c        | 8 ++++----
 5 files changed, 16 insertions(+), 13 deletions(-)

-- 
2.28.0


             reply	other threads:[~2020-10-28 23:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 12:19 John B. Wyatt IV [this message]
2020-10-28 12:19 ` [PATCH 1/8] sched: Correct misspellings in core-scheduling.rst John B. Wyatt IV
2020-10-28 12:19 ` [PATCH 2/8] sched: Fix bad function definition John B. Wyatt IV
2020-10-28 12:19 ` [PATCH 3/8] sched: Fix some style issues in test_coresched.c John B. Wyatt IV
2020-10-28 12:19 ` [PATCH 4/8] sched: Remove unused else John B. Wyatt IV
2020-10-28 12:19 ` [PATCH 5/8] sched: Add newline after declaration John B. Wyatt IV
2020-10-28 12:19 ` [PATCH 6/8] sched: Remove unneeded braces John B. Wyatt IV
2020-10-28 12:19 ` [PATCH 7/8] sched: Replace spaces with tabs John B. Wyatt IV
2020-10-28 12:19 ` [PATCH 8/8] sched: Add newlines after declarations John B. Wyatt IV
2020-10-28 14:37 ` [PATCH 0/8] Style and small fixes for core-scheduling Phil Auld
2020-10-28 18:58   ` John Wyatt

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=20201028121917.635203-1-jbwyatt4@gmail.com \
    --to=jbwyatt4@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=OWeisse@umich.edu \
    --cc=aaron.lwe@gmail.com \
    --cc=agata.gruza@intel.com \
    --cc=alexandre.chartre@oracle.com \
    --cc=antonio.gomez.iglesias@intel.com \
    --cc=aubrey.intel@gmail.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=benbjiang@tencent.com \
    --cc=chris.hyser@oracle.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=derkling@google.com \
    --cc=dfaggioli@suse.com \
    --cc=dhaval.giani@oracle.com \
    --cc=fweisbec@gmail.com \
    --cc=graf@amazon.com \
    --cc=jdesfossez@digitalocean.com \
    --cc=joel@joelfernandes.org \
    --cc=jsbarnes@google.com \
    --cc=junaids@google.com \
    --cc=keescook@chromium.org \
    --cc=kerrnel@google.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@kernel.org \
    --cc=naravamudan@digitalocean.com \
    --cc=pauld@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@intel.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=valentin.schneider@arm.com \
    --cc=vineeth@bitbyteword.org \
    --cc=viremana@linux.microsoft.com \
    --cc=yu.c.chen@intel.com \
    /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

all inboxes | Powered by JetHome®