On Mon, Jan 26, 2015 at 03:55:29PM +0300, Vladimir Davydov wrote:
> To speed up further allocations SLUB may store empty slabs in per
> cpu/node partial lists instead of freeing them immediately. This
> prevents per memcg caches destruction, because kmem caches created for a
> memory cgroup are
On Mon, 26 Jan 2015, Kumar Amit Mehta wrote:
> The comment for intel_cpu_fifo_underrun_irq_handler() is not consistent
> with the code and the rest of the comment for this routine. This patch
> fixes this typo in comment.
>
> Signed-off-by: Kumar Amit Mehta
Reviewed-by: Jani Nikula
> ---
>
On Thu, Jan 22, 2015 at 10:45:51AM +0900, Joonsoo Kim wrote:
> On Wed, Jan 21, 2015 at 09:57:59PM +0900, Akinobu Mita wrote:
> > 2015-01-21 9:07 GMT+09:00 Andrew Morton :
> > > On Tue, 20 Jan 2015 15:01:50 -0800 j...@joshtriplett.org wrote:
> > >
> > >> On Tue, Jan 20, 2015 at 02:02:00PM -0600,
On Sun, Jan 18, 2015 at 1:20 PM, Niklas Söderlund wrote:
> Configure the pinmux on kzm9d to use the serial connector for uart1.
>
> Signed-off-by: Niklas Söderlund
Acked-by: Linus Walleij
> + {
> + uart1_pins: uart@e103 {
> + renesas,groups = "uart1_ctrl",
On Sun, Jan 18, 2015 at 1:20 PM, Niklas Söderlund wrote:
> With this information all GPIOs can make use of the PFC functionality.
>
> Signed-off-by: Niklas Söderlund
Acked-by: Linus Walleij
Pls take this through the shmobile tree.'
Yours,
Linus Walleij
--
To unsubscribe from this list: send
On Sun, Jan 25, 2015 at 2:49 PM, Niklas Söderlund wrote:
> Add PFC support for the EMMA Mobile EV2 SoC including pin groups for
> on-chip devices.
>
> Signed-off-by: Niklas Söderlund
This v3 version applied with Laurent's ACK.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the
On Sun, Jan 18, 2015 at 1:20 PM, Niklas Söderlund wrote:
> Used to define pinmux configurations where the pinmux function have no
> representation in the configuration registers but instead solely depends
> on a group selection.
>
> Signed-off-by: Niklas Söderlund
Patch applied with Laurent's
Hello Torvald,
On 01/24/2015 02:12 PM, Torvald Riegel wrote:
> On Sat, 2015-01-24 at 12:35 +0100, Thomas Gleixner wrote:
>> So we should never see -EINTR in the case of a spurious wakeup here.
>>
>> But, here is the not so good news:
>>
>> I did some archaeology. The restart handling of
Hi, Davidlohr,
Any update on this? The latest news I gotten is that you finally
reproduced this.
Best Regards,
Huang, Ying
--
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
On Mon, Jan 26, 2015 at 04:15:26PM -0800, Kees Cook wrote:
> >
> > akpm3:/usr/src/25> grep -r map_files Documentation
>
> If akpm's comments weren't clear: this needs to be fixed. Everything
> in /proc should appear in Documentation.
I'll do that.
> > The 640708a2cff7f81 changelog says:
> >
> >
On 12/10/2014 07:38 AM, Joonsoo Kim wrote:
> After your patch is merged, I will resubmit these on top of it.
Hi Joonsoo,
my page stealing patches are now in -mm so are you planning to resubmit this? At
least patch 1 is an obvious bugfix, and patch 4 a clear compaction overhead
reduction. Those
On Tue, Jan 27, 2015 at 02:04:21PM +0800, Wang, Yalin wrote:
> This patch change the error return value from -1 to -ENOMEM,
> so that userspace can get the correct errno, otherwise,
> -1 will be -EPERM, userspace will print permission deny for allocation
> failure.
>
> Signed-off-by: Yalin Wang
make sure this driver depends on GENERIC_CLOCKEVENTS
compiler error was found by kbuild test robot:
>> drivers/clocksource/asm9260_timer.c:114:14: warning: its scope is only this
>> definition or declaration, which is probably not what you want
>> drivers/clocksource/asm9260_timer.c:124:16:
On Mon, Jan 26, 2015 at 10:50:23PM -0800, Andrew Morton wrote:
> On Tue, 27 Jan 2015 09:46:47 +0300 Cyrill Gorcunov wrote:
>
> > > There's one other problem here: we're assuming that the map_files
> > > implementation doesn't have bugs. If it does have bugs then relaxing
> > > permissions like
reply via{inquiryu...@blumail.org} Now.
--
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/
Hi Joerg,
Thank you for the patches.
On Tuesday 27 January 2015 00:50:26 Joerg Roedel wrote:
> Hi,
>
> here are a couple of iommu fixes and cleanups to fix compile
> errors and some warnings on ARM and PPC.
For the whole series,
Acked-by: Laurent Pinchart
> Regards,
>
> Joerg
>
>
On 2015/1/26 22:45, Rafael J. Wysocki wrote:
> On Monday, January 26, 2015 03:15:43 PM Thomas Gleixner wrote:
>> On Mon, 26 Jan 2015, Rafael J. Wysocki wrote:
>>
>>> On Monday, January 26, 2015 10:40:24 AM Thomas Gleixner wrote:
On Mon, 26 Jan 2015, Li, Aubrey wrote:
> On 2015/1/22 18:15,
Hi Russell!
On 21 January 2015 at 23:01, Russell King - ARM Linux
wrote:
> On Wed, Jan 21, 2015 at 09:46:47AM +0530, Sumit Semwal wrote:
>> +static int calc_constraints(struct device *dev,
>> + struct dma_buf_constraints *calc_cons)
>> +{
>> + struct
On Fri, Jan 23, 2015 at 03:28:33PM +0900, gyun...@gmail.com wrote:
> From: Gyungoh Yoo
>
> Signed-off-by: Gyungoh Yoo
> Acked-by: Bryan Wu
The existing Ack is only for backlight driver.
DT Ack please.
> ---
> Changes v10:
> Nothing
>
> Changes v9:
> Nothing
>
> Changes v8:
> Renamed
On Tue, Jan 20, 2015 at 10:05 AM, Viet Nga Dao wrote:
> On Thu, Jan 15, 2015 at 5:27 PM, Viet Nga Dao wrote:
>> On Tue, Jan 13, 2015 at 11:33 AM, Brian Norris
>> wrote:
>>> On Thu, Dec 18, 2014 at 12:23:16AM -0800, vn...@altera.com wrote:
From: Viet Nga Dao
Altera EPCQ
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/core.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/core.h
b/drivers/net/wireless/rtlwifi/core.h
index 624e1dc..3b37557 100644
--- a/drivers/net/wireless/rtlwifi/core.h
+++
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/rtl8188ee/rf.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192ce/rf.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192cu/rf.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192de/def.h | 1 -
drivers/net/wireless/rtlwifi/rtl8192ee/rf.h | 1 -
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/base.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/base.h
b/drivers/net/wireless/rtlwifi/base.h
index 982f245..ea3e3fc 100644
--- a/drivers/net/wireless/rtlwifi/base.h
+++
On Tue, 27 Jan 2015 09:46:47 +0300 Cyrill Gorcunov wrote:
> > There's one other problem here: we're assuming that the map_files
> > implementation doesn't have bugs. If it does have bugs then relaxing
> > permissions like this will create new vulnerabilities. And the
> > map_files
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/efuse.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/efuse.h
b/drivers/net/wireless/rtlwifi/efuse.h
index fdab824..be02e78 100644
--- a/drivers/net/wireless/rtlwifi/efuse.h
+++
HAL_RETRY_LIMIT_*
RESET_DELAY_8185
RT_IBSS_INT_MASKS
RT_AC_INT_MASKS
NUM_OF_*
BT_*,
MAX_{LINES,BYTES}_*,
*_THREE_WIRE
*_QUEUE related
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/rtl8188ee/def.h | 41
drivers/net/wireless/rtlwifi/rtl8192ce/def.h | 41
You should probably CC -rt maintainers when submitting a -rt patch.
On Tue, 2015-01-27 at 03:53 -0200, Gustavo Bittencourt wrote:
> According the ww-mutex-design.txt documentation, the
> ww_mutex_lock_interruptible and ww_mutex_lock functions should return
> -EDEADLK when faced with a
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/rtl8192cu/hw.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/hw.h
b/drivers/net/wireless/rtlwifi/rtl8192cu/hw.h
index c1e33b0..6758808 100644
---
Signed-off-by: Priit Laes
---
drivers/net/wireless/rtlwifi/cam.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/cam.h
b/drivers/net/wireless/rtlwifi/cam.h
index 3550808..e2e647d 100644
--- a/drivers/net/wireless/rtlwifi/cam.h
+++
On Mon, Jan 26, 2015 at 03:43:46PM -0800, Andrew Morton wrote:
> >
> > Looks good to me, thanks! Though I would really appreciate if someone
> > from security camp take a look as well.
>
> hm, who's that. Kees comes to mind.
yup, I managed to forget CC him.
>
> And reviewers' task would be a
Aarch64 ELF files use mapping symbols with special names $x, $d
to identify regions of Aarch64 code (see Aarch64 ELF ABI - "ARM
IHI 0056B", section "4.5.4 Mapping symbols").
The patch filters out these symbols at load time, similar to
"696b97a perf symbols: Ignore mapping symbols on ARM" changes
Hi Folks,
Here is third version of mini-series that addresses couple issues
in perf symbols handling.
Changes since V2:
o Since V2 caused some controversy wrt aarch64/arm fixes [3], replace
'perf symbols: Ignore mapping symbols on aarch64' and 'perf symbols:
improve abi compliance in arm
Currently code that tries to read corresponding debug symbol
file from .gnu_debuglink section (DSO_BINARY_TYPE__DEBUGLINK)
does not take in account symfs option, so filename__read_debuglink
function cannot open ELF file, if symfs option is used.
Fix is to add proper handling of symfs as it is
On 01/27/2015 01:55 AM, Stephen Boyd wrote:
> On 01/23/15 03:03, Tomeu Vizoso wrote:
>> Hi,
>>
>> in this v13 I have:
>>
>> * added the latest R-b tags from Stephen,
>>
>> * split some lines that went over the 80-char limit,
>>
>> * made explicit in the docs that the range limits are inclusive,
On Tue, 2015-01-27 at 09:32 +0530, Preeti U Murthy wrote:
> On 01/23/2015 10:29 AM, Michael Ellerman wrote:
> > On Tue, 2015-20-01 at 11:26:49 UTC, Preeti U Murthy wrote:
> >> @@ -177,34 +178,39 @@ static int powernv_add_idle_states(void)
> >
> >>for (i = 0; i < dt_idle_states; i++) {
> >>
On Mon, Jan 26, 2015 at 09:37:01AM -0500, Steven Rostedt wrote:
> On Mon, 26 Jan 2015 13:54:53 +0100
> Heiko Carstens wrote:
> > s390 will use the hotpatch attribute for function tracing, therefore
> > introduce a nohotpatch define, depending on CC_USING_HOTPATCH, and add it
> > to the existing
get_acl gets a reference which we must release in the error cases.
Signed-off-by: Omar Sandoval
---
fs/posix_acl.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/posix_acl.c b/fs/posix_acl.c
index 0855f77..f8f3cc2 100644
--- a/fs/posix_acl.c
+++ b/fs/posix_acl.c
@@
Because the at91_xxx_standby function is removed,
remove the struct ramc_ids .data members code.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/setup.c | 19 ---
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git
Because the at91_xxx_standby() function is substitued by the at91_pm_suspend(),
the pm_suspend entry for at91_cpuidle_device changes as well.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 17 ++---
1 file changed, 10 insertions(+), 7
This patch change the error return value from -1 to -ENOMEM,
so that userspace can get the correct errno, otherwise,
-1 will be -EPERM, userspace will print permission deny for allocation
failure.
Signed-off-by: Yalin Wang
---
drivers/staging/android/ion/ion_cma_heap.c | 6 ++
1 file
Because the the suspend to standby mode uses the sram function,
these functions will not used, remove the redundant code.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.h | 97 ---
1 file changed, 97 deletions(-)
As the file name's renaming, rename the file name at91_slow_clock()-->
at91_pm_suspend_sram_fn, rename the function handler's name at the same time.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 27 +--
Because the sram function is used for the suspend to standby mode as well,
more than suspend to memory, so renaming is more elegant.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/Makefile |2 +-
arch/arm/mach-at91/pm_slowclock.S | 281
To simply the PM code, the suspend to standby mode uses the same sram function
as the suspend to memory mode, running in the internal SRAM,
instead of the respective code for each mode.
But for the suspend to standby mode, the master clock doesn't
switch to the slow clock, and the main
The slow clock always exists, for the suspend to memory mode,
the master clock always switch to the slow clock.
To simplify the PM config, remove this config item, remove
the definition code as well.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/Kconfig | 13
Because the CONFIG_AT91_SLOW_CLOCK will be removed
to simply the PM config, so move select SRAM.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/Kconfig |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-at91/Kconfig
The SLOWDOWN_MASTER_CLOCK definition is not used, remove the redundant code.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/pm_slowclock.S | 37 -
1 file changed, 37 deletions(-)
diff --git
From: Peter Rosin
The DDRSDR controller fails miserably to put LPDDR1 memories in
self-refresh. Force the controller to think it has DDR2 memories
during the self-refresh period, as the DDR2 self-refresh spec is
equivalent to LPDDR1, and is correctly implemented in the
controller.
Assume that
To decrease the suspend time, move the copying the sram function
to the sram initialization phase, instead of every time go to suspend.
In the meanwhile, if there is no sram allocated for PM, the PM is not supported.
Signed-off-by: Wenyou Yang
Acked-by: Alexandre Belloni
---
llvm trunk now has BPF backend:
https://twitter.com/llvmweekly/status/559076464973594625
It's the one used to build samples/bpf/*_kern.c examples.
Compiler just emits extended BPF instructions. It's not
aware whether they are used for tracing or networking,
or how they're loaded into the kernel.
From: Sylvain Rochet
Assume USB PLL and PLL B are already stopped before entering sleep mode,
print a warning if this isn't the case.
Removed PLL B from slow clock code, all drivers are supposed to properly
unprepare clocks.
Signed-off-by: Sylvain Rochet
---
arch/arm/mach-at91/pm.c
From: Sylvain Rochet
Removed timeout on XTAL, PLL lock and Master Clock Ready, hang if
something went wrong instead of continuing in unknown condition. There
is not much we can do if a PLL lock never ends, we are running in SRAM
and we will not be able to connect back the sdram or ddram in order
According the ww-mutex-design.txt documentation, the
ww_mutex_lock_interruptible and ww_mutex_lock functions should return -EDEADLK
when faced with a deadlock. To do so, the flag detect_deadlock in the
rt_mutex_slowlock calls should be enabled. This patch corrects potential
deadlocks when
Hi Nicolas,
This version is rebased on the branch: at91-3.20-cleanup of the repository
git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git
It is purpose to clean up the PM code, includes the patches from Peter Rosin
and Sylvain Rochet.
Since verifying the USB clock and
On NumaChip systems, the physical processor ID assignment wasn't accounting
for the number of nodes in AMD multi-module processors, giving an incorrect
sibling map:
$ cd /sys/devices/system/cpu/cpu29/topology
$ grep . *
core_id:5
core_siblings:,ff00
core_siblings_list:24-31
Add documentation for exynos7 thermal bindings including compatible
name and special clock properties.
Signed-off-by: Abhilash Kesavan
---
.../devicetree/bindings/thermal/exynos-thermal.txt |4
1 file changed, 4 insertions(+)
diff --git
Add registers, bit fields and compatible strings for Exynos7 TMU
(Thermal Management Unit). Following are a few of the differences
in the Exynos7 TMU from earlier SoCs:
- 8 trigger levels
- Different bit offsets and more registers for the rising
and falling thresholds.
On 2015/1/24 2:09, Arend van Spriel wrote:
> On 01/23/15 16:29, Kalle Valo wrote:
>> Arend van Spriel writes:
>>
>>> On 01/22/15 14:54, Sergei Shtylyov wrote:
Hello.
On 1/22/2015 4:49 PM, Kalle Valo wrote:
>> > From 04d3fa673897ca4ccbea6c76836d0092dba2484a Mon Sep 17
On 2015/1/27 3:10, Marc Zyngier wrote:
> While debugging an unrelated issue with the GICv3 ITS driver, the
> following trace triggered:
>
> WARNING: CPU: 1 PID: 1 at kernel/irq/irqdomain.c:1121
> irq_domain_free_irqs+0x160/0x17c()
> NULL pointer, cannot free irq
> Modules linked in:
> CPU: 1
Hi Mark,
Thank you for your review.
> -Original Message-
> From: Mark Rutland [mailto:mark.rutl...@arm.com]
> Sent: Monday, January 26, 2015 7:50 PM
> To: Yang, Wenyou
> Cc: Ferre, Nicolas; li...@arm.linux.org.uk; sylvain.roc...@finsecur.com;
> Vilchez,
> Patrice;
On 1/25/15, Christoph Hellwig wrote:
> On Tue, Jan 13, 2015 at 11:44:47PM +0800, Ming Lei wrote:
>> So that users can control if kernel aio is used to submit I/O.
>
> Why do you want a sysfs flag for this instead of a flags in ->lo_flags
> at setup time? That's how all other loop-related ABI
Hi Linus,
Please pull two powerpc fixes for 3.19:
The following changes since commit ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc:
Linux 3.19-rc5 (2015-01-18 18:02:20 +1200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git
Hi Daniel,
Today's linux-next merge of the clockevents tree got a conflict in
drivers/clocksource/Kconfig between commit e074ff86e8b4 ("ARM: 8251/1:
clocksource: enable pxa_timer for SA-1100 platform") from the arm tree
and commit e4940cd76934 ("ARM: clocksource: add asm9260_timer driver")
from
Hi Alexandre,
> -Original Message-
> From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com]
> Sent: Tuesday, January 27, 2015 6:37 AM
> To: Yang, Wenyou
> Cc: Ferre, Nicolas; li...@arm.linux.org.uk;
> linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org;
Dear Guenter,
On Mon, 26 Jan 2015 20:08:04 -0800
Guenter Roeck wrote:
> On 01/26/2015 07:49 PM, Jisheng Zhang wrote:
> > Dear Doug,
> >
> > On Mon, 26 Jan 2015 15:27:15 -0800
> > Doug Anderson wrote:
> >
> >> On some dw_wdt implementations the "top" register may be initted to 0
> >> at bootup.
On Mon, Jan 26, 2015 at 09:00:18PM -0700, Jens Axboe wrote:
> On 01/26/2015 08:57 PM, Stephen Rothwell wrote:
> >Hi Jens,
> >
> >Today's linux-next merge of the block tree got a conflict in
> >drivers/block/loop.c between commit c2ca80413553 ("loop: convert to
> >vfs_iter_read/write") from the vfs
PXA1928 is an ARMv8 SOC in the PXA/MMP family. This series enables
building on ARM64 and adds support for the PXA1928. The PXA1928
GPIO differs from previous generations by adding a 6th GPIO bank.
Rob
Rob Herring (3):
gpio: pxa: remove mach IRQ includes
dt/bindings: gpio: add compatible
Add a new compatible string for PXA1928 GPIO controller. The IP block is
same as prior chips with a 6th bank added.
Signed-off-by: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: devicet...@vger.kernel.org
---
On Mon, Jan 26, 2015 at 09:34:19PM -0500, Steven Rostedt wrote:
> On Mon, 26 Jan 2015 18:37:39 -0500
> Steven Rostedt wrote:
>
>
> > > the first call of tracing_init_dentry(). Prior to that it's NULL.
> > > BTW, may I politely inquire what the fuck are those contortions in
> > >
In preparation to enable ARCH_MMP on ARM64, the include of mach/irqs.h
must be eliminated. mach/irqs.h was being included for IRQ_GPIO{0,1},
but these IRQs are always passed in as resources now. We can use irq0
and irq1 and get rid of IRQ_GPIOx. Get rid of the ifdef in the process
as it is no
Add support for PXA1928 GPIOs. The PXA1928 adds a 6th bank from previous
generations.
Signed-off-by: Jing Xiang
Signed-off-by: Xiangzhan Meng
[robh: ported to 3.19 from vendor kernel]
Signed-off-by: Rob Herring
Cc: Linus Walleij
Cc: Alexandre Courbot
---
drivers/gpio/gpio-pxa.c | 17
Hi Sylvain,
> -Original Message-
> From: Sylvain Rochet [mailto:sylvain.roc...@finsecur.com]
> Sent: Monday, January 26, 2015 6:10 PM
> To: Yang, Wenyou
> Cc: Ferre, Nicolas; li...@arm.linux.org.uk;
> linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org;
Hi Sergei,
Thank you for your review.
> -Original Message-
> From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
> Sent: Monday, January 26, 2015 9:05 PM
> To: Yang, Wenyou; Ferre, Nicolas; li...@arm.linux.org.uk
> Cc: sylvain.roc...@finsecur.com; Vilchez, Patrice;
>
On Mon, 26 Jan 2015 20:07:51 -0800
Guenter Roeck wrote:
> On 01/26/2015 07:44 PM, Jisheng Zhang wrote:
> > Dear Doug,
> >
> > On Mon, 26 Jan 2015 09:01:37 -0800
> > Doug Anderson wrote:
> >
> >> Jisheng,
> >>
> >> On Sun, Jan 25, 2015 at 10:22 PM, Jisheng Zhang
> >> wrote:
> Specifically
On Mon, Jan 26, 2015 at 08:03:50PM -0500, Steven Rostedt wrote:
> On Mon, 26 Jan 2015 20:02:18 -0500
> Steven Rostedt wrote:
>
>
> > Now you see why I found just dropping the parent mutex easier.
>
> And this is probably why kernfs does things the way it does. I can
> imagine it having the
On Mon, Jan 26, 2015 at 07:39:09PM -0500, Steven Rostedt wrote:
> On Mon, 26 Jan 2015 18:49:16 -0500
> Steven Rostedt wrote:
>
> > On Mon, 26 Jan 2015 18:43:14 -0500
> > Steven Rostedt wrote:
> >
> > > That is, we can not hold i_mutex and take trace_types_lock.
> > >
> > > trace_types_lock
On Mon, Jan 26, 2015 at 05:19:50PM +0100, Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> Some more little modifications for the DT on several products. The
> corresponding code in drivers is already queued in the relevant maintainers'
> git trees and there are no dependencies.
>
> Thanks, best
On 01/26/2015 07:49 PM, Jisheng Zhang wrote:
Dear Doug,
On Mon, 26 Jan 2015 15:27:15 -0800
Doug Anderson wrote:
On some dw_wdt implementations the "top" register may be initted to 0
at bootup. In such a case, each "pat" of the watchdog will reset the
timer to 0x. That's pretty short.
On 01/26/2015 07:44 PM, Jisheng Zhang wrote:
Dear Doug,
On Mon, 26 Jan 2015 09:01:37 -0800
Doug Anderson wrote:
Jisheng,
On Sun, Jan 25, 2015 at 10:22 PM, Jisheng Zhang wrote:
Specifically I see the register WDT_TORR that has an offset of 0x4.
That's the RANGE_REG in your code. It shows
On 01/26/2015 04:55 PM, Richard Weinberger wrote:
Am 14.01.2015 um 09:39 schrieb Richard Weinberger:
Am 14.01.2015 um 01:23 schrieb Jens Axboe:
Which is as I suspected, you'll do each segment to the length specified,
hence you don't need to track the returned count from blk_rq_map_sg().
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
drivers/ata/libata-core.c between commit 72dd299d5039 ("libata: allow
sata_sil24 to opt-out of tag ordered submission") from Linus' tree and
commit 98bd4be1ba95 ("libata: move sas ata tag allocation to
libata-scsi.c") from the
On 01/23/2015 10:29 AM, Michael Ellerman wrote:
> On Tue, 2015-20-01 at 11:26:49 UTC, Preeti U Murthy wrote:
>> @@ -177,34 +178,39 @@ static int powernv_add_idle_states(void)
>> return nr_idle_states;
>> }
>>
>> -idle_state_latency = of_get_property(power_mgt,
>> -
Hello,
On (01/27/15 12:18), Minchan Kim wrote:
> Hello Sergey,
>
> On Tue, Jan 27, 2015 at 11:17:04AM +0900, Sergey Senozhatsky wrote:
> > On (01/27/15 01:00), Minchan Kim wrote:
> > > On Mon, Jan 26, 2015 at 11:17:09PM +0900, Sergey Senozhatsky wrote:
> > > > Hello,
> > > >
> > > > On
On 01/26/2015 08:57 PM, Stephen Rothwell wrote:
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
drivers/block/loop.c between commit c2ca80413553 ("loop: convert to
vfs_iter_read/write") from the vfs tree and commit b5dd2f6047ca
("block: loop: improve performance via
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
drivers/block/loop.c between commit c2ca80413553 ("loop: convert to
vfs_iter_read/write") from the vfs tree and commit b5dd2f6047ca
("block: loop: improve performance via blk-mq") and several others from
the block tree.
I have
On 01/27/2015 02:35 AM, Kevin Cernekee wrote:
On Wed, Jan 21, 2015 at 10:36 PM, Archit Taneja wrote:
On 01/21/2015 06:24 AM, Daniel Ehrenberg wrote:
On Fri, Jan 16, 2015 at 6:48 AM, Archit Taneja
wrote:
+/*
+ * the bad block marker is readable only when we read the page with ECC
+ *
On Mon, Jan 26, 2015 at 3:53 PM, Bjorn Helgaas wrote:
> On Mon, Jan 26, 2015 at 01:24:51PM -0800, Tony Luck wrote:
>> On Mon, Jan 26, 2015 at 1:02 PM, Bjorn Helgaas wrote:
>> > Sorry for the inconvenience. Can you collect a complete dmesg log and
>> > "lspci -vv" output, too (from the kernel
Dear Doug,
On Mon, 26 Jan 2015 15:27:15 -0800
Doug Anderson wrote:
> On some dw_wdt implementations the "top" register may be initted to 0
> at bootup. In such a case, each "pat" of the watchdog will reset the
> timer to 0x. That's pretty short.
>
> The input clock of the wdt can be any
Dear Doug,
On Mon, 26 Jan 2015 09:01:37 -0800
Doug Anderson wrote:
> Jisheng,
>
> On Sun, Jan 25, 2015 at 10:22 PM, Jisheng Zhang wrote:
> >> Specifically I see the register WDT_TORR that has an offset of 0x4.
> >> That's the RANGE_REG in your code. It shows bits 3:0 set the timeout
> >>
On Mon, Jan 26, 2015 at 1:24 PM, Tony Luck wrote:
> On Mon, Jan 26, 2015 at 1:02 PM, Bjorn Helgaas wrote:
>> Sorry for the inconvenience. Can you collect a complete dmesg log and
>> "lspci -vv" output, too (from the kernel with the reverted commit)?
>> That will have more useful information
From: Alexander Morozov
The WM8904 and WM8918 has the same data type, while the WM8912
has different data type. So, use the data in dt ids table to
distinguish them.
Signed-off-by: Alexander Morozov
[voice.s...@atmel.com: add code to distinguish device type]
Signed-off-by: Bo Shen
---
Changes
The "wlf,wm8912" compatible string is used for wm8912, which
share driver with wm8904, however, the data type is different.
Signed-off-by: Bo Shen
---
Changes in v3: None
Changes in v2: None
Documentation/devicetree/bindings/sound/wm8904.txt | 2 +-
1 file changed, 1 insertion(+), 1
On 01/22/2015 04:45 PM, Thomas Gleixner wrote:
> On Thu, 22 Jan 2015, Preeti U Murthy wrote:
>> On 01/21/2015 05:16 PM, Thomas Gleixner wrote:
>> How about when the cpu that is going offline receives a timer interrupt
>> just before setting its state to CPU_DEAD ? That is still possible right
>>
Jialing Fu marvell.com> writes:
>
> The following panic is captured in ker3.14, but the issue still exists
> in latest kernel.
> -
> [ 20.738217] c0 3136 (Compiler) Unable to handle kernel NULL pointer
dereference
> at
Hi Sergei,
Thank you for your review.
> -Original Message-
> From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
> Sent: Monday, January 26, 2015 8:57 PM
> To: Yang, Wenyou; Ferre, Nicolas; li...@arm.linux.org.uk
> Cc: sylvain.roc...@finsecur.com;
Hello Ganesh,
On Mon, Jan 26, 2015 at 10:53:57AM +0800, Ganesh Mahendran wrote:
> Hello, Minchan
>
> 2015-01-21 14:14 GMT+08:00 Minchan Kim :
> > Currently, zram's handle encodes object's location directly so
> > it makes hard to support migration/compaction.
> >
> > This patch decouples handle
Linus Torvalds writes:
> Ugh. I don't see anything we can do about this on the git side, and I
> do kind of understand why 'patch' would be worried about '..' files.
> In a perfect world, patch would parse the filename and see that it
> stays within the directory structure of the project, but
On Thu, Jan 22, 2015 at 01:36:33PM -0600, Felipe Balbi wrote:
> Hi Greg,
>
> two more fixes needed from my side. Let me know if you prefer
> to handle them differently.
>
> cheers
>
> The following changes since commit ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc:
>
> Linux 3.19-rc5 (2015-01-18
Hello Ganesh,
On Tue, Jan 27, 2015 at 10:07:53AM +0800, Ganesh Mahendran wrote:
> Hello, Andrew
>
> 2015-01-27 7:19 GMT+08:00 Andrew Morton :
> > On Sat, 24 Jan 2015 21:48:41 +0800 Ganesh Mahendran
> > wrote:
> >
> >> Sometimes, we want to know whether a module is loaded or unloaded
> >> from
Hello Sergey,
On Tue, Jan 27, 2015 at 11:17:04AM +0900, Sergey Senozhatsky wrote:
> On (01/27/15 01:00), Minchan Kim wrote:
> > On Mon, Jan 26, 2015 at 11:17:09PM +0900, Sergey Senozhatsky wrote:
> > > Hello,
> > >
> > > On (01/26/15 10:33), Minchan Kim wrote:
> > > > Hello,
> > > >
> > > > On
1 - 100 of 1990 matches
Mail list logo
