Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/x86/entry/entry_64_compat.S
between commit:
cd88ec231701 ("x86: fix error handling for 32-bit compat out-of-range system
call numbers")
from Linus' tree and commit:
c73e36b775a7 ("x86/asm/entry/32: Replace
Hi Sam,
On Fri, Aug 14, 2015 at 03:07:28PM +1000, Sam Bobroff wrote:
> On Thu, May 21, 2015 at 01:57:04PM +0530, Gautham R. Shenoy wrote:
> > In guest_exit_cont we call kvmhv_commence_exit which expects the trap
> > number as the argument. However r3 doesn't contain the trap number at
> > this
Hello,
On 17 August 2015 at 03:55, Jaehoon Chung wrote:
> Hi, Michal.
>
> On 08/12/2015 09:23 PM, Michal Suchanek wrote:
>> The driver has open-coded test for SDIO cards. Use the mmc core provided
>> MMC_QUIRK_BROKEN_CLK_GATING flag instead.
>
> Did you use the clock-gating for SDIO cards?
>
Hi Inki,
On Mon, 17 Aug 2015 13:53:42 +1000 Stephen Rothwell
wrote:
>
> On Mon, 17 Aug 2015 13:51:30 +1000 Stephen Rothwell
> wrote:
> >
> > After merging the drm-exynos tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> >
2015-07-22 21:04 GMT+08:00 Lee Jones :
> Lots of platforms contain clocks which if turned off would prove fatal.
> The only way to recover from these catastrophic failures is to restart
> the board(s). Now, when a clock provider is registered with the
> framework it is possible for a list of
We give out loans at low 3% interest rate and We are always ready to cater to
your loan need no matter your credit background.I will offer you loan as you
requested, be you inform that we only attend to serious individuals, if you are
applying this loan i will want you to be serious about it, i
Hi,
On Friday 07 August 2015 06:00 PM, Chunfeng Yun wrote:
> support usb3.0 phy of mt65xx SoCs
>
> Signed-off-by: Chunfeng Yun
change $subject to phy:
> ---
> drivers/phy/Kconfig | 9 +
> drivers/phy/Makefile | 1 +
> drivers/phy/phy-mt65xx-usb3.c | 467
>
Hi James,
After merging the security tree, today's linux-next build (x86_64
allmodconfig) failed like this:
scripts/extract-cert.c:23:25: fatal error: openssl/bio.h: No such file or
directory
#include
^
compilation terminated.
scripts/sign-file.c:20:25: fatal error:
On 8/17/15 12:32 PM, Naoya Horiguchi wrote:
> [...]
> OK, so I wrote the next version against mmotm-2015-08-13-15-29 (replied to
> this email.) It moves PageSetHWPoison part into migration code, which should
> close up the reported race window and minimize the another revived race window
> of
On 08/11/2015 11:57 PM, Jungseok Lee wrote:
On Aug 4, 2015, at 4:44 PM, AKASHI Takahiro wrote:
Hi Akashi,
On arm64, an exception handler use the same stack as in non-exception
contexts, but doesn't create a stack frame for elx_xx entry, only updating
sp register. This behavior results in
Hi
On 08/11/2015 11:52 PM, Jungseok Lee wrote:
On Aug 4, 2015, at 4:44 PM, AKASHI Takahiro wrote:
Hi Akashi,
See the following threads [1],[2] for the background.
With this patch series, I'm trying to fix several problems I noticed
with stack tracer on arm64. But it is rather experimental,
Hi Neil,
Today's linux-next merge of the md tree got a conflict in:
drivers/md/raid5.c
between commit:
4246a0b63bd8 ("block: add a bi_error field to struct bio")
8ae126660fdd ("block: kill merge_bvec_fn() completely")
from the block tree and commit:
1722781be955 ("md/raid5: switch to
Hi Neil,
Today's linux-next merge of the md tree got a conflict in:
drivers/md/raid10.c
between commit:
4246a0b63bd8 ("block: add a bi_error field to struct bio")
from the block tree and commit:
90421c7cfde6 ("md/raid10: ensure device failure recorded before write request
returns.")
Hi Neil,
Today's linux-next merge of the md tree got a conflict in:
drivers/md/raid0.c
between commit:
8ae126660fdd ("block: kill merge_bvec_fn() completely")
from the block tree and commit:
927d881980b7 ("md/raid0: update queue parameter in a safer location.")
from the md tree.
I
On Mon, Aug 17, 2015 at 12:29:56AM +0200, Jiri Olsa wrote:
> hi,
> 'perf test 18' is failing on systems with AMD processor.
Hmm, still using that b0rked test box? :-)
Also, which kernel?
There have been substantial changes to the entry code recently. Although
I don't see anything being done
memory_failure() can be called at any page at any time, which means that we
can't eliminate the possibility of containment failure. In such case the best
option is to leak the page intentionally (and never touch it later.)
We have an unpoison function for testing, and it cannot handle such
num_poisoned_pages counter will be changed outside mm/memory-failure.c by a
subsequent patch, so this patch prepares wrappers to manipulate it.
Signed-off-by: Naoya Horiguchi
---
include/linux/swapops.h | 23 +++
mm/memory-failure.c | 30 ++
2
From: Wanpeng Li
Wanpeng Li reported a race between soft_offline_page() and unpoison_memory(),
which causes the following kernel panic:
[ 61.572584] BUG: Bad page state in process bash pfn:97000
[ 61.578106] page:ea00025c count:0 mapcount:1 mapping:
(null)
On Fri, Aug 14, 2015 at 05:01:34PM +0800, Wanpeng Li wrote:
> On 8/14/15 4:38 PM, Naoya Horiguchi wrote:
> > On Fri, Aug 14, 2015 at 03:59:21PM +0800, Wanpeng Li wrote:
> >> On 8/14/15 3:54 PM, Wanpeng Li wrote:
> >>> [...]
> OK, then I rethink of handling the race in unpoison_memory().
>
On Mon, Aug 17, 2015 at 11:29 AM, Leilk Liu wrote:
>
> This patch adds MT8173 spi bus controllers into device tree.
>
> Signed-off-by: Leilk Liu
Reviewed-by: Daniel Kurtz
> ---
> Change in this patch:
> pinctl and pad-select fields are board specific, so move to
> mt8173-evb.dtsi, and status
Modern Intel Core CPUs (5th and 6th generation) have a Intel Processor Trace
(PT) feature
to trace branch execution with low overhead. This is useful for performance
analysis and debugging.
simple-pt is a simple standalone driver and decoder tool to implement PT on
Linux.
Starting with Linux
On 08/13/2015 11:41 PM, Stephen Boyd wrote:
On 08/13, Rajendra Nayak wrote:
Export symbol pm_genpd_init so it can be used in loadable
kernel modules
Signed-off-by: Rajendra Nayak
Reported-by: Stephen Rothwell
---
I'd like to take this through the clk tree somehow so that we can
merge the
On Mon, Aug 17, 2015 at 11:27:01AM +0800, yalin wang wrote:
> i just want the x86 copy_from{to,in}_user() function have
> the same behaviour as other platforms.
Back to the original question from 2 mails ago:
How else would we be able to use the same function in copy_to and
copy_from variants?
Add snps,quirk-frame-length-adjustment property which provides value
for post silicon frame length adjustment
Signed-off-by: Nikhil Badola
---
Changes for v2
- changed quirk name as well description
Documentation/devicetree/bindings/usb/dwc3.txt | 3 +++
1 file changed, 3 insertions(+)
On Tue, 28 Jul 2015 16:45:15 -0300
Danilo Cesar Lemes de Paula wrote:
> Functions, Structs and Parameters definitions on kernel documentation
> are pure cosmetic, it only highlights the element.
>
> To ease the navigation in the documentation we should use inside
> those tags so readers can
On Wed, 2015-08-12 at 08:43 -0700, Paul E. McKenney wrote:
> On Wed, Aug 12, 2015 at 02:44:15PM +0100, Will Deacon wrote:
> > Hello Paul,
> >
> > On Fri, Jul 24, 2015 at 04:30:46PM +0100, Paul E. McKenney wrote:
> > > On Fri, Jul 24, 2015 at 12:31:01PM +0100, Will Deacon wrote:
> > > > On Wed,
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
drivers/md/dm.c
between commit:
bd4aaf8f9b85 ("dm: fix dm_merge_bvec regression on 32 bit systems")
from Linus' tree and commit:
8ae126660fdd ("block: kill merge_bvec_fn() completely")
from the block tree.
I fixed
Add "snps,quirk-frame-length-adjustment" property to
USB3 node for erratum A009116. This property provides
value of GFLADJ_30MHZ for post silicon frame length
adjustment.
Signed-off-by: Nikhil Badola
---
Changes for v2 :
- updated property name
arch/arm/boot/dts/ls1021a.dtsi | 1 +
1
On Sat, Aug 15, 2015 at 7:48 AM, pku.leo < pku@gmail.com > wrote:
> On Fri, Aug 14, 2015 at 1:24 AM, Yao Yuan wrote:
> > Hi Leo,
> >
> > Thanks for your review.
> > About those two methods for DMA suspend that you have mentioned. We
> have a lot of the discussions in other DMA driver like DMA
Add adjust_frame_length_quirk for writing to fladj register
which adjusts (micro)frame length to value provided by
"snps,quirk-frame-length-adjustment" property thus avoiding
USB 2.0 devices to time-out over a longer run
Signed-off-by: Nikhil Badola
---
changes for v2 :
- updated quirk's
Hi Inki,
On Mon, 17 Aug 2015 13:51:30 +1000 Stephen Rothwell
wrote:
>
> After merging the drm-exynos tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpu/drm/exynos/exynos_mixer.c: In function 'vp_video_buffer':
>
chipselect (in the case of spi-gpio: spi_gpio_chipselect, which
calls gpiod_set_raw_value_cansleep) can sleep, so we should not
hold a spinlock while calling it from spi_bitbang_setup.
This issue was introduced by this commit, which converted spi-gpio
to cansleep variants:
d9dda5a191 "spi:
On 17.08.2015 11:28, Joonyoung Shim wrote:
> On 08/17/2015 11:00 AM, Krzysztof Kozlowski wrote:
>> On 17.08.2015 10:47, Joonyoung Shim wrote:
>>> Hi,
>>>
>>> On 08/13/2015 07:02 PM, Krzysztof Kozlowski wrote:
W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
> According to datasheet, the
Hi Inki,
After merging the drm-exynos tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/gpu/drm/exynos/exynos_mixer.c: In function 'vp_video_buffer':
drivers/gpu/drm/exynos/exynos_mixer.c:395:15: error: 'struct exynos_drm_plane'
has no member named 'pixel_format'
On Fri, Aug 14, 2015 at 2:45 AM, nick wrote:
>
>
> On 2015-07-16 08:00 AM, Linus Walleij wrote:
>> On Sat, Jul 4, 2015 at 10:34 PM, Nicholas Krause wrote:
>>
>>> This fixes the build warning , warning: cast from pointer to integer
>>> of different size when building this file on a x86
Hi, Fabio,
Based on the analysis and discussion, we prefer to use
ls1021a_defconfig and remove LS1021A from imx_v6_v7_defconfig.
Thanks.
Best Regards,
Alison Wang
> On Fri, Aug 14, 2015 at 2:06 PM, Horia Geantă
> wrote:
>
> > Another thing:
> > Commit 385c0fb0e2c4 ("ARM:
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/8/3 21:10, Fu, Zhonghui wrote:
> Enable sdhci-acpi device to suspend/resume asynchronously.
> This can improve system suspend/resume speed.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/mmc/host/sdhci-acpi.c |2 ++
> 1 files
On Sun, Aug 16, 2015 at 03:06:39PM +0100, Russell King - ARM Linux wrote:
> All writel() implementations take a CPU number and write it in little
> endian format. Hence, writel() almost always uses cpu_to_le32()
> internally.
I think the reason this keeps coming up is that people aren't
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/8/3 20:39, Fu, Zhonghui wrote:
> Enable mmc host device to suspend/resume asynchronously.
> This can improve system suspend/resume speed.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/mmc/core/host.c |1 +
> 1 files changed, 1
Hi Chanwoo,
Similar patch was posted here[1].
[1]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/291023.html
Thanks,
Pankaj Dubey
On Tuesday 11 August 2015 09:16 AM, Chanwoo Choi wrote:
This patch add the uart2 devicetree node for Exynos3250 SoC.
Cc: Kukjin Kim
Cc:
This patch adds MT8173 spi bus controllers into device tree.
Signed-off-by: Leilk Liu
---
Change in this patch:
pinctl and pad-select fields are board specific, so move to
mt8173-evb.dtsi, and status = "okay".
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 18 ++
Hi Chanwoo,
Thanks for this patch. Similar patch[1] was posted long back, and there
were some concern from your side, if you think those concerns are fixed,
then my patch [1] are still valid and can be taken. If it needs to be
rebase I am happy to do that.
[1]
On 2015/8/14 20:20, Grygorii Strashko wrote:
> Now irq_chip_retrigger_hierarchy() returns -ENOSYS if it
> was not able to find at least one .irq_retrigger() callback
> implemented in IRQ domain hierarchy. As result, IRQ
> re-triggering is not working now on ARM (TI OMAP) where
> ARM GIC is not
Hi Thierry,
Today's linux-next merge of the drm-panel tree got a conflict in:
arch/arm/configs/multi_v7_defconfig
between commit:
258d9bc5e77f ("ARM: tegra: Update multi_v7_defconfig")
from the tegra tree and commit:
330b48bd700d ("drm/bridge: Add vendor prefixes")
from the drm-panel
> On Aug 14, 2015, at 00:43, Borislav Petkov wrote:
>
> On Thu, Aug 13, 2015 at 06:04:54PM +0800, yalin wang wrote:
>> we store type into one fix register, for example r12 ,
>> then in fix up code, we can know the exception is caused by copy_from
>> copy_to or copy_in user function by check r12
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/7/30 15:40, Fu, Zhonghui wrote:
> Enable SDIO card and function device to suspend/resume asynchronously.
> This can improve system suspend/resume speed.
>
> Signed-off-by: Zhonghui Fu
> ---
> drivers/mmc/core/sdio.c |4
> 1
>From the "Juno ARM Development Platform Soc Techinical Reference
>Mannual(r1p0)",
we get the following memory map sizes (3-25):
I2C : 0x7ffa 0x7ffa00ff (256B)
USB OHCI : 0x7ffb 0x7ffb0fff (4KB)
USB EHCI : 0x7ffc 0x7ffc0fff (4KB)
This
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/i915/intel_atomic.c
drivers/gpu/drm/i915/intel_display.c
between commits:
f0fdc55db0c6 ("drm/i915: calculate primary visibility changes instead of
calling from set_config")
d2944cf21305 ("drm/i915:
With typical CPU hot-addition flow on x86, PCI host bridges embedded
in physical processor are always associated with NOMA_NO_NODE, which
may cause sub-optimal performance.
1) Handle CPU hot-addition notification
acpi_processor_add()
acpi_processor_get_info()
Function i40e_clean_rx_irq() tries to reuse memory pages allocated
from the nearest node. To better support memoryless node, use
numa_mem_id() instead of numa_node_id() to get the nearest node with
memory.
This change should only affect performance.
Signed-off-by: Jiang Liu
---
Function profile_cpu_callback() allocates memory without specifying
__GFP_THISNODE flag, so replace cpu_to_mem() with cpu_to_node()
because cpu_to_mem() may cause suboptimal memory allocation if
there's no free memory on the node returned by cpu_to_mem().
It's safe to use cpu_to_mem() because
Function ovs_flow_stats_update() allocates memory with __GFP_THISNODE
flag set, which may cause permanent memory allocation failure on
memoryless node. So replace cpu_to_node() with cpu_to_mem() to better
support memoryless node. For node with memory, cpu_to_mem() is the same
as cpu_to_node().
Current kernel only updates _mem_id_[cpu] for onlined CPUs when memory
configuration changes. So kernel may allocate memory from remote node
for a CPU if the CPU is still in absent or offline state even if the
node associated with the CPU has already been onlined. This patch tries
to improve
Function i40e_clean_rx_irq() tries to reuse memory pages allocated
from the nearest node. To better support memoryless node, use
numa_mem_id() instead of numa_node_id() to get the nearest node with
memory.
This change should only affect performance.
Signed-off-by: Jiang Liu
---
With current implementation, all CPUs within a NUMA node will be
assocaited with another NUMA node if the node has no memory installed.
For example, on a four-node system, CPUs on node 2 and 3 are associated
with node 0 when are no memory install on node 2 and 3, which may
confuse users.
Function xpc_create_gru_mq_uv() allocates memory with __GFP_THISNODE
flag set, which may cause permanent memory allocation failure on
memoryless node. So replace cpu_to_node() with cpu_to_mem() to better
support memoryless node. For node with memory, cpu_to_mem() is the same
as cpu_to_node().
This is the third version to enable memoryless node support on x86
platforms. The previous version (https://lkml.org/lkml/2014/7/11/75)
blindly replaces numa_node_id()/cpu_to_node() with numa_mem_id()/
cpu_to_mem(). That's not the right solution as pointed out by Tejun
and Peter due to:
1) We
According to x86 boot sequence, early_cpu_to_node() always returns
NUMA_NO_NODE when called from numa_init(). So kill useless code
to improve code readability.
Related code sequence as below:
x86_cpu_to_node_map is set until step 2, so it is still the default
value (NUMA_NO_NODE) when accessed at
Patch has landed in -rc7, thanks David!
On Fri, Aug 14, 2015 at 12:49 PM, Alexandre Courbot wrote:
> On Wed, Aug 12, 2015 at 6:59 PM, Afzal Mohammed
> wrote:
>> Hi,
>>
>> On Wed, Aug 12, 2015 at 04:40:57PM +0900, Alexandre Courbot wrote:
>>
>>> Great, thanks. Are you also on an optimus
On 14 August 2015 at 23:27, Greg KH wrote:
> On Fri, Aug 14, 2015 at 05:47:45PM +0800, Baolin Wang wrote:
>> This patch introduces the usb charger driver based on usb gadget that
>> makes an enhancement to a power driver. It works well in practice but
>> that requires a system with suitable
Voltage tolerance isn't necessarily same on both sides of the target
voltage and regulator_set_voltage_tol() wouldn't be suitable in such
cases.
Add another routine regulator_set_voltage_triplet(), which accepts
target, min and max voltages as arguments.
This first tries to set the voltage
The following race conditions can happen when a serial port is used
as console.
Case1: CPU_B is used to detect an interrupt from a serial port,
but it can have interrupts disabled during the waiting time.
Case2: CPU_B clears UART_IER just after CPU_A sets UART_IER and then
a serial
On Fri, Aug 14, 2015 at 07:04:56PM +0800, Baolin Wang wrote:
> On 14 August 2015 at 16:55, Li Jun wrote:
> > Hi Baolin,
> >
> > On Fri, Aug 14, 2015 at 05:47:43PM +0800, Baolin Wang wrote:
> >> Currently the Linux kernel does not provide any standard integration of
> >> this
> >> feature that
When direct read IO is submitted from kernel, it is often
unnecessary to dirty pages, for example of loop, dirtying pages
have been considered in the upper filesystem(over loop) side
already, and they don't need to be dirtied again.
So this patch doesn't dirtying pages for ITER_BVEC/ITER_KVEC
If loop block is mounted via 'mount -o loop', it isn't easy
to pass file descriptor opened as O_DIRECT, so this patch
introduces a new command to support direct IO for this case.
Cc: linux-...@vger.kernel.org
Signed-off-by: Ming Lei
---
drivers/block/loop.c | 19 +++
The following patch will use dio/aio to submit IO to backing file,
then it needn't to schedule IO concurrently from work, so
use kthread_work for decreasing context switch cost a lot.
For non-AIO case, single thread has been used for long long time,
and it was just converted to work in v4.0,
It doesn't make sense to enable merge because the I/O
submitted to backing file is handled page by page.
Signed-off-by: Ming Lei
---
drivers/block/loop.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index f9889b6..eee7510 100644
---
Hi Guys,
There are about 3 advantages to use direct I/O and AIO on
read/write loop's backing file:
1) double cache can be avoided, then memory usage gets
decreased a lot
2) not like user space direct I/O, there isn't cost of
pinning pages
3) avoid context switch for obtaining good throughput
-
This patches provides one interface for enabling direct IO
from user space:
- userspace(such as losetup) can pass 'file' which is
opened/fcntl as O_DIRECT
Also __loop_update_dio() is introduced to check if direct I/O
can be used on current loop setting.
The last big change is to
There are at least 3 advantages to use direct I/O and AIO on
read/write loop's backing file:
1) double cache can be avoided, then memory usage gets
decreased a lot
2) not like user space direct I/O, there isn't cost of
pinning pages
3) avoid context switch for obtaining good throughput
- in
On 08/17/2015 11:00 AM, Krzysztof Kozlowski wrote:
> On 17.08.2015 10:47, Joonyoung Shim wrote:
>> Hi,
>>
>> On 08/13/2015 07:02 PM, Krzysztof Kozlowski wrote:
>>> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
According to datasheet, the S2MPS13X and S2MPS14X should update write
On 17-08-15, 12:17, Stephen Rothwell wrote:
> Hi Eduardo,
>
> Today's linux-next merge of the thermal-soc tree got a conflict in:
>
> drivers/thermal/cpu_cooling.c
>
> between commit:
>
> df6f527755a5 ("thermal: cpu_cooling: fix lockdep problems in cpu_cooling")
>
> from the arm tree and
On 15-08-15, 07:08, Mark Brown wrote:
> On Sat, Aug 15, 2015 at 08:41:49AM +0530, Viresh Kumar wrote:
>
> > Hopefully below version looks better ?
>
> Please don't bury patches at the end of replies to messages in the
> middle of threads, send them in a form where they can be applied
> directly.
On Fri, Aug 14, 2015 at 05:47:46PM +0800, Baolin Wang wrote:
> Integrate with the newly added USB charger interface to limit the current
> we draw from the USB input based on the input device configuration
> identified by the USB stack, allowing us to charge more quickly from high
> current inputs
Hi Eduardo,
Today's linux-next merge of the thermal-soc tree got a conflict in:
drivers/thermal/cpu_cooling.c
between commit:
df6f527755a5 ("thermal: cpu_cooling: fix lockdep problems in cpu_cooling")
from the arm tree and commits:
02373d7c69b4 ("thermal: cpu_cooling: fix lockdep
On 11.08.2015 12:46, Chanwoo Choi wrote:
> This patch add the MSHC2 (Mobile Storage Host Controller) devicetree node for
> Exynos3250 SoC.
s/add/adds/
s/devicetree/Device Tree/
>
> Cc: Kukjin Kim
> Cc: Krzysztof Kozlowski
> Signed-off-by: Chanwoo Choi
> ---
>
On 11.08.2015 12:46, Chanwoo Choi wrote:
> This patch add the uart2 devicetree node for Exynos3250 SoC.
"This patch adds the UART2 Device Tree node..."
>
> Cc: Kukjin Kim
> Cc: Krzysztof Kozlowski
> Signed-off-by: Chanwoo Choi
> ---
> arch/arm/boot/dts/exynos3250-pinctrl.dtsi | 7 +++
>
On 17 August 2015 at 08:40, Peter Chen wrote:
> On Fri, Aug 14, 2015 at 05:47:44PM +0800, Baolin Wang wrote:
>> The usb charger framework is based on usb gadget, and each usb gadget
>> can be one usb charger to set the current limitation.
>>
>> This patch adds a notifier mechanism for usb charger
On 17.08.2015 10:47, Joonyoung Shim wrote:
> Hi,
>
> On 08/13/2015 07:02 PM, Krzysztof Kozlowski wrote:
>> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
>>> According to datasheet, the S2MPS13X and S2MPS14X should update write
>>> buffer via setting WUDR bit to high after ctrl register is
Hi, Michal.
On 08/12/2015 09:23 PM, Michal Suchanek wrote:
> The driver has open-coded test for SDIO cards. Use the mmc core provided
> MMC_QUIRK_BROKEN_CLK_GATING flag instead.
Did you use the clock-gating for SDIO cards?
Doesn't MMC_CAP_SDIO_IRQ bit set? Which case is broken?
Could you explain
On Fri, Aug 14, 2015 at 05:47:44PM +0800, Baolin Wang wrote:
> The usb charger framework is based on usb gadget, and each usb gadget
> can be one usb charger to set the current limitation.
>
> This patch adds a notifier mechanism for usb charger to report to usb
> charger when the usb gadget
Hi,
On 08/13/2015 07:02 PM, Krzysztof Kozlowski wrote:
> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
>> According to datasheet, the S2MPS13X and S2MPS14X should update write
>> buffer via setting WUDR bit to high after ctrl register is updated.
>
> Hi,
>
> I cannot find this information in
On 2015/7/30 13:55, Emmanuel Grumbach wrote:
> On Thu, Jul 30, 2015 at 8:18 AM, Fu, Zhonghui
> wrote:
>> Enable wiphy device to suspend/resume asynchronously. This can improve
>> system suspend/resume speed.
>>
> How will that impact the timing with respect to the suspend call
> coming from the
On 11.08.2015 12:46, Chanwoo Choi wrote:
> This patch add the MMC2 clocks (mux, divider, gate) of Exynos3250 SoC.
>
> Cc: Sylwester Nawrocki
> Cc: Tomasz Figa
> Signed-off-by: Chanwoo Choi
> ---
> drivers/clk/samsung/clk-exynos3250.c | 9 +
> include/dt-bindings/clock/exynos3250.h |
On 08/13/2015 07:42 PM, Krzysztof Kozlowski wrote:
> W dniu 13.08.2015 o 19:02, Krzysztof Kozlowski pisze:
>> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
>>> According to datasheet, the S2MPS13X and S2MPS14X should update write
>>> buffer via setting WUDR bit to high after ctrl register is
On Thu, 13 Aug 2015, Kirill A. Shutemov wrote:
> Hugh has pointed that compound_head() call can be unsafe in some
> context. There's one example:
>
> CPU0CPU1
>
> isolate_migratepages_block()
> page_count()
> compound_head()
> !!PageTail()
Hi,
I tried myself at solving the bugzilla report 100781 that can be
found here: https://bugzilla.kernel.org/show_bug.cgi?id=100781
You'll find in the following email the patch I did for that.
I welcome any advice or remarks (or insults, but please be gentle,
I'm still a newbie!) to make that
If a non-root user tries to specify a trace event and the tracefs
files can't be read, it will tell about it in a somewhat cryptic
way and as well say that the tracepoint is unknown, which is
obvious, since the tracefs files were not read.
This patch changes this behavior by using the
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in:
drivers/cpufreq/exynos-cpufreq.c
between commit:
966f2a71a92d ("cpufreq: exynos: remove Exynos4x12 specific cpufreq driver
support")
from the samsung tree and commit:
62c3f2fddd43 ("cpufreq: exynos: Fix for memory
在 2015/8/15 6:13, Heiko Stübner 写道:
Hi Shawn,
Am Freitag, 14. August 2015, 16:34:35 schrieb Shawn Lin:
DesignWare MMC Controller can supports two types of DMA
mode: external dma and internal dma. We get a RK312x platform
integrated dw_mmc and ARM pl330 dma controller. This patch add
edmac ops
Hi Bjorn,
Today's linux-next merge of the pci tree got a conflict in:
drivers/pci/host/Kconfig
between commit:
70d334ca71b0 ("PCI: iproc: Fix BCMA dependency in Kconfig")
from the arm-soc tree and commit:
05aa7d6a72c1 ("PCI: iproc: Allow BCMA bus driver to be built as module")
from
ceph: remove redundant test of head->safe and silence static analysis
warnings
Signed-off-by: Brad Hubbard
---
fs/ceph/mds_client.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ceph/mds_client.c b/fs/ceph/mds_client.c
index 6aa07af..6e196ee 100644
---
On 11.08.2015 12:46, Chanwoo Choi wrote:
> This patch add the UART2 clocks (mux, divider, gate) of Exynos3250 SoC.
I could not confirm the exact numbers used ("reserved" in my datasheet)
but the patch itself looks correct.
Assuming that numbers/addresses are good:
Reviewed-by: Krzysztof
Dear Greg,
This is extcon-next full request for v4.3. I add detailed description of this
pull request on below. Please pull extcon with following updates.
Changes from v1:
- Fix the merge conflict of extcon-palmas.c driver on linux-next.git (Stephen
Rothwell).
Best Regards,
Chanwoo Choi
The
On 17.08.2015 09:36, Chanwoo Choi wrote:
> On 08/17/2015 09:33 AM, Krzysztof Kozlowski wrote:
>> 2015-08-11 12:46 GMT+09:00 Chanwoo Choi :
>>> This patch add the UART2 / MMC2 devicetree node for Exynos3250 SoC and add
>>> the related clocks (mux, divider, gate) of UART2 / MMC2 device.
>>
>> What
On 08/17/2015 09:33 AM, Krzysztof Kozlowski wrote:
> 2015-08-11 12:46 GMT+09:00 Chanwoo Choi :
>> This patch add the UART2 / MMC2 devicetree node for Exynos3250 SoC and add
>> the related clocks (mux, divider, gate) of UART2 / MMC2 device.
>
> What is the benefit of adding them? Why they are
On Fri, 14 Aug 2015 10:23:51 -0700 Greg KH wrote:
> On Fri, Aug 14, 2015 at 05:04:21PM +1000, NeilBrown wrote:
> >
> > commit b97e92574c0bf335db1cd2ec491d8ff5cd5d0b49 upstream
> > Use separate bitmaps for each nodes in the cluster
> >
> > bitmap_read_sb() validates the bitmap superblock
2015-08-11 12:46 GMT+09:00 Chanwoo Choi :
> This patch add the UART2 / MMC2 devicetree node for Exynos3250 SoC and add
> the related clocks (mux, divider, gate) of UART2 / MMC2 device.
What is the benefit of adding them? Why they are needed?
Best regards,
Krzysztof
>
> Chanwoo Choi (4):
>
Hi Greg,
On 2015/08/15 9:10, gre...@linuxfoundation.org wrote:
> On Mon, Aug 10, 2015 at 12:15:40AM +, Taichi Kageyama wrote:
>> The following race conditions can happen when a serial port is used
>> as console.
>>
>> Case1: CPU_B is used to detect an interrupt from a serial port,
>>
Hi all,
On Sun, 16 Aug 2015 16:49:27 -0700 Linus Torvalds
wrote:
>
> So a release next week is definitely still possible.
Which means that all new work for v4.3 should already be in linux-next
included trees and maintainers should just be tidying up their trees
for merging ...
--
Cheers,
1 - 100 of 364 matches
Mail list logo
