Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752862AbcD1K2A (ORCPT <rfc822;w@1wt.eu>);
	Thu, 28 Apr 2016 06:28:00 -0400
Received: from terminus.zytor.com ([198.137.202.10]:46972 "EHLO
	terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752338AbcD1K16 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 28 Apr 2016 06:27:58 -0400
Date: Thu, 28 Apr 2016 03:27:05 -0700
From: tip-bot for Eric Engestrom <tipbot@zytor.com>
Message-ID: <tip-1d4093d3b3a70b947822cca76d6e4132767ce089@git.kernel.org>
Cc: mingo@kernel.org, peterz@infradead.org, corbet@lwn.net,
        torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
        hpa@zytor.com, tglx@linutronix.de, eric@engestrom.ch
Reply-To: peterz@infradead.org, mingo@kernel.org, hpa@zytor.com,
        tglx@linutronix.de, eric@engestrom.ch, linux-kernel@vger.kernel.org,
        corbet@lwn.net, torvalds@linux-foundation.org
In-Reply-To: <1461566229-4717-2-git-send-email-eric@engestrom.ch>
References: <1461566229-4717-2-git-send-email-eric@engestrom.ch>
To: linux-tip-commits@vger.kernel.org
Subject: [tip:locking/core] locking/Documentation/lockdep: Fix spelling
 mistakes
Git-Commit-ID: 1d4093d3b3a70b947822cca76d6e4132767ce089
X-Mailer: tip-git-log-daemon
Robot-ID: <tip-bot.git.kernel.org>
Robot-Unsubscribe: Contact <mailto:hpa@kernel.org> to get blacklisted from
 these emails
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2014
Lines: 43

Commit-ID:  1d4093d3b3a70b947822cca76d6e4132767ce089
Gitweb:     http://git.kernel.org/tip/1d4093d3b3a70b947822cca76d6e4132767ce089
Author:     Eric Engestrom <eric@engestrom.ch>
AuthorDate: Mon, 25 Apr 2016 07:36:54 +0100
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Thu, 28 Apr 2016 10:40:57 +0200

locking/Documentation/lockdep: Fix spelling mistakes

Signed-off-by: Eric Engestrom <eric@engestrom.ch>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1461566229-4717-2-git-send-email-eric@engestrom.ch
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 Documentation/locking/lockdep-design.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/locking/lockdep-design.txt b/Documentation/locking/lockdep-design.txt
index 5001280..9de1c15 100644
--- a/Documentation/locking/lockdep-design.txt
+++ b/Documentation/locking/lockdep-design.txt
@@ -97,7 +97,7 @@ between any two lock-classes:
    <hardirq-safe>   ->  <hardirq-unsafe>
    <softirq-safe>   ->  <softirq-unsafe>
 
-The first rule comes from the fact the a hardirq-safe lock could be
+The first rule comes from the fact that a hardirq-safe lock could be
 taken by a hardirq context, interrupting a hardirq-unsafe lock - and
 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
 lock could be taken by an softirq context, interrupting a softirq-unsafe
@@ -220,7 +220,7 @@ calculated, which hash is unique for every lock chain. The hash value,
 when the chain is validated for the first time, is then put into a hash
 table, which hash-table can be checked in a lockfree manner. If the
 locking chain occurs again later on, the hash table tells us that we
-dont have to validate the chain again.
+don't have to validate the chain again.
 
 Troubleshooting:
 ----------------