From: Greg KH <gregkh@linuxfoundation.org>
To: Claudiu Beznea <claudiu.beznea@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wlan-ng: fixed "do not add new typedefs" warnings
Date: Sun, 21 Aug 2016 17:33:02 +0200 [thread overview]
Message-ID: <20160821153302.GA31647@kroah.com> (raw)
In-Reply-To: <1469895105-26735-1-git-send-email-claudiu.beznea@gmail.com>
On Sat, Jul 30, 2016 at 07:11:45PM +0300, Claudiu Beznea wrote:
> This patch suppress "do not add new typedefs" checkpatch.pl
> warnings. After this suppression some lines needs to be
> changed to avoid new checkpatch.pl complains (e.g. 80
> chars per line checkpatch.pl warning)
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea@gmail.com>
Just fix one typedef at a time, this patch is way too big to review
properly.
It also doesn't apply to my tree, so even if I wanted to take it, I
couldn't :(
Please break it up and send it as a patch series.
thanks,
greg k-h
prev parent reply other threads:[~2016-08-21 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 16:11 [PATCH] Staging: wlan-ng: fixed "do not add new typedefs" warnings Claudiu Beznea
2016-08-21 15:33 ` 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=20160821153302.GA31647@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=claudiu.beznea@gmail.com \
--cc=devel@driverdev.osuosl.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;
as well as URLs for NNTP newsgroup(s).