Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 4/7] ice1724 - adding GPIO routines for	mask and direction
Date: Wed, 16 Sep 2009 10:10:26 +0200	[thread overview]
Message-ID: <4AB09D72.4070200@ivitera.com> (raw)
In-Reply-To: <s5h4or3z5x5.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Wed, 16 Sep 2009 09:15:56 +0200,
> Pavel Hofman wrote:
>> Takashi Iwai wrote:
>>> At Wed, 16 Sep 2009 00:39:53 +0200,
>>> pavel.hofman@ivitera.com wrote:
>>>> From: pavel <pavel@nahore.(none)>
>>>>
>>>> * get/set routines for GPIO mask and direction
>>>>
>>>> Signed-off-by: Pavel Hofman <pavel.hofman@ivitera.com>
>>> The get_mask callback is still undefined for ice1724...
>> That is weird. I split the original commit using interactive git rebase
>> + edit + add interactive into three new commits - get-mask,
>> pro-rate-locked and all the external-clock. I commited all of them,
>> rechecked git status before continuing with rebase - nothing uncommitted
>> was left, no outstanding changes. But the get_mask commit did not show
>> up in the subsequent interactive rebase list of commits. I was looking
>> for it, I thought I found it in the main gpio-methods commit but
>> overlooked that it is for ice1712.c only.
>>
>> The method and its callback has disappeared from my master after the
>> rebase. Do you have any idea what could have gone wrong?
> 
> No idea...
> But rebasing is a bit dangerous operation, and I often forget to finish 
> the rebase until the last commit, getting incomplete rebase in the
> end.  So, I usually copy the original branch first before rebase
> explicitly, and check the difference from the original branch after
> rebasing.

Thanks for the info, I will do that next time.

>>
>> Yesterday I moved it from ice1712.h to quartet.h. The build succeeded
>> but when loading the new snd-ice1724 module I got dmesg messages about
>> unknown references to ak4113 methods used in the quartet code. That is
>> why I left the include in ice1712.h which works fine.
>>
>> Unfortunately my knowledge of the build/load infrastructure is very
>> limited, I can do just copy/paste in this area :)

Please, how should I change the include to fix the module load?

Thanks a lot,

Pavel.

  reply	other threads:[~2009-09-16  8:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 22:39 [PATCH 1/7] ak4114 - fix errors in output selector bits pavel.hofman
2009-09-15 22:39 ` [PATCH 2/7] ak4620 support, codec regs listed in proc pavel.hofman
2009-09-15 22:39   ` [PATCH 3/7] ak4113 support pavel.hofman
2009-09-15 22:39     ` [PATCH 4/7] ice1724 - adding GPIO routines for mask and direction pavel.hofman
2009-09-15 22:39       ` [PATCH 5/7] ice1724 - pro-rate-locking makes sense only for internal clock mode pavel.hofman
2009-09-15 22:39         ` [PATCH 6/7] Support for multiple external clock types pavel.hofman
2009-09-15 22:39           ` [PATCH 7/7] Infrasonic Quartet support pavel.hofman
2009-09-16  6:07       ` [PATCH 4/7] ice1724 - adding GPIO routines for mask and direction Takashi Iwai
2009-09-16  7:15         ` Pavel Hofman
2009-09-16  7:48           ` Takashi Iwai
2009-09-16  8:10             ` Pavel Hofman [this message]
2009-09-16  8:27               ` Takashi Iwai
2009-09-16 20:15                 ` Pavel Hofman
2009-09-17 16:30                   ` Takashi Iwai
2009-09-16  6:03 ` [PATCH 1/7] ak4114 - fix errors in output selector bits Takashi Iwai
2009-09-16  7:00   ` Pavel Hofman
2009-09-16  7:45     ` Takashi Iwai
2009-09-16  7:48       ` Pavel Hofman
  -- strict thread matches above, loose matches on Subject: below --
2009-09-16 20:25 pavel.hofman
2009-09-16 20:25 ` [PATCH 2/7] ak4620 support, codec regs listed in proc pavel.hofman
2009-09-16 20:25   ` [PATCH 3/7] ak4113 support pavel.hofman
2009-09-16 20:25     ` [PATCH 4/7] ice1724 - adding GPIO routines for mask and direction pavel.hofman

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=4AB09D72.4070200@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --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