mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: bhargav <rougueprince47@gmail.com>,
	lars@metafoo.de, Michael.Hennerich@analog.com,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] iio: frequency: ad9523: fix checkpatch warnings
Date: Sun, 22 Feb 2026 13:58:48 +0000	[thread overview]
Message-ID: <20260222135836.3f8d7a38@jic23-huawei> (raw)
In-Reply-To: <20260222135054.2e2012aa@jic23-huawei>

On Sun, 22 Feb 2026 13:50:54 +0000
Jonathan Cameron <jic23@kernel.org> wrote:

> On Fri, 20 Feb 2026 09:22:34 +0200
> Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> 
> > On Fri, Feb 20, 2026 at 03:05:46AM +0530, bhargav wrote:  
> > > Changes in v3:
> > > -Patch 1: updated macros to use '(x)' instead of 'x'.
> > > -Patch 2: collected reviewed-by (no code changes).
> > > -Patch 3: fixed vertical spacing and broken indentation.
> > > 
> > > These patches address several checkpatch warnings in the ad9523 driver.    
> > 
> > Do a new email thread for each new version of the series.
> > Do not send a new version more often than a couple of days.
> > (The very bare minimum is 24h.)
> >   
> 
> Series is simple enough I'm not going to wait on Michael
> giving it a quick look (as the driver maintainer).  Still
> time for more feedback though given I'll be rebasing the tree
> anyway on rc1 later this week.
> 
> Applied to the testing branch of iio.git.
Pulled again.  Just a small thing I need to check.

For sign off we need a "known identity" - see submitting patches.
Mostly that's a legal name, but if people are commonly known
by other names that's acceptable as well.

Given short nature of your SoB and that this is (I think?) your
first upstream commit I just wanted to check that bhargav is 
sufficient to meet this level.  

What counts for this varies a lot by culture or country so if
that is the right level of identification to use that that's
fine, just reply to let me know.

Thanks,

Jonathan


> 
> Thanks,
> 
> Jonathan
> 
> >   
> 


  reply	other threads:[~2026-02-22 13:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  1:02 [PATCH] iio:frequency:ad9523:convert symbolic permissions to octal and remove unwanted arguments in macro bhargav
2026-02-19  7:44 ` Andy Shevchenko
2026-02-19 20:32   ` [PATCH v2 0/3] iio: frequency: ad9523: fix checkpatch warnings bhargav
2026-02-19 20:32     ` [PATCH v2 1/3] iio: frequency: ad9523: fix implicit variable usage in macros bhargav
2026-02-19 20:36       ` Andy Shevchenko
2026-02-19 20:32     ` [PATCH v2 2/3] iio: frequency: ad9523: avoid multiple line dereferences for pdata bhargav
2026-02-19 20:38       ` Andy Shevchenko
2026-02-19 20:32     ` [PATCH v2 3/3] iio: frequency: ad9523: fix checkpatch warnings for symbolic permissions bhargav
2026-02-19 20:46       ` Andy Shevchenko
2026-02-19 21:35         ` [PATCH v3 0/3] iio: frequency: ad9523: fix checkpatch warnings bhargav
2026-02-19 21:35           ` [PATCH v3 1/3] iio: frequency: ad9523: fix implicit variable usage in macros bhargav
2026-02-20  7:21             ` Andy Shevchenko
2026-02-19 21:35           ` [PATCH v3 2/3] iio: frequency: ad9523: avoid multiple line dereferences for pdata bhargav
2026-02-19 21:35           ` [PATCH v3 3/3] iio: frequency: ad9523: fix checkpatch warnings for symbolic permissions bhargav
2026-02-20  7:24             ` Andy Shevchenko
2026-02-20  7:22           ` [PATCH v3 0/3] iio: frequency: ad9523: fix checkpatch warnings Andy Shevchenko
2026-02-22 13:50             ` Jonathan Cameron
2026-02-22 13:58               ` Jonathan Cameron [this message]
2026-02-22 21:19                 ` Rogue prince
2026-02-23  8:35                   ` Andy Shevchenko
2026-02-23 20:35                     ` Jonathan Cameron

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=20260222135836.3f8d7a38@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=rougueprince47@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

all inboxes | Powered by JetHome®