Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Muizelaar <muizelaar@rogers.com>
To: alsa-devel@lists.sourceforge.net
Cc: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] move a bit more old stuff into alsa-driver
Date: Sat, 24 May 2003 18:46:13 -0400	[thread overview]
Message-ID: <3ECFF635.4080405@rogers.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 127 bytes --]

The attached patches move snd_info_entry_inode_operations out of 
alsa-kernel/core/info.c into alsa-driver/acore/info.c

-Jeff

[-- Attachment #2: info-cleanup-driver.diff --]
[-- Type: text/plain, Size: 588 bytes --]

Index: acore/info.c
===================================================================
RCS file: /cvsroot/alsa/alsa-driver/acore/info.c,v
retrieving revision 1.3
diff -u -r1.3 info.c
--- acore/info.c	14 May 2003 15:31:48 -0000	1.3
+++ acore/info.c	24 May 2003 22:40:47 -0000
@@ -88,6 +88,12 @@
 		proc_unregister(parent, de->low_ino);
 	}
 }
+
+static struct inode_operations snd_info_entry_inode_operations =
+{
+	        &snd_info_entry_operations,     /* default sound info directory file-ops */
+};
+
 #endif /* LINUX_VERSION_CODE < 2.4.0 */
 
 #include "../alsa-kernel/core/info.c"

[-- Attachment #3: info-cleanup-kernel.diff --]
[-- Type: text/plain, Size: 622 bytes --]

Index: core/info.c
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/core/info.c,v
retrieving revision 1.36
diff -u -r1.36 info.c
--- core/info.c	14 May 2003 15:30:58 -0000	1.36
+++ core/info.c	24 May 2003 22:42:09 -0000
@@ -508,13 +508,6 @@
 	.release =	snd_info_entry_release,
 };
 
-#ifdef LINUX_2_2
-static struct inode_operations snd_info_entry_inode_operations =
-{
-	&snd_info_entry_operations,	/* default sound info directory file-ops */
-};
-#endif	/* LINUX_2_2 */
-
 /**
  * snd_create_proc_entry - create a procfs entry
  * @name: the name of the proc file

                 reply	other threads:[~2003-05-24 22:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3ECFF635.4080405@rogers.com \
    --to=muizelaar@rogers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox