public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Bueche <charles@bueche.ch>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Cc: Dave Sailer <dave.sailer@paytec.com>
Subject: Re: [Bluez-users] problem with keyboard/mouse
Date: Fri, 22 Oct 2004 15:24:43 +0200	[thread overview]
Message-ID: <20041022152443.251405a6@bluez.bueche.ch> (raw)
In-Reply-To: <1098449746.4704.56.camel@pegasus>

Hi,

to add my grain of salt : I run 2.6.9-gentoo with patch-2.6.9-mh1.gz,
and I see no problem at all. I have however no Microsoft hardware, only 
a Logitech MX900 mouse.

Charles

On Fri, 22 Oct 2004 14:55:46 +0200
Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Dave,
> 
> > The gentoo forums had this advice....
> > 
> > ---------------------------------
> > You'll see an error when applying the patch... Confused : 
> > Quote:
> > 
> > patching file drivers/bluetooth/hci_usb.c 
> > patching file include/net/bluetooth/bluetooth.h 
> > patching file include/net/bluetooth/hci_core.h 
> > patching file include/net/bluetooth/hci.h 
> > patching file Makefile 
> > Hunk #1 FAILED at 1. 
> > 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej 
> > patching file net/bluetooth/af_bluetooth.c 
> > patching file net/bluetooth/bnep/core.c 
> > patching file net/bluetooth/hci_conn.c 
> > patching file net/bluetooth/hci_core.c 
> > patching file net/bluetooth/hci_event.c 
> > patching file net/bluetooth/hci_sock.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/Kconfig 
> > patching file net/bluetooth/l2cap.c 
> > patching file net/bluetooth/rfcomm/sock.c 
> > That's totaly normal
> > 
> > -----------------------------
> > anyway, do you have any idea what my error might be or is this
> > something I need to go back to the gentoo folks with?
> 
> if you only see a reject for the Makefile then this ok as long as
> Makefile.rej only shows you the hunk for the EXTRAVERSION.
> 
> Maybe you wanna do a "make clean" or "make distclean" first. Or simply
> try a vanilla 2.6.9-mh1.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal Use IT products in your business? Tell us what you
> think of them. Give us Your Opinions, Get Free ThinkGeek Gift
> Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-- 
Charles Bueche <charles@bueche.ch>
sand, snow, wave, wind and net -surfer


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-10-22 13:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 10:38 [Bluez-users] problem with keyboard/mouse Dave Sailer
2004-10-22 11:10 ` Marcel Holtmann
2004-10-22 12:14   ` Stephen Crane
2004-10-22 12:21     ` Marcel Holtmann
     [not found]   ` <1098447645.11708.17.camel@dsailer>
2004-10-22 12:55     ` Marcel Holtmann
2004-10-22 13:24       ` Charles Bueche [this message]
2004-10-22 13:53         ` Marcel Holtmann
2004-10-22 14:29           ` Dave Sailer

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=20041022152443.251405a6@bluez.bueche.ch \
    --to=charles@bueche.ch \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=dave.sailer@paytec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox