All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: ukleinek@kernel.org, heikki.krogerus@linux.intel.com,
	linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] pwm: dwc: Use size macro
Date: Mon, 5 Jan 2026 20:07:07 +0200	[thread overview]
Message-ID: <aVv9y8RuA_LLm7GZ@smile.fi.intel.com> (raw)
In-Reply-To: <aVvsFsLvNHuBWvUv@black.igk.intel.com>

On Mon, Jan 05, 2026 at 05:51:34PM +0100, Raag Jadav wrote:
> On Mon, Jan 05, 2026 at 06:41:48PM +0200, Andy Shevchenko wrote:
> > On Mon, Jan 05, 2026 at 02:47:37PM +0530, Raag Jadav wrote:
> > > Use SZ_4K from size.h instead of hardcoding constant.
> > 
> > Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Thank you.
> 
> > OTOH, not sure if it's just an unneeded churn. What was the motivation to
> > create this patch?

> Your hard work[1] continues to motivate me :)

Ha-ha, but that one has a principal difference, i.e. there was _a custom macro_
*already*, which was replaced with a generic one. From the code perspective
it's not a churn as it kills the unneeded custom macro. Here the situation is
different, i.e. the explicit number 0x1000 is changed to SZ_4K. Just a line to
change, the added header inclusion and no other changes, so as a standalone one
it sounds to me like a churn.

> [1] https://lore.kernel.org/r/20250825163545.39303-3-andriy.shevchenko@linux.intel.com

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-01-05 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05  9:17 [PATCH v1] pwm: dwc: Use size macro Raag Jadav
2026-01-05 16:41 ` Andy Shevchenko
2026-01-05 16:51   ` Raag Jadav
2026-01-05 18:07     ` Andy Shevchenko [this message]
2026-01-06  9:20       ` Raag Jadav
2026-01-12  7:59 ` Uwe Kleine-König

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=aVv9y8RuA_LLm7GZ@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=raag.jadav@intel.com \
    --cc=ukleinek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.