From: Markus Elfring
Date: Fri, 17 Feb 2017 20:00:34 +0100
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kcalloc".
This issue was detected by using the Coccinelle
From: Markus Elfring
Date: Fri, 17 Feb 2017 21:34:27 +0100
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected functions.
Signed-off-by: Markus Elfring
---
On Sat, Feb 18, 2017 at 02:10:43PM -0600, Alan Tull wrote:
> On Sat, Feb 18, 2017 at 6:45 AM, Nadathur, Sundar
> wrote:
>
> > Hi all,
> >Interesting discussion. The discussion so far has brought out many
> > concerns such as OS independence. There is an existing
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:48:59 +0100
Add a missing character in this description and adjust
the comment formatting.
Signed-off-by: Markus Elfring
---
drivers/infiniband/hw/mlx4/mad.c | 6 --
1 file
On Sat, Feb 18, 2017 at 02:10:43PM -0600, Alan Tull wrote:
> On Sat, Feb 18, 2017 at 6:45 AM, Nadathur, Sundar
> wrote:
>
> > Hi all,
> >Interesting discussion. The discussion so far has brought out many
> > concerns such as OS independence. There is an existing format, well-known
> > to
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:48:59 +0100
Add a missing character in this description and adjust
the comment formatting.
Signed-off-by: Markus Elfring
---
drivers/infiniband/hw/mlx4/mad.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:20:43 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:20:43 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
On Sun, 2017-02-19 at 01:50 +0530, simran singhal wrote:
> Simplify function returns by merging assignment and return into
> one command line.
> Found with Coccinelle
> @@
> local idexpression ret;
> expression e;
> @@
>
> -ret =
> +return
> e;
> -return ret;
[]
> diff --git
On Sun, 2017-02-19 at 01:50 +0530, simran singhal wrote:
> Simplify function returns by merging assignment and return into
> one command line.
> Found with Coccinelle
> @@
> local idexpression ret;
> expression e;
> @@
>
> -ret =
> +return
> e;
> -return ret;
[]
> diff --git
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:15:02 +0100
Replace the specification of a data type by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:15:02 +0100
Replace the specification of a data type by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:05:38 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Fri, 17 Feb 2017 20:05:38 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
From: Markus Elfring
Date: Sat, 18 Feb 2017 21:34:32 +0100
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (29):
Use kcalloc() in mlx4_ib_alloc_pv_bufs()
Improve another size determination in
From: Markus Elfring
Date: Sat, 18 Feb 2017 21:34:32 +0100
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (29):
Use kcalloc() in mlx4_ib_alloc_pv_bufs()
Improve another size determination in mlx4_ib_alloc_pv_bufs()
Improve another size
On Sun, 19 Feb 2017, simran singhal wrote:
> Simplify function returns by merging assignment and return into
> one command line.
> Found with Coccinelle
> @@
> local idexpression ret;
> expression e;
> @@
>
> -ret =
> +return
> e;
> -return ret;
>
> Signed-off-by: simran singhal
On Sun, 19 Feb 2017, simran singhal wrote:
> Simplify function returns by merging assignment and return into
> one command line.
> Found with Coccinelle
> @@
> local idexpression ret;
> expression e;
> @@
>
> -ret =
> +return
> e;
> -return ret;
>
> Signed-off-by: simran singhal
> ---
>
Hi,
Please don't apply this patch and instead apply the switchtec driver as
we submitted in v2. As per the discussion in [1], not using the cdev's
kobj parent results in incorrect reference counting and a possible use
of the cdev after its containing structure is freed.
I've also done a quick
Hi,
Please don't apply this patch and instead apply the switchtec driver as
we submitted in v2. As per the discussion in [1], not using the cdev's
kobj parent results in incorrect reference counting and a possible use
of the cdev after its containing structure is freed.
I've also done a quick
Simplify function returns by merging assignment and return into
one command line.
Found with Coccinelle
@@
local idexpression ret;
expression e;
@@
-ret =
+return
e;
-return ret;
Signed-off-by: simran singhal
---
drivers/staging/vt6655/card.c | 2 +-
1 file
Simplify function returns by merging assignment and return into
one command line.
Found with Coccinelle
@@
local idexpression ret;
expression e;
@@
-ret =
+return
e;
-return ret;
Signed-off-by: simran singhal
---
drivers/staging/vt6655/card.c | 2 +-
1 file changed, 1 insertion(+), 1
commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot")
was intended to fix the case where a board uses an AXP806 in slave mode,
but the boot loader leaves it in master mode for lack of AXP806 support.
But now the driver breaks on boards where the PMIC is operating in master
commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot")
was intended to fix the case where a board uses an AXP806 in slave mode,
but the boot loader leaves it in master mode for lack of AXP806 support.
But now the driver breaks on boards where the PMIC is operating in master
On Sat, Feb 18, 2017 at 6:45 AM, Nadathur, Sundar
wrote:
> Hi all,
>Interesting discussion. The discussion so far has brought out many
> concerns such as OS independence. There is an existing format, well-known to
> developers, with widespread support, and which
On Sat, Feb 18, 2017 at 6:45 AM, Nadathur, Sundar
wrote:
> Hi all,
>Interesting discussion. The discussion so far has brought out many
> concerns such as OS independence. There is an existing format, well-known to
> developers, with widespread support, and which is quite extensible:
>
commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot")
was intended to fix the case where a board uses an AXP806 in slave mode,
but the boot loader leaves it in master mode for lack of AXP806 support.
But now the driver breaks on boards where the PMIC is operating in master
commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot")
was intended to fix the case where a board uses an AXP806 in slave mode,
but the boot loader leaves it in master mode for lack of AXP806 support.
But now the driver breaks on boards where the PMIC is operating in master
On Sat, 18 Feb 2017, Joe Perches wrote:
> On Sat, 2017-02-18 at 20:12 +0100, Julia Lawall wrote:
> > On Sun, 19 Feb 2017, simran singhal wrote:
> > > Extra parentheses were causing checkpatch issues
> > > and were removed.
> []
> > > diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > >
On Sat, 18 Feb 2017, Joe Perches wrote:
> On Sat, 2017-02-18 at 20:12 +0100, Julia Lawall wrote:
> > On Sun, 19 Feb 2017, simran singhal wrote:
> > > Extra parentheses were causing checkpatch issues
> > > and were removed.
> []
> > > diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > >
The AXP806 (and very similar AXP808) PMICs can be wired to either master
mode or slave mode on a board-by-board basis. A register on the PMIC needs
to be set accordingly for the PMIC to respond to other register accesses.
The "xpowers,master-mode" property introduced in this patch series lets a
The AXP806 (and very similar AXP808) PMICs can be wired to either master
mode or slave mode on a board-by-board basis. A register on the PMIC needs
to be set accordingly for the PMIC to respond to other register accesses.
The "xpowers,master-mode" property introduced in this patch series lets a
On 17/02/17 16:03, Fabrice Gasnier wrote:
> Document Industrial I/O GPIO trigger support.
>
> Signed-off-by: Fabrice Gasnier
Whilst I think this needs redoing for the interrupt trigger driver,
please be aware that bindings must be OS agnostic i.e. you can't
name things
On 17/02/17 16:03, Fabrice Gasnier wrote:
> Document Industrial I/O GPIO trigger support.
>
> Signed-off-by: Fabrice Gasnier
Whilst I think this needs redoing for the interrupt trigger driver,
please be aware that bindings must be OS agnostic i.e. you can't
name things after linux specific
On Sat, 2017-02-18 at 20:12 +0100, Julia Lawall wrote:
> On Sun, 19 Feb 2017, simran singhal wrote:
> > Extra parentheses were causing checkpatch issues
> > and were removed.
[]
> > diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > b/drivers/staging/rtl8192e/rtl819x_HTProc.c
[]
> > @@
On Sat, 2017-02-18 at 20:12 +0100, Julia Lawall wrote:
> On Sun, 19 Feb 2017, simran singhal wrote:
> > Extra parentheses were causing checkpatch issues
> > and were removed.
[]
> > diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > b/drivers/staging/rtl8192e/rtl819x_HTProc.c
[]
> > @@
> Am 18.02.2017 um 19:08 schrieb Pavel Machek :
>
>>> And I agree that kernel should _not_ attempt rescaling itself, as it
>>> would lose precision.
>>
>> With an almost 1:1 mapping you won't loose precision.
>
> How do you propose to do that?
something like
xinput --set-prop
> Am 18.02.2017 um 19:08 schrieb Pavel Machek :
>
>>> And I agree that kernel should _not_ attempt rescaling itself, as it
>>> would lose precision.
>>
>> With an almost 1:1 mapping you won't loose precision.
>
> How do you propose to do that?
something like
xinput --set-prop --type=float
On 17/02/17 16:16, Lars-Peter Clausen wrote:
> On 02/17/2017 05:03 PM, Fabrice Gasnier wrote:
>> GPIOs can be used to generate triggers for any IIO device.
>> Introduce generic GPIO trigger driver. It offers some options
>> to tune polarity (e.g. rising/falling edge), and label so trigger
>> name
On 17/02/17 16:16, Lars-Peter Clausen wrote:
> On 02/17/2017 05:03 PM, Fabrice Gasnier wrote:
>> GPIOs can be used to generate triggers for any IIO device.
>> Introduce generic GPIO trigger driver. It offers some options
>> to tune polarity (e.g. rising/falling edge), and label so trigger
>> name
On Sat, 2017-02-18 at 21:32 +0530, Arushi Singhal wrote:
> Unnecessary parentheses as reported by checkpatch.pl
[]
> diff --git a/drivers/staging/ks7010/ks_hostif.c
> b/drivers/staging/ks7010/ks_hostif.c
[]
> @@ -121,19 +121,19 @@ int get_current_ap(struct ks_wlan_private *priv, struct
>
On 17/02/17 16:23, Daniel Baluta wrote:
> On Fri, Feb 17, 2017 at 6:03 PM, Fabrice Gasnier
> wrote:
>> Hi,
>>
>> I send this as an RFC, as I'm digging to try to get as generic
>> as possible GPIO based trigger support, as discussed earlier in
>> other patchset "Add EXTI
On Sat, 2017-02-18 at 21:32 +0530, Arushi Singhal wrote:
> Unnecessary parentheses as reported by checkpatch.pl
[]
> diff --git a/drivers/staging/ks7010/ks_hostif.c
> b/drivers/staging/ks7010/ks_hostif.c
[]
> @@ -121,19 +121,19 @@ int get_current_ap(struct ks_wlan_private *priv, struct
>
On 17/02/17 16:23, Daniel Baluta wrote:
> On Fri, Feb 17, 2017 at 6:03 PM, Fabrice Gasnier
> wrote:
>> Hi,
>>
>> I send this as an RFC, as I'm digging to try to get as generic
>> as possible GPIO based trigger support, as discussed earlier in
>> other patchset "Add EXTI GPIO trigger support to
On Sun, 19 Feb 2017, simran singhal wrote:
> Extra parentheses were causing checkpatch issues
> and were removed.
>
> Signed-off-by: simran singhal
> ---
> drivers/staging/rtl8192e/rtl819x_HTProc.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
On Sun, 19 Feb 2017, simran singhal wrote:
> Extra parentheses were causing checkpatch issues
> and were removed.
>
> Signed-off-by: simran singhal
> ---
> drivers/staging/rtl8192e/rtl819x_HTProc.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git
On Sat, Feb 18, 2017 at 09:35:47AM +0100, Romain Perier wrote:
> The PCI pool API is deprecated. This commits replaces the PCI pool old
> API by the appropriated function with the DMA pool API.
Did not apply on linux-next-20170217
>
> Signed-off-by: Romain Perier
On Sat, Feb 18, 2017 at 09:35:47AM +0100, Romain Perier wrote:
> The PCI pool API is deprecated. This commits replaces the PCI pool old
> API by the appropriated function with the DMA pool API.
Did not apply on linux-next-20170217
>
> Signed-off-by: Romain Perier
> ---
>
Use 'pci_dma_mapping_error()' instead of 'dma_mapping_error()' because it
is more consistent with the rest of the code. It is also a little less
verbove.
While at it, remove some '(dma_addr_t)' casts in order to be consistent
within the file.
Signed-off-by: Christophe JAILLET
Use 'pci_dma_mapping_error()' instead of 'dma_mapping_error()' because it
is more consistent with the rest of the code. It is also a little less
verbove.
While at it, remove some '(dma_addr_t)' casts in order to be consistent
within the file.
Signed-off-by: Christophe JAILLET
---
This patch has locking problem. I've got lockdep splat under LTP.
[ 6633.115456] ==
[ 6633.115502] [ INFO: possible circular locking dependency detected ]
[ 6633.115553] 4.9.10-debug+ #9 Tainted: G L
[ 6633.115584]
This patch has locking problem. I've got lockdep splat under LTP.
[ 6633.115456] ==
[ 6633.115502] [ INFO: possible circular locking dependency detected ]
[ 6633.115553] 4.9.10-debug+ #9 Tainted: G L
[ 6633.115584]
On Sat, Feb 18, 2017 at 09:35:36AM +0100, Romain Perier wrote:
Tested all patches by compilation and checkpatch. All of them compile
fine, but patches 11 and 12 need some fixes. You can resend as
PATCH instead of RFC.
> The current PCI pool API are simple macro functions direct expanded to
> the
On Sat, Feb 18, 2017 at 09:35:36AM +0100, Romain Perier wrote:
Tested all patches by compilation and checkpatch. All of them compile
fine, but patches 11 and 12 need some fixes. You can resend as
PATCH instead of RFC.
> The current PCI pool API are simple macro functions direct expanded to
> the
Align * on last line, to conform to the kernal coding
style for block comments.
Signed-off-by: simran singhal
---
v2:
-Modified commit message
drivers/staging/rtl8192e/rtl819x_HT.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Align * on last line, to conform to the kernal coding
style for block comments.
Signed-off-by: simran singhal
---
v2:
-Modified commit message
drivers/staging/rtl8192e/rtl819x_HT.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8192e/rtl819x_HT.h
On Sat, Feb 18, 2017 at 09:35:48AM +0100, Romain Perier wrote:
> The PCI pool API is deprecated. This commits replaces the PCI pool old
> API by the appropriated function with the DMA pool API.
Please run checkpatch, fix the style issue and resend.
>
> Signed-off-by: Romain Perier
On Sat, Feb 18, 2017 at 09:35:48AM +0100, Romain Perier wrote:
> The PCI pool API is deprecated. This commits replaces the PCI pool old
> API by the appropriated function with the DMA pool API.
Please run checkpatch, fix the style issue and resend.
>
> Signed-off-by: Romain Perier
> ---
>
On Sat, Feb 18, 2017 at 09:35:47AM +0100, Romain Perier wrote:
Hi Romain,
Checkpatch gives some warnings you can fix related to NULL tests before
dma_pool_destroy(), and you changed indentation style in some of your
changes. Some times it is important to keep consistency within a file
even if
On Sat, Feb 18, 2017 at 09:35:47AM +0100, Romain Perier wrote:
Hi Romain,
Checkpatch gives some warnings you can fix related to NULL tests before
dma_pool_destroy(), and you changed indentation style in some of your
changes. Some times it is important to keep consistency within a file
even if
Extra parentheses were causing checkpatch issues
and were removed.
Signed-off-by: simran singhal
---
drivers/staging/rtl8192e/rtl819x_HTProc.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c
Extra parentheses were causing checkpatch issues
and were removed.
Signed-off-by: simran singhal
---
drivers/staging/rtl8192e/rtl819x_HTProc.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c
I tried to send this patch yesterday and it appeared to work. However,
I did not see an email from the list. Assuming it failed and trying
again. I apologize if this is a repeat.
I tried to send this patch yesterday and it appeared to work. However,
I did not see an email from the list. Assuming it failed and trying
again. I apologize if this is a repeat.
In Linux kernel 4.9-rc1, the function ib_get_dma_mr()
was removed and a second parameter was added to ib_alloc_pd().
As this broke the building of the ko2iblnd module in
staging, the Kconfig for LNet has marked ko2iblnd as broken
and stopped building it.
This patch fixes this breakage by:
-
In Linux kernel 4.9-rc1, the function ib_get_dma_mr()
was removed and a second parameter was added to ib_alloc_pd().
As this broke the building of the ko2iblnd module in
staging, the Kconfig for LNet has marked ko2iblnd as broken
and stopped building it.
This patch fixes this breakage by:
-
On Thu, Feb 16, 2017 at 09:41:59AM -0600, Tom Lendacky wrote:
> create mode 100644 Documentation/x86/amd-memory-encryption.txt
> create mode 100644 arch/x86/include/asm/mem_encrypt.h
> create mode 100644 arch/x86/kernel/mem_encrypt_boot.S
> create mode 100644 arch/x86/kernel/mem_encrypt_init.c
On Thu, Feb 16, 2017 at 09:41:59AM -0600, Tom Lendacky wrote:
> create mode 100644 Documentation/x86/amd-memory-encryption.txt
> create mode 100644 arch/x86/include/asm/mem_encrypt.h
> create mode 100644 arch/x86/kernel/mem_encrypt_boot.S
> create mode 100644 arch/x86/kernel/mem_encrypt_init.c
On Sat, Feb 18, 2017 at 09:29:17AM -0800, Steve Longerbeam wrote:
> On 02/18/2017 01:23 AM, Russell King - ARM Linux wrote:
> >On Fri, Feb 17, 2017 at 05:12:44PM -0800, Steve Longerbeam wrote:
> >>Hi Russell,
> >>
> >>I signed-off on this but after more review I'm not sure this is right.
> >>
>
On Sat, Feb 18, 2017 at 09:29:17AM -0800, Steve Longerbeam wrote:
> On 02/18/2017 01:23 AM, Russell King - ARM Linux wrote:
> >On Fri, Feb 17, 2017 at 05:12:44PM -0800, Steve Longerbeam wrote:
> >>Hi Russell,
> >>
> >>I signed-off on this but after more review I'm not sure this is right.
> >>
>
> > And I agree that kernel should _not_ attempt rescaling itself, as it
> > would lose precision.
>
> With an almost 1:1 mapping you won't loose precision.
How do you propose to do that?
Pavel
--
(english)
> > And I agree that kernel should _not_ attempt rescaling itself, as it
> > would lose precision.
>
> With an almost 1:1 mapping you won't loose precision.
How do you propose to do that?
Pavel
--
(english)
Hi!
> > I guess I can. But I'll only have one 80x25 screen to look at...
> >
> > .config is attached.
>
> Ah this is x86-32, interesting! I'm going to try to boot that, we never know.
>
> Thanks a lot!
Happens on x86-64, too; I'm running that normally, but for testing,
32-bit kernel is
Hi!
> > I guess I can. But I'll only have one 80x25 screen to look at...
> >
> > .config is attached.
>
> Ah this is x86-32, interesting! I'm going to try to boot that, we never know.
>
> Thanks a lot!
Happens on x86-64, too; I'm running that normally, but for testing,
32-bit kernel is
Le 18/02/2017 à 14:06, Greg Kroah-Hartman a écrit :
> On Sat, Feb 18, 2017 at 09:35:36AM +0100, Romain Perier wrote:
>> The current PCI pool API are simple macro functions direct expanded to
>> the appropriated dma pool functions. The prototypes are almost the same
>> and semantically, they are
Le 18/02/2017 à 14:06, Greg Kroah-Hartman a écrit :
> On Sat, Feb 18, 2017 at 09:35:36AM +0100, Romain Perier wrote:
>> The current PCI pool API are simple macro functions direct expanded to
>> the appropriated dma pool functions. The prototypes are almost the same
>> and semantically, they are
On Fri, Feb 17, 2017 at 06:48:13PM +0100, Boris Petkov wrote:
> LGTM.
>
> Acked-by: me
Well, it looks good but actually trying it is a different story. For
example:
$ ./perf stat -e amd_nb/event=0xe0,umask=0x1f/ sleep 1
still says because argc is not 0.
So how about the below diff instead?
On Fri, Feb 17, 2017 at 06:48:13PM +0100, Boris Petkov wrote:
> LGTM.
>
> Acked-by: me
Well, it looks good but actually trying it is a different story. For
example:
$ ./perf stat -e amd_nb/event=0xe0,umask=0x1f/ sleep 1
still says because argc is not 0.
So how about the below diff instead?
On Sat, Feb 18, 2017 at 6:28 PM, Dmitry Vyukov wrote:
> On Fri, Feb 10, 2017 at 6:17 AM, Jason Wang wrote:
>>
>>
>> On 2017年02月10日 02:10, Michael S. Tsirkin wrote:
>>>
>>> On Thu, Feb 09, 2017 at 05:02:31AM -0500, Jason Wang wrote:
-
On Sat, Feb 18, 2017 at 6:28 PM, Dmitry Vyukov wrote:
> On Fri, Feb 10, 2017 at 6:17 AM, Jason Wang wrote:
>>
>>
>> On 2017年02月10日 02:10, Michael S. Tsirkin wrote:
>>>
>>> On Thu, Feb 09, 2017 at 05:02:31AM -0500, Jason Wang wrote:
- Original Message -
>
> Hello,
>
On 02/16/2017 02:57 PM, Russell King - ARM Linux wrote:
On Thu, Feb 16, 2017 at 02:27:41PM -0800, Steve Longerbeam wrote:
On 02/16/2017 02:20 PM, Russell King - ARM Linux wrote:
On Wed, Feb 15, 2017 at 06:19:02PM -0800, Steve Longerbeam wrote:
In version 4:
With this version, I get:
On 02/16/2017 02:57 PM, Russell King - ARM Linux wrote:
On Thu, Feb 16, 2017 at 02:27:41PM -0800, Steve Longerbeam wrote:
On 02/16/2017 02:20 PM, Russell King - ARM Linux wrote:
On Wed, Feb 15, 2017 at 06:19:02PM -0800, Steve Longerbeam wrote:
In version 4:
With this version, I get:
On 02/18/2017 01:23 AM, Russell King - ARM Linux wrote:
On Fri, Feb 17, 2017 at 05:12:44PM -0800, Steve Longerbeam wrote:
Hi Russell,
I signed-off on this but after more review I'm not sure this is right.
The CSI-2 receiver really has no control over frame rate. It's output
frame rate is
On 02/18/2017 01:23 AM, Russell King - ARM Linux wrote:
On Fri, Feb 17, 2017 at 05:12:44PM -0800, Steve Longerbeam wrote:
Hi Russell,
I signed-off on this but after more review I'm not sure this is right.
The CSI-2 receiver really has no control over frame rate. It's output
frame rate is
On Fri, Feb 10, 2017 at 6:17 AM, Jason Wang wrote:
>
>
> On 2017年02月10日 02:10, Michael S. Tsirkin wrote:
>>
>> On Thu, Feb 09, 2017 at 05:02:31AM -0500, Jason Wang wrote:
>>>
>>> - Original Message -
Hello,
I've got the following report while
On Fri, Feb 10, 2017 at 6:17 AM, Jason Wang wrote:
>
>
> On 2017年02月10日 02:10, Michael S. Tsirkin wrote:
>>
>> On Thu, Feb 09, 2017 at 05:02:31AM -0500, Jason Wang wrote:
>>>
>>> - Original Message -
Hello,
I've got the following report while running syzkaller fuzzer
On Sat, 18 Feb 2017, SIMRAN SINGHAL wrote:
>
>
> On Saturday, February 18, 2017 at 9:46:48 PM UTC+5:30, Julia Lawall wrote:
>
>
> On Sat, 18 Feb 2017, SIMRAN SINGHAL wrote:
>
> >
> >
> > On Saturday, February 18, 2017 at 9:00:51 PM UTC+5:30, Julia
> Lawall wrote:
>
On Sat, 18 Feb 2017, SIMRAN SINGHAL wrote:
>
>
> On Saturday, February 18, 2017 at 9:46:48 PM UTC+5:30, Julia Lawall wrote:
>
>
> On Sat, 18 Feb 2017, SIMRAN SINGHAL wrote:
>
> >
> >
> > On Saturday, February 18, 2017 at 9:00:51 PM UTC+5:30, Julia
> Lawall wrote:
>
The mmc host was added in meson_mmc_probe, but never removed in
meson_mmc_remove.
Fix that by removing the host before deallocating other resources.
Signed-off-by: Michał Zegan
Tested-by: Michał Zegan
---
changes since v1:
rebased on top of patchset
This patch fixes the case where meson_mmc_probe function fails before
core_clk is enabled.
Originally, that would result in a try to disable the core clock, and if
it was not already enabled, it would result in a kernel warning.
This issue is similar to the one with div_clk.
Fix it by introducing
The mmc host was added in meson_mmc_probe, but never removed in
meson_mmc_remove.
Fix that by removing the host before deallocating other resources.
Signed-off-by: Michał Zegan
Tested-by: Michał Zegan
---
changes since v1:
rebased on top of patchset at
This patch fixes the case where meson_mmc_probe function fails before
core_clk is enabled.
Originally, that would result in a try to disable the core clock, and if
it was not already enabled, it would result in a kernel warning.
This issue is similar to the one with div_clk.
Fix it by introducing
On Sat, 18 Feb 2017, Arushi Singhal wrote:
> The following patch the checkpatch.pl warning:
> drivers/staging/ks7010/ks_hostif.c warning: please, no spaces at the
> start of a line
>
> Signed-off-by: Arushi Singhal
> ---
> drivers/staging/ks7010/ks_hostif.c |
On Sat, 18 Feb 2017, Arushi Singhal wrote:
> The following patch the checkpatch.pl warning:
> drivers/staging/ks7010/ks_hostif.c warning: please, no spaces at the
> start of a line
>
> Signed-off-by: Arushi Singhal
> ---
> drivers/staging/ks7010/ks_hostif.c | 4 ++--
> 1 file changed, 2
Unnecessary parentheses should be avoided as reported by checkpatch.pl
Signed-off-by: Arushi Singhal
---
drivers/staging/ks7010/ks_hostif.c | 24
drivers/staging/ks7010/ks_wlan_net.c | 20 ++--
2 files changed, 22
Unnecessary parentheses should be avoided as reported by checkpatch.pl
Signed-off-by: Arushi Singhal
---
drivers/staging/ks7010/ks_hostif.c | 24
drivers/staging/ks7010/ks_wlan_net.c | 20 ++--
2 files changed, 22 insertions(+), 22 deletions(-)
diff
On Sat, Feb 18, 2017 at 10:10:02PM +0530, Arushi Singhal wrote:
> The following patch the checkpatch.pl warning:
> drivers/staging/ks7010/ks_hostif.c warning: please, no spaces at the
> start of a line
>
> Signed-off-by: Arushi Singhal
> ---
>
On Sat, Feb 18, 2017 at 10:10:02PM +0530, Arushi Singhal wrote:
> The following patch the checkpatch.pl warning:
> drivers/staging/ks7010/ks_hostif.c warning: please, no spaces at the
> start of a line
>
> Signed-off-by: Arushi Singhal
> ---
> drivers/staging/ks7010/ks_hostif.c | 4 ++--
> 1
The following patch the checkpatch.pl warning:
drivers/staging/ks7010/ks_hostif.c warning: please, no spaces at the
start of a line
Signed-off-by: Arushi Singhal
---
drivers/staging/ks7010/ks_hostif.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The following patch the checkpatch.pl warning:
drivers/staging/ks7010/ks_hostif.c warning: please, no spaces at the
start of a line
Signed-off-by: Arushi Singhal
---
drivers/staging/ks7010/ks_hostif.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
201 - 300 of 450 matches
Mail list logo