public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Michael Hennerich" <michael.hennerich@analog.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: adc: ad7944: Add support for "3-wire mode"
Date: Mon, 18 Mar 2024 12:40:41 +0000	[thread overview]
Message-ID: <20240318124041.0000032d@Huawei.com> (raw)
In-Reply-To: <ZfX5jynjW4M9pvw1@surfacebook.localdomain>

> 
> >  struct ad7944_adc {
> >  	struct spi_device *spi;
> > +	enum ad7944_spi_mode spi_mode;
> >  	/* Chip-specific timing specifications. */
> >  	const struct ad7944_timing_spec *timing_spec;
> >  	/* GPIO connected to CNV pin. */
> > @@ -58,6 +75,9 @@ struct ad7944_adc {
> >  	 } sample __aligned(IIO_DMA_MINALIGN);
> >  };  
> 
> Have you run `pahole` to see if there is a better place for a new member?

I know this matters for structures where we see lots of them, but do we actually
care for one offs?  Whilst it doesn't matter here I'd focus much more
on readability and like parameter grouping for cases like this than wasting
a few bytes.

Jonathan


  parent reply	other threads:[~2024-03-18 12:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 17:43 [PATCH v2] iio: adc: ad7944: Add support for "3-wire mode" David Lechner
2024-03-16 14:11 ` Jonathan Cameron
2024-03-16 19:57 ` Andy Shevchenko
2024-03-16 23:10   ` David Lechner
2024-03-17  8:23     ` Andy Shevchenko
2024-03-18 14:33       ` David Lechner
2024-03-23 18:20         ` Jonathan Cameron
2024-03-18 12:40   ` Jonathan Cameron [this message]
2024-03-18 13:09     ` Andy Shevchenko
2024-03-18 14:17       ` David Lechner
2024-03-18 16:25         ` Andy Shevchenko
2024-03-18 14:29       ` Jonathan Cameron
2024-03-19 18:42         ` Arnaldo Carvalho de Melo

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=20240318124041.0000032d@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=nuno.sa@analog.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