From: Joe Perches <joe@perches.com>
To: Nathan Chancellor <natechancellor@gmail.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: linux-next: Fixes tag needs some work in the clk tree
Date: Fri, 18 Jan 2019 10:36:45 -0800 [thread overview]
Message-ID: <537b4ea9870fbb93e26f83e7a06ff2091db39ec5.camel@perches.com> (raw)
In-Reply-To: <20190118174127.GA822@flashbox>
On Fri, 2019-01-18 at 10:41 -0700, Nathan Chancellor wrote:
> On Fri, Jan 18, 2019 at 09:37:26AM -0800, Stephen Boyd wrote:
> > Do you have a patch for checkpatch too? Maybe Joe can solve my problem.
> Joe posted a checkpatch diff in another thread:
> https://lore.kernel.org/lkml/40bfc40958fca6e2cc9b86101153aa0715fac4f7.camel@perches.com/
That proposal has the negative that a Fixes: line
is often after a Signed-off-by: line and the test
does not validate Fixes lines after Signed-off-by:s.
I would still appreciate some external testing of
the proposed patch.
next prev parent reply other threads:[~2019-01-18 18:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 21:34 linux-next: Fixes tag needs some work in the clk tree Stephen Rothwell
2019-01-16 22:35 ` Stephen Boyd
2019-01-17 1:25 ` Fabio Estevam
2019-01-17 18:42 ` Stephen Boyd
2019-01-18 12:41 ` Michael Ellerman
2019-01-18 12:49 ` Fabio Estevam
2019-01-18 17:37 ` Stephen Boyd
2019-01-18 17:41 ` Nathan Chancellor
2019-01-18 18:36 ` Joe Perches [this message]
2019-05-26 10:35 Stephen Rothwell
2020-03-06 6:58 Stephen Rothwell
2020-09-23 11:46 Stephen Rothwell
2020-10-01 0:22 ` Stephen Boyd
2020-10-01 1:22 ` Stephen Rothwell
2020-12-07 22:05 Stephen Rothwell
2020-12-08 8:37 ` Geert Uytterhoeven
2020-12-09 17:29 ` Stephen Boyd
2020-12-10 7:52 ` Geert Uytterhoeven
2020-12-20 21:35 ` Stephen Rothwell
2020-12-21 8:07 ` Geert Uytterhoeven
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=537b4ea9870fbb93e26f83e7a06ff2091db39ec5.camel@perches.com \
--to=joe@perches.com \
--cc=dinguyen@kernel.org \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=mturquette@baylibre.com \
--cc=natechancellor@gmail.com \
--cc=paul.gortmaker@windriver.com \
--cc=sboyd@codeaurora.org \
--cc=sboyd@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).