From: Doug Anderson <firstname.lastname@example.org> To: Daniel Thompson <email@example.com> Cc: Catalin Marinas <firstname.lastname@example.org>, Will Deacon <email@example.com>, Jason Wessel <firstname.lastname@example.org>, email@example.com, Christophe Leroy <firstname.lastname@example.org>, LKML <email@example.com> Subject: Re: [PATCH v3 3/4] kdb: Fix "btc <cpu>" crash if the CPU didn't round up Date: Thu, 10 Oct 2019 09:38:04 -0700 [thread overview] Message-ID: <CAD=FV=VuOVpvEB60-prMxuPyjcrJ-9O2hyaLKf86c-r9BVocdg@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi, On Thu, Oct 10, 2019 at 8:07 AM Daniel Thompson <email@example.com> wrote: > > Reading through other control flows of the various backtrace commands, > > it looks like it is intentional to leave the current task changed when > > you explicitly do an action on that task (or a CPU). > > > > Actually, though, it wasn't clear to me that it ever made sense for > > any of these commands to implicitly leave the current task changed. > > If you agree, I can send a follow-up patch to change this behavior. > > Personally I don't like implicit changes of state but I might need a bit > more thinking to agree (or disagree ;-) ). I can post up a followup after this series lands and change it. I have a feeling nobody is relying on the old behavior and thus nobody will notice but it would be nice to get this cleaner. BTW: if you want me to spin to fix the commit message typo that Will found or add his Ack to the series, let me know. Otherwise I'll assume that the typo can be fixed and Acks added when the patch is applied. -Doug
next prev parent reply other threads:[~2019-10-10 16:38 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-25 20:02 [PATCH v3 0/4] kdb: Fixes for btc Douglas Anderson 2019-09-25 20:02 ` [PATCH v3 1/4] kgdb: Remove unused DCPU_SSTEP definition Douglas Anderson 2019-09-25 20:08 ` Jason Wessel 2019-09-25 20:02 ` [PATCH v3 2/4] kdb: Remove unused "argcount" param from kdb_bt1(); make btaprompt bool Douglas Anderson 2019-09-25 20:02 ` [PATCH v3 3/4] kdb: Fix "btc <cpu>" crash if the CPU didn't round up Douglas Anderson 2019-10-03 21:09 ` Will Deacon 2019-10-07 13:54 ` Daniel Thompson 2019-10-07 23:34 ` Doug Anderson 2019-10-10 15:07 ` Daniel Thompson 2019-10-10 16:38 ` Doug Anderson [this message] 2019-11-09 19:20 ` Doug Anderson 2019-09-25 20:02 ` [PATCH v3 4/4] kdb: Fix stack crawling on 'running' CPUs that aren't the master Douglas Anderson 2019-10-03 21:11 ` [PATCH v3 0/4] kdb: Fixes for btc Will Deacon 2019-10-10 16:51 ` Daniel Thompson
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='CAD=FV=VuOVpvEB60-prMxuPyjcrJ-9O2hyaLKf86c-r9BVocdg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v3 3/4] kdb: Fix "btc <cpu>" crash if the CPU didn'\''t round up' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.