public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: John Appleby <john@dnsworld.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serio keyboard issues 2.5.70
Date: Wed, 4 Jun 2003 23:23:18 +0100	[thread overview]
Message-ID: <20030604232318.D22460@flint.arm.linux.org.uk> (raw)
In-Reply-To: <434747C01D5AC443809D5FC5405011315699@bobcat.unickz.com>; from john@dnsworld.co.uk on Wed, Jun 04, 2003 at 08:23:21PM +0100

On Wed, Jun 04, 2003 at 08:23:21PM +0100, John Appleby wrote:
> And that printk is coming up fine. serio_register_device seems to add
> 0x021c2af8 to its tail, but then never finds my entry in
> list_for_each_entry and thus never calls dev->connect(). I've added some
> debugging to serio_register_device thus:
> 
> void serio_register_device(struct serio_dev *dev)
> {
>         struct serio *serio;
>         list_add_tail(&dev->node, &serio_dev_list);
> 	  printk("serio: add_tail %08x\n",&dev->node);
>         list_for_each_entry(serio, &serio_list, node) {
>                 printk("serio: register_device %08x\n",serio->dev);
>                 if (!serio->dev && dev->connect) {
>                         printk("serio: connecting...\n");
>                         dev->connect(serio, dev);
>                 }
>         }
> }
> 
> and I get nothing past "add_tail". I'd expect it to recognize my dev and
> attempt to connect to it.

Do you drop out the bottom of the function?  If you have no hardware ports
registered, I'd expect this to be the case.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-06-04 22:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <434747C01D5AC443809D5FC540501131097083@bobcat.unickz.com>
2003-06-04 19:23 ` Serio keyboard issues 2.5.70 John Appleby
2003-06-04 22:23   ` Russell King [this message]
2003-06-04 19:51 Perez-Gonzalez, Inaky
     [not found] <434747C01D5AC443809D5FC54050113109709D@bobcat.unickz.com>
2003-06-04 20:08 ` John Appleby
     [not found] <434747C01D5AC443809D5FC5405011310970EA@bobcat.unickz.com>
2003-06-04 22:44 ` John Appleby
2003-06-04 22:47   ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2003-06-04 22:59 Perez-Gonzalez, Inaky
2003-06-04 23:03 ` Russell King

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=20030604232318.D22460@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=john@dnsworld.co.uk \
    --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