Re: [dm-devel] dm-writeboost testing

2013-10-03 Thread Akira Hayakawa
Hi, Mikulas, I am sorry to say that I don't have such machines to reproduce the problem. But agree with that I am dealing with workqueue subsystem in a little bit weird way. I should clean them up. For example, free_cache() routine below is a deconstructor of the cache metadata including all the

[PATCH] omapdce : clear transaction if engine_open rpsend fails

2013-10-03 Thread Varun B Patil
The next time the same transaction structure is used, when the req_id's wrap around, it should be completely cleared (memset) to avoid corruption. Signed-off-by: Varun B Patil --- drivers/staging/omapdce/dce.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/om

[PATCH] omapdce : fix bug in ioctl_codec_process

2013-10-03 Thread Varun B Patil
Do not send already free'd pointer to rpabort when rpsend fails. Signed-off-by: Varun B Patil --- drivers/staging/omapdce/dce.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/staging/omapdce/dce.c b/drivers/staging/omapdce/dce.c index 2a7cbef..1d9b75c 100644 --

Re: [dm-devel] Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]

2013-10-03 Thread Dave Chinner
On Wed, Oct 02, 2013 at 08:01:45PM -0400, Mikulas Patocka wrote: > > > On Tue, 1 Oct 2013, Joe Thornber wrote: > > > > Alternatively, delaying them will stall the filesystem because it's > > > waiting for said REQ_FUA IO to complete. For example, journal writes > > > in XFS are extremely IO late

[PATCH] omapdce : fix transaction corruption due to wrong request id

2013-10-03 Thread Varun B Patil
ioctl_codec_process was calling get_paddr() with a wrong pointer as argument which resulted in wrong req_id being used to get the transaction inside get_paddr(). Signed-off-by: Varun B Patil --- drivers/staging/omapdce/dce.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dri

Re: lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Theodore Ts'o
On Thu, Oct 03, 2013 at 11:06:58PM +, Dilger, Andreas wrote: > > The Lustre cfs_get_random_bytes() incorporates (via cfs_rand()) a seed > which > also hashes in the addresses from any network interfaces that are > configured. > Conversely, cfs_rand() also is seeded at startup from get_random_b

Re: lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Dilger, Andreas
On 2013/10/03 1:34 PM, "Theodore Ts'o" wrote: >On Thu, Oct 03, 2013 at 10:26:21AM -0700, Greg KH wrote: >> > Does this sound reasonable? >> >> Sounds reasonable to me, care to send a patch to do so? >> > >I can do that, but I was waiting for Andras, Peng or Nikita to let me >now if there was som

Re: Drivers: scsi: FLUSH timeout

2013-10-03 Thread Eric Seppanen
On Thu, Oct 3, 2013 at 5:09 AM, Nicholas A. Bellinger wrote: > > On Wed, 2013-10-02 at 18:29 +, KY Srinivasan wrote: > > Ideally, I want this to be adjustable like the way we can change the I/O > > timeout. > > Since that has been attempted earlier and rejected (not clear what the > > reason

Re: [PATCH v2 1/3] imx-drm: Add mx6 hdmi transmitter support

2013-10-03 Thread Greg KH
On Thu, Oct 03, 2013 at 03:51:25PM -0300, Fabio Estevam wrote: > This is based on the initial work done by Sascha Hauer and Tony Prisk. > > Tested on imx6q-wandboard and imx6q-sabresd boards. Why is _any_ new work going on here instead of working to get this code out of staging? I really don't w

Re: [PATCH 1/2] staging: octeon-ethernet: don't assume that CPU 0 is special

2013-10-03 Thread Greg Kroah-Hartman
On Sat, Sep 28, 2013 at 10:50:33PM +0300, Aaro Koskinen wrote: > Currently the driver assumes that CPU 0 is handling all the hard IRQs. > This is wrong in Linux SMP systems where user is allowed to assign to > hardware IRQs to any CPU. The driver will stop working if user sets > smp_affinity so tha

Re: [PATCH v2 1/3] imx-drm: Add mx6 hdmi transmitter support

2013-10-03 Thread Dan Carpenter
On Thu, Oct 03, 2013 at 03:51:25PM -0300, Fabio Estevam wrote: > This is based on the initial work done by Sascha Hauer and Tony Prisk. > > Tested on imx6q-wandboard and imx6q-sabresd boards. > > Signed-off-by: Fabio Estevam > --- > Changes since v1: > - Rebased against 3.12-rc3 and fixed header

looking for loan

2013-10-03 Thread Aijaz Lending
Do you have a firm or company that need loan to start up a business or need,personal loan, Debt consolidation? For more information,Contact us now for a guarantee loan with low interest rate. We will provide you with loan to meet your needs. For more information contact us with the following inf

looking for loan

2013-10-03 Thread Aijaz Lending
Do you have a firm or company that need loan to start up a business or need,personal loan, Debt consolidation? For more information,Contact us now for a guarantee loan with low interest rate. We will provide you with loan to meet your needs. For more information contact us with the following inf

Re: [PATCH 1/3] imx-drm: Add mx6 hdmi transmitter support

2013-10-03 Thread Dan Carpenter
On Thu, Oct 03, 2013 at 01:40:44PM -0300, Fabio Estevam wrote: > On Thu, Oct 3, 2013 at 1:24 PM, Robert Nelson wrote: > > > Just started testing with v3.12-rc3 + > > e6e7fb1ffc875adf2dd36d4a135b8d7addda0aea (top of torvalds tree.) > > > > This needs to be: > > #include "ipu-v3/imx-ipu-v3.h" > >

Re: lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Theodore Ts'o
On Thu, Oct 03, 2013 at 10:26:21AM -0700, Greg KH wrote: > > Does this sound reasonable? > > Sounds reasonable to me, care to send a patch to do so? > I can do that, but I was waiting for Andras, Peng or Nikita to let me now if there was something I was missing or not. I'm pretty sure it's some

[PATCH v2 2/3] ARM: dts: imx6qdl-wandboard: Add HDMI support

2013-10-03 Thread Fabio Estevam
Signed-off-by: Fabio Estevam --- Changes since v1: - None arch/arm/boot/dts/imx6dl.dtsi| 4 arch/arm/boot/dts/imx6q.dtsi | 4 arch/arm/boot/dts/imx6qdl-wandboard.dtsi | 13 + arch/arm/boot/dts/imx6qdl.dtsi | 10 ++ 4 files changed

[PATCH v2 3/3] ARM: dts: imx6qdl-sabresd: Add HDMI support

2013-10-03 Thread Fabio Estevam
Signed-off-by: Fabio Estevam --- Changes since v1: - Put the dt entries in alphabetical order arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi index 39eafc2..4

RE: [PATCH] staging: dwc2: Make dwc2_hw_params.host_channels large enough

2013-10-03 Thread Paul Zimmerman
> From: Matthijs Kooijman [mailto:matth...@stdin.nl] > Sent: Thursday, October 03, 2013 12:35 AM > > > By the way, it looks like 'num_dev_ep' would have the same problem, > > I don't think so, since the hardware doesn't do the off-by-one trick > there (presumably because having 0 endpoints make s

Re: lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Greg KH
On Thu, Oct 03, 2013 at 12:39:08PM -0400, Theodore Ts'o wrote: > I've been auditing uses of get_random_bytes() since there are places > where get_random_bytes() is getting used where something weaker, such > as prandom_u32() is quite sufficient. Basically, if kernel code just > needs a random numb

lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Theodore Ts'o
I've been auditing uses of get_random_bytes() since there are places where get_random_bytes() is getting used where something weaker, such as prandom_u32() is quite sufficient. Basically, if kernel code just needs a random number which does not have any cryptographic requirements (such as in ext[2

Re: [PATCH 1/3] imx-drm: Add mx6 hdmi transmitter support

2013-10-03 Thread Fabio Estevam
On Thu, Oct 3, 2013 at 1:24 PM, Robert Nelson wrote: > Just started testing with v3.12-rc3 + > e6e7fb1ffc875adf2dd36d4a135b8d7addda0aea (top of torvalds tree.) > > This needs to be: > #include "ipu-v3/imx-ipu-v3.h" Thanks for testing, Robert. I used linux-next 20130927 to test these patches, an

Re: [PATCH 1/3] imx-drm: Add mx6 hdmi transmitter support

2013-10-03 Thread Robert Nelson
On Wed, Oct 2, 2013 at 5:45 PM, Fabio Estevam wrote: > This is based on the initial work done by Sascha Hauer and Tony Prisk. > > Tested on a mx6q wandboard and on a mx6qsabresd. > > Signed-off-by: Fabio Estevam > --- > This was tested against linux-next 20130927. > > drivers/staging/imx-drm/Kco

RE: Drivers: scsi: FLUSH timeout

2013-10-03 Thread KY Srinivasan
> -Original Message- > From: Nicholas A. Bellinger [mailto:n...@linux-iscsi.org] > Sent: Thursday, October 03, 2013 5:09 AM > To: KY Srinivasan > Cc: Geert Uytterhoeven; Mike Christie; Jack Wang; Greg KH; linux- > ker...@vger.kernel.org; de...@linuxdriverproject.org; oher...@suse.com; > j

Re: Drivers: scsi: FLUSH timeout

2013-10-03 Thread James Bottomley
On Wed, 2013-10-02 at 18:29 +, KY Srinivasan wrote: > > > -Original Message- > > From: geert.uytterhoe...@gmail.com [mailto:geert.uytterhoe...@gmail.com] > > On Behalf Of Geert Uytterhoeven > > Sent: Wednesday, September 25, 2013 1:40 AM > > To: KY Srinivasan > > Cc: Mike Christie; Jac

Re: [dm-devel] dm-writeboost testing

2013-10-03 Thread Akira Hayakawa
Hi, Mikulas, Thank you for reporting. I am really happy to see this report. First, I respond to the performance problem. I will make time later for investigating the rest and answer. Some deadlock issues are difficult to solve in short time. > I tested dm-writeboost with disk as backing device

Re: Drivers: scsi: FLUSH timeout

2013-10-03 Thread Nicholas A. Bellinger
On Wed, 2013-10-02 at 18:29 +, KY Srinivasan wrote: > > > -Original Message- > > From: geert.uytterhoe...@gmail.com [mailto:geert.uytterhoe...@gmail.com] > > On Behalf Of Geert Uytterhoeven > > Sent: Wednesday, September 25, 2013 1:40 AM > > To: KY Srinivasan > > Cc: Mike Christie; Jac

notificación de e-mail

2013-10-03 Thread Web de administración de
Web de administración de notificación de e-mail Este mensaje es de nuestro centro de mensajes de administración para toda nuestra cuenta de correo electrónico owners.We está eliminando el acceso a todos nuestros clientes de correo web. Su correo electrónico cuenta se actualizará a una interfaz d

Re: [PATCH v4 1/2] staging: dgap: tty.c: adds error handing in tty driver allocations

2013-10-03 Thread Lidza Louina
On Thu, Oct 3, 2013 at 1:23 AM, Greg KH wrote: > On Tue, Oct 01, 2013 at 12:54:20PM -0400, Lidza Louina wrote: >> + return 0; >> + >> +err_unregister_serial: >> +tty_unregister_driver(brd->SerialDriver); >> +err_free_print_ttys: >> +kfree(brd->PrintDriver->ttys); >> +err_put_tt

Re: [PATCH 0/6] OMAP4 ISS driver

2013-10-03 Thread Laurent Pinchart
Hi Hans, On Thursday 03 October 2013 09:00:07 Hans Verkuil wrote: > On 10/03/2013 01:55 AM, Laurent Pinchart wrote: > > Hello, > > > > The OMAP4 ISS driver has lived out of tree for more than two years now. > > This situation is both sad and resource-wasting, as the driver has been > > used (and

[PATCH] staging: speakup: str initialization replaced with NULL where it was initialized with int

2013-10-03 Thread Shalin Mehta
Fixed warnings in all of three files where the string was initilized with an integer instead of NULL Signed-off-by: Shalin Mehta --- drivers/staging/speakup/main.c | 2 +- drivers/staging/speakup/speakup_audptr.c | 2 +- drivers/staging/speakup/varhandlers.c| 2 +- 3 files changed

[PATCH] staging: dwc2: Make dwc2_hw_params.host_channels large enough

2013-10-03 Thread Matthijs Kooijman
The hardware offers a 4-bit register containing the number of host channels. However, the values of these register mean 1-16 host channels, not 0-15. Since the dwc2_hw_params struct stores the actual number of host channels supported instead of the raw register value, it should be 5 bits wide inste

Re: [PATCH] staging: dwc2: Make dwc2_hw_params.host_channels large enough

2013-10-03 Thread Matthijs Kooijman
Hi Paul, > By the way, it looks like 'num_dev_ep' would have the same problem, I don't think so, since the hardware doesn't do the off-by-one trick there (presumably because having 0 endpoints make sense, but 0 host channels doesn't): hw->num_dev_ep = (hwcfg2 & GHWCFG2_NUM_DEV_EP_MASK) >>

Re: [PATCH 0/6] OMAP4 ISS driver

2013-10-03 Thread Hans Verkuil
Hi Laurent, On 10/03/2013 01:55 AM, Laurent Pinchart wrote: > Hello, > > The OMAP4 ISS driver has lived out of tree for more than two years now. This > situation is both sad and resource-wasting, as the driver has been used (and > thus) hacked since then with nowhere to send patches to. Time has