Linux IIO development
 help / color / mirror / Atom feed
From: "Siratul Islam" <siratul.islam@linux.dev>
To: "Andy Shevchenko" <andriy.shevchenko@intel.com>
Cc: "Song Qiang" <songqiang1304521@gmail.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] iio: update email for Siratul Islam
Date: Tue, 21 Jul 2026 21:03:16 +0000	[thread overview]
Message-ID: <75eddcbf72d7d6a37f3ea213ffd9afc979d34a89@linux.dev> (raw)
In-Reply-To: <al_bUWguna_K1n7X@ashevche-desk.local>

July 22, 2026 at 2:49 AM, "Andy Shevchenko" <andriy.shevchenko@intel.com mailto:andriy.shevchenko@intel.com?to=%22Andy%20Shevchenko%22%20%3Candriy.shevchenko%40intel.com%3E > wrote:


> 
> On Tue, Jul 21, 2026 at 09:03:08PM +0600, Siratul Islam wrote:
> 
> > 
> > Change personal email to the Linux specific one,
> >  to have a single and focused point of interaction.
> > 
> ...
> 
> > 
> > .mailmap | 1 +
> >  .../devicetree/bindings/iio/proximity/st,vl53l0x.yaml | 2 +-
> >  MAINTAINERS | 2 +-
> >  drivers/iio/proximity/vl53l1x-i2c.c | 4 ++--
> > 
> Shouldn't DT patch be separated?
> 
checkpatch.pl --strict has a warning saying that. But I remember 
another similar patch from a few days ago where Krzysztof suggested all the changes 
in one commit.

Link: https://lore.kernel.org/linux-iio/a509d034-de90-4e46-bd7e-75f61002d6ba@kernel.org/

> -- 
> With Best Regards,
> Andy Shevchenko
>

--
Best regards,
Sirat

  reply	other threads:[~2026-07-21 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 15:03 [PATCH] iio: update email for Siratul Islam Siratul Islam
2026-07-21 20:49 ` Andy Shevchenko
2026-07-21 21:03   ` Siratul Islam [this message]
2026-07-21 21:19   ` Maxwell Doose
2026-07-22 13:14 ` Rob Herring (Arm)

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=75eddcbf72d7d6a37f3ea213ffd9afc979d34a89@linux.dev \
    --to=siratul.islam@linux.dev \
    --cc=andriy.shevchenko@intel.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 \
    --cc=songqiang1304521@gmail.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