mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Valdis.Kletnieks@vt.edu, Arjan van de Ven <arjan@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: mmotm 2009-04-14-17-24 uploaded
Date: Wed, 15 Apr 2009 19:10:01 -0700	[thread overview]
Message-ID: <20090416021000.GC2413@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20090415105613.01540866.akpm@linux-foundation.org>

On Wed, Apr 15, 2009 at 10:56:13AM -0700, Andrew Morton wrote:
> On Wed, 15 Apr 2009 01:29:34 -0400 Valdis.Kletnieks@vt.edu wrote:
> 
> > On Tue, 14 Apr 2009 17:24:57 PDT, akpm@linux-foundation.org said:
> > > The mm-of-the-moment snapshot 2009-04-14-17-24 has been uploaded to
> > > 
> > >    http://userweb.kernel.org/~akpm/mmotm/
> > 
> > patch input-add-a-dmi-table-for-the-i8042reset-option-make-msi-wind-u-100-work.patch
> > is horribly busticated - was this dependent on another patch that was dropped?
> > The reference to 'i8042_nonfatal' is odd, I can't find it defined anywhere in the tree.
> > 
> >   CC      drivers/input/serio/i8042.o
> > In file included from drivers/input/serio/i8042.h:28,
> >                  from drivers/input/serio/i8042.c:85:
> > drivers/input/serio/i8042-x86ia64io.h:501: error: redefinition of 'i8042_dmi_reset_table'
> > drivers/input/serio/i8042-x86ia64io.h:380: note: previous definition of 'i8042_dmi_reset_table' was here
> > drivers/input/serio/i8042-x86ia64io.h: In function 'i8042_pnp_init':
> > drivers/input/serio/i8042-x86ia64io.h:619: error: 'i8042_nonfatal' undeclared (first use in this function)
> > drivers/input/serio/i8042-x86ia64io.h:619: error: (Each undeclared identifier is reported only once
> > drivers/input/serio/i8042-x86ia64io.h:619: error: for each function it appears in.)
> > make[2]: *** [drivers/input/serio/i8042.o] Error 1
> > 
> 
> Sorry, someone merged something else and I had a big reject to fix and
> I never got around to actually testing it and and and.  And Dmitry
> doesn't seem very interested in the patch anyway.
> 
> I'll drop it for now - Arjan, please resend anything which you think we
> still need.
> 
> Actually, it appears that I tried to get that patch into 2.6.29 and
> we're now missing 2.6.30.  What's happening here?  Dmitry?
> 

I had some concerns but they have been resolved after I had a chance to
talk to Arjan at the collaboration summit. The patch (both paches,
actually), in a bit modified form, is in my 'next' branch and I am
planning to ask Linus to pull it with the other small fixes in the next
day or so.

-- 
Dmitry

  reply	other threads:[~2009-04-16  2:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200904150024.n3F0Ovdo019569@imap1.linux-foundation.org>
2009-04-15  5:29 ` Valdis.Kletnieks
2009-04-15 15:27   ` Arjan van de Ven
2009-04-15 17:10     ` Valdis.Kletnieks
2009-04-15 17:56   ` Andrew Morton
2009-04-16  2:10     ` Dmitry Torokhov [this message]
2009-04-15 15:39 ` mmotm 2009-04-14-17-24 uploaded (mtd) Randy Dunlap
2009-04-15 20:27   ` Andrew Morton
2009-04-15 20:38     ` Randy Dunlap

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=20090416021000.GC2413@dtor-d630.eng.vmware.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.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

Powered by JetHome