From: Saalim Quadri <danascape@gmail.com>
To: gregkh@linuxfoundation.org
Cc: Michael.Hennerich@analog.com, danascape@gmail.com,
jic23@kernel.org, lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: iio: ad5933: Fix CamelCase naming
Date: Mon, 3 Mar 2025 23:37:18 +0530 [thread overview]
Message-ID: <20250303180718.15707-1-danascape@gmail.com> (raw)
In-Reply-To: <2025030301-niece-evacuate-0f05@gregkh>
I am so sorry for such a silly mistake,
will try to read before sending patches from now on :/
Yours Sincerely,
Saalim Quadri
prev parent reply other threads:[~2025-03-03 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 12:52 [PATCH] staging: iio: ad5933: Fix CamelCase naming Saalim Quadri
2025-03-03 12:56 ` Greg KH
2025-03-03 18:07 ` Saalim Quadri [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=20250303180718.15707-1-danascape@gmail.com \
--to=danascape@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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