From: lamikr <lamikr@cc.jyu.fi>
To: Daniel Petrini <d.pensator@gmail.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] Alsa modularisations and support for tsc2101 1/7
Date: Thu, 23 Feb 2006 00:16:17 +0200 [thread overview]
Message-ID: <43FCE2B1.1070901@cc.jyu.fi> (raw)
In-Reply-To: <9268368b0602210414x6b760af1mcdd02b8f7bee18f7@mail.gmail.com>
>
>
>>>+ *
>>>+ * History:
>>>+ *
>>>+ * 2005-07-29 INdT Kernel Team - Alsa driver for omap osk.
>>>Creation of new
>>>+ * file omap-aic23.c
>>>+ *
>>>+ * 2005-12-18 Dirk Behme - Added L/R Channel Interchange fix
>>>as proposed by Ajaya Babu
>>>+ *
>>>+ * 2006-02-07 Daniel Petrini - Codec specific function separated.
>>>File renamed to
>>>+ * omap-alsa.c
>>>+ * 2006-02-10 Mika Laitio - Codec specific function pointers are set
>>>in the codec.
>>>+ * Default samplerate queried from the codec.
>>>+ */
>>>
>>>
>>I am happy to see this big development and cleaned up driver interface,
>>but I think we can trim down this History as I believe GIT is being
>>really used for this purpose. Only thing we need to take care is give
>>better comment at patch submit time :)
>>
>>
>
>Very good suggestion. We will keep in mind to do it from now on.
>
>
Is there somekind of "kernel" policy for this one.
Can we leave the first (2005-07-29) and second one (2005-12-18) from the
history to next patch round or just remove everything?
Mika
next prev parent reply other threads:[~2006-02-22 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 17:44 [PATCH] Alsa modularisations and support for tsc2101 1/7 Daniel Petrini
2006-02-20 22:11 ` Komal Shah
2006-02-21 12:14 ` Daniel Petrini
2006-02-22 22:16 ` lamikr [this message]
2006-02-23 13:15 ` Komal Shah
2006-02-24 13:24 ` Komal Shah
2006-02-26 23:06 ` lamikr
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=43FCE2B1.1070901@cc.jyu.fi \
--to=lamikr@cc.jyu.fi \
--cc=d.pensator@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.