All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: Applying Herton supplied patches ...
Date: Sat, 14 Feb 2009 22:37:39 +0000	[thread overview]
Message-ID: <gn7h3k$p1f$1@ger.gmane.org> (raw)
In-Reply-To: <499740EB.6040600@wisc.edu>

'Twas brillig, and Guy Stalnaker at 14/02/09 22:08 did gyre and gimble:
> herton or Takashi,
> 
> How does one go about applying a patch like the ones attached to Message 
> 6?  And to which files are they applied?  I assume they are meant for 
> the alsa-driver code, but that's as much as I know (well, I know how to 
> run ./configure, make, and make sudo :).  I'd very much like to see if 
> the patches work for my HP dv4 1225.

Generally these would be applied via git-am into a local git clone of 
the sources.

As many of these patches will be to the driver this means applying the 
patches to your kernel and recompiling. It's a quite involved process 
and not really for the faint hearted.

If you really want to test them out, the easiest way would be to install 
Mandriva Cooker (the development version of Mandriva) and the latest 
kernel package. I'm not sure if these patches are in the latest cooker 
kernel yet but Herton is part of the kernel team and the patches will no 
doubt show up soon if they are not there already.

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
   Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
   Mandriva Linux Contributor [http://www.mandriva.com/]
   PulseAudio Hacker [http://www.pulseaudio.org/]
   Trac Hacker [http://trac.edgewall.org/]

      reply	other threads:[~2009-02-14 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2735.1234638846.1965.alsa-devel@alsa-project.org>
2009-02-14 22:08 ` Applying Herton supplied patches Guy Stalnaker
2009-02-14 22:37   ` Colin Guthrie [this message]

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='gn7h3k$p1f$1@ger.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --cc=alsa-devel@alsa-project.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.