On Wed, Feb 19, 2014 at 02:21:02PM +0800, Kevin Hao wrote:
> + /*
> + * Matching compatible is better than matching type and name,
> + * and the specific compatible is better than the general.
> + */
> + if (matches->compatible[0] &&
>
On Tue, Feb 18, 2014 at 04:10:57PM +0530, Sachin Kamat wrote:
> Propagate the error value returned by the function instead.
Applied, thanks.
signature.asc
Description: Digital signature
On Tue, Feb 18, 2014 at 06:17:08PM -0500, Matt Porter wrote:
> +
> + rfldo_reg: regulator@0 {
> + reg = <0>;
What do these reg values mean, they don't seem to be documented in the
binding?
signature.asc
Description: Digital
On Tue, Feb 18, 2014 at 06:17:12PM -0500, Matt Porter wrote:
> + csr_reg: regulator@13 {
> + reg = <13>;
> + regulator-compatible = "csr";
> + regulator-min-microvolt = <86>;
> +
On Tue, Feb 18, 2014 at 06:17:09PM -0500, Matt Porter wrote:
> +config MFD_BCM590XX
> + bool "Broadcom BCM590xx PMUs"
> + select MFD_CORE
> + select REGMAP_I2C
> + depends on I2C=y
> + help
> + Support for the BCM590xx PMUs from Broadcom
> +
Why does this need to be
Hello,
On Tue, Feb 18, 2014 at 04:08:56PM -0800, Andrew Morton wrote:
> On Sat, 15 Feb 2014 18:14:57 -0500 "Daniel M. Weeks"
> wrote:
>
> > LZ4 as implemented in the kernel differs from the default method now
> > used by the reference implementation of LZ4. Until the in-kernel method
> > is
On Tue, Feb 18, 2014 at 06:17:10PM -0500, Matt Porter wrote:
> +static struct of_device_id bcm590xx_of_match[] = {
> + { .compatible = "brcm,bcm59056-regs", },
> + { }
> +};
This looks pretty much OK however I am in general suspicious of MFDs
that have subdevices like this in the DT - it
On Wed, Feb 19, 2014 at 01:28:43PM +0800, Nenghua Cao wrote:
>Update Liam and Mark's mail.
I can't do anything useful with patches that are quoted, sorry. None of
the tools know how to strip out quotes.
signature.asc
Description: Digital signature
On Tue, Feb 18, 2014 at 08:20:59PM +0800, Axel Lin wrote:
> Fixes below build error:
> FATAL: drivers/regulator/tps65218-regulator: struct of_device_id is not
> terminated with a NULL entry!
This is good (though I'm not seeing a build time error myself...).
> Also remove of_match_ptr as this is
On Wed, 19 Feb 2014, Xishi Qiu wrote:
> Hi all,
>
> CONFIG_KMEMCHECK=y and set command-line "kmemcheck=1", I find OS
> boot failed. The kernel is v3.14.0-rc3
>
> If set "kmemcheck=1 nowatchdog", OS will boot successfully.
>
I have automated kernel boots that have both "kmemcheck=0" and
hayeswang :
> Francois Romieu [mailto:rom...@fr.zoreil.com]
> > Hayes Wang :
> > > Replace netif_rx with netif_receive_skb to avoid disabling irq frequently
> > > for increasing the efficiency.
> >
> > read_bulk_callback is issued in irq context. It could thus use plain
> > spin_lock /
In hwdrv_apci1564.c, one static variable is zero initialized. This is
unneeded and redundant, so we remove the initialization.
Signed-off-by: Chase Southwood
---
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1564.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
There were a small handful of printk() calls in hwdrv_apci1564.c. It is
generally better to use dev_err() for error messages instead, so I
switched all the printk() calls out, as well as cleaned up the error
strings.
Signed-off-by: Chase Southwood
---
hwdrv_apci1564.c had a lot of commented out conditional statements that
were often identical to other un-commented out statements nearby, so it
should be safe to just delete all of these commented out lines. This
patch also converts the remaining comments to the preferred kernel style
for
hwdrv_apci1564.c had many single statments wrapped in braces, so we can
delete these. Also, some else statements were improperly placed, fix
these too.
Signed-off-by: Chase Southwood
---
.../comedi/drivers/addi-data/hwdrv_apci1564.c | 58 --
1 file changed, 22
On Wed, Feb 19, 2014 at 03:31:29PM +0800, Aaron Lu wrote:
> DID2 is in system memory region and has some assigned value like 0x400
> when we read it. For this case it is easy since there is only one output
> device that is of type LVDS so we can match it to connector of type eDP
> or LVDS,
On 02/13/2014 08:03 PM, Daniel Vetter wrote:
> On Thu, Feb 13, 2014 at 11:08 AM, Chris Wilson
> wrote:
>> On Thu, Feb 13, 2014 at 05:10:25PM +0800, Aaron Lu wrote:
>>> On 02/12/2014 06:31 PM, Chris Wilson wrote:
On Wed, Feb 12, 2014 at 11:05:40AM +0800, Aaron Lu wrote:
> The ACPI table
> The patch subject can be a little short like
>
> ARM: dts: vf610-twr: Enable SAI ALSA SoC DAI device
>
Yes, that looks better.
Thanks,
--
Best Regards,
Xiubo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
> > @@ -127,9 +127,27 @@
> > VF610_PAD_PTB5__UART1_RX0x21a1
> > >;
> > };
> > +
> > + pinctrl_sai2: sai2grp {
>
> To sort it alphabetically, the entry should be added before
> pinctrl_uart1.
>
> > +
>
> 'ARM: dts: vf610: ...' for patch prefix.
>
> Shawn
Please see the next version.
Thanks,
--
Best Regards,
Xiubo
--
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
A program can bundle multiple messages and commands together when
making one wire requests, which is going to be much more efficient
than sending lots of little packets one write at a time. With this
change the kernel will then bundle responses to requests that were
bundled, where it's probably
I've been running into problems on an Xen HVM domU. I've got a guest with NUMA
enabled, 60GB of RAM, and 3 disks attached (including root volume). 2 of the
disks are in an MD RAID0 in the guest, with an ext4 filesystem on top of that.
I was running the fio 'iometer-file-access-server.fio' example
On Wed, Feb 19, 2014 at 01:38:42PM +0800, Xiubo Li wrote:
> This patch adds and enables SGTL5000 codec support.
>
> Signed-off-by: Xiubo Li
> ---
> arch/arm/boot/dts/vf610-twr.dts | 19 +++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vf610-twr.dts
From: Yuan Pengfei
If -fprofile-values option is used, ctr->num and sci_ptr->num
may be zero, resulting in zero size and cv_size, which will
cause ENOMEM when opening gcov data files in debugfs.
Signed-off-by: Yuan Pengfei
---
kernel/gcov/gcc_3_4.c | 2 +-
kernel/gcov/gcc_4_7.c | 2 +-
2 files
On Wed, Feb 19, 2014 at 01:38:41PM +0800, Xiubo Li wrote:
> This patch adds and enables the SAI device.
>
> Signed-off-by: Xiubo Li
The patch subject can be a little short like
ARM: dts: vf610-twr: Enable SAI ALSA SoC DAI device
Shawn
> ---
> arch/arm/boot/dts/vf610-twr.dts | 18
At Tue, 18 Feb 2014 19:48:11 -0800,
H. Peter Anvin wrote:
>
> I just stumbled upon the function snd_intel8x0_inside_vm(), and quite
> frankly the code seems bizarre:
>
> /* detect KVM and Parallels virtual environments */
> result = kvm_para_available();
> #ifdef
On 02/19/2014 02:33 AM, Thomas Gleixner wrote:
On Tue, 18 Feb 2014, Alexey Perevalov wrote:
On 02/16/2014 07:39 PM, Thomas Gleixner wrote:
I figured out with deviation, I described before.
Which is wrong to begin with. Using the wrong method does not justify
the results. Are you actually
On Wed, Feb 19, 2014 at 01:38:40PM +0800, Xiubo Li wrote:
> This patch adds the SAI's edma mux Tx and Rx support.
>
> Signed-off-by: Xiubo Li
'ARM: dts: vf610: ...' for patch prefix.
Shawn
> ---
> arch/arm/boot/dts/vf610.dtsi | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
On Wed, Feb 19, 2014 at 01:38:41PM +0800, Xiubo Li wrote:
> This patch adds and enables the SAI device.
>
> Signed-off-by: Xiubo Li
> ---
> arch/arm/boot/dts/vf610-twr.dts | 18 ++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vf610-twr.dts
On 02/19/2014 06:12 AM, Waiman Long wrote:
On 02/18/2014 04:28 PM, Peter Zijlstra wrote:
On Tue, Feb 18, 2014 at 02:30:12PM -0500, Waiman Long wrote:
I will start looking at how to make it work with paravirt. Hopefully, it
won't take too long.
The cheap way out is to simply switch to the
On Mon, 2014-02-17 at 05:50 +0100, Mike Galbraith wrote:
> On Sun, 2014-02-16 at 08:41 -0800, Paul E. McKenney wrote:
> > So maybe start with Kevin's patch, but augment with something else for
> > the !NO_HZ_FULL case?
>
> Sure (hm, does it work without workqueue.disable_numa ?).
I took patch
Hi all,
CONFIG_KMEMCHECK=y and set command-line "kmemcheck=1", I find OS
boot failed. The kernel is v3.14.0-rc3
If set "kmemcheck=1 nowatchdog", OS will boot successfully.
Here is the boot failed log:
[ 23.586826] Freeing unused kernel memory: 1160K (8800014de000 - 88000
160)
[
At Wed, 19 Feb 2014 14:27:07 +0800,
Hsin-Yu Chao wrote:
>
> When a HDMI stream is opened with the same stream tag
> as a following opened stream to ca0132, audio will be
> heard from two ports simultaneously.
> Fix this issue by change to use snd_hda_codec_setup_stream
> and
This patch adds and enables simple-card support in DT node.
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610-twr.dts | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts b/arch/arm/boot/dts/vf610-twr.dts
index 29790c9..ff27dce
This patch adds and enables SGTL5000 codec support.
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610-twr.dts | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts b/arch/arm/boot/dts/vf610-twr.dts
index 8217854..29790c9 100644
---
Add audio card support for Vybird-TWR board
Xiubo Li (4):
ARM: dts: Add Freescale SAI ALSA SoC Digital Audio Interface node for
VF610.
ARM: dts: Enable SAI ALSA SoC DAI device for Vybrid VF610 TOWER board.
ARM: dts: Enable SGTL5000 codec based audio driver node for VF610
TOWER.
This patch adds the SAI's edma mux Tx and Rx support.
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
index 91a7757..f08df47 100644
--- a/arch/arm/boot/dts/vf610.dtsi
+++
This patch adds and enables the SAI device.
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610-twr.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts b/arch/arm/boot/dts/vf610-twr.dts
index e3a3805..8217854 100644
---
On Tue, 18 Feb 2014 15:16:50 -0800
Andrew Morton wrote:
> On Sun, 16 Feb 2014 20:31:01 +0800 Fabian Frederick wrote:
>
> > Any user can display extented attribute names without read
> > access.
> >
> > eg: attr -l
> >
> > This patch checks inode_permission in listxattr common
> > function
On 02/18/2014 11:13 PM, valdis.kletni...@vt.edu wrote:
> On Mon, 17 Feb 2014 16:51:37 +0400, Vladimir Davydov said:
>
>> out_fd = eventfd(0, 0);
>> if (out_fd < 0)
>> err(1, "eventfd");
>> ret = sendfile64(out_fd, in_fd, NULL, SIZE);
>> I'm not sure if this
When a HDMI stream is opened with the same stream tag
as a following opened stream to ca0132, audio will be
heard from two ports simultaneously.
Fix this issue by change to use snd_hda_codec_setup_stream
and snd_hda_codec_cleanup_stream instead, so that an
inactive stream can be marked as 'dirty'
On Tue, Feb 18, 2014 at 10:31:20PM +, Grant Likely wrote:
> Adds a selftest function for the of_match_node function. of_match_node
> is supposed to handle precedence for the compatible property as well as
> the name and device_type values. This patch adds some test case data and
> a function
Since clock operation within S2MPS11 and S5M8767 are similar, we can
support both the devices within a single driver.
Signed-off-by: Tushar Behera
Reviewed-by: Tomasz Figa
Reviewed-by: Yadwinder Singh Brar
---
drivers/clk/Kconfig |6 --
drivers/clk/clk-s2mps11.c |5 +
2
S5M8767 chip has 3 crystal oscillators which are operated in the same
as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
support clocks in S5M8767.
The patches are rebased on top of next-20130218.
Tushar Behera (2):
clk: clk-s2mps11: Refactor for including support for other
Incorrect ADC is picked in ca0132_capture_pcm_prepare(),
where it assumes multiple streams while there is one stream
per ADC. Note that ca0132_capture_pcm_cleanup() already does
the right thing.
The Chromebook Pixel has a microphone under the keyboard that
is attached to node id 0x8. Before this
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
to create an almost duplicate driver altogether.
Signed-off-by: Tushar Behera
Reviewed-by:
The userspace registers are stored at the top of the stack when the syscall
handler is invoked, which allows r0-r2 to act as parameters 5-7. Parameters
passed on the stack may be clobbered by the syscall handler. The solution
is to push an extra copy of the registers which might be used as syscall
In the current implementation of __of_match_node(), it will compare
each given match entry against all the node's compatible strings
with of_device_is_compatible().
To achieve multiple compatible strings per node with ordering from
specific to generic, this requires given matches to be ordered
When invoking syscall handlers on sh32, the saved userspace registers
are at the top of the stack. This seems to have been intentional, as it
is an easy way to pass r0, r1, ... to the handler as parameters 5, 6,
...
It causes problems, however, because the compiler is allowed to generate
code for
This does not appear to have been used since commit
74d99a5e262229ee865f6f68528d10b82471ead6 (sh: SH-2A FPU support) in
2007.
Signed-off-by: Bobby Bingham
---
arch/sh/math-emu/math.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/arch/sh/math-emu/math.c
The compiler is permitted to generate code which overwrites the parameters
to a function. If those parameters include the only saved copy we have of
userspace's registers, we're in trouble.
Signed-off-by: Bobby Bingham
---
arch/sh/include/asm/traps_32.h | 16
Ivan,
I'm having tremendous problems getting this driver to initialize. For
some reason, I can't get the driver to actually transition the
hardware into peripheral mode. At first I was getting a lot of probe
deferrals, based on not finding the regulators early enough in the
boot, and I thought
I re-send this patch after fixing subject.
Thanks.
Daeseok Youn
2014-02-19 15:05 GMT+09:00 David Miller :
> From: Daeseok Youn
> Date: Wed, 19 Feb 2014 14:09:49 +0900
>
>> From 18bd7236f36a248a0871f810cec3c1e98f098a91 Mon Sep 17 00:00:00 2001
>> From: Daeseok Youn
>> Date: Wed, 19 Feb 2014
>From a6ff4eec0b80ff6596a278623a02e3ed462c49ed Mon Sep 17 00:00:00 2001
From: Daeseok Youn
Date: Wed, 19 Feb 2014 13:44:24 +0900
Subject: [PATCH] ata: libahci: replace obselete simple_strtoul() with
kstrtouint()
Signed-off-by: Daeseok Youn
---
drivers/ata/libahci.c |5 +++--
1 file
Hi, All
arch/x86/kernel/pci-calgary.c is the only user of saved_max_pfn today:
int __init detect_calgary(void)
{
[..]
specified_table_size = determine_tce_table_size((is_kdump_kernel() ?
saved_max_pfn : max_pfn) * PAGE_SIZE);
[..]
}
On Tue, Feb 18, 2014 at 10:38:18PM +0300, Sergey Senozhatsky wrote:
> On (02/18/14 15:04), Minchan Kim wrote:
> [..]
> > 1.8.5.3
> >
> > As you can see, your patch made zram too much regressed when it
> > used one stream buffer. The reason I guessed is overhead of
> > scheduling by sleep/wakeup
Hello Sergey,
On Tue, Feb 18, 2014 at 12:20:17PM +0300, Sergey Senozhatsky wrote:
> Hello,
>
> On (02/18/14 15:04), Minchan Kim wrote:
> > Hello Sergey,
> >
> > On Thu, Feb 13, 2014 at 08:43:18PM +0300, Sergey Senozhatsky wrote:
> > > This patchset introduces zcomp compression backend
Function device_notifier() in intel-iommu.c fails to remove
device_domain_info data structures for PCI devices if they are
associated with si_domain because iommu_no_mapping() returns true
for those PCI devices. This will cause memory leak and caching of
stale information in domain->devices list.
On Sun, Feb 9, 2014 at 12:02 PM, Richard Weinberger wrote:
> Am 09.02.2014 19:57, schrieb Alexander Shiyan:
>>> The symbol is an orphan, get rid of it.
>>>
>>> Signed-off-by: Richard Weinberger
>>> ---
>>> arch/arm/mach-bcm/Kconfig | 1 -
>>> 1 file changed, 1 deletion(-)
>>>
>>> diff --git
Quoting Chen-Yu Tsai (2014-02-10 02:35:47)
> The Allwinner A20/A31 clock module controls the transmit clock source
> and interface type of the GMAC ethernet controller. Model this as
> a single clock for GMAC drivers to use.
>
> Signed-off-by: Chen-Yu Tsai
Looks good to me.
Regards,
Mike
>
Array 'g_iommus' may be freed twice on error recovery path in function
init_dmars() and free_dmar_iommu(), thus cause random system crash as
below.
[6.774301] IOMMU: dmar init failed
[6.778310] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[6.785615] software IO TLB [mem
Factor out function dmar_alloc_dev_scope() from dmar_parse_dev_scope()
for later reuse.
Signed-off-by: Jiang Liu
---
drivers/iommu/dmar.c | 28
include/linux/dmar.h |1 +
2 files changed, 17 insertions(+), 12 deletions(-)
diff --git a/drivers/iommu/dmar.c
Function device_notifier() in intel-iommu.c only remove domain_device_info
data structure associated with a PCI device when handling PCI device
driver unbinding events. If a PCI device has never been bound to a PCI
device driver, there won't be BUS_NOTIFY_UNBOUND_DRIVER event when
hot-removing the
Reduce duplicated code to handle virtual machine domains, there's no
functionality changes. It also improves code readability.
Signed-off-by: Jiang Liu
---
drivers/iommu/intel-iommu.c | 177 +++
1 file changed, 45 insertions(+), 132 deletions(-)
diff
Function get_domain_for_dev() is a little complex, simplify it
by factoring out dmar_search_domain_by_dev_info() and
dmar_insert_dev_info().
Signed-off-by: Jiang Liu
---
drivers/iommu/intel-iommu.c | 142 ---
1 file changed, 66 insertions(+), 76
The iommu_count field in si_domain(static identity domain) is
initialized to zero and never increases. It will underflow
when tearing down iommu unit in function free_dmar_iommu()
and leak memory. So refine code to correctly manage
si_domain->iommu_count.
Warning message caused by si_domain
Enhance function get_domain_for_dev() to release allocated resources
if failed to create domain for PCIe endpoint, otherwise the allocated
resources will get lost.
Signed-off-by: Jiang Liu
---
drivers/iommu/intel-iommu.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
Now we have a PCI bus notification based mechanism to update DMAR
device scope array, we could extend the mechanism to support boot
time initialization too, which will help to unify and simplify
the implementation.
Signed-off-by: Jiang Liu
---
drivers/iommu/dmar.c| 163
Introduce for_each_dev_scope()/for_each_active_dev_scope() to walk
{active} device scope entries. This will help following RCU lock
related patches.
Signed-off-by: Jiang Liu
---
drivers/iommu/dmar.c| 14 +++---
drivers/iommu/intel-iommu.c | 100
Domain id 0 will be assigned to invalid translation without allocating
domain data structure if DMAR unit supports caching mode. So in function
free_dmar_iommu(), we should check whether the domain pointer is NULL,
otherwise it will cause system crash as below:
[6.790519] BUG: unable to handle
Global DMA and interrupt remapping resources may be accessed in
interrupt context, so use RCU instead of rwsem to protect them
in such cases.
Signed-off-by: Jiang Liu
---
drivers/iommu/dmar.c| 33 -
drivers/iommu/intel-iommu.c | 20
Introduce a global rwsem dmar_global_lock, which will be used to
protect DMAR related global data structures from DMAR/PCI/memory
device hotplug operations in process context.
DMA and interrupt remapping related data structures are read most,
and only change when memory/PCI/DMAR hotplug event
Current Intel IOMMU driver only matches a PCIe root port with the first
DRHD unit with the samge segment number. It will report false result
if there are multiple DRHD units with the same segment number, thus fail
to detect ATS capability for some PCIe devices.
This patch refines function
Current Intel DMAR/IOMMU driver assumes that all PCI devices associated
with DMAR/RMRR/ATSR device scope arrays are created at boot time and
won't change at runtime, so it caches pointers of associated PCI device
object. That assumption may be wrong now due to:
1) introduction of PCI host bridge
If static identity domain is created, IOMMU driver needs to update
si_domain page table when memory hotplug event happens. Otherwise
PCI device DMA operations can't access the hot-added memory regions.
Signed-off-by: Jiang Liu
---
drivers/iommu/intel-iommu.c | 71
Move private structures and variables into intel-iommu.c, which will
help to simplify locking policy for hotplug. Also delete redundant
declarations.
Signed-off-by: Jiang Liu
---
drivers/iommu/intel-iommu.c | 31 +--
include/linux/dmar.h| 23
Intel DMA/interrupt remapping drivers scan available PCI/memory devices
at startup and cache discovered hardware topologies. They don't update
cached information if PCI/memory hotplug event happens at runtime, then
the stale information may break DMA/interrupt remapping logic.
This patchset first
From: Daeseok Youn
Date: Wed, 19 Feb 2014 14:09:49 +0900
> From 18bd7236f36a248a0871f810cec3c1e98f098a91 Mon Sep 17 00:00:00 2001
> From: Daeseok Youn
> Date: Wed, 19 Feb 2014 13:44:24 +0900
> Subject: [PATCH] atm: libahci: replace obselete simple_strtoul() with
> kstrtouint()
>
>
Use public function acpi_evaluate_ost() to replace open-coded
version of evaluating ACPI _OST method.
Signed-off-by: Jiang Liu
---
drivers/xen/xen-acpi-pad.c | 26 +++---
1 file changed, 7 insertions(+), 19 deletions(-)
diff --git a/drivers/xen/xen-acpi-pad.c
Use public function acpi_evaluate_ost() to replace open-coded
version of evaluating ACPI _OST method.
Signed-off-by: Jiang Liu
---
drivers/acpi/processor_perflib.c | 14 +++---
1 file changed, 3 insertions(+), 11 deletions(-)
diff --git a/drivers/acpi/processor_perflib.c
Use public function acpi_evaluate_ost() to replace open-coded
version of evaluating ACPI _OST method.
Signed-off-by: Jiang Liu
---
drivers/acpi/acpi_pad.c | 24 +---
1 file changed, 5 insertions(+), 19 deletions(-)
diff --git a/drivers/acpi/acpi_pad.c
Rename acpi_evaluate_hotplug_ost() to acpi_evaluate_ost() for later resue.
Signed-off-by: Jiang Liu
---
drivers/acpi/utils.c| 14 --
include/acpi/acpi_bus.h | 10 +-
2 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/drivers/acpi/utils.c
Use device name "LNXSYBUS:xx" instead of "device.xx" for ACPI objects
\_SB and \_TZ.
BTW, the original check of "handle == ACPI_ROOT_OBJECT" in statment
"else if (list_empty(>ids) && handle == ACPI_ROOT_OBJECT)"
is always false because of the code at the begin of that block.
if
Hi Rafael,
Thanks for reminder, will fix it in next version.
Cheers!
Gerry
On 2014/2/18 9:07, Rafael J. Wysocki wrote:
> On Monday, February 17, 2014 01:02:50 PM Jiang Liu wrote:
>> Use public function acpi_evaluate_pad() to replace open-coded
>
> I suppose you mean acpi_evaluate_ost()?
hello,
I made http://www.xrefs.info available to open source community in
the hope of making open source developers more productive.
The site hosts many open source code projects' cross references based
on OpenGrok, which is a very fast cross reference tool, and easy to use.
To access, you can go
(more than usual) the powerpc allyesconfig build.
Changes since 20140218:
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The sound-asoc tree gained a build failure for which I disabled a new
driver.
Non-mer
Hi Rafael,
We have following code to deal with existing users.
+#ifdef ACPI_HOTPLUG_OST
+#defineacpi_evaluate_hotplug_ost acpi_evaluate_ost
+#else
+static inline acpi_status
acpi_evaluate_hotplug_ost(acpi_handle handle, u32 source_event,
- u32
Thanks, Rafael. I will drop this patch then.
On 2014/2/18 9:06, Rafael J. Wysocki wrote:
> On Monday, February 17, 2014 01:02:48 PM Jiang Liu wrote:
>> Use callback acpi_drv_ops->notify to simplify acpi_pad driver's
>> notification handling code.
>>
>> Signed-off-by: Jiang Liu
>
> There is a
On Wednesday 19 February 2014 01:40 AM, Greg KH wrote:
> On Mon, Feb 17, 2014 at 02:29:17PM +0530, Kishon Vijay Abraham I wrote:
>> Hi Greg,
>>
>> Here's the PULL requeust for PHY subsystem for this -rc cycle. There isn't
>> anything major but a bunch of obvious fixes and cleanup.
>>
>> Let me
On Wednesday 19 February 2014 01:41 AM, Greg KH wrote:
> On Mon, Feb 17, 2014 at 02:29:20PM +0530, Kishon Vijay Abraham I wrote:
>> From: Sachin Kamat
>>
>> PTR_ERR_OR_ZERO simplifies the code.
>>
>> Signed-off-by: Sachin Kamat
>> Cc: Matt Porter
>> Signed-off-by: Kishon Vijay Abraham I
>> ---
Update Liam and Mark's mail.
On 02/19/2014 01:20 PM, Nenghua Cao wrote:
> From: Nenghua Cao
>
> In snd_soc_bytes_put function, it forces cpu to do cpu_to_be translation,
> but for mmio bus which uses REGMAP_ENDIAN_NATIVE, it doesn't need to do
> endian translation. So it is better to use
Update Liam and Mark's mail.
On 02/19/2014 01:19 PM, Nenghua Cao wrote:
> From: Nenghua Cao
>
> In some cases, we need regmap's format parse_val function
> to do be/le translation according to the bus configuration.
> For example, snd_soc_bytes_put() uses regmap to write/read values,
>
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
sound/soc/intel/sst-dsp.c: In function 'sst_dsp_outbox_write':
sound/soc/intel/sst-dsp.c:218:2: error: implicit declaration of function
'memcpy_toio' [-Werror=implicit-function-declaration]
From: Nenghua Cao
In some cases, we need regmap's format parse_val function
to do be/le translation according to the bus configuration.
For example, snd_soc_bytes_put() uses regmap to write/read values,
and use cpu_to_be() directly to covert MASK into big endian. This
is a defect, and should
Since cpu which is put into quiescent mode, would remove itself
from kernel's sched_domain. So we could use search sched_domain
method to check whether this cpu don't want to be disturbed as
idle load balance would send IPI to it.
Signed-off-by: Lei Wen
---
kernel/sched/fair.c | 14
From: Nenghua Cao
In snd_soc_bytes_put function, it forces cpu to do cpu_to_be translation,
but for mmio bus which uses REGMAP_ENDIAN_NATIVE, it doesn't need to do
endian translation. So it is better to use regmap's api which can decide
if this translation is needed according to bus
>From 6297aabeff748777b520cc0ee835af0a3ddc79e2 Mon Sep 17 00:00:00 2001
From: Daeseok Youn
Date: Wed, 19 Feb 2014 10:49:12 +0900
Subject: [PATCH] atm: solos-pci: make solos_bh() as static
sparse says:
drivers/atm/solos-pci.c:763:6: warning:
symbol 'solos_bh' was not declared. Should it be
>From c320d2ea1ed51c88255c33a50c74fa3598ab7be6 Mon Sep 17 00:00:00 2001
From: Daeseok Youn
Date: Wed, 19 Feb 2014 10:10:11 +0900
Subject: [PATCH] atm: nicstar: use NULL instead of 0 for pointer
sparse says:
drivers/atm/nicstar.c:642:27: warning:
Using plain integer as NULL pointer
_PDC related stuff in processor_core.c is little bit X86/IA64
dependent, macros of ACPI_PDC_* are _PDC bit definitions for
Intel processors, if we use these macros in processor_core.c,
we can not compile it when ACPI is enabled on ARM/ARM64.
This patch reworks the code to make it more
>From 932e928d53b1e588dc17019e7f9fa7a61b8b7468 Mon Sep 17 00:00:00 2001
From: Daeseok Youn
Date: Wed, 19 Feb 2014 10:35:41 +0900
Subject: [PATCH] atm: ambassador: use NULL instead of 0 for pointer
sparse says:
drivers/atm/ambassador.c:1928:24: warning:
Using plain integer as NULL pointer
1 - 100 of 2250 matches
Mail list logo
