[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKUZ0zJW6ihoNTu_Lecztn7fqci31Q1sb5oJJHcnAw_TxrDFxg@mail.gmail.com>
Date: Thu, 17 Apr 2025 13:22:51 -0400
From: Gabriel Shahrouzi <gshahrouzi@...il.com>
To: David Lechner <dlechner@...libre.com>
Cc: gregkh@...uxfoundation.org, jic23@...nel.org, lars@...afoo.de,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-staging@...ts.linux.dev, Michael.Hennerich@...log.com,
skhan@...uxfoundation.org, linux-kernel-mentees@...ts.linux.dev
Subject: Re: [PATCH] iio: frequency:: Remove unused parameter from data documentation
On Thu, Apr 17, 2025 at 12:17 PM David Lechner <dlechner@...libre.com> wrote:
>
> On 4/17/25 9:32 AM, Gabriel Shahrouzi wrote:
> > The AD9832 driver uses the Common Clock Framework (CCF) to obtain the
> > master clock (MCLK) frequency rather than relying on a frequency value
> > passed from platform data.
> >
> > Signed-off-by: Gabriel Shahrouzi <gshahrouzi@...il.com>
> > ---
> > drivers/staging/iio/frequency/ad9832.h | 1 -
> > 1 file changed, 1 deletion(-)
> >
> Please include the driver name in your patch subjects. Otherwise readers will
> assume that this is something that affects all IIO frequency drivers. I noticed
> you are doing this on all of the patches you are sending, not just this one.
Whoops. I thought that would be redundant because the information is
in the git commit body. However, I realized it would be useful for
people quickly glancing over emails to categorize them or get an
initial idea of it solely based on the git commit title. Therefore, it
makes the most sense to be specify the driver to indicate specifically
what the change is being made towards. I'll use this convention for
future patches.
>
>
> [PATCH] iio: frequency: ad9832: Remove unused parameter from data documentation
Powered by blists - more mailing lists