All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Gary Guo" <gary@garyguo.net>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	"Viresh Kumar" <viresh.kumar@linaro.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	linux-pm@vger.kernel.org, rust-for-linux@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: cpufreq: fix clippy::double_parens warning in Policy doctest
Date: Wed, 04 Mar 2026 20:39:58 +0000	[thread overview]
Message-ID: <DGUAE329P4FH.3QPNCVLNA99MC@garyguo.net> (raw)
In-Reply-To: <DGUA5GY2DGYN.3PG0FKLG7GFN1@garyguo.net>

On Wed Mar 4, 2026 at 8:28 PM GMT, Gary Guo wrote:
> On Wed Mar 4, 2026 at 8:07 PM GMT, John Hubbard wrote:
>> On 3/4/26 12:06 PM, Gary Guo wrote:
>>> On Wed Mar 4, 2026 at 7:53 PM GMT, John Hubbard wrote:
>>>> Clippy reports:
>>>>     warning: consider removing unnecessary double parentheses
>>>>       --> rust/kernel/cpufreq.rs:410:60
>>>>        |
>>>>    410 |     pr_info!("The policy details are: {:?}\n", (policy.cpu(), policy.cur()));
>>>>        |                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> 
>>> This looks like a false positive, probably due to how our fmt macro works?
>>
>> Probably, but in any case we need to remain clippy clean, so this
>> work-around seems about right, yes?
>>
>>
>> thanks,
>
> Can you try this?
>
> Best,
> Gary
>
> -- >8 --
>
> diff --git a/rust/macros/fmt.rs b/rust/macros/fmt.rs
> index ce6c7249305a..51988a69af21 100644
> --- a/rust/macros/fmt.rs
> +++ b/rust/macros/fmt.rs
> @@ -2,7 +2,7 @@
>  
>  use std::collections::BTreeSet;
>  
> -use proc_macro2::{Ident, TokenStream, TokenTree};
> +use proc_macro2::{Group, Ident, TokenStream, TokenTree};
>  use quote::quote_spanned;
>  
>  /// Please see [`crate::fmt`] for documentation.
> @@ -69,7 +69,8 @@ pub(crate) fn fmt(input: TokenStream) -> TokenStream {
>                      }
>                      (None, acc)
>                  })();
> -                args.extend(quote_spanned!(first_span => #lhs #adapter(&(#rhs))));
> +                let rhs = Group::new(proc_macro2::Delimiter::None, rhs);
> +                args.extend(quote_spanned!(first_span => #lhs #adapter(&#rhs)));

Actually `Delimiter::None` isn't fully fixed [1], so perhaps let's done use this
approach.

Injecting a `#[allow(clippy::double_parens)]` would probably a better approach
today.

Best,
Gary

Link: https://github.com/rust-lang/rust/issues/67062 [1]

>              }
>          };


  parent reply	other threads:[~2026-03-04 20:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 19:53 [PATCH] rust: cpufreq: fix clippy::double_parens warning in Policy doctest John Hubbard
2026-03-04 20:06 ` Gary Guo
2026-03-04 20:07   ` John Hubbard
2026-03-04 20:28     ` Gary Guo
2026-03-04 20:32       ` John Hubbard
2026-03-04 20:39       ` Gary Guo [this message]
2026-03-04 21:13         ` John Hubbard
2026-03-05 12:31           ` Gary Guo
2026-03-06 12:36             ` Miguel Ojeda
2026-03-07 17:09               ` [RFC PATCH] rust: kbuild: support global per-version flags Miguel Ojeda
2026-03-15 21:21                 ` Miguel Ojeda
2026-03-15 21:22                   ` Miguel Ojeda
2026-03-16  0:04                   ` Mark Brown
2026-03-16  4:49                     ` Miguel Ojeda
2026-03-16 12:50                       ` Mark Brown
2026-03-16 12:31                         ` Danilo Krummrich
2026-03-16 13:42                         ` Miguel Ojeda
2026-03-04 20:30 ` [PATCH] rust: cpufreq: fix clippy::double_parens warning in Policy doctest Gary Guo
2026-03-04 20:34   ` John Hubbard

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=DGUAE329P4FH.3QPNCVLNA99MC@garyguo.net \
    --to=gary@garyguo.net \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rafael@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=viresh.kumar@linaro.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 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.