From: Takashi Iwai <tiwai@suse.de>
To: karsten wiese <annabellesgarden@yahoo.de>
Cc: Clemens Ladisch <clemens@ladisch.de>,
Devel Alsa <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] reenable MIDI for usx2y
Date: Wed, 30 Mar 2005 15:54:29 +0200 [thread overview]
Message-ID: <s5hzmwlfdd6.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050330134927.33563.qmail@web26507.mail.ukl.yahoo.com>
At Wed, 30 Mar 2005 15:49:27 +0200 (CEST),
karsten wiese wrote:
>
>
> --- Takashi Iwai <tiwai@suse.de> wrote:
> > At Sun, 27 Mar 2005 14:00:12 +0200 (CEST),
> > karsten wiese wrote:
> > >
> > > Hi Clemens,
> > >
> > > usx2y needs to specify exactly what usb-endpoints to
> > use.
> > > this feature got lost lately and is restored by
> > attached
> > > patch. Please apply!
> >
> > IMO, it's better to fix snd_usbmidi_detect_endpoints() to
> > check
> > in_ep and out_ep rather than its caller.
>
> I'd prefer a new function snd_usbmidi_check_endpoints()
> then.
> Caller would call snd_usbmidi_check_endpoints() if
> ep_out/ep_in would be set by client and would call
> snd_usbmidi_detect_endpoints() in the other case.
> How about that?
Hmm, I thought the old code detects in/out endpoints if they are NULL.
That is, if out_ep == NULL and in_ep != NULL, out_ep is detected but
in_ep is used as it is.
If this isn't the case, checking in the caller side seems OK.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-30 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 13:49 [PATCH] reenable MIDI for usx2y karsten wiese
2005-03-30 13:54 ` Takashi Iwai [this message]
2005-03-30 15:22 ` Clemens Ladisch
-- strict thread matches above, loose matches on Subject: below --
2005-03-27 12:00 karsten wiese
2005-03-30 13:00 ` 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=s5hzmwlfdd6.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=annabellesgarden@yahoo.de \
--cc=clemens@ladisch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox