mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dhruva Gole <d-gole@ti.com>
To: bhanuseshukumar <bhanuseshukumar@gmail.com>
Cc: <cw00.choi@samsung.com>, <myungjoo.ham@samsung.com>,
	<kyungmin.park@samsung.com>, <skhan@linuxfoundation.org>,
	<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: devfreq: Fix typo 'enabeld' to 'enabled' in devfreq-event.c
Date: Tue, 27 May 2025 11:26:35 +0530	[thread overview]
Message-ID: <20250527055635.qgpf2v7artictbf2@lcpd911> (raw)
In-Reply-To: <20250526133839.64455-1-bhanuseshukumar@gmail.com>

On May 26, 2025 at 19:08:39 +0530, bhanuseshukumar wrote:
> Fixed a typo in  description of the function 
> 
> This is me trying my way into opensource linux kernel contribution
> journey beginning with this  first patch of trivial spelling 
> mistake fix. 

We appreciate your contribution, and welcome you to the community :)

However, this is not something that's meaningful to be part of a "git
log". commit messages in the git log should convey explanation or
reasoning behind purely the content of the patch itself.
So it's fine in this case to write just "Fix a typo...."

Read more about this here:
https://docs.kernel.org/process/submitting-patches.html#explanation-body

> 
> Signed-off-by: bhanuseshukumar <bhanuseshukumar@gmail.com>
> ---
>  drivers/devfreq/devfreq-event.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/devfreq/devfreq-event.c b/drivers/devfreq/devfreq-event.c
> index 70219099c604..020fe30ed5d9 100644
> --- a/drivers/devfreq/devfreq-event.c
> +++ b/drivers/devfreq/devfreq-event.c
> @@ -100,7 +100,7 @@ EXPORT_SYMBOL_GPL(devfreq_event_disable_edev);
>   * @edev	: the devfreq-event device
>   *
>   * Note that this function check whether devfreq-event dev is enabled or not.
> - * If return true, the devfreq-event dev is enabeld. If return false, the
> + * If return true, the devfreq-event dev is enabled. If return false, the
>   * devfreq-event dev is disabled.
>   */
>  bool devfreq_event_is_enabled(struct devfreq_event_dev *edev)
> -- 
> 2.34.1
> 
> 

-- 
Best regards,
Dhruva Gole
Texas Instruments Incorporated

      reply	other threads:[~2025-05-27  5:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 13:38 bhanuseshukumar
2025-05-27  5:56 ` Dhruva Gole [this message]

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=20250527055635.qgpf2v7artictbf2@lcpd911 \
    --to=d-gole@ti.com \
    --cc=bhanuseshukumar@gmail.com \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®