From: john.hubbard@gmail.com
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH 0/1] checkpatch: revert broken NOTIFIER_HEAD check
Date: Sun, 11 Aug 2019 15:54:42 -0700 [thread overview]
Message-ID: <20190811225443.31161-1-jhubbard@nvidia.com> (raw)
From: John Hubbard <jhubbard@nvidia.com>
Hi,
This happens on today's linux-next.
If the commit message of the original patch were just a bit clearer,
I might have been able to attempt a fix, instead of a revert, but so far,
both the Perl and the English are beyond me. And we can't leave
checkpatch broken.
I'll be glad to test out actual fixes, if you like. But here's a crude
revert to kick off the discussion anyway. :)
John Hubbard (1):
checkpatch: revert broken NOTIFIER_HEAD check
scripts/checkpatch.pl | 1 -
1 file changed, 1 deletion(-)
--
2.22.0
next reply other threads:[~2019-08-11 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 22:54 john.hubbard [this message]
2019-08-11 22:54 ` [PATCH 1/1] checkpatch: revert broken NOTIFIER_HEAD check john.hubbard
2019-08-12 1:30 ` Stephen Rothwell
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=20190811225443.31161-1-jhubbard@nvidia.com \
--to=john.hubbard@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).