All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Dmitry Torokhov <dtor@insightbb.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] [git pull] Input updates for 2.6.25-rc0
Date: Fri, 08 Feb 2008 16:00:47 -0800	[thread overview]
Message-ID: <47ACED2F.30006@oracle.com> (raw)
In-Reply-To: <20080208155459.fdbcf610.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Fri, 8 Feb 2008 15:37:41 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> 
>>> I think someone already sent a patch to select the LEDS
>> I did... and more.  Who will merge it?  (below)
>>
>> ---
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Add I2C to config since the driver makes several i2c*() calls.
>>
>> Add to help text that the Intel I2C ICH (i801) driver is also needed
>> for this kernel.
>>
>> Add LEDS_CLASS to config since the driver makes les_classdev_*() calls:
>> ERROR: "led_classdev_register" [drivers/input/misc/apanel.ko] undefined!
>> ERROR: "__led_classdev_unregister" [drivers/input/misc/apanel.ko] undefined!
> 
> I have assumed that Dmitry will be handling this one.

Yes, that would be it's normal route, but when builds are easily broken,
it would be nice to have a fast-track mechanism...

But then I (we?) still think that people should use Documentation/SubmitChecklist
etc. also.  :(

-- 
~Randy

      reply	other threads:[~2008-02-09  0:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06  6:08 [git pull] Input updates for 2.6.25-rc0 Dmitry Torokhov
2008-02-06  6:32 ` Andrew Morton
2008-02-06  6:49   ` Dmitry Torokhov
2008-02-06  7:56     ` Sam Ravnborg
2008-02-06 14:19       ` Dmitry Torokhov
2008-02-07 20:05   ` Dmitry Torokhov
2008-02-07 21:00     ` Andrew Morton
2008-02-06  7:00 ` Andrew Morton
2008-02-08 23:25 ` Ingo Molnar
2008-02-08 23:28   ` Stephen Hemminger
2008-02-08 23:37     ` [patch] " Randy Dunlap
2008-02-08 23:49       ` Jesper Juhl
2008-02-08 23:54       ` Andrew Morton
2008-02-09  0:00         ` Randy Dunlap [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=47ACED2F.30006@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=dtor@insightbb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shemminger@linux-foundation.org \
    --cc=torvalds@linux-foundation.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.