All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	tj@kernel.org, linux-next@vger.kernel.org
Subject: Re: Intel sound proke in today;s next
Date: Mon, 26 Jul 2010 22:54:42 +0200	[thread overview]
Message-ID: <4C4DF612.6020404@example.com> (raw)
In-Reply-To: <s5hk4oi9ewg.wl%tiwai@suse.de>

On 26.07.2010 22:17, Takashi Iwai wrote:

>>>> You need to pass the branch. In this case, pass for-next
>>>
>>> I passed topic/hda and rebuilt the kernel and now everything is working.
>>
>> I have just git pulled for-next and saw many files downloaded so I
>> wonder how synced with topic/hda it's working.
>
> It contains other two branches, topic/misc and topic/asoc.
> (Also sometimes missing fix/asoc and fix/misc merges).
>
> topic/asoc branch is specific to ASoC, so very likely irrelevant.
> If any, some changes in the sound core code in topic/misc might
> influence in your case...

Ok, so I'll use for-next then. Thank you again, you taught me a lot.

Regards,

Piotr Hosowicz

-- 
Zatrzymuje się samochód na sejmowym parkingu. Podchodzi do niego 
ochroniarz i mówi:
- Pan tu parkuje?! Tu Sejm ... Ministrowie, politycy, posłowiei ...
- Dzięki, włączę alarm.
NP: Patrick O'Hearn - Magnificent River
NB: 2.6.35-rc6-20100726-1827-sndfix+

  reply	other threads:[~2010-07-26 20:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  6:49 linux-next: Tree for July 23 Stephen Rothwell
2010-07-23 16:08 ` linux-next: Tree for July 23 (fscache) Randy Dunlap
2010-07-23 18:24   ` Intel sound proke in today;s next Piotr Hosowicz
2010-07-23 18:27     ` Piotr Hosowicz
2010-07-24  1:59     ` Stephen Rothwell
2010-07-25 15:27       ` Takashi Iwai
2010-07-25 15:56         ` Piotr Hosowicz
2010-07-26  7:29           ` Takashi Iwai
2010-07-26 16:57             ` Piotr Hosowicz
2010-07-26 17:24               ` Takashi Iwai
2010-07-26 17:33                 ` Piotr Hosowicz
2010-07-26 18:00                   ` Takashi Iwai
2010-07-26 18:30                     ` Piotr Hosowicz
2010-07-26 19:03                       ` Piotr Hosowicz
2010-07-26 20:17                         ` Takashi Iwai
2010-07-26 20:54                           ` Piotr Hosowicz [this message]
2010-07-27  5:41                             ` Takashi Iwai
2010-07-24  9:14   ` [PATCH wq#for-next] fscache: fix build on !CONFIG_SYSCTL Tejun Heo
2010-07-25 22:18     ` Randy Dunlap
2010-07-23 16:41 ` [PATCH -next] compal-laptop: depends on POWER_SUPPLY Randy Dunlap

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=4C4DF612.6020404@example.com \
    --to=piotr@hosowicz.com \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    --cc=tj@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 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.