On Tue, Nov 5, 2013 at 8:19 PM, Greg Kroah-Hartman
wrote:
> On Tue, Nov 05, 2013 at 01:54:51PM -0600, Felipe Contreras wrote:
>> On Tue, Nov 5, 2013 at 9:16 AM, Greg Kroah-Hartman
>> wrote:
>> > On Tue, Nov 05, 2013 at 08:29:40AM -0600, Felipe Contreras wrote:
>> >> On Tue, Nov 5, 2013 at 6:52 AM
On Tue, Nov 05, 2013 at 01:54:51PM -0600, Felipe Contreras wrote:
> On Tue, Nov 5, 2013 at 9:16 AM, Greg Kroah-Hartman
> wrote:
> > On Tue, Nov 05, 2013 at 08:29:40AM -0600, Felipe Contreras wrote:
> >> On Tue, Nov 5, 2013 at 6:52 AM, Greg Kroah-Hartman
> >> wrote:
> >> > On Tue, Nov 05, 2013 at
Hi Dan,
On 11/05/2013 07:02 PM, Dan Carpenter wrote:
> On Tue, Nov 05, 2013 at 06:01:00PM +0800, Gu Zheng wrote:
>> The lock sequence of dcon_blank_fb(fb_info->lock ---> console_lock) is
>> against
>> with the one of console_callback(console_lock ---> fb_info->lock), it'll
>> lead to a potential
On Mon, Nov 4, 2013 at 7:13 PM, Fabio Estevam wrote:
> On Mon, Nov 4, 2013 at 9:20 PM, Matt Sealey wrote:
>
>> Fabio, Shawn, could you go so far as to bring this up with the i.MX
>> guys responsible for documentation or find the original transmitter IP
>> specs, or find the two pages missing from
MS card can not use auto read/write mode, so it will fail at
initialize and long data transfer. This patch is used to add
support for ms card.
Shall I re-send this patch to add more info?
On 11/06/2013 05:10 AM, Andrew Morton wrote:
On Wed, 30 Oct 2013 14:40:16 +0800 wrote:
unlike mspro card
On Tue, Nov 5, 2013 at 5:35 PM, Fabio Estevam wrote:
> On Tue, Nov 5, 2013 at 9:29 PM, Matt Sealey wrote:
>
>> I know about that one. BTW this isn't in the MX6SDL errata
>> documentation, but it is in the MX6QD errata. If this actually affects
>> the Solo etc. as Russell dictates, isn't the errat
On Tue, Nov 5, 2013 at 9:29 PM, Matt Sealey wrote:
> I know about that one. BTW this isn't in the MX6SDL errata
> documentation, but it is in the MX6QD errata. If this actually affects
> the Solo etc. as Russell dictates, isn't the errata document missing
> some info here?
If you read the code y
On Fri, 19 Jul 2013 09:58:49 +0200
Ricardo Ribalda Delgado wrote:
> The struct vb2_dma_sg_desc has been replaced with the generic sg_table
> to describe the location of the video buffers.
>
> Signed-off-by: Ricardo Ribalda Delgado
Acked-by: Ismael Luceno
<...>
signature.asc
Description: PGP
On Wed, 30 Oct 2013 14:40:16 +0800 wrote:
> unlike mspro card, ms card use normal read/write mode for DMA
> data transfer.
What are the user-visible effects of this bug?
Please always include this information when fixing bugs so that others
can decide whether they (or their customers) need the
- Original Message -
> From: "Martyn Welch"
> Subject: Re: [PATCH 1/3] vme_user: Ensure driver compiles after VME bridges
>
> On 05/11/13 17:53, Aaron Sierra wrote:
> > Martyn,
> > Can you please elaborate on why you feel it is not a fix? For instance,
> > will this type of solution not b
Hello Dulshani Gunawardhana,
The patch 44ee8e801137: "staging: media: Use dev_err() instead of
pr_err()" from Oct 20, 2013, leads to the following
GCC warning:
drivers/staging/media/go7007/go7007-usb.c: In function ‘go7007_usb_probe’:
drivers/staging/media/go7007/go7007-usb.c:1100:13: warning:
On Tue, Nov 5, 2013 at 9:16 AM, Greg Kroah-Hartman
wrote:
> On Tue, Nov 05, 2013 at 08:29:40AM -0600, Felipe Contreras wrote:
>> On Tue, Nov 5, 2013 at 6:52 AM, Greg Kroah-Hartman
>> wrote:
>> > On Tue, Nov 05, 2013 at 02:59:47AM -0600, Felipe Contreras wrote:
>> >> Simple driver to enable contro
On 05/11/13 17:53, Aaron Sierra wrote:
> Martyn,
> Can you please elaborate on why you feel it is not a fix? For instance,
> will this type of solution not be accepted upstream? Is this solution not
> complete enough? Do you feel that it doesn't resolve any issue?
>
> -Aaron
The vme_user driver i
On Tue, Nov 05, 2013 at 05:01:10PM +, Martyn Welch wrote:
> Greg - I don't have any experience dealing with a mixture of 32-bit user space
> and a 64-bit kernel, is this the correct thing to do?
It might be, we need to do something here. I'll review it when I get
through my patch queue, hopef
- Original Message -
> From: "Martyn Welch"
>
> I'm sorry, this is not a fix.
>
> Martyn
Martyn,
Can you please elaborate on why you feel it is not a fix? For instance,
will this type of solution not be accepted upstream? Is this solution not
complete enough? Do you feel that it doesn't
Greg - I don't have any experience dealing with a mixture of 32-bit user space
and a 64-bit kernel, is this the correct thing to do?
On 31/10/13 23:47, Aaron Sierra wrote:
> This patch updates the vme_master and vme_slave structures to use
> types with well defined size and to prevent the compiler
I'm sorry, this is not a fix.
Martyn
On 31/10/13 23:47, Aaron Sierra wrote:
> If VME bridge and vme_user modules are compiled into the kernel, then
> vme_user will attempt to register itself before any VME buses have been
> probed. This results in a kernel panic.
>
> This patch removes the stagi
On Tue, Nov 05, 2013 at 08:29:40AM -0600, Felipe Contreras wrote:
> On Tue, Nov 5, 2013 at 6:52 AM, Greg Kroah-Hartman
> wrote:
> > On Tue, Nov 05, 2013 at 02:59:47AM -0600, Felipe Contreras wrote:
> >> Simple driver to enable control of the fan in ASUS laptops. So far this
> >> has only been test
On Tue, Nov 5, 2013 at 6:52 AM, Greg Kroah-Hartman
wrote:
> On Tue, Nov 05, 2013 at 02:59:47AM -0600, Felipe Contreras wrote:
>> Simple driver to enable control of the fan in ASUS laptops. So far this
>> has only been tested in ASUS Zenbook Prime UX31A, but according to some
>> online reference [1
Simple driver to enable control of the fan in ASUS laptops. So far this
has only been tested in ASUS Zenbook Prime UX31A, but according to some
online reference [1], it should work in other models as well.
The implementation is very straight-forward, the only caveat is that the
fan speed needs to
On Tue, Nov 05, 2013 at 02:59:47AM -0600, Felipe Contreras wrote:
> Simple driver to enable control of the fan in ASUS laptops. So far this
> has only been tested in ASUS Zenbook Prime UX31A, but according to some
> online reference [1], it should work in other models as well.
>
> The implementati
On Tue, Nov 05, 2013 at 06:01:00PM +0800, Gu Zheng wrote:
> The lock sequence of dcon_blank_fb(fb_info->lock ---> console_lock) is against
> with the one of console_callback(console_lock ---> fb_info->lock), it'll
> lead to a potential dead lock, so reorder the lock sequence of dcon_blank_fb
> to a
My Very good friend
Do you know that we can make a difference by helping the less privilege and the
poor.
Psalm 41:1, Blessed is he that considereth the poor,the lord will deliver him
in time of trouble.
I want you to use my money to help the poor as i am already suffering from a
very serious i
The lock sequence of dcon_blank_fb(fb_info->lock ---> console_lock) is against
with the one of console_callback(console_lock ---> fb_info->lock), it'll
lead to a potential dead lock, so reorder the lock sequence of dcon_blank_fb
to avoid the potential dead lock.
Signed-off-by: Gu Zheng
---
drive
Simple driver to enable control of the fan in ASUS laptops. So far this
has only been tested in ASUS Zenbook Prime UX31A, but according to some
online reference [1], it should work in other models as well.
The implementation is very straight-forward, the only caveat is that the
fan speed needs to
25 matches
Mail list logo
