All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bluez-dtl1-workaround not provided?
Date: Fri, 26 Nov 2010 10:59:31 +0000	[thread overview]
Message-ID: <1290769171.20979.51.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <AANLkTinbu9JpEw5fdX8pHcxraf4uTdCf7JKm9v1UekeS@mail.gmail.com>

On Thu, 2010-11-25 at 18:24 +0100, Andrea Adami wrote:
> So, first doubt is: why make this mandatory for everyone having pcmcia?

It shouldn't be.  The dependency in kernel-module-dtl1-cs should be
sufficient to pull it in for (only) those people who are installing the
driver that needs those bits.

p.





  parent reply	other threads:[~2010-11-26 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 17:24 bluez-dtl1-workaround not provided? Andrea Adami
2010-11-25 20:48 ` Frans Meulenbroeks
2010-11-26  7:46 ` Martin Jansa
2010-11-30 22:09   ` Khem Raj
2010-12-01  6:07     ` [PATCHv2] kernel.bbclass: put bluez-dtl1-workaround to DEPENDS directly Martin Jansa
2010-11-26  8:29 ` bluez-dtl1-workaround not provided? Marcin Juszkiewicz
2010-11-26 10:59 ` Phil Blundell [this message]
2010-11-27 18:46   ` Andrea Adami
2010-11-30 18:50   ` Martin Jansa

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=1290769171.20979.51.camel@mill.internal.reciva.com \
    --to=philb@gnu.org \
    --cc=openembedded-devel@lists.openembedded.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.