Hello.
On 9/23/2016 6:32 AM, Sean Wang wrote:
From: Sean Wang
adds PHY-mode "trgmii" as an extension for the operation mode of the
PHY interface for PHY_INTERFACE_MODE_TRGMII.
.. deleted
What? Why?
switch (of_get_phy_mode(np)) {
+ case
Hello.
On 9/23/2016 6:32 AM, Sean Wang wrote:
From: Sean Wang
adds PHY-mode "trgmii" as an extension for the operation mode of the
PHY interface for PHY_INTERFACE_MODE_TRGMII.
.. deleted
What? Why?
switch (of_get_phy_mode(np)) {
+ case PHY_INTERFACE_MODE_TRGMII:
+
On Thu, 22 Sep 2016, Waiman Long wrote:
> On 09/22/2016 09:32 AM, Thomas Gleixner wrote:
> > > + WARN_ON(!pi_state->owner);
> > > + if (pi_state->owner)
> > > + wake_up_process(pi_state->owner);
> > And what handles or sanity checks the
On Thu, 22 Sep 2016, Waiman Long wrote:
> On 09/22/2016 09:32 AM, Thomas Gleixner wrote:
> > > + WARN_ON(!pi_state->owner);
> > > + if (pi_state->owner)
> > > + wake_up_process(pi_state->owner);
> > And what handles or sanity checks the
On 22/09/16 22:02, Boris Ostrovsky wrote:
> On 09/22/2016 04:45 AM, Juergen Gross wrote:
>> The Xen pciback driver has a list of all pci devices it is ready to
>> seize. There is no check whether a to be added entry already exists.
>> While this might be no problem in the common case it might
On 22/09/16 22:02, Boris Ostrovsky wrote:
> On 09/22/2016 04:45 AM, Juergen Gross wrote:
>> The Xen pciback driver has a list of all pci devices it is ready to
>> seize. There is no check whether a to be added entry already exists.
>> While this might be no problem in the common case it might
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Leroy
commit 8540571e01f973d321b0821f4f32ed6e9ae8263c upstream.
Commit 7aef4136566b0 ("powerpc32: rewrite csum_partial_copy_generic()
based on
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Leroy
commit 8540571e01f973d321b0821f4f32ed6e9ae8263c upstream.
Commit 7aef4136566b0 ("powerpc32: rewrite csum_partial_copy_generic()
based on copy_tofrom_user()") introduced a bug
[+ Zhang Rui]
On Thu, Sep 22, 2016 at 05:10:42PM -0500, Bjorn Helgaas wrote:
> On Thu, Sep 22, 2016 at 01:31:01PM -0500, Bjorn Helgaas wrote:
> > On Thu, Sep 22, 2016 at 01:44:46PM +0100, Lorenzo Pieralisi wrote:
> > > On Thu, Sep 22, 2016 at 11:10:13AM +, Gabriele Paoloni wrote:
> > > > Hi
[+ Zhang Rui]
On Thu, Sep 22, 2016 at 05:10:42PM -0500, Bjorn Helgaas wrote:
> On Thu, Sep 22, 2016 at 01:31:01PM -0500, Bjorn Helgaas wrote:
> > On Thu, Sep 22, 2016 at 01:44:46PM +0100, Lorenzo Pieralisi wrote:
> > > On Thu, Sep 22, 2016 at 11:10:13AM +, Gabriele Paoloni wrote:
> > > > Hi
> Hi All,
>
> Resending this wider audience
>
> Currently I am working on AMD future platform. I am hitting the same bug of
> ATA Failure Regression reported in past.
> (https://patchwork.kernel.org/patch/6875661/) or
> http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
>
> I am
> Hi All,
>
> Resending this wider audience
>
> Currently I am working on AMD future platform. I am hitting the same bug of
> ATA Failure Regression reported in past.
> (https://patchwork.kernel.org/patch/6875661/) or
> http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
>
> I am
[...]
Is there anything else needed in msm sdhci driver so that the auto
tuning is taken care of?
>>>
>>>
>>> I am not familiar with any other than sdhci-esdhc-imx which supports
>>> the SDHCI_TUNING_MODE_3. I may be wrong though.
>>>
>>> In the sdhci-esdhc-imx case, enabling of auto
[...]
Is there anything else needed in msm sdhci driver so that the auto
tuning is taken care of?
>>>
>>>
>>> I am not familiar with any other than sdhci-esdhc-imx which supports
>>> the SDHCI_TUNING_MODE_3. I may be wrong though.
>>>
>>> In the sdhci-esdhc-imx case, enabling of auto
On Thu, 22 Sep 2016, Frank Haverkamp wrote:
> > On 12.09.2016, at 20:09, Sebastian Ott wrote:
> > Genwqe uses dma_alloc_coherent and depends on zero initialized memory. On
> > one occasion it ueses an explicit memset on others it uses un-initialized
> > memory.
> >
> >
On Thu, 22 Sep 2016, Frank Haverkamp wrote:
> > On 12.09.2016, at 20:09, Sebastian Ott wrote:
> > Genwqe uses dma_alloc_coherent and depends on zero initialized memory. On
> > one occasion it ueses an explicit memset on others it uses un-initialized
> > memory.
> >
> > This bug was covered
On Thu, Sep 22, 2016 at 05:13:38PM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> Correct the error message sent out in the case of a single
> bit error IRQ allocation.
>
> Signed-off-by: Thor Thayer
> ---
>
On Thu, Sep 22, 2016 at 05:13:38PM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> Correct the error message sent out in the case of a single
> bit error IRQ allocation.
>
> Signed-off-by: Thor Thayer
> ---
> drivers/edac/altera_edac.c |2 +-
> 1 file changed, 1
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote:
>
> dmesg -c
> echo 9 > /proc/sysrq-trigger
> modprobe cdc_acm
> echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
>
> [plug your device in]
>
> and provide the full output of dmesg after that.
That is not
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote:
>
> dmesg -c
> echo 9 > /proc/sysrq-trigger
> modprobe cdc_acm
> echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
>
> [plug your device in]
>
> and provide the full output of dmesg after that.
That is not
On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote:
> On Wed, Sep 21, 2016 at 11:16:35AM +0200, Johannes Stezenbach wrote:
> > There is an ADBG ("TI_DCOVE") in PMI2._STA, so Dollar Cove
> > sounds like a good guess.
>
> David (CC'd) is working on getting the Dollar Cove PMIC driver
>
Hi All,
Resending this wider audience
Currently I am working on AMD future platform. I am hitting the same bug of
ATA Failure Regression reported in past.
(https://patchwork.kernel.org/patch/6875661/) or
http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
I am newbie to this and
On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote:
> On Wed, Sep 21, 2016 at 11:16:35AM +0200, Johannes Stezenbach wrote:
> > There is an ADBG ("TI_DCOVE") in PMI2._STA, so Dollar Cove
> > sounds like a good guess.
>
> David (CC'd) is working on getting the Dollar Cove PMIC driver
>
Hi All,
Resending this wider audience
Currently I am working on AMD future platform. I am hitting the same bug of
ATA Failure Regression reported in past.
(https://patchwork.kernel.org/patch/6875661/) or
http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
I am newbie to this and
On 09/23/2016 11:42 AM, David Laight wrote:
> From: Vlastimil Babka
>> Sent: 22 September 2016 18:55
> ...
>> So in the case of select() it seems like the memory we need 6 bits per file
>> descriptor, multiplied by the highest possible file descriptor (nfds) as
>> passed
>> to the syscall.
On 09/23/2016 11:42 AM, David Laight wrote:
> From: Vlastimil Babka
>> Sent: 22 September 2016 18:55
> ...
>> So in the case of select() it seems like the memory we need 6 bits per file
>> descriptor, multiplied by the highest possible file descriptor (nfds) as
>> passed
>> to the syscall.
>
> Signed-off-by: Tomas Winkler
> Signed-off-by: Alexander Usyskin
Tested-by: Avri Altman
- mmc - full functionality. One issue found that was fixed on V6: patch V6 2/9.
- ufs - read & read counter only.
>
> Signed-off-by: Tomas Winkler
> Signed-off-by: Alexander Usyskin
Tested-by: Avri Altman
- mmc - full functionality. One issue found that was fixed on V6: patch V6 2/9.
- ufs - read & read counter only. Testing is still wip.
> +static int rpmb_request_verify(struct rpmb_dev *rdev,
On Friday, September 23, 2016 12:27:17 AM CEST zhichang.yuan wrote:
> For this patch sketch, I have a question.
> Do we call pci_address_to_pio in arch_of_address_to_pio to get the
> corresponding logical IO port
> for LPC??
No, of course not, that would be silly:
The argument to
On Friday, September 23, 2016 12:27:17 AM CEST zhichang.yuan wrote:
> For this patch sketch, I have a question.
> Do we call pci_address_to_pio in arch_of_address_to_pio to get the
> corresponding logical IO port
> for LPC??
No, of course not, that would be silly:
The argument to
Sorry for delay, I was offline. I'll try to return to this problem next
week, currently I can't even read this thread but at first glance the
proposed patch(es) do not look right...
On 09/21, Michal Hocko wrote:
>
> The further investigation shown that the tracer (strace) is stuck
> waiting for
Sorry for delay, I was offline. I'll try to return to this problem next
week, currently I can't even read this thread but at first glance the
proposed patch(es) do not look right...
On 09/21, Michal Hocko wrote:
>
> The further investigation shown that the tracer (strace) is stuck
> waiting for
On Fri, Sep 23, 2016 at 09:33:00PM +1200, Kai Huang wrote:
> How is this even possible? The spec clearly says under SEV only in long mode
> or PAE mode guest can control whether memory is encrypted via c-bit, and in
> other modes guest will be always in encrypted mode.
I was suggesting the
On Fri, Sep 23, 2016 at 09:33:00PM +1200, Kai Huang wrote:
> How is this even possible? The spec clearly says under SEV only in long mode
> or PAE mode guest can control whether memory is encrypted via c-bit, and in
> other modes guest will be always in encrypted mode.
I was suggesting the
This patch removes the empty function rmem_ion_device_release
Signed-off-by: Yannis Damigos
---
drivers/staging/android/ion/ion_of.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/staging/android/ion/ion_of.c
b/drivers/staging/android/ion/ion_of.c
This patch removes the empty function rmem_ion_device_release
Signed-off-by: Yannis Damigos
---
drivers/staging/android/ion/ion_of.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/staging/android/ion/ion_of.c
b/drivers/staging/android/ion/ion_of.c
index 49f052c..91c0642
From: Jagan Teki
Added basic dts support for MicroZed board.
- UART
- SDHCI
- Ethernet
Cc: Soren Brinkmann
Cc: Michal Simek
Signed-off-by: Jagan Teki
---
Changes for v3:
- Add Xilinx
From: Jagan Teki
Added basic dts support for MicroZed board.
- UART
- SDHCI
- Ethernet
Cc: Soren Brinkmann
Cc: Michal Simek
Signed-off-by: Jagan Teki
---
Changes for v3:
- Add Xilinx copyright
Changes for v2:
- Add SDHCI
- Add Ethernet
arch/arm/boot/dts/Makefile
From: Vlastimil Babka
> Sent: 22 September 2016 18:55
...
> So in the case of select() it seems like the memory we need 6 bits per file
> descriptor, multiplied by the highest possible file descriptor (nfds) as
> passed
> to the syscall. According to the man page of select:
>
> EINVAL
From: Vlastimil Babka
> Sent: 22 September 2016 18:55
...
> So in the case of select() it seems like the memory we need 6 bits per file
> descriptor, multiplied by the highest possible file descriptor (nfds) as
> passed
> to the syscall. According to the man page of select:
>
> EINVAL
First of all please stop sending your patches as a reply to an earlier
and completely unrelated series.
Second please prefix all TTM related patches with "drm/ttm:".
Additional to that I don't really see the point in renaming some of the
jump labels, if you call it "restart" or "lock_restart"
First of all please stop sending your patches as a reply to an earlier
and completely unrelated series.
Second please prefix all TTM related patches with "drm/ttm:".
Additional to that I don't really see the point in renaming some of the
jump labels, if you call it "restart" or "lock_restart"
On Tue, Sep 20, 2016 at 12:33 AM, Russell King - ARM Linux
wrote:
> On Fri, Sep 16, 2016 at 01:52:50PM +0200, Linus Walleij wrote:
>> Russell/ARM SoC: heads-up and ACK request.
>
> Fine with one exception:
>
>> diff --git a/arch/arm/mach-sa1100/h3xxx.c
On Tue, Sep 20, 2016 at 12:33 AM, Russell King - ARM Linux
wrote:
> On Fri, Sep 16, 2016 at 01:52:50PM +0200, Linus Walleij wrote:
>> Russell/ARM SoC: heads-up and ACK request.
>
> Fine with one exception:
>
>> diff --git a/arch/arm/mach-sa1100/h3xxx.c b/arch/arm/mach-sa1100/h3xxx.c
>> index
Add an additional status check before starting a transaction. If the
check fails wait for some time to tolerate multi-master mode. After the
timeout expires trigger the recovery.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon-core.c | 29
Add an additional status check before starting a transaction. If the
check fails wait for some time to tolerate multi-master mode. After the
timeout expires trigger the recovery.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon-core.c | 29 +
1 file
2016-09-23 17:35 GMT+08:00 Paolo Bonzini :
>
>
> On 23/09/2016 01:18, Radim Krčmář wrote:
>> We've had 10 page-sized bitmaps that were being allocated and freed one
>> by one when we could just use a cycle and MSR bitmaps had a lot of
>> useless code lying around.
>>
>> This
On Sat, Sep 17, 2016 at 5:05 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 17 Sep 2016 16:56:56 +0200
>
> Several update suggestions were taken into account
> from static source code analysis.
All look very nice!
2016-09-23 17:35 GMT+08:00 Paolo Bonzini :
>
>
> On 23/09/2016 01:18, Radim Krčmář wrote:
>> We've had 10 page-sized bitmaps that were being allocated and freed one
>> by one when we could just use a cycle and MSR bitmaps had a lot of
>> useless code lying around.
>>
>> This patch
>> * enumerates
On Sat, Sep 17, 2016 at 5:05 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 17 Sep 2016 16:56:56 +0200
>
> Several update suggestions were taken into account
> from static source code analysis.
All look very nice!
Reviewed-by: Linus Walleij
Vinod, please apply them all!
Do not infinitely retry register readq and writeq operations
in order to not lock up the CPU in case the TWSI gets stuck.
Return -ETIMEDOUT in case of a failed data read. For all other
cases just return so subsequent operations will fail
and trigger the recovery.
Signed-off-by: Jan Glauber
Do not infinitely retry register readq and writeq operations
in order to not lock up the CPU in case the TWSI gets stuck.
Return -ETIMEDOUT in case of a failed data read. For all other
cases just return so subsequent operations will fail
and trigger the recovery.
Signed-off-by: Jan Glauber
---
Hi Wolfram,
here are the remaining two patches with iopoll.h usage and a timed wait
before entering the recovery on a failed bus check.
thanks,
Jan
-
Jan Glauber (2):
i2c: octeon: thunderx: Check bus state before starting a transaction
i2c: octeon: thunderx: Limit
Hi Wolfram,
here are the remaining two patches with iopoll.h usage and a timed wait
before entering the recovery on a failed bus check.
thanks,
Jan
-
Jan Glauber (2):
i2c: octeon: thunderx: Check bus state before starting a transaction
i2c: octeon: thunderx: Limit
On 23/09/2016 01:18, Radim Krčmář wrote:
> We've had 10 page-sized bitmaps that were being allocated and freed one
> by one when we could just use a cycle and MSR bitmaps had a lot of
> useless code lying around.
>
> This patch
> * enumerates vmx bitmaps and uses an array to store them
> *
On 23/09/2016 01:18, Radim Krčmář wrote:
> We've had 10 page-sized bitmaps that were being allocated and freed one
> by one when we could just use a cycle and MSR bitmaps had a lot of
> useless code lying around.
>
> This patch
> * enumerates vmx bitmaps and uses an array to store them
> *
On 09/22, Waiman Long wrote:
>
> This patch is currently only active for 64-bit architectures.
Why?
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2485,6 +2485,16 @@ void __set_current_blocked(const sigset_t *newset)
> {
> struct task_struct *tsk = current;
>
> + /*
> +
On 09/22, Waiman Long wrote:
>
> This patch is currently only active for 64-bit architectures.
Why?
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2485,6 +2485,16 @@ void __set_current_blocked(const sigset_t *newset)
> {
> struct task_struct *tsk = current;
>
> + /*
> +
On Fri, Sep 23, 2016 at 09:05:50AM +0200, Daniel Vetter wrote:
> On Thu, Sep 22, 2016 at 4:14 PM, Brian Starkey wrote:
> > On Thu, Sep 22, 2016 at 04:22:40AM -0700, Sean Paul wrote:
> >>
> >> On Thu, Sep 22, 2016 at 3:51 AM, Russell King - ARM Linux
> >>
On Fri, Sep 23, 2016 at 09:05:50AM +0200, Daniel Vetter wrote:
> On Thu, Sep 22, 2016 at 4:14 PM, Brian Starkey wrote:
> > On Thu, Sep 22, 2016 at 04:22:40AM -0700, Sean Paul wrote:
> >>
> >> On Thu, Sep 22, 2016 at 3:51 AM, Russell King - ARM Linux
> >> wrote:
> >>>
> >>> On Thu, Sep 22, 2016
On 23/09/16 06:37, Borislav Petkov wrote:
On Thu, Sep 22, 2016 at 08:23:36PM +0200, Paolo Bonzini wrote:
Unless this is part of some spec, it's easier if things are the same in
SME and SEV.
Yeah, I was pondering over how sprinkling sev_active checks might not be
so clean.
I'm wondering if
On 23/09/16 06:37, Borislav Petkov wrote:
On Thu, Sep 22, 2016 at 08:23:36PM +0200, Paolo Bonzini wrote:
Unless this is part of some spec, it's easier if things are the same in
SME and SEV.
Yeah, I was pondering over how sprinkling sev_active checks might not be
so clean.
I'm wondering if
On 23/09/16 10:25, Christoffer Dall wrote:
> On Fri, Sep 23, 2016 at 03:13:25PM +0800, Alison Wang wrote:
>> The ARMv8 architecture supports two execution state, AArch64 and
>> AArch32. To support KVM in AArch32 execution state for ARMv8, Cortex-A53
>> and Cortex-A72 need to be added for
On 23/09/16 10:25, Christoffer Dall wrote:
> On Fri, Sep 23, 2016 at 03:13:25PM +0800, Alison Wang wrote:
>> The ARMv8 architecture supports two execution state, AArch64 and
>> AArch32. To support KVM in AArch32 execution state for ARMv8, Cortex-A53
>> and Cortex-A72 need to be added for
On Thu, Sep 22, 2016 at 01:33:59PM -0500, Eric W. Biederman wrote:
>
> ebied...@xmission.com (Eric W. Biederman) writes:
>
> > Greg please apply the following patches to tty-next. If tty-next is not
> > the proper tree please let me know and I will take these patches through
> > my user
On Thu, Sep 22, 2016 at 01:33:59PM -0500, Eric W. Biederman wrote:
>
> ebied...@xmission.com (Eric W. Biederman) writes:
>
> > Greg please apply the following patches to tty-next. If tty-next is not
> > the proper tree please let me know and I will take these patches through
> > my user
Hi Jassi,
Please see my inline reply.
On Thu, 2016-09-22 at 13:47 +0530, Jassi Brar wrote:
> On Mon, Sep 5, 2016 at 7:14 AM, HS Liao wrote:
[...]
> > +struct cmdq_base *cmdq_register_device(struct device *dev)
> > +{
> > + struct cmdq_base *cmdq_base;
> > +
On Thu, 2016-09-22 at 13:22 +0530, Jassi Brar wrote:
> On Mon, Sep 5, 2016 at 7:14 AM, HS Liao wrote:
> > Use clk_disable_unprepare instead of clk_disable to save more energy
> > when CMDQ is idle.
> >
> > Signed-off-by: HS Liao
> > ---
> >
Hi Jassi,
Please see my inline reply.
On Thu, 2016-09-22 at 13:47 +0530, Jassi Brar wrote:
> On Mon, Sep 5, 2016 at 7:14 AM, HS Liao wrote:
[...]
> > +struct cmdq_base *cmdq_register_device(struct device *dev)
> > +{
> > + struct cmdq_base *cmdq_base;
> > + struct resource res;
> >
On Thu, 2016-09-22 at 13:22 +0530, Jassi Brar wrote:
> On Mon, Sep 5, 2016 at 7:14 AM, HS Liao wrote:
> > Use clk_disable_unprepare instead of clk_disable to save more energy
> > when CMDQ is idle.
> >
> > Signed-off-by: HS Liao
> > ---
> > drivers/mailbox/mtk-cmdq.c | 54
> >
* Thomas Gleixner wrote:
> On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> > On Fri, Sep 23, 2016 at 10:00:37AM +0200, Thomas Gleixner wrote:
> > > On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> > > > It is, might_sleep() implies might_resched(). In fact, that's all what
> > > >
* Thomas Gleixner wrote:
> On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> > On Fri, Sep 23, 2016 at 10:00:37AM +0200, Thomas Gleixner wrote:
> > > On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> > > > It is, might_sleep() implies might_resched(). In fact, that's all what
> > > > PREEMPT_VOLUNTARY
On Thu, Sep 22, 2016 at 10:37:03AM -0700, Hugh Dickins wrote:
> Under swapping load on huge tmpfs, /proc/meminfo's Committed_AS grows
> bigger and bigger: just a cosmetic issue for most users, but disabling
> for those who run without overcommit (/proc/sys/vm/overcommit_memory 2).
>
>
On Thu, Sep 22, 2016 at 10:37:03AM -0700, Hugh Dickins wrote:
> Under swapping load on huge tmpfs, /proc/meminfo's Committed_AS grows
> bigger and bigger: just a cosmetic issue for most users, but disabling
> for those who run without overcommit (/proc/sys/vm/overcommit_memory 2).
>
>
On Fri, Sep 23, 2016 at 03:13:25PM +0800, Alison Wang wrote:
> The ARMv8 architecture supports two execution state, AArch64 and
> AArch32. To support KVM in AArch32 execution state for ARMv8, Cortex-A53
> and Cortex-A72 need to be added for target-specific checks.
>
> Signed-off-by: Alison Wang
On Fri, Sep 23, 2016 at 03:13:25PM +0800, Alison Wang wrote:
> The ARMv8 architecture supports two execution state, AArch64 and
> AArch32. To support KVM in AArch32 execution state for ARMv8, Cortex-A53
> and Cortex-A72 need to be added for target-specific checks.
>
> Signed-off-by: Alison Wang
On 09/17/2016 04:47 AM, John Stultz wrote:
From: Srinivas Kandagatla
This patch enables the Audio Data and Clock pads to the adv7533 bridge.
Without this patch audio can not be played.
Cc: David Airlie
Cc: Archit Taneja
On 09/17/2016 04:47 AM, John Stultz wrote:
From: Srinivas Kandagatla
This patch enables the Audio Data and Clock pads to the adv7533 bridge.
Without this patch audio can not be played.
Cc: David Airlie
Cc: Archit Taneja
Cc: Laurent Pinchart
Cc: Wolfram Sang
Cc: Srinivas Kandagatla
Cc:
On Thu, Sep 22, 2016 at 10:44 PM, Gerd Hoffmann wrote:
> On Mo, 2016-09-19 at 17:13 +0100, Eric Anholt wrote:
>> This gets us hotplug detection of HDMI, so that graphics now works at
>> boot. Tested with watching the output of xrandr while plugging and
>> unplugging the HDMI
On Thu, Sep 22, 2016 at 10:44 PM, Gerd Hoffmann wrote:
> On Mo, 2016-09-19 at 17:13 +0100, Eric Anholt wrote:
>> This gets us hotplug detection of HDMI, so that graphics now works at
>> boot. Tested with watching the output of xrandr while plugging and
>> unplugging the HDMI cable.
>
> Very
On 09/17/2016 04:47 AM, John Stultz wrote:
This patch adds support to Audio for both adv7511 and adv7533
bridge chips.
This patch was originally from [1] by Lars-Peter Clausen
and was adapted by Archit Taneja and
Srinivas Kandagatla
On 09/17/2016 04:47 AM, John Stultz wrote:
This patch adds support to Audio for both adv7511 and adv7533
bridge chips.
This patch was originally from [1] by Lars-Peter Clausen
and was adapted by Archit Taneja and
Srinivas Kandagatla .
Then I heavily reworked it to use the hdmi-codec
On Tue, Sep 20, 2016 at 10:32 AM, Nava kishore Manne
wrote:
> From: Nava kishore Manne
>
> This patch adds zynq specific check for bank 0 pins 7 and 8
> are special and cannot be used as inputs
>
> Signed-off-by: Nava kishore Manne
On Tue, Sep 20, 2016 at 10:32 AM, Nava kishore Manne
wrote:
> From: Nava kishore Manne
>
> This patch adds zynq specific check for bank 0 pins 7 and 8
> are special and cannot be used as inputs
>
> Signed-off-by: Nava kishore Manne
I'm waiting for a revised version of this patch with comments
On Fri, Sep 23, 2016 at 10:43:27AM +0200, Holger Hoffstätte wrote:
> On 09/23/16 10:14, Greg Kroah-Hartman wrote:
> > On Thu, Sep 22, 2016 at 09:56:28PM +0200, Holger Hoffstätte wrote:
> >> did you forget to add the -net patches in stable-queue.git/tree/net-4.4
> >> or are they on hold for some
On Fri, Sep 23, 2016 at 10:43:27AM +0200, Holger Hoffstätte wrote:
> On 09/23/16 10:14, Greg Kroah-Hartman wrote:
> > On Thu, Sep 22, 2016 at 09:56:28PM +0200, Holger Hoffstätte wrote:
> >> did you forget to add the -net patches in stable-queue.git/tree/net-4.4
> >> or are they on hold for some
On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> On Fri, Sep 23, 2016 at 10:00:37AM +0200, Thomas Gleixner wrote:
> > On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> > > It is, might_sleep() implies might_resched(). In fact, that's all what
> > > PREEMPT_VOLUNTARY is, make the might_sleep() debug test
On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> On Fri, Sep 23, 2016 at 10:00:37AM +0200, Thomas Gleixner wrote:
> > On Fri, 23 Sep 2016, Peter Zijlstra wrote:
> > > It is, might_sleep() implies might_resched(). In fact, that's all what
> > > PREEMPT_VOLUNTARY is, make the might_sleep() debug test
On Fri 23-09-16 16:44:26, Hillf Danton wrote:
> On Friday, September 23, 2016 4:32 PM, Michal Hocko wrote
> > On Fri 23-09-16 16:29:36, Hillf Danton wrote:
> > [...]
> > > > @@ -3659,6 +3661,15 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned
> > > > int order,
> > > > else
> > > >
On Fri 23-09-16 16:44:26, Hillf Danton wrote:
> On Friday, September 23, 2016 4:32 PM, Michal Hocko wrote
> > On Fri 23-09-16 16:29:36, Hillf Danton wrote:
> > [...]
> > > > @@ -3659,6 +3661,15 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned
> > > > int order,
> > > > else
> > > >
axxia_i2c_probe() does not disable clock in case of failure
in i2c_add_adapter(). Also it ignores returned value from
clk_prepare_enable().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/i2c/busses/i2c-axxia.c
On 21-9-2016 8:23, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This function is called from get_station callback which means that every
> time user space was getting/dumping station(s) we were leaking 2 KiB.
>
Acked-by: Arend van Spriel
>
axxia_i2c_probe() does not disable clock in case of failure
in i2c_add_adapter(). Also it ignores returned value from
clk_prepare_enable().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/i2c/busses/i2c-axxia.c | 14 --
1
On 21-9-2016 8:23, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This function is called from get_station callback which means that every
> time user space was getting/dumping station(s) we were leaking 2 KiB.
>
Acked-by: Arend van Spriel
> Signed-off-by: Rafał Miłecki
> Fixes: 1f0dc59a6de
Hi,
There should be some fixes in linux-next today for this.
/Jesper
On Thu, Sep 22, 2016 at 09:15:38PM +0800, kbuild test robot wrote:
> Hi Daniel,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head:
Hi,
There should be some fixes in linux-next today for this.
/Jesper
On Thu, Sep 22, 2016 at 09:15:38PM +0800, kbuild test robot wrote:
> Hi Daniel,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head:
From: Sunil Goutham
These patches add byte queue limit support and also fixes a regression
issue introduced by commit
'net: thunderx: Use netdev's name for naming VF's interrupts'
Changes from v1:
- As suggested added 'Fixes' tag with commit id of previous commit
which
From: Sunil Goutham
These patches add byte queue limit support and also fixes a regression
issue introduced by commit
'net: thunderx: Use netdev's name for naming VF's interrupts'
Changes from v1:
- As suggested added 'Fixes' tag with commit id of previous commit
which cuased issue.
- Also
The axp20x driver contains device specific and device independant parts.
This patch moves the independant parts to new .c/.h files.
Signed-off-by: Jean-Francois Moine
---
drivers/regulator/Makefile | 2 +-
drivers/regulator/axp-regulator.c| 308
The axp20x driver contains device specific and device independant parts.
This patch moves the independant parts to new .c/.h files.
Signed-off-by: Jean-Francois Moine
---
drivers/regulator/Makefile | 2 +-
drivers/regulator/axp-regulator.c| 308 ++
1301 - 1400 of 1596 matches
Mail list logo