public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: scjody@modernduck.com, linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] the overdue removal of RAW1394_REQ_ISO_{LISTEN,SEND}
Date: Sat, 08 Apr 2006 07:53:04 +0200	[thread overview]
Message-ID: <44374FC0.3070507@s5r6.in-berlin.de> (raw)
In-Reply-To: <20060406224706.GD7118@stusta.de>

Adrian Bunk wrote:
> This patch contains the overdue removal of the RAW1394_REQ_ISO_SEND and 
> RAW1394_REQ_ISO_LISTEN request types plus all support code for them.
[...]

I am not familiar with the isochronous part of Linux' 1394 software 
stack, so I can't comment whether there are high-profile applications 
which still did not migrate away from this interface, or did so only 
recently.

However I have a few remarks about this patch:

  1. You are not only removing the two ioctls but also two EXPORTs and
     their implementations, i.e. hpsb_listen_channel() and
     hpsb_make_isopacket().
     1.a  Nobody scheduled to remove these EXPORTs.
     1.b  So far we moved unused ieee1394 EXPORTs into #if/#endif blocks
          and let people reactivate them via kernel config.

  2. If it will be decided to remove or hide the EXPORTs and
     implementations, then the following should go as well:
     2.a  EXPORT and implementation of hpsb_unlisten_channel()
     2.b  struct member hpsb_host.iso_listen_count[]

  3. These should go regardless of the EXPORTs matter:
     struct members file_info.listen_channels, file_info.iso_buffer,
     file_info.iso_buffer_length.

Perhaps there is even *much* more code which becomes superfluous which I 
am unable to identify now.
-- 
Stefan Richter
-=====-=-==- -=-- -=---
http://arcgraph.de/sr/

  parent reply	other threads:[~2006-04-08  5:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 22:47 [RFC: 2.6 patch] the overdue removal of RAW1394_REQ_ISO_{LISTEN,SEND} Adrian Bunk
2006-04-07  0:35 ` Gene Heskett
2006-04-07  0:40   ` Lee Revell
2006-04-07  1:13     ` Gene Heskett
2006-04-07  2:09       ` Gene Heskett
2006-04-07  5:52   ` Denis Vlasenko
2006-04-07  6:15     ` Gene Heskett
2006-04-08  5:53 ` Stefan Richter [this message]
2006-04-08 19:18   ` Dan Dennedy
2006-04-08 19:49     ` Stefan Richter
2006-04-08 19:53       ` Stefan Richter
2006-04-18  9:45         ` Jody McIntyre
2006-04-18 23:59           ` Dan Dennedy
2006-04-09  1:25       ` Dan Dennedy
2006-04-18  9:48       ` Jody McIntyre

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=44374FC0.3070507@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=scjody@modernduck.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox