Hi,
> From: Chanwoo Choi
> Sent: Wednesday, November 30, 2016 2:58 PM
>
> This patch replaces the deprecated extcon API as following:
> - extcon_get_cable_state_() -> extcon_get_state()
>
> Signed-off-by: Chanwoo Choi
Thank you for the patch!
Acked-by: Yoshihiro
Hi,
> From: Chanwoo Choi
> Sent: Wednesday, November 30, 2016 2:58 PM
>
> This patch replaces the deprecated extcon API as following:
> - extcon_get_cable_state_() -> extcon_get_state()
>
> Signed-off-by: Chanwoo Choi
Thank you for the patch!
Acked-by: Yoshihiro Shimoda
Best regards,
From: Randy Dunlap
Keep fonts together and indented (in menu) as much as possible.
This moves the Sparc font choices to the end of the menu since they
have different dependencies.
Signed-off-by: Randy Dunlap
Cc: Geert Uytterhoeven
From: Randy Dunlap
Keep fonts together and indented (in menu) as much as possible.
This moves the Sparc font choices to the end of the menu since they
have different dependencies.
Signed-off-by: Randy Dunlap
Cc: Geert Uytterhoeven
---
lib/fonts/Kconfig | 16
1 file
Hi,
> From: Chanwoo Choi
> Sent: Wednesday, November 30, 2016 2:57 PM
>
> This patch replaces the deprecated extcon API as following:
> - extcon_set_cable_state_() -> extcon_set_state_sync()
>
> Signed-off-by: Chanwoo Choi
Thank you for the patch!
Acked-by: Yoshihiro
Hi,
> From: Chanwoo Choi
> Sent: Wednesday, November 30, 2016 2:57 PM
>
> This patch replaces the deprecated extcon API as following:
> - extcon_set_cable_state_() -> extcon_set_state_sync()
>
> Signed-off-by: Chanwoo Choi
Thank you for the patch!
Acked-by: Yoshihiro Shimoda
Best regards,
Support for setting the RGMII_IDMODE bit was added in commit:
"drivers: net: cpsw-phy-sel: add support to configure rgmii internal delay"
However, that commit did not add the symmetrical clearing of the bit
by way of setting it in "mask". Add it here.
Note that the documentation marks clearing
Support for setting the RGMII_IDMODE bit was added in commit:
"drivers: net: cpsw-phy-sel: add support to configure rgmii internal delay"
However, that commit did not add the symmetrical clearing of the bit
by way of setting it in "mask". Add it here.
Note that the documentation marks clearing
This patch introduces the power domain driver of zx296718
which belongs to zte's 2967 family.
Signed-off-by: Baoyou Xie
---
drivers/soc/zte/Makefile | 2 +-
drivers/soc/zte/zx296718_pm_domains.c | 182 ++
2 files changed, 183
This patch introduces the power domain driver of zx296718
which belongs to zte's 2967 family.
Signed-off-by: Baoyou Xie
---
drivers/soc/zte/Makefile | 2 +-
drivers/soc/zte/zx296718_pm_domains.c | 182 ++
2 files changed, 183 insertions(+), 1
On Mon, Dec 05, 2016 at 10:19:23AM -0500, Pan Xinhui wrote:
> Add two corresponding helper functions to support pv-qspinlock.
>
> For normal use, __spin_yield_cpu will confer current vcpu slices to the
> target vcpu(say, a lock holder). If target vcpu is not specified or it
> is in running state,
在 2016/12/6 08:58, Boqun Feng 写道:
On Mon, Dec 05, 2016 at 10:19:22AM -0500, Pan Xinhui wrote:
pSeries/powerNV will use qspinlock from now on.
Signed-off-by: Pan Xinhui
---
arch/powerpc/platforms/pseries/Kconfig | 8
1 file changed, 8 insertions(+)
On Mon, Dec 05, 2016 at 10:19:23AM -0500, Pan Xinhui wrote:
> Add two corresponding helper functions to support pv-qspinlock.
>
> For normal use, __spin_yield_cpu will confer current vcpu slices to the
> target vcpu(say, a lock holder). If target vcpu is not specified or it
> is in running state,
在 2016/12/6 08:58, Boqun Feng 写道:
On Mon, Dec 05, 2016 at 10:19:22AM -0500, Pan Xinhui wrote:
pSeries/powerNV will use qspinlock from now on.
Signed-off-by: Pan Xinhui
---
arch/powerpc/platforms/pseries/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git
On Wed, 2016-09-21 at 10:11 +0200, Christophe Leroy wrote:
> Today there are two implementations of hugetlbpages which are managed
> by exclusive #ifdefs:
> * FSL_BOOKE: several directory entries points to the same single hugepage
> * BOOK3S: one upper level directory entry points to a table of
On Wed, 2016-09-21 at 10:11 +0200, Christophe Leroy wrote:
> Today there are two implementations of hugetlbpages which are managed
> by exclusive #ifdefs:
> * FSL_BOOKE: several directory entries points to the same single hugepage
> * BOOK3S: one upper level directory entry points to a table of
On 12/5/2016 1:45 AM, Sergei Shtylyov wrote:
Hello!
On 12/5/2016 9:57 AM, Santosh Shilimkar wrote:
[...]
-void rds_walk_conn_path_info(struct socket *sock, unsigned int len,
+static void rds_walk_conn_path_info(struct socket *sock, unsigned int
len,
struct
On 12/5/2016 1:45 AM, Sergei Shtylyov wrote:
Hello!
On 12/5/2016 9:57 AM, Santosh Shilimkar wrote:
[...]
-void rds_walk_conn_path_info(struct socket *sock, unsigned int len,
+static void rds_walk_conn_path_info(struct socket *sock, unsigned int
len,
struct
correct waiman's address.
在 2016/12/6 08:47, Boqun Feng 写道:
On Mon, Dec 05, 2016 at 10:19:21AM -0500, Pan Xinhui wrote:
This patch add basic code to enable qspinlock on powerpc. qspinlock is
one kind of fairlock implementation. And seen some performance improvement
under some scenarios.
correct waiman's address.
在 2016/12/6 08:47, Boqun Feng 写道:
On Mon, Dec 05, 2016 at 10:19:21AM -0500, Pan Xinhui wrote:
This patch add basic code to enable qspinlock on powerpc. qspinlock is
one kind of fairlock implementation. And seen some performance improvement
under some scenarios.
That message isn't at all clear -- what does "Legacy x87" even
mean?
Clarify it. If there's no FPU, say "x86/fpu: No FPU detected". If
there's an FPU that doesn't have XSAVE, say "x86/fpu: Pre-XSAVE x87
FPU detected".
Signed-off-by: Andy Lutomirski
---
That message isn't at all clear -- what does "Legacy x87" even
mean?
Clarify it. If there's no FPU, say "x86/fpu: No FPU detected". If
there's an FPU that doesn't have XSAVE, say "x86/fpu: Pre-XSAVE x87
FPU detected".
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/fpu/xstate.c | 7
The old code didn't work at all because it adjusted the current caps
instead of the forced caps. Anything it did would be undone later
during cpu identification. Fix that and, while we're at it, improve
the logging and don't bother running it if CPUID is available.
Signed-off-by: Andy
Calling get_cpu_cap() will reset a bunch of CPU features. This will
cause the system to lose track of force-set and force-cleared
featueres in the words that are reset until the end of CPU
initialization. This can cause X86_FEATURE_FPU, for example, to
change back and forth during boot and
Calling get_cpu_cap() will reset a bunch of CPU features. This will
cause the system to lose track of force-set and force-cleared
featueres in the words that are reset until the end of CPU
initialization. This can cause X86_FEATURE_FPU, for example, to
change back and forth during boot and
The old code didn't work at all because it adjusted the current caps
instead of the forced caps. Anything it did would be undone later
during cpu identification. Fix that and, while we're at it, improve
the logging and don't bother running it if CPUID is available.
Signed-off-by: Andy
On Wed, 16 Nov 2016, Dan Williams wrote:
> The device-dax implementation originally tried to be tricky and allow
> private read-only mappings, but in the process allowed writable
> MAP_PRIVATE + MAP_NORESERVE mappings. For simplicity and predictability
> just fail all private mapping attempts
From: Borislav Petkov
Add a synthetic CPUID flag denoting whether the CPU sports the CPUID
instruction or not. This will come useful later when accomodating
CPUID-less CPUs.
Signed-off-by: Borislav Petkov
Signed-off-by: Andy Lutomirski
---
On Wed, 16 Nov 2016, Dan Williams wrote:
> The device-dax implementation originally tried to be tricky and allow
> private read-only mappings, but in the process allowed writable
> MAP_PRIVATE + MAP_NORESERVE mappings. For simplicity and predictability
> just fail all private mapping attempts
From: Borislav Petkov
Add a synthetic CPUID flag denoting whether the CPU sports the CPUID
instruction or not. This will come useful later when accomodating
CPUID-less CPUs.
Signed-off-by: Borislav Petkov
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/cpufeatures.h | 2 +-
We would never print "Giving up, no FPU found" because
X86_FEATURE_FPU was in REQUIRED_MASK on non-FPU-emulating builds, so
the boot_cpu_has() test didn't do anything.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/fpu/init.c | 2 +-
1 file changed, 1 insertion(+), 1
We would never print "Giving up, no FPU found" because
X86_FEATURE_FPU was in REQUIRED_MASK on non-FPU-emulating builds, so
the boot_cpu_has() test didn't do anything.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/fpu/init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Our CPUID-less FPU detection code was terminally broken and, as far
as I can tell, it's been broken for a long, long time. This series
tries to improve the situation.
Thoughts?
Andy Lutomirski (5):
x86/cpu: Factor out application of forced cpu caps
x86/cpu: Re-apply forced caps every time
Our CPUID-less FPU detection code was terminally broken and, as far
as I can tell, it's been broken for a long, long time. This series
tries to improve the situation.
Thoughts?
Andy Lutomirski (5):
x86/cpu: Factor out application of forced cpu caps
x86/cpu: Re-apply forced caps every time
There are multiple call sites that apply forced CPU caps. Factor
them into a helper.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/cpu/common.c | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c
There are multiple call sites that apply forced CPU caps. Factor
them into a helper.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/cpu/common.c | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c
On Mon, Dec 05, 2016 at 10:19:22AM -0500, Pan Xinhui wrote:
> pSeries/powerNV will use qspinlock from now on.
>
> Signed-off-by: Pan Xinhui
> ---
> arch/powerpc/platforms/pseries/Kconfig | 8
> 1 file changed, 8 insertions(+)
>
> diff --git
On Mon, Dec 05, 2016 at 10:19:22AM -0500, Pan Xinhui wrote:
> pSeries/powerNV will use qspinlock from now on.
>
> Signed-off-by: Pan Xinhui
> ---
> arch/powerpc/platforms/pseries/Kconfig | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/powerpc/platforms/pseries/Kconfig
>
Hi Rob
> I'd expect the top level node to be the card node that knows how to find
> all the components. The graph should reflect the data flow. For example,
> the data goes to audio DSP to I2S host to codec to amp.
Do you mean, is this OK for OF graph ?
in driver point of view, "I2S" is
Hi Rob
> I'd expect the top level node to be the card node that knows how to find
> all the components. The graph should reflect the data flow. For example,
> the data goes to audio DSP to I2S host to codec to amp.
Do you mean, is this OK for OF graph ?
in driver point of view, "I2S" is
From: Nikita Yushchenko
Date: Mon, 5 Dec 2016 20:41:01 +0300
> Commit 4dfb80d18d05 ("net: fec: cache statistics while device is down")
> introduced unconditional statistics-related actions.
I do not see this commit in any of my trees:
[davem@localhost
Hi Takashi,
On Fri, Dec 02, 2016 at 11:55:07AM +0100, Takashi Iwai wrote:
> On Thu, 01 Dec 2016 08:19:46 +0100,
> Takashi Iwai wrote:
> >
> > On Thu, 01 Dec 2016 03:29:23 +0100,
> > Dmitry Torokhov wrote:
> > >
> > > Hi Takashi,
> > >
> > > On Mon, Nov 28, 2016 at 02:56:36PM +0100, Takashi
From: Nikita Yushchenko
Date: Mon, 5 Dec 2016 20:41:01 +0300
> Commit 4dfb80d18d05 ("net: fec: cache statistics while device is down")
> introduced unconditional statistics-related actions.
I do not see this commit in any of my trees:
[davem@localhost net-next]$ git describe 4dfb80d18d05
Hi Takashi,
On Fri, Dec 02, 2016 at 11:55:07AM +0100, Takashi Iwai wrote:
> On Thu, 01 Dec 2016 08:19:46 +0100,
> Takashi Iwai wrote:
> >
> > On Thu, 01 Dec 2016 03:29:23 +0100,
> > Dmitry Torokhov wrote:
> > >
> > > Hi Takashi,
> > >
> > > On Mon, Nov 28, 2016 at 02:56:36PM +0100, Takashi
On Sat, Dec 3, 2016 at 1:52 AM, Jani Nikula wrote:
> On Sat, 03 Dec 2016, Matt Turner wrote:
>> From these instructions, users assume that /sys/class/drm/card0/error
>> contains all the information a developer needs to diagnose and fix a GPU
>>
On Sat, Dec 3, 2016 at 1:52 AM, Jani Nikula wrote:
> On Sat, 03 Dec 2016, Matt Turner wrote:
>> From these instructions, users assume that /sys/class/drm/card0/error
>> contains all the information a developer needs to diagnose and fix a GPU
>> hang.
>>
>> In fact it doesn't, and we have no
Add the following files to .gitignore
compile
libsrc/libusbip_la-sysfs_utils.lo
libsrc/libusbip_la-usbip_device_driver.lo
libsrc/libusbip_la-usbip_host_common.lo
Signed-off-by: Shuah Khan
---
tools/usb/usbip/.gitignore | 4
1 file changed, 4 insertions(+)
diff
Add the following files to .gitignore
compile
libsrc/libusbip_la-sysfs_utils.lo
libsrc/libusbip_la-usbip_device_driver.lo
libsrc/libusbip_la-usbip_host_common.lo
Signed-off-by: Shuah Khan
---
tools/usb/usbip/.gitignore | 4
1 file changed, 4 insertions(+)
diff --git
On 11/29/2016 10:55 AM, Laura Abbott wrote:
> __pa_symbol is technically the marco that should be used for kernel
> symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which
> will do bounds checking. As part of this, introduce lm_alias, a
> macro which wraps the __va(__pa(...)) idiom
On 11/29/2016 10:55 AM, Laura Abbott wrote:
> __pa_symbol is technically the marco that should be used for kernel
> symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which
> will do bounds checking. As part of this, introduce lm_alias, a
> macro which wraps the __va(__pa(...)) idiom
Many Motorola phones like droid 4 are using a custom PMIC called CPCAP
or 6556002. We can support it's core features quite easily with regmap_spi
and regmap_irq.
The children of cpcap, such as regulators, ADC and USB, can be just regular
device drivers and defined in the dts file. They get probed
Many Motorola phones like droid 4 are using a custom PMIC called CPCAP
or 6556002. We can support it's core features quite easily with regmap_spi
and regmap_irq.
The children of cpcap, such as regulators, ADC and USB, can be just regular
device drivers and defined in the dts file. They get probed
On Mon, Dec 05, 2016 at 10:19:21AM -0500, Pan Xinhui wrote:
> This patch add basic code to enable qspinlock on powerpc. qspinlock is
> one kind of fairlock implementation. And seen some performance improvement
> under some scenarios.
>
> queued_spin_unlock() release the lock by just one write of
On Mon, Dec 05, 2016 at 10:19:21AM -0500, Pan Xinhui wrote:
> This patch add basic code to enable qspinlock on powerpc. qspinlock is
> one kind of fairlock implementation. And seen some performance improvement
> under some scenarios.
>
> queued_spin_unlock() release the lock by just one write of
From: Herbert Xu
Date: Mon, 5 Dec 2016 15:28:21 +0800
> It is wrong to schedule a work from sk_destruct using the socket
> as the memory reserve because the socket will be freed immediately
> after the return from sk_destruct.
>
> Instead we should do the deferral
From: Herbert Xu
Date: Mon, 5 Dec 2016 15:28:21 +0800
> It is wrong to schedule a work from sk_destruct using the socket
> as the memory reserve because the socket will be freed immediately
> after the return from sk_destruct.
>
> Instead we should do the deferral prior to sk_free.
>
> This
INCI_VOICECODEC dependency for
> CQ0093VC")
>
> I have used the sound-asoc tree from next-20161205 for today.
As I indicated on cover letter, this patch is based on
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ::
for-mfd-next
Especially this commit
INCI_VOICECODEC dependency for
> CQ0093VC")
>
> I have used the sound-asoc tree from next-20161205 for today.
As I indicated on cover letter, this patch is based on
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ::
for-mfd-next
Especially this commit
I noticed some wakeirq flakeyness with consumer drivers not using
autosuspend. For drivers not using autosuspend, the wakeirq may never
get unmasked in rpm_suspend() because of irq desc->depth.
We are configuring dedicated wakeirqs to start with IRQ_NOAUTOEN as we
naturally don't want them
On 12/05/2016 04:21 PM, Laurent Pinchart wrote:
> Hi Shuah,
>
> On Monday 05 Dec 2016 15:44:30 Shuah Khan wrote:
>> On 11/30/2016 03:01 PM, Shuah Khan wrote:
>>> Change ALSA driver to use Media Controller API to share media resources
>>> with DVB, and V4L2 drivers on a AU0828 media device.
>>>
On 12/05/2016 04:21 PM, Laurent Pinchart wrote:
> Hi Shuah,
>
> On Monday 05 Dec 2016 15:44:30 Shuah Khan wrote:
>> On 11/30/2016 03:01 PM, Shuah Khan wrote:
>>> Change ALSA driver to use Media Controller API to share media resources
>>> with DVB, and V4L2 drivers on a AU0828 media device.
>>>
I noticed some wakeirq flakeyness with consumer drivers not using
autosuspend. For drivers not using autosuspend, the wakeirq may never
get unmasked in rpm_suspend() because of irq desc->depth.
We are configuring dedicated wakeirqs to start with IRQ_NOAUTOEN as we
naturally don't want them
On Mon, Dec 5, 2016 at 4:28 PM, John Stultz wrote:
> On Tue, Nov 22, 2016 at 4:57 PM, John Stultz wrote:
>> On Tue, Nov 8, 2016 at 4:12 PM, Andy Lutomirski wrote:
>>> On Tue, Nov 8, 2016 at 4:03 PM, Alexei Starovoitov
>>>
On Mon, Dec 5, 2016 at 4:28 PM, John Stultz wrote:
> On Tue, Nov 22, 2016 at 4:57 PM, John Stultz wrote:
>> On Tue, Nov 8, 2016 at 4:12 PM, Andy Lutomirski wrote:
>>> On Tue, Nov 8, 2016 at 4:03 PM, Alexei Starovoitov
>>> wrote:
On Tue, Nov 08, 2016 at 03:51:40PM -0800, Andy Lutomirski
Any comments on this patch series?
Thanks
Jin Yao
On 11/29/2016 10:55 PM, Jin Yao wrote:
It would be useful for perf to support a mode to query the
inline stack for callgraph addresses. This would simplify
finding the right code in code that does a lot of inlining.
For example, the c code:
Any comments on this patch series?
Thanks
Jin Yao
On 11/29/2016 10:55 PM, Jin Yao wrote:
It would be useful for perf to support a mode to query the
inline stack for callgraph addresses. This would simplify
finding the right code in code that does a lot of inlining.
For example, the c code:
On Mon, Dec 5, 2016 at 3:52 PM, Duc Dang wrote:
> Hi Jon,
>
> On Mon, Dec 5, 2016 at 3:27 PM, Jon Masters wrote:
>> Duc, Aleksey, all,
>>
>> I have a question about this...
>>
>> On 12/05/2016 01:51 PM, Duc Dang wrote:
>>> On Mon, Dec 5, 2016 at 5:05 AM, Aleksey
On Mon, Dec 5, 2016 at 3:52 PM, Duc Dang wrote:
> Hi Jon,
>
> On Mon, Dec 5, 2016 at 3:27 PM, Jon Masters wrote:
>> Duc, Aleksey, all,
>>
>> I have a question about this...
>>
>> On 12/05/2016 01:51 PM, Duc Dang wrote:
>>> On Mon, Dec 5, 2016 at 5:05 AM, Aleksey Makarov
>>> wrote:
Check
On Mon, Dec 05, 2016 at 05:59:08PM -0600, Rob Herring wrote:
> On Thu, Dec 01, 2016 at 09:24:50AM -0800, Brian Norris wrote:
> > Hi Benjamin and Rob,
> >
> > On Thu, Dec 01, 2016 at 03:34:34PM +0100, Benjamin Tissoires wrote:
> > > On Nov 30 2016 or thereabouts, Brian Norris wrote:
> > > > From:
On Mon, Dec 05, 2016 at 05:59:08PM -0600, Rob Herring wrote:
> On Thu, Dec 01, 2016 at 09:24:50AM -0800, Brian Norris wrote:
> > Hi Benjamin and Rob,
> >
> > On Thu, Dec 01, 2016 at 03:34:34PM +0100, Benjamin Tissoires wrote:
> > > On Nov 30 2016 or thereabouts, Brian Norris wrote:
> > > > From:
On Tue, Nov 22, 2016 at 4:57 PM, John Stultz wrote:
> On Tue, Nov 8, 2016 at 4:12 PM, Andy Lutomirski wrote:
>> On Tue, Nov 8, 2016 at 4:03 PM, Alexei Starovoitov
>> wrote:
>>> On Tue, Nov 08, 2016 at 03:51:40PM -0800,
On Tue, Nov 22, 2016 at 4:57 PM, John Stultz wrote:
> On Tue, Nov 8, 2016 at 4:12 PM, Andy Lutomirski wrote:
>> On Tue, Nov 8, 2016 at 4:03 PM, Alexei Starovoitov
>> wrote:
>>> On Tue, Nov 08, 2016 at 03:51:40PM -0800, Andy Lutomirski wrote:
I hate to say it, but I think I may see a
On Thu, 1 Dec 2016, Greg KH wrote:
> On Wed, Nov 30, 2016 at 10:32:55AM -0600, Alan Tull wrote:
> > Hi Greg,
> >
> > Please pull these changes for FPGA.
> >
> > Thanks!
> > Alan
> >
> > The following changes since commit e663c5dbad2999aa824045c8e01fed459d1fc833:
> >
> > uio: pruss: add
On Thu, 1 Dec 2016, Greg KH wrote:
> On Wed, Nov 30, 2016 at 10:32:55AM -0600, Alan Tull wrote:
> > Hi Greg,
> >
> > Please pull these changes for FPGA.
> >
> > Thanks!
> > Alan
> >
> > The following changes since commit e663c5dbad2999aa824045c8e01fed459d1fc833:
> >
> > uio: pruss: add
Hi Sebastian,
Could you please review and pick the patch3/4 for power-supply driver?
Best Regards,
Chanwoo Choi
On 2016년 11월 30일 14:57, Chanwoo Choi wrote:
> This patch uses the resource-managed extcon API for extcon_register_notifier()
> and replaces the deprecated extcon API as following:
> -
Hi Sebastian,
Could you please review and pick the patch3/4 for power-supply driver?
Best Regards,
Chanwoo Choi
On 2016년 11월 30일 14:57, Chanwoo Choi wrote:
> This patch uses the resource-managed extcon API for extcon_register_notifier()
> and replaces the deprecated extcon API as following:
> -
Hi Kishon,
Could you review and pick the patch1/2 for phy driver?
Best Regards,
Chanwoo Choi
On 2016년 11월 30일 14:57, Chanwoo Choi wrote:
> This patch replaces the deprecated extcon API as following:
> - extcon_set_cable_state_() -> extcon_set_state_sync()
>
> Signed-off-by: Chanwoo Choi
On Thu, Dec 01, 2016 at 10:05:59AM +0100, Neil Armstrong wrote:
> Reviewed-by: Laurent Pinchart
> Signed-off-by: Neil Armstrong
> ---
> .../bindings/display/amlogic,meson-vpu.txt | 112
> +
> 1 file
Hi Kishon,
Could you review and pick the patch1/2 for phy driver?
Best Regards,
Chanwoo Choi
On 2016년 11월 30일 14:57, Chanwoo Choi wrote:
> This patch replaces the deprecated extcon API as following:
> - extcon_set_cable_state_() -> extcon_set_state_sync()
>
> Signed-off-by: Chanwoo Choi
> ---
On Thu, Dec 01, 2016 at 10:05:59AM +0100, Neil Armstrong wrote:
> Reviewed-by: Laurent Pinchart
> Signed-off-by: Neil Armstrong
> ---
> .../bindings/display/amlogic,meson-vpu.txt | 112
> +
> 1 file changed, 112 insertions(+)
> create mode 100644
>
information
information
This patch adds header with values used for ZTE 2967
SoC's power domain driver.
Signed-off-by: Baoyou Xie
---
include/dt-bindings/arm/zte_pm_domains.h | 23 +++
1 file changed, 23 insertions(+)
create mode 100644
This patch adds header with values used for ZTE 2967
SoC's power domain driver.
Signed-off-by: Baoyou Xie
---
include/dt-bindings/arm/zte_pm_domains.h | 23 +++
1 file changed, 23 insertions(+)
create mode 100644 include/dt-bindings/arm/zte_pm_domains.h
diff --git
On 2016년 12월 06일 01:32, Bin Liu wrote:
> On Wed, Nov 30, 2016 at 09:45:03AM +0100, Maxime Ripard wrote:
>> On Wed, Nov 30, 2016 at 02:57:35PM +0900, Chanwoo Choi wrote:
>>> This patch just uses the resource-managed extcon API when registering
>>> the extcon notifier.
>>>
>>> Signed-off-by: Chanwoo
On Thu, Dec 01, 2016 at 11:03:14AM +0200, Stanimir Varbanov wrote:
> Add binding document for Venus video encoder/decoder driver
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Stanimir Varbanov
On 2016년 12월 06일 01:32, Bin Liu wrote:
> On Wed, Nov 30, 2016 at 09:45:03AM +0100, Maxime Ripard wrote:
>> On Wed, Nov 30, 2016 at 02:57:35PM +0900, Chanwoo Choi wrote:
>>> This patch just uses the resource-managed extcon API when registering
>>> the extcon notifier.
>>>
>>> Signed-off-by: Chanwoo
On Thu, Dec 01, 2016 at 11:03:14AM +0200, Stanimir Varbanov wrote:
> Add binding document for Venus video encoder/decoder driver
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Stanimir Varbanov
> ---
> Rob, I have removed vmem clocks, interrupts and
On 06/12/16 10:40, Robert LeBlanc wrote:
I'm not seeing a tag at
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/
. Was it pushed?
You should probably be looking at
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/, where
the tag certainly was pushed.
On 06/12/16 10:40, Robert LeBlanc wrote:
I'm not seeing a tag at
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/
. Was it pushed?
You should probably be looking at
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/, where
the tag certainly was pushed.
4de429888c5b ("ASoC: cq93vc: remove MFD_DAVINCI_VOICECODEC dependency for
CQ0093VC")
I have used the sound-asoc tree from next-20161205 for today.
--
Cheers,
Stephen Rothwell
4de429888c5b ("ASoC: cq93vc: remove MFD_DAVINCI_VOICECODEC dependency for
CQ0093VC")
I have used the sound-asoc tree from next-20161205 for today.
--
Cheers,
Stephen Rothwell
Hi all,
After merging the sound-asoc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
sound/soc/soc-topology.c: In function 'soc_tplg_dapm_widget_create':
sound/soc/soc-topology.c:1566:36: warning: 'kcontrol_type' may be used
uninitialized in this function
Hi all,
After merging the sound-asoc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
sound/soc/soc-topology.c: In function 'soc_tplg_dapm_widget_create':
sound/soc/soc-topology.c:1566:36: warning: 'kcontrol_type' may be used
uninitialized in this function
On Mon, Dec 05, 2016 at 11:53:39PM +0300, Dan Carpenter wrote:
> On Sat, Dec 03, 2016 at 09:19:36PM -0500, Brian Masney wrote:
> > Fixed warning found by make W=2 to reduce the amount of build noise:
> >
> > warning: comparison between signed and unsigned integer expressions
> > [-Wsign-compare]
On Mon, Dec 05, 2016 at 11:53:39PM +0300, Dan Carpenter wrote:
> On Sat, Dec 03, 2016 at 09:19:36PM -0500, Brian Masney wrote:
> > Fixed warning found by make W=2 to reduce the amount of build noise:
> >
> > warning: comparison between signed and unsigned integer expressions
> > [-Wsign-compare]
On 12/05/2016 06:52 PM, Duc Dang wrote:
> But I am still curious why setting subtype to '0' does not work on
> your board. Are you using Mustang or m400?
m400 with updated tables (that are correctly overriding not appending)
provided via INITRD override. I am looking at why it's not working.
[
On 12/05/2016 06:52 PM, Duc Dang wrote:
> But I am still curious why setting subtype to '0' does not work on
> your board. Are you using Mustang or m400?
m400 with updated tables (that are correctly overriding not appending)
provided via INITRD override. I am looking at why it's not working.
[
On Mon, Dec 05, 2016 at 11:00:53PM +0800, Yang Ling wrote:
> Add watchdog timer specific driver for Loongson1 SoC.
>
> Signed-off-by: Yang Ling
>
> ---
> V2.4:
> Set DEFAULT_HEARTBEAT to 0.
> V2.3:
> Set DEFAULT_HEARTBEAT value to ls1x_wdt->timeout.
> V2.2:
> Remove
Nicolai Stange writes:
> ---
> Applicable to next-20161202.
>
> Note that after this patch, I'm seeing a single
> EXT4-fs (dm-1): Delayed block allocation failed for inode 2625094 at
> logical offset 2032 with max blocks 2 with error 121
> with 121 ==
301 - 400 of 1768 matches
Mail list logo