public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc3-mm3: ALSA broken ?
Date: Mon, 30 May 2005 17:21:42 +0200	[thread overview]
Message-ID: <s5hzmucviwp.wl@alsa2.suse.de> (raw)
In-Reply-To: <1117463446l.7266l.0l@werewolf.able.es>

At Mon, 30 May 2005 14:30:46 +0000,
J.A. Magallon wrote:
> 
> The correct question is: how do I generate a patch against a given kernel,
> from the alsa-driver-x.y.z.tar.gz I can download from alsa.org ?
> I thought it was enough to diff -ruN the alsa-kernel dir (minus the Documentation
> folder) vs the /usr/src/linux-xxxxx/sound folder.
> 
> I have seen that there are some scripts in the tarball that install the new
> drivers on a given kernel tree via symlinks, but I would like to get just
> a patch. I think I will have to diff selected directories, or create
> an exclude list... Are there files that are just copied from mainline and do
> not change in ALSA tree, or anything can change under alsa-kernel ?

Basically diff should work for some of subdirectories in alsa-kernel.
Although we've tried to sync the files in sound/ directory with
mainline, better not to diff them.

As an example, I've checked the kernel sync between ALSA and mainline
trees with the script.  Note that sound_core.c etc in sound/ are not
checked.  ~/alsa-kernel-excludes contains the files to ignore like .*,
*.o, CVS, etc.

> Now that I think of it, if you work against Linus tree,
> would it be more correct to diff against 2.6.12-rc5, and then try to apply
> to -rc5-mm1 ? 

Yes.  The alsa-kernel tree is for Linus tree, in principle.

> Whe you do a release, which is your reference, latest stable (2.6.11),
> latest rc or latest git ? 

The released alsa-drivers are for the latest Linus tree.
The patches to stable tree are taken occasionally, so they are not
collected...

> About git, I don't really like the idea of storing a full kernel tree just
> to do 'git update' or the like, and use the 'sound' part.

I understand it - Although git works great, I won't use it with the
analog modem connection at home :)


Takashi


#!/bin/sh
#
# diff-alsa-26 [-R] linux-kernel alsa-kernel
#

reverse=
if [ "$1" = "-R" ]; then
  reverse=1
  shift
fi
if [ -z "$1" -o -z "$2" ]; then
    echo "usage: diff-alsa-26 linux-kernel alsa-kernel"
    exit 1
fi

LINUX=$1
ALSA=$2

diffopts=--exclude-from=$HOME/alsa-kernel-excludes

if [ -n "$reverse" ]; then
  for i in arm core drivers i2c isa parisc pci pcmcia ppc sparc synth usb; do
      diff -rupN $diffopts $ALSA/$i $LINUX/sound/$i | grep -v '^[A-Z]' | sed -es@$ALSA/@linux/sound/@g
  done
  diff -ruN $diffopts $ALSA/include $LINUX/include/sound | grep -v '^[A-Z]' | sed -es@$ALSA/include/@linux/include/sound/@g
  diff -ruN $diffopts $ALSA/Documentation $LINUX/Documentation/sound/alsa | grep -v '^[A-Z]' | sed -es@$ALSA/Documentation/@linux/Documentation/sound/alsa/@g
else
  for i in arm core drivers i2c isa parisc pci pcmcia ppc sparc synth usb; do
      diff -rupN $diffopts $LINUX/sound/$i $ALSA/$i | grep -v '^[A-Z]' | sed -es@$ALSA/@linux/sound/@g
  done
  diff -ruN $diffopts $LINUX/include/sound $ALSA/include | grep -v '^[A-Z]' | sed -es@$ALSA/include/@linux/include/sound/@g
  diff -ruN $diffopts $LINUX/Documentation/sound/alsa $ALSA/Documentation | grep -v '^[A-Z]' | sed -es@$ALSA/Documentation/@linux/Documentation/sound/alsa/@g
fi

exit 0


  reply	other threads:[~2005-05-30 15:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05  5:10 2.6.12-rc3-mm3 Andrew Morton
2005-05-05  7:08 ` 2.6.12-rc3-mm3 Richard A Nelson
2005-05-05 11:55 ` 2.6.12-rc3-mm3 Francois Romieu
2005-05-05 18:00   ` 2.6.12-rc3-mm3 Andrew Morton
2005-05-05 12:39 ` 2.6.12-rc3-mm3 Rafael J. Wysocki
2005-05-05 12:58 ` 2.6.12-rc3-mm3 Rafael J. Wysocki
2005-05-05 22:47   ` 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 Rafael J. Wysocki
2005-05-05 14:57 ` 2.6.12-rc3-mm3 Valdis.Kletnieks
2005-05-05 15:22   ` 2.6.12-rc3-mm3 Adrian Bunk
2005-05-05 15:49     ` 2.6.12-rc3-mm3 Valdis.Kletnieks
2005-05-05 16:44       ` 2.6.12-rc3-mm3 Adrian Bunk
2005-05-05 14:59 ` 2.6.12-rc3-mm3 Borislav Petkov
2005-05-08  0:07 ` 2.6.12-rc3-mm3: ALSA broken ? J.A. Magallon
2005-05-08 23:24   ` J.A. Magallon
2005-05-11 14:23     ` Takashi Iwai
2005-05-12 22:27       ` J.A. Magallon
2005-05-13  9:57         ` Takashi Iwai
2005-05-17 12:02           ` J.A. Magallon
2005-05-17 12:20             ` Takashi Iwai
2005-05-17 22:39               ` J.A. Magallon
2005-05-18 13:39                 ` Takashi Iwai
2005-05-26 23:51                   ` J.A. Magallon
2005-05-27  9:41                     ` Takashi Iwai
2005-05-27 21:18                       ` J.A. Magallon
2005-05-30 13:37                         ` Takashi Iwai
2005-05-30 14:30                           ` J.A. Magallon
2005-05-30 15:21                             ` Takashi Iwai [this message]
2005-05-30 17:58                           ` Takashi Iwai
2005-05-27 14:52                     ` Lee Revell
2005-05-28  0:11                       ` J.A. Magallon
2005-05-30 13:26                         ` Takashi Iwai
     [not found]     ` <20050526001828.0b3959f6.akpm@osdl.org>
2005-05-27  6:54       ` J.A. Magallon

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=s5hzmucviwp.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    /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