From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Fixed coding style problem
Date: Thu, 29 May 2014 22:03:19 +0000 [thread overview]
Message-ID: <20140529220319.GE15585@mwanda> (raw)
In-Reply-To: <1401400436-4396-1-git-send-email-cmroliv@gmail.com>
Work against linux-next. Someone already fixed this. The subject
should have been:
[PATCH] staging: wlan-ng: <something something netdev_err()>
With correct prefix and a more descriptive title. See how Vitaly did
it: http://www.spinics.net/lists/linux-driver-devel/msg46770.html
regards,
dan carpenter
next prev parent reply other threads:[~2014-05-29 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 21:53 [PATCH] Fixed coding style problem Miguel Oliveira
2014-05-29 21:57 ` Greg KH
2014-05-29 22:03 ` Dan Carpenter [this message]
2014-05-29 22:07 ` Miguel Oliveira
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=20140529220319.GE15585@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@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