public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-iio@vger.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH] kernel-doc: add support for ____cacheline_aligned attribute
Date: Wed, 16 Sep 2020 12:36:49 -0600	[thread overview]
Message-ID: <20200916123649.20d7d999@lwn.net> (raw)
In-Reply-To: <20200910185415.653139-1-jic23@kernel.org>

On Thu, 10 Sep 2020 19:54:15 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> Subroutine dump_struct uses type attributes to check if the struct
> syntax is valid. Then, it removes all attributes before using it for
> output. `____cacheline_aligned` is an attribute that is
> not included in both steps. Add it, since it is used by kernel structs.
> 
> Based on previous patch to add ____cacheline_aligned_in_smp.
> Motivated by patches to reorder this attribute to before the
> variable name.   Whilst we could do that in all cases, that would
> be a massive change and it is more common in the kernel to place
> this particular attribute after the variable name. A quick grep
> suggests approximately 400 instances of which 341 have this
> attribute just before a semicolon and hence after the variable name.
> 
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Lee Jones <lee.jones@linaro.org>
> ---
> 
> Note I haven't figured out what this is actually doing and hence the
> patch is done by copying the changes made for ____cacheline_aligned_in_smp.
> It seems to work. :)

The little secret is that *nobody* really understands what all the regexes
in kernel-doc do :)  Anyway, it does indeed seem to work; applied, thanks.

jon

      reply	other threads:[~2020-09-16 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 18:54 [PATCH] kernel-doc: add support for ____cacheline_aligned attribute Jonathan Cameron
2020-09-16 18:36 ` Jonathan Corbet [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=20200916123649.20d7d999@lwn.net \
    --to=corbet@lwn.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=jic23@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.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