mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Rapoport <mike.rapoport@gmail.com>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Mike Rapoport <mike.rapoport@gmail.com>
Subject: [PATCH] staging: android: TODO: remove irrelevant parts
Date: Tue, 11 Aug 2015 22:08:38 +0300	[thread overview]
Message-ID: <1439320118-4673-1-git-send-email-mike.rapoport@gmail.com> (raw)
In-Reply-To: <20150811181017.GA29765@kroah.com>

- remove "make sure things build as modules properly"
- remove kuid_t related remarks, they were relevant for logger, but it
  is gone half year ago
- remove dead e-mail address of Brian Swetland

Signed-off-by: Mike Rapoport <mike.rapoport@gmail.com>
---
 drivers/staging/android/TODO | 11 +----------
 1 file changed, 1 insertion(+), 10 deletions(-)

diff --git a/drivers/staging/android/TODO b/drivers/staging/android/TODO
index 06954cd..37c90aa 100644
--- a/drivers/staging/android/TODO
+++ b/drivers/staging/android/TODO
@@ -2,16 +2,7 @@ TODO:
 	- checkpatch.pl cleanups
 	- sparse fixes
 	- rename files to be not so "generic"
-	- make sure things build as modules properly
 	- add proper arch dependencies as needed
 	- audit userspace interfaces to make sure they are sane
-	- kuid_t should never be exposed to user space as it is
-          kernel internal type. Data structure for this kuid_t is:
-          typedef struct {
-          	uid_t val;
-          } kuid_t;
-	- This bug is introduced by Xiong Zhou in the patch bd471258f2e09
-	- ("staging: android: logger: use kuid_t instead of uid_t")
 
-Please send patches to Greg Kroah-Hartman <greg@kroah.com> and Cc:
-Brian Swetland <swetland@google.com>
+Please send patches to Greg Kroah-Hartman <greg@kroah.com>
-- 
1.8.3.1


  reply	other threads:[~2015-08-11 19:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  6:24 [PATCH 0/6] staging: android: allow building some drivers as a module Mike Rapoport
2015-08-10  6:24 ` [PATCH 1/6] staging: android: allow building timed_gpio " Mike Rapoport
2015-08-10  6:24 ` [PATCH 2/6] staging: android: sync_debug.c: add include for linux/module.h Mike Rapoport
2015-08-10  6:24 ` [PATCH 3/6] staging: android: combine sync.o and sync_debug.o into sync-core.o Mike Rapoport
2015-08-10  6:24 ` [PATCH 4/6] staging: android: allow building sync and sw_sync as a module Mike Rapoport
2015-08-10  6:24 ` [PATCH 5/6] mm: export shmem_zero_setup for modules Mike Rapoport
2015-08-10  7:47   ` Christoph Hellwig
2015-08-10  6:24 ` [PATCH 6/6] staging: android: allow building ashmem as a module Mike Rapoport
2015-08-10 15:38 ` [PATCH 0/6] staging: android: allow building some drivers " Greg Kroah-Hartman
2015-08-10 20:10   ` Mike Rapoport
2015-08-10 21:03     ` Greg Kroah-Hartman
2015-08-11 13:09       ` Mike Rapoport
2015-08-11 18:10         ` Greg Kroah-Hartman
2015-08-11 19:08           ` Mike Rapoport [this message]
2015-08-11 23:39             ` [PATCH] staging: android: TODO: remove irrelevant parts Joe Perches
2015-08-12 18:08               ` [PATCH v2] staging: android: update TODO Mike Rapoport

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=1439320118-4673-1-git-send-email-mike.rapoport@gmail.com \
    --to=mike.rapoport@gmail.com \
    --cc=greg@kroah.com \
    --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

all inboxes | Powered by JetHome®