From: pmarzo <marzo.pedro@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
haticeerturk27@gmail.com, linux-kernel@vger.kernel.org,
dilekuzulmez@gmail.com, navyasri.tech@gmail.com,
senija.stanojevic@gmail.com
Subject: Re: [PATCH] Fixed coding style issues at ieee80211_crypt_wep.c
Date: Mon, 18 May 2015 19:32:18 +0200 [thread overview]
Message-ID: <1431970338.9328.14.camel@pedrito-laptop> (raw)
In-Reply-To: <20150518083352.GH14154@mwanda>
On Mon, 2015-05-18 at 11:33 +0300, Dan Carpenter wrote:
> Also the use a subsystem prefix in the subject:
>
> [PATCH] Staging: rtl8192u: whatever...
>
>
> regards,
> dan carpenter
>
Thanku for your comments, I will send an v2 patch version
regards, Pedro
prev parent reply other threads:[~2015-05-18 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 8:40 Pedro Marzo Perez
2015-05-16 6:56 ` Joe Perches
2015-05-18 8:33 ` Dan Carpenter
2015-05-18 17:32 ` pmarzo [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=1431970338.9328.14.camel@pedrito-laptop \
--to=marzo.pedro@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dilekuzulmez@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=haticeerturk27@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=navyasri.tech@gmail.com \
--cc=senija.stanojevic@gmail.com \
/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®