From: Stephen Boyd <swboyd@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Kieran Bingham <kbingham@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Douglas Anderson <dianders@chromium.org>,
Nikolay Borisov <n.borisov.lkml@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Jackie Liu <liuyun01@kylinos.cn>
Subject: Re: [PATCH 0/4] gdb script for kconfig and timer list
Date: Tue, 26 Mar 2019 13:35:54 -0700 [thread overview]
Message-ID: <155363255431.20095.9223713398808071323@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <0cb6bd11-b98e-2d76-f464-b06afab74e97@kernel.org>
Quoting Kieran Bingham (2019-03-26 01:39:43)
> Hi Stephen,
>
> Thank you for these patches,
>
> Could you check them through with PEP8 please?
>
> While we are not entirely "pep8 clean", Your series adds the following
> warnings:
Sure. I didn't know what was desired here because python in the kernel
is not checked by anything like checkpatch. I've fixed it all up and
things got a little shorter so it must be better! Now to test it out.
prev parent reply other threads:[~2019-03-26 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 18:45 [PATCH 0/4] gdb script for kconfig and timer list Stephen Boyd
2019-03-25 18:45 ` [PATCH 1/4] scripts/gdb: Find vmlinux where it was before Stephen Boyd
2019-03-25 18:45 ` [PATCH 2/4] scripts/gdb: Add kernel config dumping command Stephen Boyd
2019-03-25 18:45 ` [PATCH 3/4] scripts/gdb: Add rb tree iterating utilities Stephen Boyd
2019-03-26 8:52 ` Kieran Bingham
2019-03-26 17:05 ` Stephen Boyd
2019-03-26 17:21 ` Jan Kiszka
2019-03-26 20:39 ` Stephen Boyd
2019-03-27 10:37 ` Kieran Bingham
2019-03-25 18:45 ` [PATCH 4/4] scripts/gdb: Add a timer list command Stephen Boyd
2019-03-26 8:39 ` [PATCH 0/4] gdb script for kconfig and timer list Kieran Bingham
2019-03-26 20:35 ` Stephen Boyd [this message]
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=155363255431.20095.9223713398808071323@swboyd.mtv.corp.google.com \
--to=swboyd@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyun01@kylinos.cn \
--cc=n.borisov.lkml@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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).