public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Dixit Parmar <dixitparmar19@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] iio: magnetometer: add support for Infineon TLV493D 3D Magentic sensor
Date: Fri, 22 Aug 2025 08:10:20 +0530	[thread overview]
Message-ID: <aKfYlP-yWdQi34db@dixit> (raw)
In-Reply-To: <CAHp75Vdw5X1Y057fpGjdvVGwKq0x0UBdm8py+m+55RbzXi1PJw@mail.gmail.com>

On Thu, Aug 21, 2025 at 10:41:03AM +0300, Andy Shevchenko wrote:
> On Thu, Aug 21, 2025 at 6:02 AM Dixit Parmar <dixitparmar19@gmail.com> wrote:
> > On Wed, Aug 20, 2025 at 05:08:38PM +0300, Andy Shevchenko wrote:
> 
> ...
> 
> > > >  st_magn-$(CONFIG_IIO_BUFFER) += st_magn_buffer.o
> > > >  obj-$(CONFIG_IIO_ST_MAGN_I2C_3AXIS) += st_magn_i2c.o
> > > >  obj-$(CONFIG_IIO_ST_MAGN_SPI_3AXIS) += st_magn_spi.o
> > > >
> > > > +obj-$(CONFIG_INFINEON_TLV493D)             += tlv493d.o
> > > > +
> > > >  obj-$(CONFIG_SENSORS_HMC5843)              += hmc5843_core.o
> > > >  obj-$(CONFIG_SENSORS_HMC5843_I2C)  += hmc5843_i2c.o
> > > >  obj-$(CONFIG_SENSORS_HMC5843_SPI)  += hmc5843_spi.o
> > >
> > > I haven't got the ordering rules here and in Kconfig. Can it be alphabetical?
> > From what I can see, the order is alphabetical based on the CONFIG option in the
> > Makefile and Kconfig, and I kept CONFIG_INFINEO_TLV493D after CONFIG_IIO_ST*.
> > Isn't it in correct order? or my understanding is incorrect?
> 
> I dunno, The file name there is with the vendor prefix, in many cases
> the configuration option is with vendor prefix as well, but the file.
Hi Jonathan, Can you please suggest best possible way here?

> 
> > > Interestingly that you have used 100 limit and suddenly don't do it here
> > > and maybe elsewhere. Why inconsistent style? Please, go through the whole
> > > file and make sure the style is consistent in all of the aspects:
> > > - C style used
> > > - comments style (one-line and multi-line)
> > > - indentation
> > > - etc.
> > I tried to follow 80 limit(except few places where it was just on border or not
> > clear to read). I belive the standard is to use 80 limit(correct me if I referred
> > wrong place) and I will recheck to meet that.
> 
> There are two standards, the old and strict one -- 80 characters, and
> this subsystem _tries_ to follow it and relaxed with 100 limit.
> The exceptions are possible when it affects readability.
Understood, I will go with 100 limit and make sure everything is well within it.

Thanks,
Dixit

  reply	other threads:[~2025-08-22  2:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  2:53 [PATCH v4 0/2] iio: magnetometer: add support for Infineon TLV493D 3D Magnetic Sensor Dixit Parmar
2025-08-14  2:53 ` [PATCH v4 1/2] iio: magnetometer: add support for Infineon TLV493D 3D Magentic sensor Dixit Parmar
2025-08-16 13:04   ` Jonathan Cameron
2025-08-20  4:46     ` Dixit Parmar
2025-08-20 13:56       ` Andy Shevchenko
2025-08-20 14:08   ` Andy Shevchenko
2025-08-21  3:02     ` Dixit Parmar
2025-08-21  7:41       ` Andy Shevchenko
2025-08-22  2:40         ` Dixit Parmar [this message]
2025-08-22  6:11           ` Andy Shevchenko
2025-08-25  3:03           ` Dixit Parmar
2025-08-25  9:50             ` Jonathan Cameron
2025-08-26  2:52               ` Dixit Parmar
2025-08-26  3:02                 ` Dixit Parmar
2025-08-30 14:53                   ` Jonathan Cameron
2025-08-14  2:53 ` [PATCH v4 2/2] dt-bindings: iio: magnetometer: document Infineon TLV493D 3D Magnetic sensor Dixit Parmar

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=aKfYlP-yWdQi34db@dixit \
    --to=dixitparmar19@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@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