All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Jason Low <jason.low2@hpe.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: Bad MAINTAINERS pattern in section 'LOCKING PRIMITIVES'
Date: Mon, 1 Oct 2018 15:28:56 +0100	[thread overview]
Message-ID: <20181001142856.GC9716@arm.com> (raw)
In-Reply-To: <20180928215436.29842-1-joe@perches.com>

On Fri, Sep 28, 2018 at 02:54:36PM -0700, Joe Perches wrote:
> Please fix this defect appropriately.

Patch below, which was probably less effort to write than your report ;)

Will

--->8

From 867b47473ad490c21591378a7041fe7c06b71b59 Mon Sep 17 00:00:00 2001
From: Will Deacon <will.deacon@arm.com>
Date: Mon, 1 Oct 2018 14:47:58 +0100
Subject: [PATCH] MAINTAINERS: Remove dead path from LOCKING PRIMITIVES entry

Since 890658b7ab48 ("locking/mutex: Kill arch specific code"), there
are no mutex header files under arch/, so we can remove the redundant
entry from MAINTAINERS.

Reported-by: Joe Perches <joe@perches.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index d870cb57c887..276c32df137a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8582,7 +8582,6 @@ F:	include/linux/spinlock*.h
 F:	arch/*/include/asm/spinlock*.h
 F:	include/linux/rwlock*.h
 F:	include/linux/mutex*.h
-F:	arch/*/include/asm/mutex*.h
 F:	include/linux/rwsem*.h
 F:	arch/*/include/asm/rwsem.h
 F:	include/linux/seqlock.h
-- 
2.1.4


  reply	other threads:[~2018-10-01 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 21:54 Bad MAINTAINERS pattern in section 'LOCKING PRIMITIVES' Joe Perches
2018-10-01 14:28 ` Will Deacon [this message]
2018-10-02 10:15   ` [tip:locking/urgent] MAINTAINERS: Remove dead path from LOCKING PRIMITIVES entry tip-bot for Will Deacon

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=20181001142856.GC9716@arm.com \
    --to=will.deacon@arm.com \
    --cc=jason.low2@hpe.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 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.