Hi Mike, Hannes, Ben
On 1/22/2016 10:29 PM, Mike Snitzer wrote:
[Hannes please fix your mail client, seems you dropped all the original CCs]
On Fri, Jan 22 2016 at 8:42am -0500,
Hannes Reinecke wrote:
> On 01/22/2016 02:31 PM, Ravikanth Nalla wrote:
> >
> > Functionality
On Fri, 29 Jan 2016, Oleg Nesterov wrote:
> > [] sigsuspend+0x18e/0x1f0 kernel/signal.c:3513
>
> See http://marc.info/?t=14537372204 the patch is already in -mm tree.
Nice! So my analysis was not that far off.
Thanks,
tglx
[Re: Regression: 4.5-rc1 (bisect: hugetlb: make mm and fs code explicitly
non-modular vs CONFIG_TIMER_STATS)] On 28/01/2016 (Thu 16:27) Mike Kravetz
wrote:
> On 01/28/2016 02:59 PM, Paul Gortmaker wrote:
> > [Re: Regression: 4.5-rc1 (bisect: hugetlb: make mm and fs code explicitly
> >
Richard Weinberger writes:
> Am 29.01.2016 um 02:32 schrieb Nicolai Stange:
>> Richard Weinberger writes:
>>
>>> Am 29.01.2016 um 00:56 schrieb Nicolai Stange:
Commit 16da306849d0 ("um: kill pfn_t")
introduced a compile warning for defconfig:
In case vfio_msi_set_vector_signal fails we tear down everything.
In the tear down loop we compare int j against unsigned start. Given
the arithmetic conversion I think it is converted into an unsigned and
becomes 0x, leading to the loop being entered again and things
turn bad when
On Tue, Jan 26, 2016 at 09:44:24PM -0800, Andy Lutomirski wrote:
> On Tue, Jan 26, 2016 at 8:40 PM, Matthew Wilcox wrote:
> > On Mon, Jan 25, 2016 at 09:33:35AM -0800, Andy Lutomirski wrote:
> >> On Mon, Jan 25, 2016 at 9:25 AM, Matthew Wilcox
> >>
So far, we have been blindly assuming that if a memory-mapped timer
frame exists, then we have access to it. Whilst it's the firmware's
job to give us non-secure access to frames in the first place, we
should not rely on it always being generous enough to also configure
CNTACR if it's not even
On Fri, 2016-01-29 at 09:27 +0100, Ingo Molnar wrote:
> * Toshi Kani wrote:
:
> > ---
> > arch/x86/lib/copy_user_64.S | 44 ---
> >
> > 1 file changed, 33 insertions(+), 11 deletions(-)
> >
> > diff --git
On Fri, Jan 29, 2016 at 06:09:41AM -0500, Tejun Heo wrote:
> I posted a patch to disable
> disable flush dependency checks on those workqueues and there's a
> outreachy project to weed out the users of the old interface, so
> hopefully this won't be an issue soon.
Will that same project review
On Fri 29-01-16 19:35:18, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > From: Michal Hocko
> >
> > zone_reclaimable_pages is used in should_reclaim_retry which uses it to
> > calculate the target for the watermark check. This means that precise
> > numbers are important for the
On Wed, 27 Jan 2016, Joshua Kinard wrote:
> On 06/05/2015 09:10, Ralf Baechle wrote:
> >
> > Maciej,
> >
> > do you have an R4000 / R4600 / R5000 / R7000 / SiByte system at hand to
> > test this? I think we don't need to test that SYNC actually works as
> > intended but the simpler test that
The midi controller times-out while initializing reports, this
causes boot to take an extra 10 seconds. The device descriptor
advertises that it has an internal HID device but seems to not
actually do anything useful.
Signed-off-by: Stafford Horne
---
Resending the same patch
On Thu, 28 Jan 2016, Leonid Yegoshin wrote:
> In http://patchwork.linux-mips.org/patch/10505/ the very last mesg exchange
> is:
[...]
> ... and that stops forever...
Thanks for the reminder -- last June was very hectic, I travelled a lot
and I lost the discussion from my radar. Apologies for
On Fri, 29 Jan 2016 13:57:49 +0100
Heiko Carstens wrote:
> Surpringly it wasn't one of my own patches which broke the stack tracer on
> s390, but one from Steven:
>
> 72ac426a5bb0 ("tracing: Clean up stack tracing and fix fentry updates")
>
> Now I only need to
From: "Peter Zijlstra (Intel)"
The existing wait queue support has support for custom wake up call
backs, wake flags, wake key (passed to call back) and exclusive
flags that allow wakers to be tagged as exclusive, for limiting
the number of wakers.
In a lot of cases, none
As the function name already indicates that get_opt_bool() parses
for a bool. It is not a surprise that compiler is complaining
about it when -Werror=incompatible-pointer-types is used:
drivers/video/fbdev/intelfb/intelfbdrv.c: In function ‘intelfb_setup’:
On Fri, Jan 29, 2016 at 2:57 PM, Thomas Gleixner wrote:
> On Fri, 29 Jan 2016, Dmitry Vyukov wrote:
>> On Fri, Jan 29, 2016 at 12:53 PM, Thomas Gleixner wrote:
>> > Dmitry,
>> >
>> > On Fri, 29 Jan 2016, Dmitry Vyukov wrote:
>> >> WARNING: CPU: 2 PID:
Bluetooth is only supported when network support is part of the kernel,
so it is a bit pointless to build the tosa-bt support without networking.
If we try anyway, we get a Kconfig warning:
warning: (TOSA_BT && H1940BT) selects RFKILL which has unmet direct
dependencies (NET)
This adds a
Hi Linus,
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-fixes-v4.5-rc1
for you to fetch changes up to
On Mon, Jan 25, 2016 at 10:37:44AM -0800, Andy Lutomirski wrote:
> On my Skylake laptop, INVPCID function 2 (flush absolutely
> everything) takes about 376ns, whereas saving flags, twiddling
> CR4.PGE to flush global mappings, and restoring flags takes about
> 539ns.
FWIW, I ran your
On 01/28/2016 05:51 AM, Joonsoo Kim wrote:
> On Wed, Jan 27, 2016 at 02:35:04PM +0100, Vlastimil Babka wrote:
>> On 01/14/2016 06:24 AM, Joonsoo Kim wrote:
>> > In fact, I tested another idea implementing OBJFREELIST_SLAB with
>> > extendable linked array through another freed object. It can
On Fri, 29 Jan 2016 15:45:22 +0100
Heiko Carstens wrote:
> On Fri, Jan 29, 2016 at 08:59:36AM -0500, Steven Rostedt wrote:
> > On Fri, 29 Jan 2016 13:57:49 +0100
> > Heiko Carstens wrote:
> >
> > > Surpringly it wasn't one of my own
Linus,
please pull sound fixes for v4.5-rc2 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.5-rc2
The topmost commit is 6639484ddaf6707b41082c9fa9ca9af342df6402
sound fixes for 4.5-rc2
There
On Fri, Jan 29, 2016 at 2:18 PM, Dmitry Vyukov wrote:
> On Fri, Jan 29, 2016 at 1:23 PM, Tejun Heo wrote:
>> Hello, Dmitry.
>>
>> On Fri, Jan 29, 2016 at 12:59:49PM +0100, Dmitry Vyukov wrote:
>>> > Hmmm... the port interrupt handler checks for IDLE before
On Fri, 2016-01-29 at 13:50 +0800, Peter Hung wrote:
> Andy Shevchenko 於 2016/1/28 下午 07:55 寫道:
> > > +obj-$(CONFIG_MFD_FINTEK_F81504_CORE) += f81504-core.o
> +static int f81504_port_init(struct pci_dev *dev)
> > > +{
> > > + size_t i, j;
> > > + u32 max_port, iobase, gpio_addr;
> > > + u32
From: Paul Gortmaker
As of commit dae6e64d2bcfd4b06304ab864c7e3a4f6b5fedf4 ("rcu: Introduce
proper blocking to no-CBs kthreads GP waits") the RCU subsystem started
making use of wait queues.
Here we convert all additions of RCU wait queues to use simple wait
With the introduction of the simple wait API we have two very
similar APIs in the kernel. For example wake_up() and swake_up()
is only one character away. Although the compiler will warn
happily the wrong usage it keeps on going an even links the kernel.
Thomas and Peter would rather like to see
Commit-ID: 742563777e8da62197d6cb4b99f4027f59454735
Gitweb: http://git.kernel.org/tip/742563777e8da62197d6cb4b99f4027f59454735
Author: Matt Fleming
AuthorDate: Fri, 29 Jan 2016 11:36:10 +
Committer: Thomas Gleixner
CommitDate: Fri, 29
On Fri, 29 Jan 2016, Dmitry Vyukov wrote:
> On Fri, Jan 29, 2016 at 2:57 PM, Thomas Gleixner wrote:
> I need something that will work without supervision. I need to use
> /proc/sys/kernel/ftrace_dump_on_oops instead of
> /proc/sys/kernel/traceoff_on_warning then, right?
>
>
On Fri, Jan 22, 2016 at 03:48:55PM +0300, Andrey Ryabinin wrote:
> 2016-01-19 17:31 GMT+03:00 Peter Zijlstra :
> > On Sun, Jan 10, 2016 at 03:55:13PM -0500, Sasha Levin wrote:
> >> Hi all,
> >>
> >> While fuzzing with trinity inside a KVM tools guest, running the latest
> >>
On Fri, 29 Jan 2016 15:10:18 +0100 (CET)
Thomas Gleixner wrote:
> The time depends on the serial speed and the trace buffer size and the number
> of cpus. Don't worry about the uptime. The buffer is a ringbuffer with limited
> capacity, so the dump time is constant.
>
> If
Hi Alex,
On 01/28/2016 10:51 PM, Alex Williamson wrote:
> On Tue, 2016-01-26 at 13:12 +, Eric Auger wrote:
>> This series addresses KVM PCIe passthrough with MSI enabled on ARM/ARM64.
>> It pursues the efforts done on [1], [2], [3]. It also aims at covering the
>> same need on some PowerPC
On Fri, Jan 29, 2016 at 03:45:59PM +0100, Vlastimil Babka wrote:
> This should be applied on top. There are no restarts anymore.
Quite right. Sorry I missed the comment.
Acked-by: Matthwe Wilcox
> 8<
> >From 3b0bdd370b57fb6d83b213e140cd1fb0e8962af8 Mon Sep 17
On Fri, Jan 29, 2016 at 05:59:46AM -0500, Tejun Heo wrote:
> fca839c00a12 ("workqueue: warn if memory reclaim tries to flush
> !WQ_MEM_RECLAIM workqueue") implemented flush dependency warning which
> triggers if a PF_MEMALLOC task or WQ_MEM_RECLAIM workqueue tries to
> flush a !WQ_MEM_RECLAIM
On Fri, Jan 15, 2016 at 10:15:11AM +0100, Luca Abeni wrote:
> There is also a newer paper, that will be published at ACM SAC 2016
> (so, it is not available yet), but is based on this technical report:
> http://arxiv.org/abs/1512.01984
> This second paper describes some more complex algorithms
Dynamically enabling DAX requires that the page cache first be flushed
and invalidated. This must occur atomically with the change of DAX mode
otherwise we confuse the fsync/msync tracking and violate data
durability guarantees. Eliminate the possibilty of DAX-disabled to
DAX-enabled transitions
The dax support for a raw block device did not account for page cache
entries established by the kernel for partition reads. This breaks dax
as it assumes that page cache entries are limited to covering holes in
files, or are exceptional entries marking dirty pages.
Additionally, the facility to
Avoid populating pagecache when the block device is in DAX mode.
Otherwise these page cache entries collide with the fsync/msync
implementation and break data durability guarantees.
Cc: Jan Kara
Cc: Jeff Moyer
Cc: Christoph Hellwig
Cc: Dave
On Fri, 29 Jan 2016, Dmitry Vyukov wrote:
> On Fri, Jan 29, 2016 at 12:53 PM, Thomas Gleixner wrote:
> > Dmitry,
> >
> > On Fri, 29 Jan 2016, Dmitry Vyukov wrote:
> >> WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h:236
> >> sigsuspend+0x18e/0x1f0()
> >>
GPIO_SYSFS is a common kernel functionality, not something
that a board specific Kconfig should have to worry about.
In MIOA701, we get a warning about the select when CONFIG_SYSFS
is disabled:
warning: (MACH_MIOA701) selects GPIO_SYSFS which has unmet direct dependencies
(GPIOLIB && SYSFS)
We should not dereference registers as pointers, so use readl/writel
instead for these registers.
The clock registers are accessed in multiple files, so we have to
change them all at once.
I stumbled over these registers while looking at something unrelated.
There are in fact other registers
This function is only used when CONFIG_PCMCIA is enabled, otherwise
we get a harmless warning:
arch/arm/mach-pxa/spitz.c:204:13: warning: 'spitz_card_pwr_ctrl' defined but
not used [-Wunused-function]
Marking it as __maybe_unused keeps the logic simple and avoids the
warning on randconfig
Two variables in eseries.c are used on multiple platforms,
but are not referenced when those are all disabled:
eseries.c:60:31: warning: 'e7xx_gpio_vbus' defined but not used
[-Wunused-variable]
eseries.c:129:20: warning: 'eseries_register_clks' defined but not used
[-Wunused-function]
Marking
On Fri, 29 Jan 2016 01:43:47 -0500
Jessica Yu wrote:
> ---
> kernel/trace/ftrace.c | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index eca592f..bdd7bfc 100644
> --- a/kernel/trace/ftrace.c
> +++
Tycho Andersen writes:
> Operations with the GENL_ADMIN_PERM flag fail permissions checks because
> this flag means we call netlink_capable, which uses the init user ns.
>
> Instead, let's do permissions checks in each function, but use the netlink
> socket's user
On Fri, Jan 29, 2016 at 01:57:12PM +, Alasdair G Kergon wrote:
> On Thu, Jan 28, 2016 at 01:50:19PM +, Andy Whitcroft wrote:
> > However this also removed the possibility of a dm target having target
> > specific ioctls. Currently this is not used by any in-tree targets but
> > was
Hi Jiancheng,
Driver looks mostly good. Few comments below.
On 29 Jan 04:03 PM, Jiancheng Xue wrote:
> add hisilicon spi-nor flash controller driver
>
Nitpick: "Add hisilicon spi-nor flash controller driver."
> Signed-off-by: Jiancheng Xue
> Acked-by: Rob Herring
On 01/27/2016 10:17 PM, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> Instead of a 'goto restart', we can now use radix_tree_iter_retry()
> to restart from our current position. This will make a difference
> when there are more ways to happen across an indirect
On Fri, 29 Jan 2016 12:59:13 +0100
Alexander Potapenko wrote:
> On the other hand, this will require including into
> various files that currently use __irq_section.
> But that header has a comment saying:
>
> /*
> * Please do not include this file in generic code. There
On Fri, Jan 29, 2016 at 08:59:36AM -0500, Steven Rostedt wrote:
> On Fri, 29 Jan 2016 13:57:49 +0100
> Heiko Carstens wrote:
>
> > Surpringly it wasn't one of my own patches which broke the stack tracer on
> > s390, but one from Steven:
> >
> > 72ac426a5bb0 ("tracing:
On Fri, Jan 29, 2016 at 6:42 PM, Ulf Hansson wrote:
> On 21 January 2016 at 06:26, Chen-Yu Tsai wrote:
>> Allwinner's mmc controller supports signal voltage switching. This is
>> supported in code in Allwinner's kernel. However, publicly available
>> boards
Em Fri, Jan 29, 2016 at 09:02:19PM +0800, Wangnan (F) escreveu:
> I tested this patch in my platform with
>
> $ make build-test
> $ make -f ./tests/make
>
> All test cases passed for me.
Thanks, I've testing this now,
- Arnaldo
> Thank you.
>
> On 2016/1/29 19:51, Wang Nan wrote:
> >To
gta02_configure_pmu_for_charger is only used when CONFIG_PCF50633_ADC
is set, and otherwise we get a warning about an unused symbol:
arch/arm/mach-s3c24xx/mach-gta02.c:158:1: warning:
'gta02_configure_pmu_for_charger' defined but not used [-Wunused-function]
Em Fri, Jan 29, 2016 at 05:57:30AM +, Wang Nan escreveu:
> 'make feature-dump' should give a stable result, so even 'NO_SOMETHING=1'
> is given (for babeltrace, if LIBBABELTRACE=1 is not given), we should
> try to detect those feature and {C,LD}FLAGS. Build or not should be
> controled
From: Chen Feng
This patch adds the device tree binding documentation for
hi655x PMIC regulator.
Signed-off-by: Chen Feng
Signed-off-by: Fei Wang
Signed-off-by: Xinwei Kong
Reviewed-by: Haojian
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:
An optimization for irq-restore, the SSM instruction is quite a bit slower
than an if-statement and a STOSM.
The
Add hw-trips sub-node for soctherm, which is
used to describe the hardware trip points for
each soctherm sensors.
Signed-off-by: Wei Ni
---
.../devicetree/bindings/thermal/tegra-soctherm.txt | 24 ++
1 file changed, 24 insertions(+)
diff --git
Add suspend/resume function in soctherm driver.
And enable it for Tegra124 and Tegra210.
Signed-off-by: Wei Ni
---
drivers/thermal/tegra/soctherm.c | 172 +++
1 file changed, 120 insertions(+), 52 deletions(-)
diff --git
Set cpu and gpu's thermtrip temperatures for Tegra124.
Signed-off-by: Wei Ni
---
arch/arm/boot/dts/tegra124.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/tegra124.dtsi b/arch/arm/boot/dts/tegra124.dtsi
index 68669f791c8b..17aa73648a81
Add support for hardware critical thermal limits to the SOC_THERM
driver. This is implemented outside the Linux thermal framework.
If these limits are breached, the chip will reset, and if appropriately
configured, will turn off the PMIC.
This support is critical for safe usage of the chip.
Adds soctherm node for Tegra210, and add cpu,
gpu, mem, pllx as thermal-zones.
Signed-off-by: Wei Ni
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 53
1 file changed, 53 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
Hi Alexander,
Am Freitag, 29. Januar 2016, 10:58:02 schrieb Alexander Kochetkov:
> Allow sclk_i2s0 and i2s0_frac to change their parents rate as
> that the upstream dividers are purely there to feed sclk_i2s0
>
> Tested on radxarock-lite.
>
> Signed-off-by: Alexander Kochetkov
Determine the regmap max_register configuration from the io resource size
and the reg-io-width device tree property.
Signed-off-by: Philipp Zabel
---
drivers/mfd/syscon.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/syscon.c
On Fri, 2016-01-29 at 00:13 +0100, Mark Brown wrote:
> On Thu, Jan 28, 2016 at 07:13:48PM +0100, John Crispin wrote:
>
> > would the following two bindings be ok ? I would create patches to add them.
>
> > * regulator-allow-mode; or regulator-allow-change-mode;
>
> This seems redundant, if we
On 2016/1/29 6:46, Alex Williamson wrote:
On Fri, 2016-01-15 at 15:06 +0800, Yongji Xie wrote:
MSI-X tables are not allowed to be mmapped in vfio-pci
driver in case that user get to touch this directly.
This will cause some performance issues when when PCI
adapters have critical registers in
On 21 January 2016 at 06:26, Chen-Yu Tsai wrote:
> Allwinner's mmc controller supports signal voltage switching. This is
> supported in code in Allwinner's kernel. However, publicly available
> boards all tie it to a fixed 3.0/3.3V regulator, with options to tie
> it to 1.8V for
Hi!
> By default, page poisoning uses a poison value (0xaa) on free. If this
> is changed to 0, the page is not only sanitized but zeroing on alloc
> with __GFP_ZERO can be skipped as well. The tradeoff is that detecting
> corruption from the poisoning is harder to detect. This feature also
>
On Fri, Jan 29, 2016 at 06:59:38AM +0100, Lothar Waßmann wrote:
> On Thu, 28 Jan 2016 23:33:52 +0100 Mark Brown wrote:
> > On Wed, Jan 20, 2016 at 01:30:38PM +0100, Lothar Waßmann wrote:
> > > - select SND_SOC_FSL_SSI
> > > + select SND_SOC_FSL_SAI if SOC_IMX6UL
> > > + select SND_SOC_FSL_SSI if
Hi all, Ping?
Does this patch has others issues need to fix? Thank you.
Charles
On 09/03/2015 10:16 PM, Johannes Thumshirn wrote:
Charles Chiou writes:
From 9d7973dfa05a7785d0eb1e9bcfb0fb6d2c493209 Mon Sep 17 00:00:00 2001
From: Charles
On Mon, Jan 25, 2016 at 10:37:43AM -0800, Andy Lutomirski wrote:
<--- Commit message please, albeit a trivial one like "Add a chicken bit ..."
> Signed-off-by: Andy Lutomirski
> ---
> Documentation/kernel-parameters.txt | 2 ++
> arch/x86/kernel/cpu/common.c| 16
On Tue, Jan 19, 2016 at 03:03:00PM +0800, Shunqian Zheng wrote:
> From: ZhengShunQian
>
> There are some IPs, such as video encoder/decoder, contains 2 slave iommus,
> one for reading and the other for writing. They share the same irq and
> clock with master.
>
> This
On Wed, Jan 27, 2016 at 01:40:24PM +1100, Stephen Rothwell wrote:
> Hi Benjamin,
>
> On Tue, 12 Jan 2016 11:38:35 -0500 Benjamin LaHaise wrote:
> >
> > On Tue, Jan 12, 2016 at 04:40:34PM +1100, Stephen Rothwell wrote:
> > >
> > > After merging the aio tree, today's linux-next
On 15/01/16 12:52, Arnd Bergmann wrote:
> The omapdrm dss driver currently fails to build in some configurations when
> the pinctrl and seq_print declarations are not visible:
>
> omapdrm/dss/dss.c:1268:2: error: implicit declaration of function
> 'pinctrl_pm_select_sleep_state'
There are a couple of nasty truncation bugs lurking in the pageattr
code that can be triggered when mapping EFI regions, e.g. when we pass
a cpa->pgd pointer. Because cpa->numpages is a 32-bit value, shifting
left by PAGE_SHIFT will truncate the resultant address to 32-bits.
Viorel-Cătălin
Commit-ID: 3e65654e3db6df6aba9c5b895f8b8e6a8d8eb508
Gitweb: http://git.kernel.org/tip/3e65654e3db6df6aba9c5b895f8b8e6a8d8eb508
Author: Andy Lutomirski
AuthorDate: Thu, 28 Jan 2016 15:11:23 -0800
Committer: Ingo Molnar
CommitDate: Fri, 29 Jan 2016
Commit-ID: 302f5b260c322696cbeb962a263a4d2d99864aed
Gitweb: http://git.kernel.org/tip/302f5b260c322696cbeb962a263a4d2d99864aed
Author: Andy Lutomirski
AuthorDate: Thu, 28 Jan 2016 15:11:25 -0800
Committer: Ingo Molnar
CommitDate: Fri, 29 Jan 2016
Commit-ID: cfcbadb49dabb05efa23e1a0f95f3391c0a815bc
Gitweb: http://git.kernel.org/tip/cfcbadb49dabb05efa23e1a0f95f3391c0a815bc
Author: Andy Lutomirski
AuthorDate: Thu, 28 Jan 2016 15:11:24 -0800
Committer: Ingo Molnar
CommitDate: Fri, 29 Jan 2016
On 25/01/16 17:03, Arnd Bergmann wrote:
> resource_size_t cannot be printed using the %x format string
> when we it is defined as u64:
>
> drivers/video/fbdev/mmp/hw/mmp_ctrl.c: In function 'mmphw_probe':
> drivers/video/fbdev/mmp/hw/mmp_ctrl.c:506:22: error: format '%x' expects
> argument of
On 21 January 2016 at 06:26, Chen-Yu Tsai wrote:
> eMMC chips require 2 power supplies, vmmc for internal logic, and vqmmc
> for driving output buffers. vqmmc also controls signaling voltage. Most
> boards we've seen use the same regulator for both, nevertheless the 2
> have
>From a588afc920bc50e894f6ae2874c4281c795e0979 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 29 Jan 2016 07:06:53 -0500
ata_sff_hsm_move() triggers BUG if it sees a host state machine state
that it dind't expect. The risk for data corruption when the
condition occurs is
>From e20cd50a8f612dbc720d31d269e748215607a0b8 Mon Sep 17 00:00:00 2001
From: "Kirill A. Shutemov"
Date: Fri, 29 Jan 2016 14:55:40 +0300
Subject: [PATCH 1/2] mm: fix bogus VM_BUG_ON_PAGE() in isolate_lru_page()
We don't care if there's a tail pages which is not
On Fri, 2016-01-29 at 16:20 +0800, Peter Hung wrote:
> Hi Andy,
>
> Andy Shevchenko 於 2016/1/28 下午 08:04 寫道:
> > On Thu, 2016-01-28 at 17:20 +0800, Peter Hung wrote:
> > > - /* Fintek PCI serial cards */
> > > - { PCI_DEVICE(0x1c29, 0x1104), .driver_data =
> > > pbn_fintek_4 },
> > > - {
On Wed, Jan 27, 2016 at 11:09:04AM +0100, Thomas Gleixner wrote:
> On Mon, 25 Jan 2016, Andy Lutomirski wrote:
> > This is a straightforward speedup on Ivy Bridge and newer, IIRC.
> > (I tested on Skylake. INVPCID is not available on Sandy Bridge.
> > I don't have Ivy Bridge, Haswell or Broadwell
fca839c00a12 ("workqueue: warn if memory reclaim tries to flush
!WQ_MEM_RECLAIM workqueue") implemented flush dependency warning which
triggers if a PF_MEMALLOC task or WQ_MEM_RECLAIM workqueue tries to
flush a !WQ_MEM_RECLAIM workquee.
This assumes that workqueues marked with WQ_MEM_RECLAIM sit
add cs4271 and cs42727 support for fsl-asoc-card
Signed-off-by: Felipe F. Tonello
---
Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 9 +
sound/soc/fsl/Kconfig | 4 ++--
sound/soc/fsl/fsl-asoc-card.c
On Thu, 2016-01-28 at 18:31 -0800, Andy Lutomirski wrote:
>
> To everyone else: we've waffled on this for way too long. I think
> we should to get DMA API implementation in with a conservative
> policy like this rather than waiting until we achieve perfection.
> I'm tired of carrying these
Signed-off-by: Felipe F. Tonello
---
Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/sound/fsl-asoc-card.txt
On Wed, Jan 27, 2016 at 01:01:52PM -0800, W. Trevor King wrote:
> This should have happened in 6255c46f (cgroup: rename cgroup
> documentations, 2016-01-11).
>
> Signed-off-by: W. Trevor King
Applied to cgroup/for-4.5-fixes.
Thanks.
--
tejun
Commit-ID: e03e7ee34fdd1c3ef494949a75cb8c61c7265fa9
Gitweb: http://git.kernel.org/tip/e03e7ee34fdd1c3ef494949a75cb8c61c7265fa9
Author: Alexei Starovoitov
AuthorDate: Mon, 25 Jan 2016 20:59:49 -0800
Committer: Ingo Molnar
CommitDate: Fri,
On 26 January 2016 at 16:26, Arnd Bergmann wrote:
> When DT based probing is used but the DMA request fails, the
> driver will print uninitialized stack data from the rx_req
> and tx_req variables, as indicated by this warning:
>
> drivers/mmc/host/omap_hsmmc.c: In function
On 26 January 2016 at 03:15, Fu, Zhonghui wrote:
>
>
> On 1/22/2016 10:51 PM, Ulf Hansson wrote:
>> On 22 January 2016 at 04:32, Fu, Zhonghui
>> wrote:
>>> This patch enables mmc hosts to suspend/resume asynchronously.
>>> This will
The bgmac driver depends on BCMA_HOST_SOC, which is only used
when CONFIG_BCMA is enabled. However, it is a bool option and can
be set when CONFIG_BCMA=m, and then bgmac can be built-in, leading
to an obvious link error:
drivers/built-in.o: In function `bgmac_init':
:(.init.text+0x7f2c):
On 21 January 2016 at 06:26, Chen-Yu Tsai wrote:
> sunxi_mmc_init_host() originated from Allwinner kernel sources. The
> magic numbers written to various registers was never documented.
>
> Add comments for values found in Allwinner user manuals.
>
> Signed-off-by: Chen-Yu Tsai
The moxart ethernet driver confuses coherent DMA buffers with
MMIO registers.
moxart_ether.c: In function 'moxart_mac_setup_desc_ring':
moxart_ether.c:146:428: error: passing argument 1 of '__fswab32' makes integer
from pointer without a cast [-Werror=int-conversion]
moxart_ether.c:74:39:
On 21 January 2016 at 06:26, Chen-Yu Tsai wrote:
> Let .set_ios() fail if mmc_regulator_set_ocr() fails to enable and set a
> proper voltage for vmmc.
>
> Signed-off-by: Chen-Yu Tsai
Thanks, applied for next!
Kind regards
Uffe
> ---
>
To prevent feature check run too many times, this patch utilizes
previous introduced feature-dump make target and FEATURES_DUMP
variable, makes sure the feature checkers run only once when doing
build-test for normal test cases.
However, since standard users doesn't reuse features dump result,
On Fri, Jan 29, 2016 at 01:05:00PM +0900, Sergey Senozhatsky wrote:
> then this will explode:
>
> printk
> spin_lock
> >> coding error <<
> spin_unlock
> printk
>spin_lock
> printk
> spin_lock
> printk
>spin_lock
> ... boom
>
> vprintk_emit() recursion
Thin out Cc list since mostly off topic message here.
On Fri, 2016-01-29 at 08:21 +, Lee Jones wrote:
> I prefer '-' in MFD.
Have to memorize that.
/* A bit of off topic */
I will cook and send one patch regarding to Intel Quark SoC, i.e. UART
driver, but I'm not sure it's a good idea now
I tested this patch in my platform with
$ make build-test
$ make -f ./tests/make
All test cases passed for me.
Thank you.
On 2016/1/29 19:51, Wang Nan wrote:
To prevent feature check run too many times, this patch utilizes
previous introduced feature-dump make target and FEATURES_DUMP
On Fri, Jan 29, 2016 at 1:23 PM, Tejun Heo wrote:
> Hello, Dmitry.
>
> On Fri, Jan 29, 2016 at 12:59:49PM +0100, Dmitry Vyukov wrote:
>> > Hmmm... the port interrupt handler checks for IDLE before calling into
>> > hsm_move, so the only explanation would be that something is
801 - 900 of 1538 matches
Mail list logo