All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Hugo Villeneuve <hugo@hugovil.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	alsa-devel@alsa-project.org, Mark Brown <broonie@sirena.org.uk>
Subject: Re: [PATCH 4/4] ALSA: ASoC: Davinci: Fixed missing McBSP pinmux for SFFSDR
Date: Tue, 10 Mar 2009 10:11:22 -0700	[thread overview]
Message-ID: <87y6vds3ph.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090310130734.c877b1f6.hugo@hugovil.com> (Hugo Villeneuve's message of "Tue\, 10 Mar 2009 13\:07\:34 -0400")

Hugo Villeneuve <hugo@hugovil.com> writes:

> On Tue, 10 Mar 2009 09:20:15 -0700
> Kevin Hilman <khilman@deeprootsystems.com> wrote:
>
>> Hugo Villeneuve <hugo@hugovil.com> writes:
>> 
>> > On Tue, 10 Mar 2009 08:55:06 -0700
>> > Kevin Hilman <khilman@deeprootsystems.com> wrote:
>> >
>> >> Hugo Villeneuve <hugo@hugovil.com> writes:
>> >> 
>> >> > On Tue, 10 Mar 2009 15:16:32 +0000
>> >> > Mark Brown <broonie@sirena.org.uk> wrote:
>> >> >
>> >> >> On Tue, Mar 10, 2009 at 10:03:41AM -0400, Hugo Villeneuve wrote:
>> >> >> 
>> >> >> > I based those patches on the latest linux-davinci git tree,
>> >> >> > which has the function.
>> >> >> 
>> >> >> Do not submit patches for mainline which are not based on
>> >> >> mainline trees.  Code which relies on out of tree changes needs
>> >> >> to wait for those out of tree changes to be merged before
>> >> >> submitting to mainline.
>> >> >
>> >> > I did not know that these changes were not in mainline yet. I was
>> >> > told that all davinci ASoC code changes were to be submitted only
>> >> > to ALSA, and then were imported back into the davinci git tree.
>> >> > Apparently this is not quite like that anymore.
>> >> >
>> >> > Kevin, what is the new rule to submit davinci ASoC patches?
>> >> >
>> >> 
>> >> The DaVinci ASoC code is indeed in mainline, but not all of the
>> >> DaVinci core (in this case the pin mux) is yet in mainline.  I
>> >> will be pushing it during the next merge window.
>> >
>> > That doesn't really answer my question.
>> >
>> > I can see that David Brownell pushed a patch to the davinci tree
>> > directly modifying sound/soc/davinci/davinci-evm.c which IS in
>> > mainline. Does this means that as of now all ASoC patches should be
>> > sent first to the Davinci list, and then you will push those to the
>> > mainline kernel?
>> >
>> 
>> No ASoc patches should be generated against an ASoC tree and submitted
>> to alsa-devel, and CC davinci list.
>> 
>> This means that the until the DaVinci core is in mainline, DaVinci
>> git will have slightly different looking ASoC drivers, but those
>> changes will be minimal.
>
> Ok, so the patch affecting sound/soc/davinci/davinci-evm.c SHOULD have
> been submitted to ALSA first.

Yes, but it should've been a patch against an ASoC tree, not against
DaVinci git which may contain things not (yet) in the ASoC tree.

> It is not easy following you guys. You say something and then do the
> opposite.

Heh, sorry.

Do as I do, not as I say.  ;)

Kevin

  reply	other threads:[~2009-03-10 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  3:32 Fix audio for Lyrtech SFFSDR board Hugo Villeneuve
2009-03-10  3:32 ` [PATCH 1/4] ALSA: ASoC: Davinci: Fix SFFSDR FPGA module codec FS bug Hugo Villeneuve
2009-03-10 15:53   ` Mark Brown
2009-03-10  3:32 ` [PATCH 2/4] ALSA: ASoC: Davinci: Replaced DAI format RIGHT_J by DSP_B for SFFSDR Hugo Villeneuve
     [not found] ` <1236655929-31688-1-git-send-email-hugo-rg2e/+w5TaNBDgjK7y7TUQ@public.gmane.org>
2009-03-10  3:32   ` [PATCH 3/4] ALSA: ASoC: Davinci: Updated sffsdr_hw_params() function to new format Hugo Villeneuve
2009-03-10  3:32   ` [PATCH 4/4] ALSA: ASoC: Davinci: Fixed missing McBSP pinmux for SFFSDR Hugo Villeneuve
     [not found]     ` <20090310102921.GA12297@sirena.org.uk>
2009-03-10 14:03       ` Hugo Villeneuve
2009-03-10 15:16         ` Mark Brown
2009-03-10 15:42           ` Hugo Villeneuve
2009-03-10 15:55             ` Kevin Hilman
2009-03-10 16:02               ` Mark Brown
2009-03-10 16:08                 ` Kevin Hilman
2009-03-10 16:04               ` Hugo Villeneuve
2009-03-10 16:20                 ` Kevin Hilman
2009-03-10 17:07                   ` Hugo Villeneuve
2009-03-10 17:11                     ` Kevin Hilman [this message]
2009-03-10 18:10                       ` David Brownell
2009-03-10 19:42                     ` Mark Brown

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=87y6vds3ph.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=hugo@hugovil.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.