public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: tim culwins <mail0123456789101112@yahoo.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] patch failed...
Date: Sat, 3 Mar 2007 12:56:17 -0800 (PST)	[thread overview]
Message-ID: <721148.87368.qm@web31712.mail.mud.yahoo.com> (raw)
In-Reply-To: <1172956943.5752.0.camel@aeonflux.holtmann.net>

thanks for the help,

ok i tried again using the kernel form
http://www.kernel.org/
and still get this:

sudo zcat patch-2.6.20-mh1.gz | patch -p
patch: option requires an argument -- p
patch: Try `patch --help' for more information.
root@arc:/usr/src/linux# sudo zcat patch-2.6.20-mh1.gz
| patch -p1
patching file drivers/bluetooth/bcm203x.c
patching file drivers/bluetooth/bfusb.c
patching file drivers/bluetooth/bt3c_cs.c
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_core.c
patching file net/bluetooth/hidp/core.c
patching file net/bluetooth/hidp/hidp.h
patching file net/bluetooth/hidp/Kconfig
patching file net/bluetooth/hidp/sock.c
root@arc:/usr/src/linux# 



--- Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Tim,
> 
> > so im trying to apply the new patch to my ubuntu
> > kernel. and i get this error message. any idea
> whats
> > wrong?
> 
> the patch is not meant to be applied against the
> Ubuntu kernel. It is
> for the plain vanilla upstream kernel. You must take
> this to the Ubunutu
> guys.
> 
> Regards
> 
> Marcel
> 
> 
> 
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
> the chance to share your
> opinions on IT & business topics through brief
> surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/bluez-users
> 



 
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-03-03 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 14:34 [Bluez-users] undefined reference to `XML_StopParser' vikram
2007-03-03 11:36 ` Marcel Holtmann
2007-03-03 19:24   ` [Bluez-users] patch failed tim culwins
2007-03-03 21:22     ` Marcel Holtmann
2007-03-03 20:56       ` tim culwins [this message]
2007-03-04  2:59         ` Marcel Holtmann
2007-03-07  0:15           ` tim culwins

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=721148.87368.qm@web31712.mail.mud.yahoo.com \
    --to=mail0123456789101112@yahoo.com \
    --cc=bluez-users@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