public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Adam Dixon" <adamtdixon@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] headset and input noise
Date: Sat, 28 Apr 2007 14:14:50 +0930	[thread overview]
Message-ID: <b92d97be0704272144m715e02bj8be217a328e62ed0@mail.gmail.com> (raw)
In-Reply-To: <a72d33330704260237l10d76906ma50d45cb9e0f0fb8@mail.gmail.com>

Hello,
I have followed this guide to build kernel rpm in fedora vs
kernel-2.6.20-1.2944.fc6.src.rpm - I like Ma am struggling to get the
patch applied ok.
For those interested ( http://www.howtoforge.com/kernel_compilation_fedora )

I get the following error when building from the edited spec file.
+ echo 'Patch #8 (sco-flowcontrol-v4.2.diff):'
+ patch -p1 -s
error: Bad exit status from /var/tmp/rpm-tmp.12170 (%prep)
    Bad exit status from /var/tmp/rpm-tmp.12170 (%prep)

I defined the patch as %patch8 -p1 ( I dont know if p1 is a suitable
argument - but all other patches used p1. Is this right?)

Does this patch only work against an older kernel ? Or do I need to
place the patch in a later number. Any hints? Even if just hints to
get more debug from this process would be nice.

Thanks allot,
Adam

On 4/26/07, Ma Begaj <derliebegott@gmail.com> wrote:
> 2007/4/26, Brad Midgley <bmidgley@xmission.com>:
> >
> > >> are you using the sco flowcontrol kernel patch from the plugz module
> > >> under the patches directory?
> > >
> >
> > making a distro-friendly custom kernel differs from distro to distro, so
> > search around for fedora guides on doing a custom kernel. I don't use
> > fedora so I don't know.
> >
> > Brad
>
> Hi,
>
> I tried yesterday to patch my kernel with the
> plugz/patches/sco....v4.2.diff  and v.4-1. No chance for patch to
> succeed.
>
> I tried version 4.2 with 2.6.20.6, but a half of the patch did not
> work. I tried it with 2.6.21-rc7, again with half of the patch skipped
> ...
>
> Everything was tested with vanilla kernel without any other patches.
>
> M.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-04-28  4:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24  3:57 [Bluez-users] headset and input noise Adam Dixon
2007-04-24 13:02 ` walt shekrota
2007-04-24 13:20 ` Brad Midgley
2007-04-24 23:17   ` Adam Dixon
2007-04-26  5:25   ` Adam Dixon
2007-04-26  7:20     ` Brad Midgley
2007-04-26  9:37       ` Ma Begaj
2007-04-28  4:44         ` Adam Dixon [this message]
2007-04-28 10:22           ` Ma Begaj

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=b92d97be0704272144m715e02bj8be217a328e62ed0@mail.gmail.com \
    --to=adamtdixon@gmail.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