From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Stephen Boyd <sboyd@kernel•org>
Cc: Mike Turquette <mturquette@baylibre•com>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Dinh Nguyen <dinguyen@kernel•org>
Subject: Re: linux-next: Fixes tag needs some work in the clk tree
Date: Thu, 1 Oct 2020 11:22:02 +1000 [thread overview]
Message-ID: <20201001112202.74a7e72a@canb.auug.org.au> (raw)
In-Reply-To: <160151172628.310579.596467424545504483@swboyd.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
Hi Stephen,
On Wed, 30 Sep 2020 17:22:06 -0700 Stephen Boyd <sboyd@kernel•org> wrote:
>
> Thanks for pointing that out. Is this part of checkpatch? I run
> checkpatch on most patches and didn't see any complaint.
This is not part of checkpatch, just some scripts I run after fetching
each tree each day.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-01 1:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:46 linux-next: Fixes tag needs some work in the clk tree Stephen Rothwell
2020-10-01 0:22 ` Stephen Boyd
2020-10-01 1:22 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 21:09 Stephen Rothwell
2024-11-08 9:08 ` Jerome Brunet
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
2020-03-06 6:58 Stephen Rothwell
2019-05-26 10:35 Stephen Rothwell
2019-01-15 21:34 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
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=20201001112202.74a7e72a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dinguyen@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mturquette@baylibre$(echo .)com \
--cc=sboyd@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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