From: Joe Perches <joe@perches.com>
To: Peng Sun <sironhide0null@gmail.com>
Cc: gregkh@linuxfoundation.org, arve@android.com,
riandrews@android.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] fix drivers/staging/android several coding issues
Date: Tue, 25 Aug 2015 08:18:47 -0700 [thread overview]
Message-ID: <1440515927.2670.85.camel@perches.com> (raw)
In-Reply-To: <1440485632-17242-1-git-send-email-sironhide0null@gmail.com>
On Tue, 2015-08-25 at 14:53 +0800, Peng Sun wrote:
> patches based on linux-next next-20150824
> Corrections based on checkpatch.pl with --strict
>
> Peng Sun (6):
> fix android/ashmem.c several coding style issues
> fix android/lowmemorykiller.c several coding style issues
> fix android/sw_sync.c several coding style issues
> fix android/sync.c several coding style issues
> fix android/sync.h several coding style issues
> fix android/timed_gpio.c several coding style issues
Most here would rather you submit multiple
patches by fix type rather than sending
patches with multiple fix types per file.
prev parent reply other threads:[~2015-08-25 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 6:53 [PATCH 0/6] fix drivers/staging/android several coding issues Peng Sun
2015-08-25 6:53 ` [PATCH 1/6] fix android/ashmem.c several coding style issues Peng Sun
2015-08-25 6:53 ` [PATCH 2/6] fix android/lowmemorykiller.c " Peng Sun
2015-08-25 6:53 ` [PATCH 3/6] fix android/sw_sync.c " Peng Sun
2015-08-25 6:53 ` [PATCH 4/6] fix android/sync.c " Peng Sun
2015-08-25 6:53 ` [PATCH 5/6] fix android/sync.h " Peng Sun
2015-08-25 6:53 ` [PATCH 6/6] fix android/timed_gpio.c " Peng Sun
2015-08-25 15:18 ` Joe Perches [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=1440515927.2670.85.camel@perches.com \
--to=joe@perches.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=sironhide0null@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.