From: Sohny Thomas <sohnythomas@zoho.com>
To: gregkh@linuxfoundation.org, arve@android.com,
riandrews@android.com, sumit.semwal@linaro.org,
carlos@cgarcia.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: [PATCH v2 0/3] Staging: android: Fix coding style and TODO file
Date: Wed, 01 Jul 2015 13:55:03 +0000 [thread overview]
Message-ID: <5593EE67.8050302@zoho.com> (raw)
In-Reply-To: <5593E448.70307@zoho.com>
These set of patches Fixes the following issues in the android staging driver
- removed non-existent issue from TODO file
kuid_t or uid_t not present in staging/android
- fixed 80 char limit exceeding line
- a newline after declarations as per checkpatch.pl
- fixed an unnecessary typedef as reported by checkpatch.pl
-Regards,
Sohny
WARNING: multiple messages have this Message-ID (diff)
From: Sohny Thomas <sohnythomas@zoho.com>
To: gregkh@linuxfoundation.org, arve@android.com,
riandrews@android.com, sumit.semwal@linaro.org,
carlos@cgarcia.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: [PATCH v2 0/3] Staging: android: Fix coding style and TODO file
Date: Wed, 1 Jul 2015 19:13:03 +0530 [thread overview]
Message-ID: <5593EE67.8050302@zoho.com> (raw)
In-Reply-To: <5593E448.70307@zoho.com>
These set of patches Fixes the following issues in the android staging driver
- removed non-existent issue from TODO file
kuid_t or uid_t not present in staging/android
- fixed 80 char limit exceeding line
- a newline after declarations as per checkpatch.pl
- fixed an unnecessary typedef as reported by checkpatch.pl
-Regards,
Sohny
next parent reply other threads:[~2015-07-01 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5593E448.70307@zoho.com>
2015-07-01 13:43 ` Sohny Thomas [this message]
2015-07-01 13:55 ` [PATCH v2 0/3] Staging: android: Fix coding style and TODO file Sohny Thomas
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=5593EE67.8050302@zoho.com \
--to=sohnythomas@zoho.com \
--cc=arve@android.com \
--cc=carlos@cgarcia.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=sumit.semwal@linaro.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 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.