linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David Härdeman" <david@hardeman.nu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: 2.6.32 -mm merge plans
Date: Wed, 16 Sep 2009 10:33:39 +0200 (CEST)	[thread overview]
Message-ID: <a26097d80818626d3fdb4ba668cc115b.squirrel@www.hardeman.nu> (raw)
In-Reply-To: <20090915211408.bb614be5.akpm@linux-foundation.org>

On Wed, September 16, 2009 06:14, Andrew Morton wrote:
> On Tue, 15 Sep 2009 20:46:50 -0700 Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
>>>
>>> input-add-a-shutdown-method-to-pnp-drivers.patch
>>
>> This should go through PNP tree (do we have one?).
>
> Not really.  Bjorn heeps an eye on pnp.  Sometimes merges through acpi,
> sometimes through -mm.
>
> I'll merge it I guess, but where is the corresponding change to the
> winbond driver?

I posted the most recent version of my patch, which is based on the pnp
layer rather than the acpi layer and which addresses every single comment
I've gotten so far, to linux-input, linux-kernel, Dmitry and you.

It's archived here (among other places):
http://www.spinics.net/lists/linux-input/msg04396.html

I assumed that Dmitry would be the logical person to push the patch
upstream and he indicated some hesitation if the driver would change its
mode of operation completely in a later revision (if the input subsystem
grows IR capabilities that is), see the relevant parts at the end of:

http://www.spinics.net/lists/linux-input/msg04395.html

I don't think these fears are reason enough to block the driver from
inclusion, if the input subsystem grows additional IR capabilities any and
all IR drivers will have to change accordingly and the IR capabilities
will serve to support additional functionality rather than providing a
drastic change to existing functionality.

-- 
David Hardeman

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-09-16  8:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 23:15 Andrew Morton
2009-09-16  3:46 ` Dmitry Torokhov
2009-09-16  4:14   ` Andrew Morton
2009-09-16  8:33     ` David Härdeman [this message]
2009-09-16 15:00     ` Bjorn Helgaas
2009-09-16 20:00       ` Andrew Morton
2009-09-16  7:37 ` memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans) Balbir Singh
2009-09-16  7:51   ` Daisuke Nishimura
2009-09-16  7:58   ` KAMEZAWA Hiroyuki
2009-09-16  8:45 ` stack limits [was Re: 2.6.32 -mm merge plans] Pavel Machek
2009-09-16  9:42 ` hwpoison fixes was Re: 2.6.32 -mm merge plans Andi Kleen
2009-09-17 20:15 ` cgrooups && " Oleg Nesterov
2009-09-17 20:38   ` Andrew Morton
2009-09-17 21:08     ` Oleg Nesterov
2009-09-17 20:32 ` do_wait() changes " Oleg Nesterov
2009-09-17 20:46 ` tracehooks " Oleg Nesterov
2009-09-17 21:56   ` Roland McGrath

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=a26097d80818626d3fdb4ba668cc115b.squirrel@www.hardeman.nu \
    --to=david@hardeman.nu \
    --cc=akpm@linux-foundation.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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