public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Eiden <seiden@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Andrew Jones <andrew.jones@linux.dev>
Subject: Re: [kvm-unit-tests PATCH] clang-format: add project-wide configuration file
Date: Wed, 26 Apr 2023 18:31:17 +0200	[thread overview]
Message-ID: <4e4b227c-e8f1-d959-20a3-e1f4b38521a2@linux.ibm.com> (raw)
In-Reply-To: <243608a7-484c-4844-9274-0b02dc32ec25@redhat.com>



On 4/26/23 16:41, Thomas Huth wrote:
>> +# Taken from:
>> +#   git grep -h '^#define [^[:space:]]*for_each[^[:space:]]*(' 
>> include/ tools/ \
>> +#   | sed "s,^#define \([^[:space:]]*for_each[^[:space:]]*\)(.*$,  - 
>> '\1'," \
>> +#   | LC_ALL=C sort -u
>> +ForEachMacros:
>> +  - '__ata_qc_for_each'
>> +  - '__bio_for_each_bvec'
>> +  - '__bio_for_each_segment'
>> +  - '__evlist__for_each_entry'
>> +  - '__evlist__for_each_entry_continue'
>> +  - '__evlist__for_each_entry_from'
>> +  - '__evlist__for_each_entry_reverse'
>> +  - '__evlist__for_each_entry_safe'
>> +  - '__for_each_mem_range'
>> +  - '__for_each_mem_range_rev'
>> +  - '__for_each_thread'
>> +  - '__hlist_for_each_rcu'
>> +  - '__map__for_each_symbol_by_name'
>> +  - '__perf_evlist__for_each_entry'
>> +  - '__perf_evlist__for_each_entry_reverse'
>> +  - '__perf_evlist__for_each_entry_safe'
>> +  - '__rq_for_each_bio'
>> +  - '__shost_for_each_device'
> ...
> 
> I think this ForEachMacros list should be adapted for the k-u-ts.
> The "git grep" statement results in this list for the k-u-ts:
> 
>    - 'dt_for_each_subnode'
>    - 'fdt_for_each_property_offset'
>    - 'fdt_for_each_subnode'
>    - 'for_each_cpu'
>    - 'for_each_online_cpu'
>    - 'for_each_present_cpu'
> 
> which is definitely much shorter 😄
> 
>   Thomas
Makes sense. I'll do that.

      reply	other threads:[~2023-04-26 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 14:08 [kvm-unit-tests PATCH] clang-format: add project-wide configuration file Steffen Eiden
2023-04-26 14:41 ` Thomas Huth
2023-04-26 16:31   ` Steffen Eiden [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=4e4b227c-e8f1-d959-20a3-e1f4b38521a2@linux.ibm.com \
    --to=seiden@linux.ibm.com \
    --cc=andrew.jones@linux.dev \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=thuth@redhat.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