All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Pete Leigh <pete.leigh@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Fwd: Support for Roland VG-99 (working code, but could use help)
Date: Fri, 19 Oct 2012 20:21:40 +0200	[thread overview]
Message-ID: <50819A34.4010600@gmail.com> (raw)
In-Reply-To: <CABn3OEHmJqtkkKz1TeLh_Q52meUkuzKYnp8sTH5LtSjMG73sCg@mail.gmail.com>

On 19.10.2012 20:18, Pete Leigh wrote:
> On 19 October 2012 18:46, Daniel Mack <zonque@gmail.com> wrote:
>> On 19.10.2012 19:02, Pete Leigh wrote:
> 
>>> I quickly tested the VG-99 quirk (modified as per Clemens' suggestion)
>>> and that works too, so I'll work on generating a patch as per the
>>> instructions on alsa-project.org.
> 
> Actually, I'm struggling a bit with this. I'm guessing
> (alsa-project.org doesn't seem to say...) that you need to check out
> the release branch in alsa-driver to work on, and do your commit
> against that (master branch contains only a README) but the wiki also
> advises to do a rebase origin/master after your commit. It seemed
> weird, but I tried it, to no useful effect of course.
> 
> As a relative novice, this is pretty confusing stuff. Is there a plain
> step-by-step of the procedure to generate a patch? Would  it be
> acceptable to send the patch against the sound.git tree?

Yes, sound.git is the reference, and your patch should apply cleanly on
top of it.


Daniel

  reply	other threads:[~2012-10-19 18:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABn3OEFatrnhGs1xzpmOfXSxpSLuGwgRtN8v=1B96i6=7_9vTg@mail.gmail.com>
2012-10-15 23:59 ` Fwd: Support for Roland VG-99 (working code, but could use help) Pete Leigh
2012-10-16  7:40   ` Daniel Mack
2012-10-16  8:31     ` Pete Leigh
2012-10-16  8:36       ` Daniel Mack
2012-10-18 23:38         ` Pete Leigh
2012-10-19  7:45           ` Daniel Mack
2012-10-19  8:23             ` Pete Leigh
2012-10-19  8:24               ` Daniel Mack
2012-10-19  8:49                 ` Pete Leigh
2012-10-19 17:02                   ` Pete Leigh
2012-10-19 17:46                     ` Daniel Mack
2012-10-19 18:18                       ` Pete Leigh
2012-10-19 18:21                         ` Daniel Mack [this message]
2012-10-19 22:24                       ` Pete Leigh
2012-10-20  0:17                         ` Pete Leigh
2012-10-20  2:21                           ` Pete Leigh
2012-10-16  9:19       ` Clemens Ladisch
2012-10-16 11:38         ` Pete Leigh
2012-10-16 12:27           ` Clemens Ladisch

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=50819A34.4010600@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=pete.leigh@gmail.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 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.