From: Sudeep Holla <sudeep.holla@arm.com>
To: Biancaa Ramesh <biancaa2210329@ssn.edu.in>
Cc: linux-kernel@vger.kernel.org, peng.fan@nxp.com,
cristian.marussi@arm.com, shawnguo@kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
s.hauer@pengutronix.de, festevam@gmail.com
Subject: Re: [PATCH] [PATCH] doc: fix typo "mannual" →"manual"imx95.rst
Date: Wed, 22 Oct 2025 21:15:39 +0100 [thread overview]
Message-ID: <aPk7a6OuEVtP6mZe@bogus> (raw)
In-Reply-To: <20251022200508.72941-1-biancaa2210329@ssn.edu.in>
On Thu, Oct 23, 2025 at 01:35:08AM +0530, Biancaa Ramesh wrote:
> --
> ::DISCLAIMER::
>
> ---------------------------------------------------------------------
> The
> contents of this e-mail and any attachment(s) are confidential and
> intended
> for the named recipient(s) only. Views or opinions, if any,
> presented in
> this email are solely those of the author and may not
> necessarily reflect
> the views or opinions of SSN Institutions (SSN) or its
> affiliates. Any form
> of reproduction, dissemination, copying, disclosure,
> modification,
> distribution and / or publication of this message without the
> prior written
> consent of authorized representative of SSN is strictly
> prohibited. If you
> have received this email in error please delete it and
> notify the sender
> immediately.
Again deleted as per your disclaimer. Please find a way to get rid of it
as I need to keep deleting your emails as suggested in the disclaimer.
> ---------------------------------------------------------------------
> Header of this mail should have a valid DKIM signature for the domain
> ssn.edu.in <http://www.ssn.edu.in/>
--
Regards,
Sudeep
prev parent reply other threads:[~2025-10-22 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 19:45 [PATCH] Subject: Modifying mannual to manual Biancaa Ramesh
2025-10-22 19:52 ` Sudeep Holla
2025-10-22 20:05 ` [PATCH] [PATCH] doc: fix typo "mannual" →"manual"imx95.rst Biancaa Ramesh
2025-10-22 20:15 ` Sudeep Holla [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=aPk7a6OuEVtP6mZe@bogus \
--to=sudeep.holla@arm.com \
--cc=biancaa2210329@ssn.edu.in \
--cc=cristian.marussi@arm.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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.