From: Greg KH <gregkh@suse.de>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: Dima Zavin <dima@android.com>,
Kashyap Gada <gada.kashyap@gmail.com>,
rebecca@android.com, rschultz@google.com, jgennis@google.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] Staging: android: Add KERN_ facility level in printk () in pmem.c
Date: Fri, 27 Jan 2012 10:00:12 -0800 [thread overview]
Message-ID: <20120127180012.GA28500@suse.de> (raw)
In-Reply-To: <1327686693.3077.12.camel@lorien.americas.hpqcorp.net>
On Fri, Jan 27, 2012 at 10:51:33AM -0700, Shuah Khan wrote:
> On Mon, 2012-01-23 at 09:31 -0800, Greg KH wrote:
> > On Mon, Jan 23, 2012 at 09:22:27AM -0800, Dima Zavin wrote:
> > > We really should just get rid of pmem.c altogether. We will remove it
> > > from our android common tree too. We don't actually use it anymore in
> > > any of our products. There are some legacy users of it, like Qualcomm,
> > > but I'm sure they have a bunch of patches on top of it and thus are
> > > maintaining it separately anyway.
> >
> > Ok, I'll be glad to drop it if you all don't use it anymore and it's not
> > needed. That makes life a lot easier for me :)
> >
> > thanks,
> >
> > greg k-h
>
> Done. I sent a patch to remove pmem driver yesterday.
>
> https://lkml.org/lkml/2012/1/26/368
And yet you failed to cc: me so that I can accept it :(
Please, the scripts/get_maintainer.pl tool is there for you to use, not
just admire from afar...
I'll go dig it out of lkml and queue it up,
greg k-h
next prev parent reply other threads:[~2012-01-27 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 3:24 [PATCH 5/5] Staging: android: Add KERN_ facility level in printk () in pmem.c Kashyap Gada
2012-01-23 17:22 ` Dima Zavin
2012-01-23 17:31 ` Greg KH
2012-01-27 17:51 ` Shuah Khan
2012-01-27 18:00 ` Greg KH [this message]
2012-01-26 12:09 ` Alan Cox
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=20120127180012.GA28500@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=dima@android.com \
--cc=gada.kashyap@gmail.com \
--cc=jgennis@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rebecca@android.com \
--cc=rschultz@google.com \
--cc=shuahkhan@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.