From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] fallthrough pseudo-keyword macro conversions for 5.9-rc3
Date: Mon, 24 Aug 2020 15:58:41 -0500 [thread overview]
Message-ID: <a99adda0-c44d-2ce7-b28c-5549dcf90352@embeddedor.com> (raw)
In-Reply-To: <CAHk-=wh8a8crLw5Lbs7C2Mz34fAUQn1tTHWqqOXCxbXF1bc_WA@mail.gmail.com>
On 8/24/20 13:46, Linus Torvalds wrote:
> On Sun, Aug 23, 2020 at 8:42 PM Gustavo A. R. Silva
> <gustavoars@kernel.org> wrote:
>>
>> Not sure what the problem was with my pull-request for -rc2. So, I'm giving
>> this a second try because I think it is worth it.
>
> Just "a ton of lines changed across subsystems, I feel like I need to check it".
>
Yep; you're right. These are tons of changes...
> For example, you say that you remove unnecessary fall-through
> markings, but I'm not sure what your pattern for that was.
>
fall-through markings are not necessary for consecutive case labels.
I will soon send a patch to add this info to "Implicit switch case fall-through"
in deprecated.rst
> You left the one in arch/arm64/kernel/cpuinfo.c:
> cpuinfo_detect_icache_policy(), for example.
>> And you've fixed up indentation clearly by hand in places, but then
> it's incorrectly done in other places (dib8096_set_param_override())
>
Yeah; I overlooked those two. I'll address them in a future pull-request.
> I've pulled it, but these kinds of "trivial" conversions do make me
> nervous. We've had a lot of cases of them breaking things, and it's a
> pain to find when it happens.
>
I know; don't worry, I'll be here to fix anything that has to do with
this change ASAP, like in this case:
https://lore.kernel.org/lkml/20200824203614.GA28543@embeddedor/
could you take it?
> I think I'd have preferred to get this as a couple of scripts that do
> the obvious 1:1 direct conversion of the simple cases that cover 90%
> of it all, so then the manual fixups separately.
>
I've got it. I will certainly take this into account for future PRs.
> Oh well. I've pulled it.
>
Awesome. :)
Thank you!
--
Gustavo
next prev parent reply other threads:[~2020-08-24 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 3:48 Gustavo A. R. Silva
2020-08-24 18:46 ` Linus Torvalds
2020-08-24 18:56 ` Joe Perches
2020-08-24 20:58 ` Gustavo A. R. Silva [this message]
2020-08-24 19:21 ` pr-tracker-bot
2020-08-24 19:43 ` Nathan Chancellor
2020-08-24 20:04 ` Gustavo A. R. Silva
2020-08-25 23:36 ` Peter Rosin
2020-08-26 0:16 ` Gustavo A. R. Silva
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=a99adda0-c44d-2ce7-b28c-5549dcf90352@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®