All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vovan <vovan888@gmail.com>
To: Komal Shah <komal.shah802003@gmail.com>,
	linux-omap-open-source <linux-omap-open-source@linux.omap.com>
Subject: Re: sx1 alsa build failure
Date: Sun, 03 Dec 2006 21:20:50 +0300	[thread overview]
Message-ID: <op.tjzw80b2dbah4f@localhost> (raw)
In-Reply-To: <3a5b1be00612031013v14ca1789ge5c58d125733e675@mail.gmail.com>

03.12.06 в 21:13 Komal Shah в своём письме писал(а):

> Hi Vladimir Ananiev,
>
> Could you please send a patch to fix this build error.?
>
> sound/arm/omap/omap-alsa-sx1.c:32: error: `CN_IDX_SX1SND' undeclared
> here (not in a function)
> sound/arm/omap/omap-alsa-sx1.c:32: error: initializer element is not  
> constant
> sound/arm/omap/omap-alsa-sx1.c:32: error: (near initialization for
> `cn_sx1snd_id.idx')
> sound/arm/omap/omap-alsa-sx1.c:32: error: `CN_VAL_SX1SND' undeclared
> here (not in a function)
> sound/arm/omap/omap-alsa-sx1.c:32: error: initializer element is not  
> constant
> sound/arm/omap/omap-alsa-sx1.c:32: error: (near initialization for
> `cn_sx1snd_id.val')
>
>

Sure, here it is:

diff --git a/include/linux/connector.h b/include/linux/connector.h
index 4c02119..0e2cbf1 100644
--- a/include/linux/connector.h
+++ b/include/linux/connector.h
@@ -36,9 +36,13 @@ #define CN_IDX_CIFS                  0x2
  #define CN_VAL_CIFS                     0x1
  #define CN_W1_IDX                      0x3     /* w1 communication */
  #define CN_W1_VAL                      0x1
+#define CN_IDX_SX1SND          0x4
+#define CN_VAL_SX1SND          0x1
+#define CN_IDX_SX1PM           0x5
+#define CN_VAL_SX1PM           0x1


-#define CN_NETLINK_USERS               4
+#define CN_NETLINK_USERS               6

  /*
   * Maximum connector's message size.


-- 
Vladimir Ananiev

      reply	other threads:[~2006-12-03 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 18:13 sx1 alsa build failure Komal Shah
2006-12-03 18:20 ` Vovan [this message]

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=op.tjzw80b2dbah4f@localhost \
    --to=vovan888@gmail.com \
    --cc=komal.shah802003@gmail.com \
    --cc=linux-omap-open-source@linux.omap.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 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.