On Thu, Nov 28, 2013 at 09:08:45PM +0100, Jan Engelhardt wrote:
> On Wednesday 2013-11-27 12:08, Chris Wilson wrote:
> >On Wed, Nov 27, 2013 at 11:59:56AM +0100, Jan Engelhardt wrote:
> >>
> >> Despite the i915/drm fixes added in v3.11.8, the X server still
> >> terminates due to some pipe state
On Thu, Nov 21, 2013 at 7:15 PM, Prabhakar Lad
wrote:
> From: "Lad, Prabhakar"
>
> This patch series does the following
> 1> Ports the driver to use irqdomain.
> 2> Adds dt binding support for gpio-davinci.
> 3> Adds DA850 dt support goio.
>
> Changes for v6:
> 1: GPIO driver now migrated to
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
One performance improvement and a few bug fixes. Two of the fixes deal
with the clock related problems we have seen on recent
On Tue, Nov 26, 2013 at 6:12 PM, Sekhar Nori wrote:
> On Tuesday 26 November 2013 06:03 PM, Grygorii Strashko wrote:
>> Actually, the same was proposed by Linus, but we've tried avoid such huge
>> rework -
>> by switching to one irq_domain per all banks for example.
>
> I didn't really read
On Thu, Nov 21, 2013 at 7:15 PM, Prabhakar Lad
wrote:
> From: "Lad, Prabhakar"
>
> As the davinci-gpio driver is migrated to use irqdomain
> there is no need to pass the irq base for the gpio driver.
> This patch removes this variable from davinci_gpio_platform_data
> and also the refrences
No fault if !MUU, thus make might_fault to be a nop for !MMU.
This fixes below build error if
!CONFIG_MMU && (CONFIG_PROVE_LOCKING=y || CONFIG_DEBUG_ATOMIC_SLEEP=y):
arch/arm/kernel/built-in.o: In function `arch_ptrace':
arch/arm/kernel/ptrace.c:852: undefined reference to `might_fault'
On Fri, Nov 29, 2013 at 3:17 AM, Greg KH wrote:
> On Thu, Nov 28, 2013 at 03:28:39PM +0800, Xiaotian Feng wrote:
>> On Thu, Nov 28, 2013 at 12:11 PM, Greg KH wrote:
>> > On Thu, Nov 28, 2013 at 11:25:32AM +0800, Xiaotian Feng wrote:
>> >> Hi,
>> >>
>> >> When I upgrade to latest kernel, I
On Wed 16-10-13 20:38:07, Jan Kara wrote:
> On Wed 16-10-13 08:56:07, Davidlohr Bueso wrote:
> > On Wed, 2013-10-16 at 14:50 +0200, Jan Kara wrote:
> > > On Tue 15-10-13 19:02:04, Davidlohr Bueso wrote:
> > > > Hello Jan,
> > > >
> > > > Just wanted to let you know I hit this[1] again on Linus'
usb: chipidea: hw_phymode_configure moved before ci_usb_phy_init
hw_phymode_configure configures the PORTSC registers and allow the
following phy_inits to operate on the right parameters. This fix a problem
where the UPLI (ISP1504) could not detected, because the Viewport was not
available and
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git
usb: chipidea: Reallocate regmap only if lpm is detected
The regmap only needs to reallocate if the hw_read on the CAP register shows
lpm is used. Therefore the if() statement check the change.
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |3 ++-
1 file changed, 2
From: Andy Fleming
phy_attach_direct() may now attach to a generic 10G driver. It can
also be used exactly as phy_connect_direct(), which will be useful
when using of_mdio, as phy_connect (and therefore of_phy_connect)
start the PHY state machine, which is currently irrelevant for 10G
PHYs.
From: Andy Fleming
10G PHYs don't currently support running the state machine, which
is implicitly setup via of_phy_connect(). Therefore, it is necessary
to implement an OF version of phy_attach(), which does everything
except start the state machine.
Signed-off-by: Andy Fleming
Signed-off-by:
From: Andy Fleming
Very incomplete, but will allow for binding an ethernet controller
to it.
Signed-off-by: Andy Fleming
Signed-off-by: Shaohui Xie
---
v3 changes: splitted from v2 patch 3/5.
drivers/net/phy/phy_device.c | 80
1 file changed, 80
From: Shaohui Xie
Then other generic phy driver such as generic 10g phy driver can join it.
Signed-off-by: Shaohui Xie
---
Splitted from previous v2 patch 3/5.
drivers/net/phy/phy_device.c | 27 +++
1 file changed, 19 insertions(+), 8 deletions(-)
diff --git
From: Andy Fleming
Need an extra parameter to read or write Clause 45 PHYs, so
need a different API with the extra parameter.
Signed-off-by: Andy Fleming
Signed-off-by: Shaohui Xie
---
v3 changes: add C45 check.
include/linux/phy.h | 39 +++
1 file
From: Shaohui Xie
Signed-off-by: Andy Fleming
Signed-off-by: Shaohui Xie
Acked-by: Florian Fainelli
---
v3: no changes.
drivers/of/of_net.c | 1 +
include/linux/phy.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/of/of_net.c b/drivers/of/of_net.c
index 8f9be2e..a208a45
> > +#define FTM_CNTIN_VAL 0x00
>
> Do we really need this?
>
Maybe not, I think that the initial value maybe modified in the future.
And this can be more easy to ajust it.
> > + period_cycles = fsl_rate_to_cycles(fpc, period_ns);
> > + if (period_cycles > 0x) {
> > +
Hi Jiri,
On Thu, 28 Nov 2013 12:33:19 +0100, Jiri Olsa wrote:
> Removing malloc_or_die calls from plugin_function.c,
> replacing them with standard malloc and error path.
>
> Suggested-by: Namhyung Kim
> Signed-off-by: Jiri Olsa
> Cc: Corey Ashford
> Cc: Frederic Weisbecker
> Cc: Ingo Molnar
On 2013/11/29 13:05, Serge Hallyn wrote:
> Quoting Libo Chen (clbchenlibo.c...@huawei.com):
>> Hello LXC experts,
>>
>> I meet a problem. When using vlan as network device in suse11 system
>> container,
>> I can not use halt to stop this container. It hung on "eth0 is still used
>> from
> On Thu, Nov 28, 2013 at 10:46 AM, Alexandre Courbot
> wrote:
One missed, but not least, thing.
>> +static struct gpiod_lookup_table *gpiod_find_lookup_table(struct device
>> *dev)
>> {
>> const char *dev_id = dev ? dev_name(dev) : NULL;
>> - struct gpio_desc *desc =
> -Original Message-
> From: Kalle Valo [mailto:kv...@qca.qualcomm.com]
> Sent: Tuesday, November 26, 2013 6:40 PM
> To: Liu Hui-R64343
> Cc: linux-arm-ker...@lists.infradead.org; linvi...@tuxdriver.com; linux-
> wirel...@vger.kernel.org; net...@vger.kernel.org; linux-
>
Hi Thierry,
Thanks for your detail comments.
> > + switch (fpc->counter_clk_select) {
> > + case VF610_CLK_FTM0:
> > + reg |= FTMSC_CLKSYS;
> > + break;
> > + case VF610_CLK_FTM0_FIX_SEL:
> > + reg |= FTMSC_CLKFIX;
> > + break;
> > + case
On Sun, Nov 24, 2013 at 10:36:28PM -0800, Shawn Landden wrote:
> Commit 35f9c09fe (tcp: tcp_sendpages() should call tcp_push() once)
> added an internal flag MSG_SENDPAGE_NOTLAST, similar to
> MSG_MORE.
>
> algif_hash, algif_skcipher, and udp used MSG_MORE from tcp_sendpages()
> and need to see
On 28 November 2013 18:12, Lukasz Majewski wrote:
> To make the driver multiplatform-friendly, unconditional initialization
> in an initcall is replaced with a platform driver probed only if
> respective platform device is registered.
>
> Tested at: Exynos4210 (TRATS) and Exynos4412 (TRATS2)
>
>
IPv6 stats are 64 bits and thus are protected with a seqlock. By not
disabling bottom-half we could deadlock here if we don't disable bh and
a softirq reentrantly updates the same mib.
Cc: Eric Dumazet
Signed-off-by: Hannes Frederic Sowa
---
net/ipv6/ip6_output.c | 4 ++--
1 file changed, 2
Quoting Libo Chen (clbchenlibo.c...@huawei.com):
> Hello LXC experts,
>
> I meet a problem. When using vlan as network device in suse11 system
> container,
> I can not use halt to stop this container. It hung on "eth0 is still used
> from interfaces eth0" in cycle.
>
> The config file:
>
(2013/11/29 13:23), Atsushi Kumagai wrote:
> On 2013/11/29 12:24:45, kexec wrote:
>> (2013/11/29 12:02), Atsushi Kumagai wrote:
>>> On 2013/11/28 16:50:21, kexec wrote:
>> ping, in case you overlooked this...
>
> Sorry for the delayed response, I prioritize the release of v1.5.5 now.
>
> On Friday, November 29, 2013 11:27 AM, Peter Chen wrote:
> >
> >> * init the sts flag to 0 (missed)
> >> * set the sts flag only if not 0
> >>
> > does PORTSC_STS bit as 1 or 0 affect your case?
> > If not, please remove hw_write(ci, OP_DEVLC, DEVLC_STS, sts),
> > since it is useless at
On Wednesday 27 November 2013 08:01 PM, Ivan Khoronzhuk wrote:
> The problem that the set timings code contains the call of Davinci
> platform function davinci_aemif_setup_timing() which is not
> accessible if kernel is built for another platform like Keystone.
>
> The Keysone platform is going
On Friday, November 29, 2013 11:27 AM, Peter Chen wrote:
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
does PORTSC_STS bit as 1 or 0 affect your case?
If not, please remove hw_write(ci, OP_DEVLC, DEVLC_STS, sts),
since it is useless at current code logic.
Peter
Hi Dave,
I aplogize for wrong formatting of multiline comments.
> I really think this shouldn't be separated out in this way, because it
> means the decoder has to be implemented twice, and moving the checks far
> away from the code that the checks need to match.
I believe that you are right in
On 2013/11/29 12:24:45, kexec wrote:
> (2013/11/29 12:02), Atsushi Kumagai wrote:
> > On 2013/11/28 16:50:21, kexec wrote:
> ping, in case you overlooked this...
> >>>
> >>> Sorry for the delayed response, I prioritize the release of v1.5.5 now.
> >>>
> >>> Thanks for your advice,
On some systems we can't really say what frequency we're running at the moment
and so for these we shouldn't check if we are running at a frequency present in
frequency table. For now mark all x86 drivers with this flag:
CPUFREQ_SKIP_INITIAL_FREQ_CHECK.
Signed-off-by: Viresh Kumar
---
Rafael,
Sometimes boot loaders set CPU frequency to a value outside of frequency table
present with cpufreq core. In such cases CPU might be unstable if it has to run
on that frequency for long duration of time and so its better to set it to a
frequency which is specified in freq-table. This also makes
After this patch, excluding the VGA_CONSOLE issue, the hexagon can pass
allmodconfig. :-)
Please help check all related patches when you have time.
Thanks.
On 11/29/2013 12:01 PM, Chen Gang wrote:
> Need export all related functions and symbols for various modules with
> allmodconfig. The
'pm_power_off' is a function pointer, not a function, so need change
its type, and also need export it, or can not pass compiling with
allmodconfig. The related error:
MODPOST 2879 modules
ERROR: "pm_power_off" [drivers/char/ipmi/ipmi_poweroff.ko] undefined!
Signed-off-by: Chen Gang
---
Need export all related functions and symbols for various modules with
allmodconfig. The related errors:
MODPOST 2879 modules
ERROR: "__vmyield" [sound/sound_firmware.ko] undefined!
ERROR: "__phys_offset" [sound/drivers/snd-dummy.ko] undefined!
ERROR: "ioremap_nocache"
>
> hw_phymode_configure configures the PORTSC registers and allow the
> following phy_inits to operate on the right parameters. This fix a
> problem
> where the UPLI (ISP1504) could not detected, because the Viewport was not
> available and returns 0's only.
>
> Signed-off-by: Chris Ruehl
>
>
> * init the sts flag to 0 (missed)
> * set the sts flag only if not 0
>
does PORTSC_STS bit as 1 or 0 affect your case?
If not, please remove hw_write(ci, OP_DEVLC, DEVLC_STS, sts),
since it is useless at current code logic.
Peter
> Signed-off-by: Chris Ruehl
> ---
>
On 29 November 2013 01:59, Rafael J. Wysocki wrote:
> So I'm reading this as "the version of the patch in bleeding-edge is OK".
>
> I hope that really is the case. :-)
Yeah, that's correct.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
(2013/11/29 12:02), Atsushi Kumagai wrote:
> On 2013/11/28 16:50:21, kexec wrote:
ping, in case you overlooked this...
>>>
>>> Sorry for the delayed response, I prioritize the release of v1.5.5 now.
>>>
>>> Thanks for your advice, check_cyclic_buffer_overrun() should be fixed
>>> as you
>
> Signed-off-by: Chris Ruehl
> ---
> drivers/usb/chipidea/core.c |3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
> index 5d8981c..5075407 100644
> --- a/drivers/usb/chipidea/core.c
> +++
On Wed, Nov 27, 2013 at 10:46:52AM -0800, Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman
>
> The PCI MSI sysfs code is a mess with kobjects for things that don't
> really need to be kobjects. This patch creates attributes dynamically
> for the MSI interrupts instead of using kobjects.
>
On 11/20/13 at 12:50pm, Vivek Goyal wrote:
> diff --git a/arch/x86/kernel/machine_kexec_64.c
> b/arch/x86/kernel/machine_kexec_64.c
> index 4eabc16..fb41b73 100644
> --- a/arch/x86/kernel/machine_kexec_64.c
> +++ b/arch/x86/kernel/machine_kexec_64.c
> @@ -22,6 +22,13 @@
> #include
> #include
On 2013/11/28 16:50:21, kexec wrote:
> >> ping, in case you overlooked this...
> >
> > Sorry for the delayed response, I prioritize the release of v1.5.5 now.
> >
> > Thanks for your advice, check_cyclic_buffer_overrun() should be fixed
> > as you said. In addition, I'm considering other way to
On 11/29/2013 10:29 AM, Chen Gang wrote:
> Only find "DECLARE_EXPORT(__hexagon_*i3)", no related implementations
> and callers, so remove them, or will cause ld issue with allmodconfig,
> the related error:
>
> LD init/built-in.o
>
Hi all,
Changes since 20131128:
The slave-dma tree gained conflicts against the imx-mxs tree.
The sound-asoc tree gained a build failure so I used teh version from
next-20131128.
Non-merge commits (relative to Linus' tree): 1585
1774 files changed, 68549 insertions(+), 33718 deletions
Hi Rafael,
Replying to this mail may be wrong.
Do you remember following your patch?
http://lkml.org/lkml/2013/2/23/97
I want to add autoeject variable in acpi_hotplug_profile structure and
set autoecjet of container device "false".
Currently, I have a problem on ejecting container device.
On Fri, Nov 29, 2013 at 12:29 AM, Chris Ruehl wrote:
> yeah, the hw_phymode_configure() was in the probe but not called before the
> ci_usb_phy_init(ci) which triggers the inits in phy-generic.c (in my case)
>
> My pending patches relay on this.
>
> Did you move the hw_phy before the
Hi Fabio
On Friday, November 29, 2013 10:14 AM, Fabio Estevam wrote:
Hi Chris,
On Fri, Nov 29, 2013 at 12:08 AM, Chris Ruehl wrote:
hw_phymode_configure configures the PORTSC registers and allow the
following phy_inits to operate on the right parameters. This fix a problem
where the UPLI
Only find "DECLARE_EXPORT(__hexagon_*i3)", no related implementations
and callers, so remove them, or will cause ld issue with allmodconfig,
the related error:
LD init/built-in.o
arch/hexagon/kernel/built-in.o:(___ksymtab+__hexagon_umodsi3+0x0): undefined
reference to
On 2013年11月29日 08:36, Rafael J. Wysocki wrote:
> Hi,
>
> Now that we store a pointer to struct acpi_device as the ACPI companion in
> struct device, the code making associations between "physical" devices and
> ACPI device objects can be modified to work with struct acpi_device pointers
> instead
hw_phymode_configure configures the PORTSC registers and allow the
following phy_inits to operate on the right parameters. This fix a problem
where the UPLI (ISP1504) could not detected, because the Viewport was not
available and returns 0's only.
Signed-off-by: Chris Ruehl
---
Hi Chris,
On Fri, Nov 29, 2013 at 12:08 AM, Chris Ruehl wrote:
> hw_phymode_configure configures the PORTSC registers and allow the
> following phy_inits to operate on the right parameters. This fix a problem
> where the UPLI (ISP1504) could not detected, because the Viewport was not
> available
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
index 5075407..1a6010e 100644
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
index 5d8981c..5075407 100644
--- a/drivers/usb/chipidea/core.c
+++ b/drivers/usb/chipidea/core.c
@@
We will do more stress test in more machine at the same time
-Original Message-
From: Ma, Xindong
Sent: Friday, November 29, 2013 10:06 AM
To: Oleg Nesterov; Michal Hocko
Cc: William Dauchy; Johannes Weiner; a...@linux-foundation.org;
rient...@google.com; ru...@rustcorp.com.au;
-- Original Message ---
Sender : Eric Dumazet
Date : 2013-11-29 02:51 (GMT+09:00)
Title : [PATCH v2] inet: fix possible seqlock deadlocks
>
> From: Eric Dumazet
>
> In commit c9e9042994d3 ("ipv4: fix possible seqlock deadlock") I left
> another places where IP_INC_STATS_BH() were
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> From: Oleg Nesterov [mailto:o...@redhat.com]
> Sent: Friday, November 29, 2013 2:39 AM
> To: Michal Hocko
> Cc: William Dauchy; Johannes Weiner; Ma, Xindong;
> a...@linux-foundation.org; rient...@google.com; ru...@rustcorp.com.au;
> linux...@kvack.org; linux-kernel@vger.kernel.org; Peter
On 2013年11月29日 08:37, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Replace the .find_device function pointer in struct acpi_bus_type
> with a new one, .find_copmanion, that is supposed to point to a
-^
A typo
> function returning struct acpi_device pointer
On Thu, Nov 28, 2013 at 07:16:27PM +0200, Cristian Stoica wrote:
> Signed-off-by: Cristian Stoica
> ---
> crypto/authenc.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/crypto/authenc.c b/crypto/authenc.c
> index 1875e70..7d4bfaa 100644
> --- a/crypto/authenc.c
> +++
On 11/28/13, 5:48 PM, Namhyung Kim wrote:
Do we really need to look up the callchain to find out an idle thread?
$ perf sched script | grep swapper | head
swapper 0 [001] 4294177.326996: sched:sched_switch:
prev_comm=swapper/1 prev_pid=0 prev_prio=120 prev_state=R ==>
Thunderbolt switches have a plug events capability. This patch adds the
tb_plug_events_active method and uses it to activate plug events on
switch allocation.
Signed-off-by: Andreas Noever
---
drivers/thunderbolt/tb.c | 49 +++-
We reveive a plug event callback whenever a thunderbolt device is added
or removed. This patch fills in the tb_handle_hotplug method and starts
reacting to these events by adding/removing switches from the hierarchy.
Signed-off-by: Andreas Noever
---
drivers/thunderbolt/tb.c | 83
Add struct tb which will contain our view of the thunderbolt bus. For
now it just contains a pointer to the configuration channel and a
workqueue for hotplug events.
Add thunderbolt_alloc_and_start() and thunderbolt_shutdown_and_free()
which are responsible for setup and teardown of struct tb.
Every thunderbolt device consists (logically) of a switch with multiple
ports. Every port contains multiple config regions (HOPS, PORT, SWITCH,
COUNTERS) which are used to configure the device.
The tb_regs.h file contains all known registers and capabilities from these
config regions.
Add utility methods tb_port_state and tb_wait_for_port. Add tb_scan_port
which checks whether a port is connected and if so allocates a
downstream switch.
Signed-off-by: Andreas Noever
---
drivers/thunderbolt/tb.c | 160 +++
drivers/thunderbolt/tb.h |
This patch adds the structures tb_switch and tb_port as well as code to
reset and configure the root switch.
Signed-off-by: Andreas Noever
---
drivers/thunderbolt/tb.c | 229 ++-
drivers/thunderbolt/tb.h | 113 +++
2 files changed,
A pci downstream and pci upstream port can be connected through a
tunnel. To establish the tunnel we have to setup two unidirectional
paths between the two ports.
Right now we only support paths with two hops (i.e. no chaining) and at
most one pci device per thunderbolt device.
Signed-off-by:
A thunderbolt path is a unidirectional channel between two thunderbolt
ports. Two such paths are needed to establish a pci tunnel.
This patch introduces struct tb_path as well as a set of tb_path_*
methods which are used do activate & deactive paths.
Signed-off-by: Andreas Noever
---
Use the tb_pci_* methods introduces in the last patch to activate
a the first PCI device on every plugged in thunderbolt device.
Signed-off-by: Andreas Noever
---
drivers/thunderbolt/tb.c | 118 +--
1 file changed, 115 insertions(+), 3 deletions(-)
Thunderbolt hotplug is supposed to be handled by the firmware. But Apple
decided to implement thunderbolt at the operating system level. The
firmare only initializes thunderbolt devices that are present at boot
time. This driver enables hotplug of thunderbolt of non-chained thunderbolt
devices on
Thunderbolt devices are configured by reading/writing into their
configuration space (similar to pci). This is done by sending packets
through the NHI (native host interface) onto the configuration channel.
This patch handles the low level packet based protocol and exposes
higher level operations
Thunderbolt config areas contain capability lists similar to those found
on pci devices. This patch introduces a tb_find_cap utility method to search
for capabilities.
Signed-off-by: Andreas Noever
---
drivers/thunderbolt/tb.c | 103 +++
Thunderbolt hotplug is supposed to be implemented by the firmware. But Apple's
firmeware only initializes devices during boot and ignores hotplugged devices.
This patch series adds a driver for the Intel Cactus Ridge Thunderbolt
controller. The driver supports hotplug operations of simple (one PCI
On Thursday, November 28, 2013 3:24 PM, Joe Perches wrote:
>On Wed, 2013-11-27 at 21:53 -0800, 'Greg Kroah-Hartman' wrote:
>>On Wed, Nov 27, 2013 at 09:40:13PM -0800, Joe Perches wrote:
>>>On Thu, 2013-11-28 at 14:29 +0900, Jingoo Han wrote:
On Thursday, November 28, 2013 1:08 PM, Greg
On 11/29/2013 04:47 AM, Dave Martin wrote:
On Thu, Nov 28, 2013 at 04:58:33PM +, Stephen Warren wrote:
On 11/27/2013 11:02 PM, Alexandre Courbot wrote:
On Wed, Nov 27, 2013 at 1:47 AM, Dave Martin wrote:
On Tue, Nov 26, 2013 at 10:35:58AM +0900, Alexandre Courbot wrote:
On Tue, Nov 26,
->chgfreq_divisor = val32;
^
Caused by commit 391fc59db876 ("ASoC: cs42l52: Add devicetree support for
CS42L52").
I have used the sound-asoc tree from next-20131128 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpTCRaRuWOyY.pgp
Description: PGP signature
Hi David,
On Thu, 28 Nov 2013 09:01:23 -0700, David Ahern wrote:
> On 11/28/13, 8:38 AM, Namhyung Kim wrote:
>> On Tue, Nov 19, 2013 at 5:32 AM, David Ahern wrote:
>>
>> [SNIP]
>>> +static bool is_idle_sample(struct perf_sample *sample,
>>> + struct perf_evsel *evsel,
Hi Vinod,
Today's linux-next merge of the slave-dma tree got a conflict in
arch/arm/boot/dts/imx53.dtsi between commit a0cd556100d0 ("ARM: imx53:
use clock defines in DTS files") from the imx-mxs tree and commit
786f0db6d439 ("ARM: dts: imx: use dual-fifo sdma script for ssi") from
the slave-dma
Hi Vinod,
Today's linux-next merge of the slave-dma tree got a conflict in
arch/arm/boot/dts/imx51.dtsi between commit 975bbc1e679b ("ARM: imx51:
use clock defines in DTS files") from the imx-mxs tree and commit
786f0db6d439 ("ARM: dts: imx: use dual-fifo sdma script for ssi") from
the slave-dma
From: Rafael J. Wysocki
Replace the .find_device function pointer in struct acpi_bus_type
with a new one, .find_copmanion, that is supposed to point to a
function returning struct acpi_device pointer (instead of an int)
and takes one argument (instead of two). This way the role of
this callback
Hi,
Now that we store a pointer to struct acpi_device as the ACPI companion in
struct device, the code making associations between "physical" devices and
ACPI device objects can be modified to work with struct acpi_device pointers
instead of ACPI handles too. The first two of the following
From: Rafael J. Wysocki
There is no reason to pass an ACPI handle to acpi_bind_one() instead
of a struct acpi_device pointer to the target device object, so
modify that function to take a struct acpi_device pointer as its
second argument and update all code depending on it accordingly.
From: Rafael J. Wysocki
Since drivers/ide/ide-acpi.c is the only remaining user of
acpi_get_child(), move that function into that file as a static
routine.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/glue.c | 12
drivers/ide/ide-acpi.c | 11 +++
Hi Oleg,
On Thu, 28 Nov 2013 17:31:48 +0100, Oleg Nesterov wrote:
> On 11/28, Namhyung Kim wrote:
>>
>> I thought we need a fetch_param anyway if we will add support for
>> cross-fetch later. But I won't insist it strongly, I can delay it to
>> later work and make current code simpler if you
On Friday, November 29, 2013 2:15 AM, Mark Brown wrote:
> > Add "const" to "static struct regmap_irq" and "static struct
> > regmap_config".
>
> Reviewed-by: Mark Brown
Acked-by: Sangbeom Kim
Thanks,
Sangbeom.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Thursday, November 28, 2013 5:10 PM, Krzysztof Kozlowski wrote:
> Add PM suspend/resume ops to rtc-s5m driver and enable IRQ wake during
> suspend so the RTC would act like a wake up source. This allows waking
> up from suspend to RAM on RTC alarm interrupt.
>
> Signed-off-by: Krzysztof
On Wednesday, November 27, 2013 02:58:54 AM Rafael J. Wysocki wrote:
> On Tuesday, November 26, 2013 06:40:28 PM Toshi Kani wrote:
[...]
> >
> > Yes, the system booted fine with 3/4 & 4/4. :-)
>
> Thanks for the verification!
In fact, I've made one more mistake in that patch. Namely,
On Thursday, November 28, 2013 10:48 PM, Mark Brown wrote:
> > After setting alarm or time the driver is waiting for UDR register to be
> > cleared indicating that registers data have been transferred.
> >
> > Limit the endless loop to only 5 retries.
>
> Reviwed-by: Mark Brown
Acked-by:
On Thursday, November 28, 2013 10:47 PM, Mark Brown wrote:
> > Fix rtc-s5m interrupt request by using regmap_irq_get_virq() for mapping
> > the IRQ.
>
> Reviwed-by: Mark Brown
Acked-by: Sangbeom Kim
Thanks,
Sangbeom.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Thursday, November 28, 2013 10:51 PM, Mark Brown wrote:
> > On S5M8767A registers were not properly updated and read due to usage
> > of the same regmap as the PMIC. This could be observed in various
> > hangs, e.g. in infinite loop during waiting for UDR field change.
>
> Reviwed-by: Mark
In order to remove the following ugly message:
BUG: mapping for 0x at 0xff00 out of vmalloc space
the iotable mappings should be re-located inside the vmalloc
region. Such move was introduced at commit:
commit 0536bdf33faff4d940ac094c77998cfac368cfff
Author: Nicolas Pitre
Date:
From: Andy Whitcroft
Date: Mon, 25 Nov 2013 16:52:34 +
> We are now using csum_ipv6_magic, include the appropriate header.
> Avoids the following error:
>
> drivers/net/xen-netback/netback.c:1313:4: error: implicit declaration of
> function 'csum_ipv6_magic'
Some of the patches in this series add new features, therefore please this
series when the net-next tree opens back up.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Jason Wang
Date: Mon, 25 Nov 2013 17:19:04 +0800
> After commit 8ffab51b3dfc54876f145f15b351c41f3f703195
> (macvlan: lockless tx path), tx stat counter were converted to percpu stat
> structure. So we need use to this also for tx_dropped in macvtap. Otherwise,
> the
> management won't
From:
Date: Mon, 25 Nov 2013 12:40:49 +0800
> From: Shaohui Xie
>
> Phy is compatible with Vitesse 82xx
>
> Signed-off-by: Shaohui Xie
Applied, thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
From: Xufeng Zhang
Date: Mon, 25 Nov 2013 11:26:57 +0800
> Currently retransmitted DATA chunks could also be used for
> RTT measurements since there are no flag to identify whether
> the transmitted DATA chunk is a new one or a retransmitted one.
> This problem is introduced by commit ae19c5486
1 - 100 of 1012 matches
Mail list logo
