All of lore.kernel.org
 help / color / mirror / Atom feed
From: Delio Brignoli <dbrignoli@audioscience.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH] asihpi update
Date: Sat, 19 Nov 2005 01:21:37 +1300	[thread overview]
Message-ID: <437DC751.6040900@audioscience.com> (raw)
In-Reply-To: <s5hr79ep3ih.wl%tiwai@suse.de>


Hello Takashi,

Takashi Iwai wrote:
> OK, my concern was the change of alsa-driver/asihpi/Makefile in your
> last patch.  You added the stuff to generate at compile time there.
> I'm not against at all to process it _manually_ on your side.

The extra rules in the makefile are to be used by us internally to 
prepare dist files (and are only triggered when source files are 
missing) or by customers that want to compile ALSA with bleeding edge 
code from our CVS rep.

I'm not 100% sure about what you mean with "_manually_".
if you mean that: I generate code for an ALSA dist from our CVS, then 
diff, send the patch to alsa-devel. Then it's fine. :)

> Ah, then it might be my fix in alsa-driver tree.
> HW32 must be u32 (equivalent with unsigned int) on linux kernel.
> Using long for 32bit is wrong.

I'll look into this one too.

thanks
--
Delio


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click

  reply	other threads:[~2005-11-18 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <437D1FAE.3000400@audioscience.com>
2005-11-18 11:20 ` [PATCH] asihpi update Takashi Iwai
2005-11-18 11:58   ` Delio Brignoli
2005-11-18 12:03     ` Takashi Iwai
2005-11-18 12:21       ` Delio Brignoli [this message]
2005-11-18 13:17         ` Takashi Iwai
2005-11-22  1:22       ` Delio Brignoli
2005-11-22 10:11         ` Takashi Iwai

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=437DC751.6040900@audioscience.com \
    --to=dbrignoli@audioscience.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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.