>From: Menon, Nishanth
>
>Ramirez Luna, Omar had written, on 01/11/2010 12:46 PM, the following:
>>> From: Menon, Nishanth
>>>
>>> Ramirez Luna, Omar had written, on 01/11/2010 11:50 AM, the following:
>>>> This is the official 0.1 dspbridge version.
>>>>
>>>> CC: Felipe Contreras <felipe.contreras@xxxxxxxxx>
>>>> CC: Hiroshi Doyu <Hiroshi.DOYU@xxxxxxxxx>
>>>> CC: Ameya Palande <ameya.palande@xxxxxxxxx>
>>>> CC: Nishant Menon <nm@xxxxxx>
>>>>
>>>> Signed-off-by: Omar Ramirez Luna <omar.ramirez@xxxxxx>
>>>> ---
>>>> drivers/dsp/bridge/rmgr/drv_interface.c | 2 ++
>>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/drivers/dsp/bridge/rmgr/drv_interface.c b/drivers/dsp/bridge/rmgr/drv_interface.c
>>>> index c853854..efce35d 100644
>>>> --- a/drivers/dsp/bridge/rmgr/drv_interface.c
>>>> +++ b/drivers/dsp/bridge/rmgr/drv_interface.c
>>>> @@ -101,6 +101,7 @@
>>>> #define BRIDGE_NAME "C6410"
>>>> /* ----------------------------------- Globals */
>>>> #define DRIVER_NAME "DspBridge"
>>>> +#define DSPBRIDGE_VERSION "0.1"
>>>> s32 dsp_debug;
>>>>
>>>> struct platform_device *omap_dspbridge_dev;
>>>> @@ -177,6 +178,7 @@ MODULE_PARM_DESC(tc_wordswapon, "TC Word Swap Option. default = 0");
>>>>
>>>> MODULE_AUTHOR("Texas Instruments");
>>>> MODULE_LICENSE("GPL");
>>>> +MODULE_VERSION(DSPBRIDGE_VERSION);
>>>>
>>>> static char *driver_name = DRIVER_NAME;
>>>>
>>> is the IOCTL patch before or after the 0.1?
>>
>> IOCTL patch is after 0.1
>>
>> I'll be resending v2 of IOCTL patch but should be applied after this patch.
>sounds reasonable. I wonder what happened to
>http://marc.info/?l=linux-omap&m=125729526105560&w=2
To the change: currently is on hold given the amount of changes but
scheduled for this month (hopefully ;))
To the request: I have a patch queue to be applied after 0.1 patch and v2 of
ioctl, the patches have already been sent to this mailing list but changes
didn't fit prior to 0.1 alignment
Regards,
omar
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
