From: Timo Veith <tv@rz-zw.fh-kl.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard
Date: Tue, 22 Mar 2005 00:51:56 +0100 [thread overview]
Message-ID: <423F5E1C.8030301@rz-zw.fh-kl.de> (raw)
In-Reply-To: <423F5B7F.9060200@rz-zw.fh-kl.de>
Hm if I try to patch the gentoo-dev-sources kernel I get this:
tristan linux # zcat /home/timo/tmp/patch-2.6.11-mh2.gz | patch -p1
--dry-run
patching file drivers/bluetooth/bluecard_cs.c
patching file drivers/bluetooth/hci_bcsp.c
patching file drivers/bluetooth/hci_usb.c
patching file include/net/bluetooth/hci_core.h
patching file MAINTAINERS
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file net/bluetooth/hci_conn.c
patching file net/bluetooth/hci_event.c
patching file net/bluetooth/hci_sysfs.c
patching file net/bluetooth/hidp/core.c
patching file net/bluetooth/hidp/hid.c
patching file net/bluetooth/hidp/hid.h
patching file net/bluetooth/hidp/hidp.h
patching file net/bluetooth/hidp/Makefile
patching file net/bluetooth/rfcomm/core.c
There is one failure. Should I use vanilla sources or is this ok? I
found a little HOWTO in the gentoo forums where a similar failure was
described as "normal".
http://forums.gentoo.org/viewtopic-t-231506-highlight-devices+hci.html
Timo
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-21 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 22:01 [Bluez-devel] Problem with BlueLogic WingKey Keyboard Timo Veith
2005-03-21 12:32 ` Marcel Holtmann
2005-03-21 23:40 ` Timo Veith
2005-03-21 23:51 ` Timo Veith [this message]
2005-03-22 0:59 ` Marcel Holtmann
2005-03-22 19:08 ` Timo Veith
2005-03-22 22:26 ` Marcel Holtmann
2005-03-22 1:02 ` Marcel Holtmann
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=423F5E1C.8030301@rz-zw.fh-kl.de \
--to=tv@rz-zw.fh-kl.de \
--cc=bluez-devel@lists.sourceforge.net \
/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