From: Greg KH <gregkh@linuxfoundation.org>
To: Vikas Kumar Sharma <ks.vikas@globaledgesoft.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] This patch fixes the check-patch errors
Date: Tue, 2 Mar 2021 13:53:57 +0100 [thread overview]
Message-ID: <YD41ZR5tuXJsWfMo@kroah.com> (raw)
In-Reply-To: <20210302124254.GA2349431@vijayakumar>
On Tue, Mar 02, 2021 at 06:12:54PM +0530, Vikas Kumar Sharma wrote:
> Disclaimer:This message is intended only for the designated recipient(s).
> It may contain confidential or proprietary information and may be subject
> to other confidentiality protections. If you are not a designated
> recipient, you may not review, copy or distribute this message. Please
> notify the sender by e-mail and delete this message. GlobalEdge does not
> accept any liability for virus infected mails.
Email is now deleted, sorry, this does not belong on any emails sent to
public mailing lists for kernel development efforts.
prev parent reply other threads:[~2021-03-02 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 12:42 [PATCH] This patch fixes the check-patch errors Vikas Kumar Sharma
2021-03-02 12:53 ` Greg KH [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=YD41ZR5tuXJsWfMo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=ks.vikas@globaledgesoft.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox