On Thu, Dec 1, 2016 at 8:54 PM, Masahiro Yamada
wrote:
> Hi Rob,
> (+CC Dinh)
>
> 2016-12-02 1:05 GMT+09:00 Rob Herring :
>> On Sun, Nov 27, 2016 at 03:06:25AM +0900, Masahiro Yamada wrote:
>>> Add two compatible strings for UniPhier SoCs. The
On Thu, Dec 1, 2016 at 8:54 PM, Masahiro Yamada
wrote:
> Hi Rob,
> (+CC Dinh)
>
> 2016-12-02 1:05 GMT+09:00 Rob Herring :
>> On Sun, Nov 27, 2016 at 03:06:25AM +0900, Masahiro Yamada wrote:
>>> Add two compatible strings for UniPhier SoCs. The revision register
>>> on both shows revision 5.0,
On Fri, Dec 02, 2016 at 11:45:00AM +0100, Robert Richter wrote:
> On 02.12.16 11:06:24, Tomasz Nowicki wrote:
> > On 02.12.2016 07:42, Duc Dang wrote:
>
> > >@@ -98,16 +98,16 @@ struct mcfg_fixup {
> > >{ "CAVIUM", "THUNDERX", rev, seg, MCFG_BUS_ANY, \
> > >
On Fri, Dec 02, 2016 at 11:45:00AM +0100, Robert Richter wrote:
> On 02.12.16 11:06:24, Tomasz Nowicki wrote:
> > On 02.12.2016 07:42, Duc Dang wrote:
>
> > >@@ -98,16 +98,16 @@ struct mcfg_fixup {
> > >{ "CAVIUM", "THUNDERX", rev, seg, MCFG_BUS_ANY, \
> > >
Hi,
On 12/02/2016 03:42 PM, Nathan Sullivan wrote:
Support the National Instruments 169445 board.
Interesting patch.
But do you happen to have a link to a description of the board?
I couldn't find anything with a quick search.
Perhaps the public name is something else?
Thanks,
ZubairLK
Hi,
On 12/02/2016 03:42 PM, Nathan Sullivan wrote:
Support the National Instruments 169445 board.
Interesting patch.
But do you happen to have a link to a description of the board?
I couldn't find anything with a quick search.
Perhaps the public name is something else?
Thanks,
ZubairLK
From: Colin Ian King
A previous fix of a memory leak now prints the string 'name'
that was previously free'd. Fix this by free'ing the string
at the end of the function and adding an error exit path for
the error conditions.
CoverityScan CID#1384523 ("Use after free")
From: Colin Ian King
A previous fix of a memory leak now prints the string 'name'
that was previously free'd. Fix this by free'ing the string
at the end of the function and adding an error exit path for
the error conditions.
CoverityScan CID#1384523 ("Use after free")
Fixes: 2bd362d5f45c1
On 12/02/2016 05:42 PM, Josh Poimboeuf wrote:
> diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
> index 0e9505f..e9d8ba0 100644
> --- a/mm/kasan/kasan.c
> +++ b/mm/kasan/kasan.c
> @@ -80,7 +80,14 @@ void kasan_unpoison_task_stack(struct task_struct *task)
> /* Unpoison the stack for the
On 12/02/2016 05:42 PM, Josh Poimboeuf wrote:
> diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
> index 0e9505f..e9d8ba0 100644
> --- a/mm/kasan/kasan.c
> +++ b/mm/kasan/kasan.c
> @@ -80,7 +80,14 @@ void kasan_unpoison_task_stack(struct task_struct *task)
> /* Unpoison the stack for the
On 02/12/2016 at 15:59:57 +, David Laight wrote :
> From: Alexandre Belloni
> > Sent: 01 December 2016 10:27
> > Use devm_kasprintf instead of simple kasprintf to free the allocated memory
> > when needed.
>
> s/when needed/when the device is freed/
>
> > Suggested-by: Peter Rosin
On 02/12/2016 at 15:59:57 +, David Laight wrote :
> From: Alexandre Belloni
> > Sent: 01 December 2016 10:27
> > Use devm_kasprintf instead of simple kasprintf to free the allocated memory
> > when needed.
>
> s/when needed/when the device is freed/
>
> > Suggested-by: Peter Rosin
> >
Hi cuilifei,
[auto build test WARNING on fuse/for-next]
[also build test WARNING on v4.9-rc7 next-20161202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/cuilifei/fuse-freezing-abort-when-use
Hi cuilifei,
[auto build test WARNING on fuse/for-next]
[also build test WARNING on v4.9-rc7 next-20161202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/cuilifei/fuse-freezing-abort-when-use
Hi Sricharan,
On 02/12/16 14:55, Sricharan R wrote:
> This series is a resend of the V5 that Mitch sent sometime back [2]
> All the patches are the same and i have just rebased. Not sure why this
> finally did not make it last time. The last patch in the previous
> series does not apply now [3],
Hi Sricharan,
On 02/12/16 14:55, Sricharan R wrote:
> This series is a resend of the V5 that Mitch sent sometime back [2]
> All the patches are the same and i have just rebased. Not sure why this
> finally did not make it last time. The last patch in the previous
> series does not apply now [3],
From: Basil Gunn
Date: Wed, 30 Nov 2016 11:15:25 -0800
> AX.25 uses sock_queue_rcv_skb() to queue an iframe received packet.
> This routine writes NULL to the socket buffer device structure
> pointer. The socket buffer is subsequently serviced by
> __netif_receiv_skb_core()
From: Basil Gunn
Date: Wed, 30 Nov 2016 11:15:25 -0800
> AX.25 uses sock_queue_rcv_skb() to queue an iframe received packet.
> This routine writes NULL to the socket buffer device structure
> pointer. The socket buffer is subsequently serviced by
> __netif_receiv_skb_core() which dereferences
Hi,
On 02/12/16 14:32, Icenowy Zheng wrote:
>
>
> 02.12.2016, 22:30, "Hans de Goede" :
>> Hi,
>>
>> On 02-12-16 15:22, Icenowy Zheng wrote:
>>> 01.12.2016, 17:36, "Maxime Ripard" :
On Mon, Nov 28, 2016 at 12:29:07AM +, André
Hi,
On 02/12/16 14:32, Icenowy Zheng wrote:
>
>
> 02.12.2016, 22:30, "Hans de Goede" :
>> Hi,
>>
>> On 02-12-16 15:22, Icenowy Zheng wrote:
>>> 01.12.2016, 17:36, "Maxime Ripard" :
On Mon, Nov 28, 2016 at 12:29:07AM +, André Przywara wrote:
> > Something more interesting
On Fri, Dec 2, 2016 at 4:58 PM, Greg Kroah-Hartman
wrote:
> On Fri, Dec 02, 2016 at 03:35:44PM +0100, Andrey Konovalov wrote:
>> Hi!
>>
>> I've got the following error report while booting the kernel with
>> various usb configs enabled.
>
> Any hint as to what these
On Fri, Dec 2, 2016 at 4:58 PM, Greg Kroah-Hartman
wrote:
> On Fri, Dec 02, 2016 at 03:35:44PM +0100, Andrey Konovalov wrote:
>> Hi!
>>
>> I've got the following error report while booting the kernel with
>> various usb configs enabled.
>
> Any hint as to what these "various usb configs" are?
Hi
The fact that the --children option is enabled by default is buried deep
at the end of the help page, in the overhead calculation section. This
make it explicit right where the option is listed, following the same
way other default options are described
Signed-off-by: Yannick Brosseau
The fact that the --children option is enabled by default is buried deep
at the end of the help page, in the overhead calculation section. This
make it explicit right where the option is listed, following the same
way other default options are described
Signed-off-by: Yannick Brosseau
---
* Boris Ostrovsky wrote:
> On 12/02/2016 04:45 AM, Ingo Molnar wrote:
> > * Boris Ostrovsky wrote:
> >
> >> On 10/31/2016 08:33 AM, Boris Ostrovsky wrote:
> >>>
> >>> On 10/14/2016 02:05 PM, Boris Ostrovsky wrote:
> From: Matt
* Boris Ostrovsky wrote:
> On 12/02/2016 04:45 AM, Ingo Molnar wrote:
> > * Boris Ostrovsky wrote:
> >
> >> On 10/31/2016 08:33 AM, Boris Ostrovsky wrote:
> >>>
> >>> On 10/14/2016 02:05 PM, Boris Ostrovsky wrote:
> From: Matt Fleming
>
> The new Xen PVH entry point requires
On Fri, Dec 02, 2016 at 03:35:44PM +0100, Andrey Konovalov wrote:
> Hi!
>
> I've got the following error report while booting the kernel with
> various usb configs enabled.
Any hint as to what these "various usb configs" are?
> On commit 2caceb3294a78c389b462e7e236a4e744a53a474 (Dec 1).
>
>
On Fri, Dec 02, 2016 at 03:35:44PM +0100, Andrey Konovalov wrote:
> Hi!
>
> I've got the following error report while booting the kernel with
> various usb configs enabled.
Any hint as to what these "various usb configs" are?
> On commit 2caceb3294a78c389b462e7e236a4e744a53a474 (Dec 1).
>
>
On Fri, Dec 02, 2016 at 04:56:15PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 02, 2016 at 04:07:38PM +0100, Andrey Konovalov wrote:
> > Hi!
> >
> > I've got the following error report while running the syzkaller fuzzer.
> >
> > The length passed to memdup_user() directly without limitations.
On Fri, Dec 02, 2016 at 04:56:15PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 02, 2016 at 04:07:38PM +0100, Andrey Konovalov wrote:
> > Hi!
> >
> > I've got the following error report while running the syzkaller fuzzer.
> >
> > The length passed to memdup_user() directly without limitations.
On Thu, Dec 1, 2016 at 10:54 PM, Archit Taneja wrote:
> Hi,
>
> On 12/02/2016 08:02 AM, zain wang wrote:
>>
>> We will ignored PSR setting if panel not support it. So, in this case, we
>> should
>> return from analogix_dp_enable/disable_psr() without any error code.
>>
On Thu, Dec 1, 2016 at 10:54 PM, Archit Taneja wrote:
> Hi,
>
> On 12/02/2016 08:02 AM, zain wang wrote:
>>
>> We will ignored PSR setting if panel not support it. So, in this case, we
>> should
>> return from analogix_dp_enable/disable_psr() without any error code.
>> Let's retrun 0 instead of
Hi Alex
On 12/2/2016 3:26 PM, Alexandre Torgue wrote:
4.4 has no GMAC4 support.
Alex, do you remember any patches to fix that?
No sorry Peppe.
Pavel,
Sorry but I'm a little bit confused. I'm dropped in some mails without
historic. I see cleanup, coalescence issue and TSO question.
What is
Hi Alex
On 12/2/2016 3:26 PM, Alexandre Torgue wrote:
4.4 has no GMAC4 support.
Alex, do you remember any patches to fix that?
No sorry Peppe.
Pavel,
Sorry but I'm a little bit confused. I'm dropped in some mails without
historic. I see cleanup, coalescence issue and TSO question.
What is
Hi Pavel
On 12/2/2016 11:42 AM, Pavel Machek wrote:
Hi!
Anyway... since you asked. I belive I have way to disable NAPI / tx
coalescing in the driver. Unfortunately, locking is missing on the rx
path, and needs to be extended to _irqsave variant on tx path.
I have just replied to a previous
Hi Pavel
On 12/2/2016 11:42 AM, Pavel Machek wrote:
Hi!
Anyway... since you asked. I belive I have way to disable NAPI / tx
coalescing in the driver. Unfortunately, locking is missing on the rx
path, and needs to be extended to _irqsave variant on tx path.
I have just replied to a previous
On Fri, Dec 02, 2016 at 03:38:51PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Thursday, December 1, 2016 11:36 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org;
On Fri, Dec 02, 2016 at 03:38:51PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Thursday, December 1, 2016 11:36 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> >
On 12/02/2016 04:11 PM, Oliver Hartkopp wrote:
>
>
> On 12/02/2016 02:24 PM, Marc Kleine-Budde wrote:
>> On 12/02/2016 01:43 PM, Andrey Konovalov wrote:
>
>
>>> [] raw_setsockopt+0x1be/0x9f0 net/can/raw.c:506
>>
>> We should add a check for a sensible optlen
>>
>>> static int
On 12/02/2016 04:11 PM, Oliver Hartkopp wrote:
>
>
> On 12/02/2016 02:24 PM, Marc Kleine-Budde wrote:
>> On 12/02/2016 01:43 PM, Andrey Konovalov wrote:
>
>
>>> [] raw_setsockopt+0x1be/0x9f0 net/can/raw.c:506
>>
>> We should add a check for a sensible optlen
>>
>>> static int
In function ioat_xor_val_self_test(), when the calls to
dma_mapping_error() fail, the value of return variable err is 0
(indicates no error). As a result, the return value may be inconsistent
with the execution status. This patch fixes the bug by assigning
"-ENOMEM" to err on the error path.
From: Alexandre Belloni
> Sent: 01 December 2016 10:27
> Use devm_kasprintf instead of simple kasprintf to free the allocated memory
> when needed.
s/when needed/when the device is freed/
> Suggested-by: Peter Rosin
> Signed-off-by: Alexandre Belloni
In function ioat_xor_val_self_test(), when the calls to
dma_mapping_error() fail, the value of return variable err is 0
(indicates no error). As a result, the return value may be inconsistent
with the execution status. This patch fixes the bug by assigning
"-ENOMEM" to err on the error path.
From: Alexandre Belloni
> Sent: 01 December 2016 10:27
> Use devm_kasprintf instead of simple kasprintf to free the allocated memory
> when needed.
s/when needed/when the device is freed/
> Suggested-by: Peter Rosin
> Signed-off-by: Alexandre Belloni
> ---
>
On Fri, Dec 02, 2016 at 04:07:38PM +0100, Andrey Konovalov wrote:
> Hi!
>
> I've got the following error report while running the syzkaller fuzzer.
>
> The length passed to memdup_user() directly without limitations.
>
> On commit 2caceb3294a78c389b462e7e236a4e744a53a474 (Dec 1).
>
> WARNING:
On Fri, Dec 02, 2016 at 04:07:38PM +0100, Andrey Konovalov wrote:
> Hi!
>
> I've got the following error report while running the syzkaller fuzzer.
>
> The length passed to memdup_user() directly without limitations.
>
> On commit 2caceb3294a78c389b462e7e236a4e744a53a474 (Dec 1).
>
> WARNING:
> On 02.12.2016, at 09:19, Eric Biggers wrote:
>
> On Thu, Dec 01, 2016 at 11:14:55PM +0100, Richard Weinberger wrote:
>> + * @lblk_num: Logical block number. This must be unique for multiple
>> + * calls with same page.
>
> Must be unique for all calls with
> On 02.12.2016, at 09:19, Eric Biggers wrote:
>
> On Thu, Dec 01, 2016 at 11:14:55PM +0100, Richard Weinberger wrote:
>> + * @lblk_num: Logical block number. This must be unique for multiple
>> + * calls with same page.
>
> Must be unique for all calls with the same *inode*,
On Thu, Dec 1, 2016 at 10:31 PM, Nicholas Piggin
wrote:
>
> On 2 Dec 2016 2:35 AM, "Luis R. Rodriguez" wrote:
>>
>> On Wed, Nov 30, 2016 at 9:20 PM, Nicholas Piggin
>> wrote:
>> > On Thu, 1 Dec 2016 16:04:30 +1100
>> > Nicholas
On Thu, Dec 1, 2016 at 10:31 PM, Nicholas Piggin
wrote:
>
> On 2 Dec 2016 2:35 AM, "Luis R. Rodriguez" wrote:
>>
>> On Wed, Nov 30, 2016 at 9:20 PM, Nicholas Piggin
>> wrote:
>> > On Thu, 1 Dec 2016 16:04:30 +1100
>> > Nicholas Piggin wrote:
>> >
>> >> On Wed, 30 Nov 2016 19:15:27 -0800
>> >>
Em Sat, Nov 26, 2016 at 07:03:34AM +, Wang Nan escreveu:
> Add basic clang support in clang.cpp and test__clang() testcase. The
> first testcase checks if builtin clang is able to generate LLVM IR.
>
> tests/clang.c is a proxy. Real testcase resides in
> utils/c++/clang-test.cpp in c++ and
On Fri, 2016-12-02 at 16:37 +0100, Jesper Dangaard Brouer wrote:
> On Thu, 01 Dec 2016 23:17:48 +0100
> Paolo Abeni wrote:
>
> > On Thu, 2016-12-01 at 18:34 +0100, Jesper Dangaard Brouer wrote:
> > > (Cc. netdev, we might have an issue with Paolo's UDP accounting and
> > >
Em Sat, Nov 26, 2016 at 07:03:34AM +, Wang Nan escreveu:
> Add basic clang support in clang.cpp and test__clang() testcase. The
> first testcase checks if builtin clang is able to generate LLVM IR.
>
> tests/clang.c is a proxy. Real testcase resides in
> utils/c++/clang-test.cpp in c++ and
On Fri, 2016-12-02 at 16:37 +0100, Jesper Dangaard Brouer wrote:
> On Thu, 01 Dec 2016 23:17:48 +0100
> Paolo Abeni wrote:
>
> > On Thu, 2016-12-01 at 18:34 +0100, Jesper Dangaard Brouer wrote:
> > > (Cc. netdev, we might have an issue with Paolo's UDP accounting and
> > > small socket queues)
>
From: Johan Hovold
Date: Wed, 30 Nov 2016 15:29:48 +0100
> This series fixes a number of issues with the stmmac-driver probe error
> handling, which for example left clocks enabled after probe failures.
>
> The final patch fixes a failure to deregister and free any fixed-link
From: Johan Hovold
Date: Wed, 30 Nov 2016 15:29:48 +0100
> This series fixes a number of issues with the stmmac-driver probe error
> handling, which for example left clocks enabled after probe failures.
>
> The final patch fixes a failure to deregister and free any fixed-link
> PHYs that were
On Thu, Dec 01, 2016 at 03:41:20PM -0500, Vivien Didelot wrote:
> Hi Andrew,
>
> Andrew Lunn writes:
>
> >> diff --git a/drivers/net/dsa/mv88e6xxx/mv88e6xxx.h
> >> b/drivers/net/dsa/mv88e6xxx/mv88e6xxx.h
> >> index ab52c37..9e51405 100644
> >> ---
On Thu, Dec 01, 2016 at 03:41:20PM -0500, Vivien Didelot wrote:
> Hi Andrew,
>
> Andrew Lunn writes:
>
> >> diff --git a/drivers/net/dsa/mv88e6xxx/mv88e6xxx.h
> >> b/drivers/net/dsa/mv88e6xxx/mv88e6xxx.h
> >> index ab52c37..9e51405 100644
> >> --- a/drivers/net/dsa/mv88e6xxx/mv88e6xxx.h
> >>
Dave Hansen writes:
> Andrew, you can drop proc-mm-export-pte-sizes-directly-in-smaps-v2.patch,
> and replace it with this.
>
.
> diff -puN mm/hugetlb.c~smaps-pte-sizes mm/hugetlb.c
> --- a/mm/hugetlb.c~smaps-pte-sizes2016-11-28 14:21:37.19365 -0800
> +++
Dave Hansen writes:
> Andrew, you can drop proc-mm-export-pte-sizes-directly-in-smaps-v2.patch,
> and replace it with this.
>
.
> diff -puN mm/hugetlb.c~smaps-pte-sizes mm/hugetlb.c
> --- a/mm/hugetlb.c~smaps-pte-sizes2016-11-28 14:21:37.19365 -0800
> +++ b/mm/hugetlb.c
While trying to set the pll0 rate from the kernel I noticed there are
two issues with da850 clocks. The first patch fixes an infinite loop
in propagate_rate(). The third fixes an oops in da850_set_pll0rate().
The second patch is just a coding style fix, while we're at it.
v1 -> v2:
- change the
While trying to set the pll0 rate from the kernel I noticed there are
two issues with da850 clocks. The first patch fixes an infinite loop
in propagate_rate(). The third fixes an oops in da850_set_pll0rate().
The second patch is just a coding style fix, while we're at it.
v1 -> v2:
- change the
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, December 1, 2016 11:36 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
>
Hi Thierry,
On Fri, Dec 2, 2016 at 7:35 AM, Thierry Escande
wrote:
> Hi Benson,
>
> This series adds support for the LPC Microchip Embedded Controller 1322.
Thanks. I'll queue these up for the first batch of changes I'll work
on as chrome platform maintainer.
>
>
Hi Thierry,
On Fri, Dec 2, 2016 at 7:35 AM, Thierry Escande
wrote:
> Hi Benson,
>
> This series adds support for the LPC Microchip Embedded Controller 1322.
Thanks. I'll queue these up for the first batch of changes I'll work
on as chrome platform maintainer.
>
> v2:
> -Add a few lines in
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, December 1, 2016 11:36 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com;
Fix alignment of the clock lookup table entries.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da850.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-davinci/da850.c b/arch/arm/mach-davinci/da850.c
index
Fix alignment of the clock lookup table entries.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da850.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-davinci/da850.c b/arch/arm/mach-davinci/da850.c
index 1fcc986..a55101c 100644
---
On Thu, 01 Dec 2016 23:17:48 +0100
Paolo Abeni wrote:
> On Thu, 2016-12-01 at 18:34 +0100, Jesper Dangaard Brouer wrote:
> > (Cc. netdev, we might have an issue with Paolo's UDP accounting and
> > small socket queues)
> >
> > On Wed, 30 Nov 2016 16:35:20 +
> > Mel Gorman
On Thu, 01 Dec 2016 23:17:48 +0100
Paolo Abeni wrote:
> On Thu, 2016-12-01 at 18:34 +0100, Jesper Dangaard Brouer wrote:
> > (Cc. netdev, we might have an issue with Paolo's UDP accounting and
> > small socket queues)
> >
> > On Wed, 30 Nov 2016 16:35:20 +
> > Mel Gorman wrote:
> >
> >
This function is broken - its second argument is an index to the freq
table, not the requested clock rate in Hz. It leads to an oops when
called from clk_set_rate() since this argument isn't bounds checked
either.
Fix it by iterating over the array of supported frequencies and
selecting a one
This function is broken - its second argument is an index to the freq
table, not the requested clock rate in Hz. It leads to an oops when
called from clk_set_rate() since this argument isn't bounds checked
either.
Fix it by iterating over the array of supported frequencies and
selecting a one
The aemif clock is added twice to the lookup table in da850.c. This
breaks the children list of pll0_sysclk3 as we're using the same list
links in struct clk. When calling clk_set_rate(), we get stuck in
propagate_rate().
Create a separate clock for nand, inheriting the rate of the aemif
clock
The aemif clock is added twice to the lookup table in da850.c. This
breaks the children list of pll0_sysclk3 as we're using the same list
links in struct clk. When calling clk_set_rate(), we get stuck in
propagate_rate().
Create a separate clock for nand, inheriting the rate of the aemif
clock
From: Neill Whillans
Date: Wed, 30 Nov 2016 13:41:03 +
> These patches were created as part of work to add support for SGMII
> PCS functionality to the Altera TSE MAC. Patches are based on 4.9-rc6
> git tree.
>
> The first patch in the series adds support for
From: Neill Whillans
Date: Wed, 30 Nov 2016 13:41:03 +
> These patches were created as part of work to add support for SGMII
> PCS functionality to the Altera TSE MAC. Patches are based on 4.9-rc6
> git tree.
>
> The first patch in the series adds support for the VSC8572 dual-port
> Gigabit
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan
---
"devicetree: add vendor prefix for National Instruments" added the ni vendor
prefix.
This patch is needed for
Rafael, Mark, Suravee,
On Mon, Nov 21, 2016 at 10:01:39AM +, Lorenzo Pieralisi wrote:
> On DT based systems, the of_dma_configure() API implements DMA
> configuration for a given device. On ACPI systems an API equivalent to
> of_dma_configure() is missing which implies that it is currently
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan
---
"devicetree: add vendor prefix for National Instruments" added the ni vendor
prefix.
This patch is needed for "MIPS: NI 169445 board
Rafael, Mark, Suravee,
On Mon, Nov 21, 2016 at 10:01:39AM +, Lorenzo Pieralisi wrote:
> On DT based systems, the of_dma_configure() API implements DMA
> configuration for a given device. On ACPI systems an API equivalent to
> of_dma_configure() is missing which implies that it is currently
From: Shawn Nematbakhsh
This adds support for the ChromeOS LPC Microchip Embedded Controller
(mec1322) variant.
mec1322 accesses I/O region [800h, 9ffh] through embedded memory
interface (EMI) rather than LPC.
Signed-off-by: Shawn Nematbakhsh
From: Shawn Nematbakhsh
This adds support for the ChromeOS LPC Microchip Embedded Controller
(mec1322) variant.
mec1322 accesses I/O region [800h, 9ffh] through embedded memory
interface (EMI) rather than LPC.
Signed-off-by: Shawn Nematbakhsh
Signed-off-by: Thierry Escande
---
On Fri, Dec 02, 2016 at 01:40:27PM +0100, Arnd Bergmann wrote:
> With binutils-2.16 and before, a weak missing symbol was kept during the
> final link, and a missing CRC for an export would lead to that CRC
> being treated as zero implicitly. With binutils-2.17, the crc
> symbol gets dropped, and
On Fri, Dec 02, 2016 at 01:40:27PM +0100, Arnd Bergmann wrote:
> With binutils-2.16 and before, a weak missing symbol was kept during the
> final link, and a missing CRC for an export would lead to that CRC
> being treated as zero implicitly. With binutils-2.17, the crc
> symbol gets dropped, and
Hi Benson,
This series adds support for the LPC Microchip Embedded Controller 1322.
v2:
-Add a few lines in Kconfig description
-Fixed coding style issues
-Updated copyright to year 2016
Shawn Nematbakhsh (2):
platform/chrome: cros_ec_lpc: Add R/W helpers to LPC protocol variants
From: Shawn Nematbakhsh
Call common functions for read / write to prepare support for future
LPC protocol variants which use different I/O ops than inb / outb.
Signed-off-by: Shawn Nematbakhsh
Signed-off-by: Thierry Escande
Hi Benson,
This series adds support for the LPC Microchip Embedded Controller 1322.
v2:
-Add a few lines in Kconfig description
-Fixed coding style issues
-Updated copyright to year 2016
Shawn Nematbakhsh (2):
platform/chrome: cros_ec_lpc: Add R/W helpers to LPC protocol variants
From: Shawn Nematbakhsh
Call common functions for read / write to prepare support for future
LPC protocol variants which use different I/O ops than inb / outb.
Signed-off-by: Shawn Nematbakhsh
Signed-off-by: Thierry Escande
---
drivers/platform/chrome/Makefile | 3 +-
Signed-off-by: Nathan Sullivan
---
This is required by "gpio: mmio: add support for NI 169445 NAND GPIO"
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
Signed-off-by: Nathan Sullivan
---
This is required by "gpio: mmio: add support for NI 169445 NAND GPIO"
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
From: Colin Ian King
allocates string 'new' is not free'd on the exit path when
cdm_element_count <= 0. Fix this by kfree'ing it.
Fixes CoverityScan CID#1375923 "Resource Leak"
Signed-off-by: Colin Ian King
---
From: Colin Ian King
allocates string 'new' is not free'd on the exit path when
cdm_element_count <= 0. Fix this by kfree'ing it.
Fixes CoverityScan CID#1375923 "Resource Leak"
Signed-off-by: Colin Ian King
---
fs/orangefs/orangefs-debugfs.c | 4 +++-
1 file changed, 3 insertions(+), 1
On 12/02/2016 02:24 PM, Marc Kleine-Budde wrote:
On 12/02/2016 01:43 PM, Andrey Konovalov wrote:
[] raw_setsockopt+0x1be/0x9f0 net/can/raw.c:506
We should add a check for a sensible optlen
static int raw_setsockopt(struct socket *sock, int level, int optname,
On 12/02/2016 02:24 PM, Marc Kleine-Budde wrote:
On 12/02/2016 01:43 PM, Andrey Konovalov wrote:
[] raw_setsockopt+0x1be/0x9f0 net/can/raw.c:506
We should add a check for a sensible optlen
static int raw_setsockopt(struct socket *sock, int level, int optname,
Hi Michael,
On 12/02/2016 06:26 AM, Michael Walle wrote:
This patch adds support for the min, max and alarm attributes of the
voltage and temperature channels. Additionally, the temp2_fault attribute
is supported which indicates a fault of the external temperature diode.
Signed-off-by: Michael
Hi Michael,
On 12/02/2016 06:26 AM, Michael Walle wrote:
This patch adds support for the min, max and alarm attributes of the
voltage and temperature channels. Additionally, the temp2_fault attribute
is supported which indicates a fault of the external temperature diode.
Signed-off-by: Michael
On 30 November 2016 at 15:24, Morten Rasmussen wrote:
> On Wed, Nov 30, 2016 at 02:54:00PM +0100, Vincent Guittot wrote:
>> On 30 November 2016 at 14:49, Vincent Guittot
>> wrote:
>> > On 30 November 2016 at 13:49, Morten Rasmussen
On 30 November 2016 at 15:24, Morten Rasmussen wrote:
> On Wed, Nov 30, 2016 at 02:54:00PM +0100, Vincent Guittot wrote:
>> On 30 November 2016 at 14:49, Vincent Guittot
>> wrote:
>> > On 30 November 2016 at 13:49, Morten Rasmussen
>> > wrote:
>> >> On Fri, Nov 25, 2016 at 04:34:33PM +0100,
[Let's CC more people - the thread started
http://lkml.kernel.org/r/1480540516-6458-1-git-send-email-yuz...@google.com]
On Fri 02-12-16 09:56:26, Dan Streetman wrote:
> On Fri, Dec 2, 2016 at 9:44 AM, Michal Hocko wrote:
> > On Fri 02-12-16 15:38:48, Michal Hocko wrote:
> >>
[Let's CC more people - the thread started
http://lkml.kernel.org/r/1480540516-6458-1-git-send-email-yuz...@google.com]
On Fri 02-12-16 09:56:26, Dan Streetman wrote:
> On Fri, Dec 2, 2016 at 9:44 AM, Michal Hocko wrote:
> > On Fri 02-12-16 15:38:48, Michal Hocko wrote:
> >> On Fri 02-12-16
601 - 700 of 1302 matches
Mail list logo