public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R Jayadurga <jayad@cdac.in>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: florian.c.schilhabel@googlemail.com,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Larry.Finger@lwfinger.net, linux-kernel@vger.kernel.org,
	driverdev-devel@linuxdriverproject.org,
	devel@driverdev.osuosl.org
Subject: Re: [PATCH 10/10] Staging: rtl8712: ieee80211: fixed coding style issue
Date: Tue, 13 Jun 2017 12:22:08 +0530 (IST)	[thread overview]
Message-ID: <432983150.161.1497336728606.JavaMail.open-xchange@webmail.cdac.in> (raw)
In-Reply-To: <20170613055511.GB17475@kroah.com>

sorry for the inconvenience caused i have corrected it.

Regards,
Jaya Durga R

On June 13, 2017 at 11:25 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> On Tue, Jun 13, 2017 at 10:47:58AM +0530, R Jayadurga wrote:
> > This e-mail is for the sole use of the intended recipient(s) and may
> > contain confidential and privileged information. If you are not the
> > intended recipient, please contact the sender by reply e-mail and destroy
> > all copies and the original message. Any unauthorized review, use,
> > disclosure, dissemination, forwarding, printing or copying of this email
> > is strictly prohibited and appropriate legal action will be taken.
> > -------------------------------------------------------------------------------------------------------------------------------
>
> As per your footer, I am deleting your email.
>
> Please note that I'm really not supposed to be responding to this at
> all, as this type of text is not allowed at all on kernel development
> mialing lists...

-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------

  reply	other threads:[~2017-06-13  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-11 18:44 [PATCH 10/10] Staging: rtl8712: ieee80211: fixed coding style issue Jaya Durga
2017-06-12 12:12 ` Dan Carpenter
     [not found]   ` <1515429128.1447.1497331078332.JavaMail.open-xchange@webmail.cdac.in>
2017-06-13  5:55     ` Greg KH
2017-06-13  6:52       ` R Jayadurga [this message]
2017-06-12 20:57 ` [10/10] " Guenter Roeck

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=432983150.161.1497336728606.JavaMail.open-xchange@webmail.cdac.in \
    --to=jayad@cdac.in \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --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