All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-omap-open-source@linux.omap.com
Subject: Re: Pending October patches
Date: Fri, 3 Nov 2006 11:52:15 -0800	[thread overview]
Message-ID: <200611031152.16397.david-b@pacbell.net> (raw)
In-Reply-To: <20061101212850.GD6833@atomide.com>

On Wednesday 01 November 2006 1:28 pm, tony@atomide.com wrote:

> > 27. [PATCH] [USB/CORE/USB.C] Fixes autosuspend and auto_pm 
> > fields missing
> > http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008234.html
> 
> Sounds like this is getting fixed in the mainline tree.

No, the root cause of the problem is a borked h2 defconfig; but I'm
not clear how it got past the build step that's supposed to make sure
the current config matches all the Kconfig constraints.

(That is, USB_SUSPEND depends on PM, but only one of them was set in
the defconfig yet the build was proceeding ...)

  parent reply	other threads:[~2006-11-03 19:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 15:54 Pending October patches Dirk Behme
2006-11-01 21:28 ` tony
2006-11-02 17:00   ` Dirk Behme
2006-11-03 10:50     ` Komal Shah
2006-11-05 10:32       ` I2C zero length transfers and SMBUS_QUICK, was: " Dirk Behme
2006-11-05 19:49         ` Komal Shah
2006-11-06 10:36           ` Arnaud Patard
2006-11-06 18:33             ` Broken N770, was: I2C zero length transfers and SMBUS_QUICK Dirk Behme
2006-11-06 19:49               ` Arnaud Patard
2006-11-06 20:18                 ` Broken N770 Dirk Behme
2006-11-06 20:24                   ` Arnaud Patard
2006-11-06  1:37         ` I2C zero length transfers and SMBUS_QUICK, was: Pending October patches David Brownell
2006-11-07 17:40           ` tony
2006-11-07 20:24             ` I2C zero length transfers and SMBUS_QUICK David Brownell
2006-11-09  2:32               ` Tony Lindgren
2006-11-03 19:52   ` David Brownell [this message]
2006-11-03 20:18     ` Pending October patches Dirk Behme

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=200611031152.16397.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap-open-source@linux.omap.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.