On Mon, Jun 06, 2016 at 06:43:47PM -0400, Javier Martinez Canillas wrote:
> Hello,
>
> On 06/06/2016 06:32 PM, Tyler Baker wrote:
> > On 6 June 2016 at 06:55, Kevin Hilman wrote:
> >> kernelci.org bot writes:
> >>
> >>> stable-queue boot: 73 boots: 3 failed, 68 passed with 2 offline
> >>> (v4.6
Well, I have some bad news.
This patch does not fix the issue 100% of the time apparently, I just hit it
again.
Only this time it's much harder to trigger, but stack is the same
(looks a bit different due to a compiler change). Must be some much narrower
race now.
I still don't have a crashdum
Hi Eric,
On Mon, 06 Jun 2016 15:08:26 -0700 Eric Anholt wrote:
>
> I was going to bother you to add a bunch more trees to pull into -next
> now that I'll be merging arm64 changes for the Raspberry Pi 3, but
> instead I've decided to start using the maint-scripts to make generating
> a single for-
On 06/06, Oleg Nesterov wrote:
>
> On 06/01, Dmitry Safonov wrote:
> >
> > static int fill_thread_core_info(struct elf_thread_core_info *t,
> > const struct user_regset_view *view,
> > -long signr, size_t *total)
> > +
This binding describes the control interface for the Qualcomm WCNSS.
Signed-off-by: Bjorn Andersson
---
Changes since v2:
- Fixup some misstakes in the document pointed out by Rob
Changes since v1:
- Introduce reference to wcnss block node for register block definition
- Use wcnss block node co
We need the signal from wcnss_ctrl indicating that the firmware is up
and running before we can communicate with the other components of the
chip. So make these other components children of the wcnss_ctrl device,
so they can be probed in order.
The process seems to take between 1/2-5 seconds, so t
On Mon, Jun 06, 2016 at 04:33:14PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Jun 06, 2016 at 06:43:47PM -0400, Javier Martinez Canillas wrote:
> > I'm not familiar with the apq8016-sbc board or Qualcomm platforms in general
> > but this patch is known to cause deadlocks when looking up regulators
On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> Since the LRUs were split into anon and file lists, the VM has been
> balancing between page cache and anonymous pages based on per-list
> ratios of scanned vs. rotated pages. In most cases that tips page
> reclaim towards the list that is
Gerd Hoffmann writes:
> From: Eric Anholt
>
> This commit needs to be split up and cleaned up. Also we should add
> interrupt support before pushing upstream.
>
> Signed-off-by: Eric Anholt
OK, I've confirmed with the firmware maintainers: We really can't drive
this natively from Linux. The
On Mon, 6 Jun 2016, Al Viro wrote:
>
> True in general, but here we really do a lot under that ->d_lock - all
> list traversals are under it. So I suspect that contention on nested
> lock is not an issue in that particular load. It's certainly a separate
> commit, so we'll see how much does it
On 6/6/16, 18:58, "Rob Landley" wrote:
>From: Rob Landley
>
>The kernel has string parsing code for NFS mount options, but it seems
>to have bit-rotted over the years, so toybox mount needs the following
>patch to be able to mount nfs. Without it, the kernel returns "invalid
>argument" before
On Fri, Jun 03, 2016 at 10:16:12PM +0800, Xing Zheng wrote:
> I refered to MTK's mt8173-rt5650-rt5514.txt on upstream, that compatible
> name is "mediatek,mt8173-rt5650-rt5514".
> Because our platform need to support 3 codecs (max98357a / da7219 / rt5514).
> Perhaps, you maybe feel that name is to
This binding describes the control interface for the Qualcomm WCNSS.
Signed-off-by: Bjorn Andersson
---
Changes since v3:
- Included missed fixup of the smem-state properties
Changes since v2:
- Fixup some misstakes in the document pointed out by Rob
Changes since v1:
- Introduce reference to
We need the signal from wcnss_ctrl indicating that the firmware is up
and running before we can communicate with the other components of the
chip. So make these other components children of the wcnss_ctrl device,
so they can be probed in order.
The process seems to take between 1/2-5 seconds, so t
On Mon, Jun 6, 2016 at 4:50 PM, Linus Torvalds
wrote:
>
>
> And I do want to repeat that the patch is entirely untested. It compiles.
> I looked at the assembly it generated. It looks fine to me, but I might
> have had a brainfart and done something completely broken.
Dammit.
I did that whole dc
On 06/01/2016 02:43 PM, Gerd Hoffmann wrote:
> From: Eric Anholt
>
> This commit needs to be split up and cleaned up. Also we should add
> interrupt support before pushing upstream.
>
> Signed-off-by: Eric Anholt
>
> Conflicts:
> arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts
> ---
>
Your Unicef endorsed grant of 1,600,000 USD has been issued through our
foundation email : lee.keefoundat...@outlook.com for more details.
On 06/06, David Rientjes wrote:
>
> > There is a potential race where we kill the oom disabled task which is
> > highly unlikely but possible. It would happen if __set_oom_adj raced
> > with select_bad_process and then it is OK to consider the old value or
> > with fork when it should be acceptable
Hi Johannes,
Thanks for the nice work. I didn't read all patchset yet but the design
makes sense to me so it would be better for zram-based on workload
compared to as is.
On Mon, Jun 06, 2016 at 03:48:27PM -0400, Johannes Weiner wrote:
> With the advent of fast random IO devices (SSDs, PMEM) and
On Thu, Jun 02, 2016 at 05:06:55PM +0200, Arnd Bergmann wrote:
> On Thursday, June 2, 2016 9:00:01 AM CEST Bjorn Helgaas wrote:
> > > I just did a count of the implementations of pci_ops: I found 107
> > > instances of 'struct pci_ops', and 67 of them treat type0 and type1
> > > access differently
On Mon, Jun 6, 2016 at 4:59 PM, Linus Torvalds
wrote:
>
> So the patch I sent out was indeed a terminal brainfart, but with that
> fix to change that return to a "break" it *might* work.
It seems to at least survive some trivial testing with that fixed..
Linus
Hi Rob
On 06/06/2016 10:27 PM, Rob Herring wrote:
On Fri, Jun 03, 2016 at 11:15:08PM +0800, Chris Zhong wrote:
This patch adds a binding that describes the Rockchip USB Type-C PHY
for rk3399
Signed-off-by: Chris Zhong
---
Changes in v1:
- add extcon node description
- move the registers in
On Thu, 2 Jun 2016 23:26:20 -0400
David Long wrote:
> From: Pratyush Anand
>
> Entry symbols are not kprobe safe. So blacklist them for kprobing.
>
> Signed-off-by: Pratyush Anand
> Signed-off-by: David A. Long
Looks good to me.
Acked-by: Masami Hiramatsu
> ---
> arch/arm64/kernel/entr
On Mon, Jun 06, 2016 at 04:50:59PM -0700, Linus Torvalds wrote:
>
>
> On Mon, 6 Jun 2016, Al Viro wrote:
> >
> > True in general, but here we really do a lot under that ->d_lock - all
> > list traversals are under it. So I suspect that contention on nested
> > lock is not an issue in that parti
On Tue, Jun 07, 2016 at 01:40:58AM +0100, Al Viro wrote:
> On Mon, Jun 06, 2016 at 04:50:59PM -0700, Linus Torvalds wrote:
> >
> >
> > On Mon, 6 Jun 2016, Al Viro wrote:
> > >
> > > True in general, but here we really do a lot under that ->d_lock - all
> > > list traversals are under it. So I s
On 2016年06月02日 22:31, Boris Brezillon wrote:
All outputss have a 1:1 relationship between connectors and encoders
and the driver is relying on the atomic helpers: we can drop the custom
->best_encoder() implementations and let the core call
drm_atomic_helper_best_encoder() for us.
Good, All co
On 2016年06月06日 15:58, Yakir Yang wrote:
From: Mark Yao
When the input color format is YUV, we need to do some external scale
for CBCR. Like,
* In YUV420 data format:
cbcr_xscale = dst_w / src_w * 2;
cbcr_yscale = dst_h / src_h * 2;
* In YUV422 data format:
cbcr_xscale = ds
On 2016年06月06日 15:58, Yakir Yang wrote:
The WIN0 of RK3036 VOP could support YUV data format, but driver
forget to add the uv_vir register field for it.
Signed-off-by: Yakir Yang
---
drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/d
Update reserved-memory in accordance with memory the detailed memory map
for 8916, so that we will be able to reference the firmware memory
regions.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 41 ---
1 file changed, 38 insertions(+)
On Mon, Jun 6, 2016 at 5:40 PM, Al Viro wrote:
>
> static struct dentry *next_positive(struct dentry *parent,
> struct dentry *child, int count)
> {
> struct list_head *p = child ? &child->d_child : &parent->d_subdirs;
>From your description, you seem t
On Tue, Jun 07, 2016 at 01:40:58AM +0100, Al Viro wrote:
> as initial attempt at lockless next_positive(); barriers are probably wrong,
> though...
More than just barriers... _Absolutely_ untested variant pushed into
vfs.git#untested.dcache_readdir (the last 3 commits in there). It
compiles, bu
This patch adds the smsm and smp2p nodes for the hexagon and wcnss
cores.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 82 +++
1 file changed, 82 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
b/arch/arm64/boot/dts
From: Aaron Conole
Date: Fri, 3 Jun 2016 16:57:12 -0400
> This commit adds the feature bit and associated mtu device entry for the
> virtio network device. When a virtio device comes up, it checks the
> feature bit for the VIRTIO_NET_F_MTU feature. If such feature bit is
> enabled, the driver
On Mon, 2016-06-06 at 18:15 -0400, Johannes Weiner wrote:
> On Mon, Jun 06, 2016 at 05:56:09PM -0400, Rik van Riel wrote:
> >
> > On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> > >
> > >
> > > +void lru_cache_putback(struct page *page)
> > > +{
> > > + struct pagevec *pvec = &get_c
From: Bhaktipriya Shridhar
Date: Sat, 4 Jun 2016 20:21:40 +0530
> alloc_workqueue replaces deprecated create_workqueue().
>
> A dedicated workqueue has been used since the workitem viz
> (&cwq->wk.work which maps to oct_poll_req_completion) is involved
> in normal device operation. WQ_MEM_RECLAI
From: Bhaktipriya Shridhar
Date: Sat, 4 Jun 2016 20:54:00 +0530
> alloc_workqueue replaces deprecated create_workqueue().
>
> A dedicated workqueue has been used since the workitem viz
> (&db_wq->wk.work which maps to check_db_timeout) is involved
> in normal device operation. WQ_MEM_RECLAIM has
On Mon, Jun 06, 2016 at 05:58:53PM -0700, Linus Torvalds wrote:
> >From your description, you seem to be very confused about what "child
> == NULL" means. Here it means that it's a cursor to the beginning, but
> in your commentary on move_cursor(), you say "moves cursor immediately
> past child *or
On Mon, 2016-06-06 at 15:40 +0200, Paolo Bonzini wrote:
>
> On 02/06/2016 15:59, Rik van Riel wrote:
> >
> > If a guest is saved to disk and later restored (eg. after
> > a host reboot), or live migrated to another host, I would
> > expect to get totally disjoint steal time statistics from
> > th
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
Documentation/DocBook/device-drivers.tmpl
between commit:
eae1760fc838 ("doc: update/fixup dma-buf related DocBook")
from Linus' tree and commit:
ddac4b5a6c08 ("Documentation: add fence-array to kernel DocBook")
f
My mistake in the initial support patches.
Signed-off-by: Masahiro Yamada
---
drivers/pinctrl/uniphier/pinctrl-uniphier-ld11.c | 2 +-
drivers/pinctrl/uniphier/pinctrl-uniphier-ld20.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pinctrl/uniphier/pinctrl-uniphie
Hi
I recently noticed that alternating between "make" and "make targz-pkg"
rebuilds the whole Kernel. This was not happening before. As a Kernel
developer, my build/install/test environment heavily relies on the fact
that "make targz-pkg" only quickly generates the tarball if everything
is already
Hi Sergey,
On Fri, Jun 03, 2016 at 07:24:32PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> On (06/03/16 17:23), Minchan Kim wrote:
> > On Fri, Jun 03, 2016 at 05:01:41PM +0900, Sergey Senozhatsky wrote:
> > > On (06/03/16 11:08), Minchan Kim wrote:
> > > > Now, zram is very popular for some of e
Hi,
On Mon, Jun 06, 2016 at 09:42:03AM -0700, Chris Brand wrote:
> On Thu, Jun 2, 2016 at 7:38 PM, Sebastian Reichel wrote:
> > Feel free to queue it via arm-soc with
> >
> > Acked-By: Sebastian Reichel
> >
> > If I didn't overlook it, it's missing DT documentation, though.
>
> Thanks, Sebastia
Ping.
Hi Rob,
I add some comment about gpio-keys and extcon-gpio.
I'm waiting for your reply.
On 2016년 05월 31일 23:34, Chanwoo Choi wrote:
> Hi Rob,
>
> On Tue, May 31, 2016 at 10:35 PM, Rob Herring wrote:
>> On Tue, May 31, 2016 at 2:35 AM, Chanwoo Choi wrote:
>>> Hi Rob,
>>>
>>> On 2016년 05월
From: Colin King Sent: Monday, June 06, 2016 4:22 PM
> To: Fugang Duan ; net...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Subject: [PATCH][V2] net: fec: fix spelling mistakes and add missing newline
>
> From: Colin Ian King
>
> trivial fix to spelling mistakes and add missing newline
There is no error number returned if loop driver fails in function
alloc_disk to add new loop device. Add a correct error number to make
user notify in this case.
Signed-off-by: Minfei Huang
---
drivers/block/loop.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/block/loop.c b/drive
This patch fixes the checkpatch.pl error to procfs.c:
ERROR:INITIALISED_STATIC: do not initialise statics to NULL
Signed-off-by: Wei Tang
---
fs/reiserfs/procfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/reiserfs/procfs.c b/fs/reiserfs/procfs.c
index fe99915..22882
On 6 June 2016 at 22:59, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> On ARM64 platform, it will set 'dummy_dma_ops' for device dma_ops if
>> it did not call 'arch_setup_dma_ops' at device creation time, that will
>> cause failure when setting the dma mask for device.
>>
>> Thus this pa
>> From: Jaewon
>>
>> There was an alignment mismatch issue for CMA and it was fixed by
>> commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with
>> CMA setup").
>> However the way of the commit considers not only dma-contiguous(CMA) but also
>> dma-coherent which has no tha
On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> When the splitlru patches divided page cache and swap-backed pages
> into separate LRU lists, the pressure balance between the lists was
> biased to account for the fact that streaming IO can cause memory
> pressure with a flood of pages t
This patch fixes the checkpatch.pl error to inotify_fsnotify.c:
ERROR: do not initialise statics to false
Signed-off-by: Wei Tang
---
fs/notify/inotify/inotify_fsnotify.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/notify/inotify/inotify_fsnotify.c
b/fs/notify/inotif
Hi Stefan,
Sorry for reply late, I was on PTO. And another PTO on June 9~11, 2016.UTC+8
> >> static const struct regmap_config fsl_dcu_regmap_config = {
> >> .reg_bits = 32,
> >> .reg_stride = 4,
> >> .val_bits = 32,
> >> .cache_type = REGCACHE_RBTREE,
> >
> > This needs to be a
> "Mike" == Mike Snitzer writes:
Mike> But hch was originally in favor of _always_ dropping EOPNOTSUPP on
Mike> the floor (that is what his commit 38f25255330 did). Then he said
Mike> he disagrees with these interfaces playing games with masking
Mike> EOPNOTSUPP -- to which you seemingly rea
On Mon, Jun 6, 2016 at 1:11 AM, Daniel Borkmann wrote:
> On 06/06/2016 06:56 AM, Z Lim wrote:
> [...]
>>
>> How about the attached patch? Fixes compilation error on build
>> !CONFIG_BPF_SYSCALL.
>>
>> Also, should this patch be sent to net or net-next (along with this
>> series)?
>
>
> Looks good,
On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> Currently, scan pressure between the anon and file LRU lists is
> balanced based on a mixture of reclaim efficiency and a somewhat
> vague
> notion of "value" of having certain pages in memory over others. That
> concept of value is proble
The Kconfig currently controlling compilation of this code is:
config PINCTRL_LPC18XX
bool "NXP LPC18XX/43XX SCU pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driv
The Kconfig currently controlling compilation of this code is:
config PINCTRL_AMD
bool "AMD GPIO pin control"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver there is no doub
The Kconfig currently controlling compilation of this code is:
config PINCTRL_PALMAS
bool "Pinctrl driver for the PALMAS Series MFD devices"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when read
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/Kconfig:config PINCTRL_AT91PIO4
drivers/pinctrl/Kconfig:bool "AT91 PIO4 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially o
The Kconfig currently controlling compilation of this code is:
config PINCTRL_ZYNQ
bool "Pinctrl driver for Xilinx Zynq"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver there
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/Kconfig:config PINCTRL_DIGICOLOR
drivers/pinctrl/Kconfig:bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when read
For anyone new to the underlying goal of this cleanup, we are trying to
not use module support for code that can never be built as a module since:
(1) it is easy to accidentally write unused module_exit and remove code
(2) it can be misleading when reading the source, thinking it can be
mod
On Fri, 2016-06-03 at 18:41 +0530, Jassi Brar wrote:
> On Fri, Jun 3, 2016 at 4:48 PM, Matthias Brugger
> wrote:
> > On 03/06/16 08:12, Horng-Shyang Liao wrote:
> >> On Thu, 2016-06-02 at 10:46 +0200, Matthias Brugger wrote:
>
> >>> I keep thinking about how to get rid of the two data structures
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/Kconfig:config PINCTRL_AT91
drivers/pinctrl/Kconfig:bool "AT91 pinctrl driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned,
The Kconfig currently controlling compilation of this code is:
config PINCTRL_AS3722
bool "Pinctrl and GPIO driver for ams AS3722 PMIC"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading t
The Kconfig currently controlling compilation of this code is:
config PINCTRL_BAYTRAIL
bool "Intel Baytrail GPIO pin control"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver
On Tue, Jun 7, 2016 at 10:05 AM, Minfei Huang wrote:
> There is no error number returned if loop driver fails in function
> alloc_disk to add new loop device. Add a correct error number to make
> user notify in this case.
>
> Signed-off-by: Minfei Huang
Good catch!
Reviewed-by: Ming Lei
> ---
Hi Mark,
On 2016年06月07日 07:50, Mark Brown wrote:
On Fri, Jun 03, 2016 at 10:16:12PM +0800, Xing Zheng wrote:
I refered to MTK's mt8173-rt5650-rt5514.txt on upstream, that compatible
name is "mediatek,mt8173-rt5650-rt5514".
Because our platform need to support 3 codecs (max98357a / da7219 / rt5
On 2016-06-06 19:16, Meng Yi wrote:
> Hi Stefan,
>
> Sorry for reply late, I was on PTO. And another PTO on June 9~11, 2016.UTC+8
>
>> >> static const struct regmap_config fsl_dcu_regmap_config = {
>> >> .reg_bits = 32,
>> >> .reg_stride = 4,
>> >> .val_bits = 32,
>> >> .cache_ty
On Mon, 2016-06-06 at 22:43:06 -0400, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> config PINCTRL_ZYNQ
> bool "Pinctrl driver for Xilinx Zynq"
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove the modu
Hi Daniel,
Today's linux-next merge of the clockevents tree got conflicts in:
arch/arm/Kconfig
arch/arm/mach-mxs/Kconfig
between commit:
5c34a4e89c74 ("ARM: do away with ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB")
from the arm-soc tree and commits:
db01e25865a3 ("clocksource/drivers/clps_7
Hi Heiko & Mark,
On 2016/6/6 20:33, Heiko Stübner wrote:
Am Montag, 6. Juni 2016, 12:27:54 schrieb Mark Rutland:
On Mon, Jun 06, 2016 at 05:20:03PM +0800, Frank Wang wrote:
Signed-off-by: Frank Wang
---
Changes in v3:
- Added 'clocks' and 'clock-names' optional properties.
- Specified 'o
Hi Vincent,
On Mon, Jun 06, 2016 at 02:32:39PM +0200, Vincent Guittot wrote:
> > Unlike the switch to fair class case, if the task is on_rq, it will be
> > enqueued after we move task groups, so the simplest solution is to reset
> > the task's last_update_time when we do task_move_group(), but not
From: Tien Hock Loh
This adds support for TSE PCS that uses SGMII adapter when the phy-mode of
the dwmac is set to sgmii
Signed-off-by: Tien Hock Loh
---
v2:
- Refactored the TSE PCS out from the dwmac-socfpga.c file
- Added binding documentation for TSE PCS sgmii adapter
v3:
- Added missing l
Hi Daniel,
Today's linux-next merge of the clockevents tree got a conflict in:
drivers/clocksource/arm_arch_timer.c
between commit:
d9b5e41591ca ("clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get
the virtual IRQ")
from Linus' tree and commit:
e6f3cf51efde ("clocksource/dr
On 06/05/16 21:20, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160603:
on x86_64:
ERROR: "ip_compute_csum" [drivers/scsi/scsi_debug.ko] undefined!
CONFIG_GENERIC_CSUM doesn't seem to exist for x86, so lib/checksum.o is not
built.
--
~Randy
On Mon, Jun 06, 2016 at 03:03:38PM +0100, Matt Fleming wrote:
> > #ifdef CONFIG_FAIR_GROUP_SCHED
> > -static void task_move_group_fair(struct task_struct *p)
> > +static void task_move_group_fair(struct task_struct *p, bool fork)
> > {
> > - detach_task_cfs_rq(p);
> > + /*
> > +* Newly fo
RE(versatile, "arm,versatile-sysreg",
^
Caused by commit
339ecd4051c3 ("clocksource/drivers/versatile: Convert init function to return
error")
I have used the clockevents tree from next-20160606 for today.
--
Cheers,
Stephen Rothwell
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been used since the workqueue
acpi_thermal_pm_queue with workitem &tz->thermal_check_work
(maps to acpi_thermal_check_fn), is involved in thermal zone polling.
Wallclock time is actually important and getting delayed
> "John" == John Garry writes:
John> This patchset introduces 2 separate features/fixes: - v2 hw ACPI
John> support: implemented the same as v1 hw - fix inconsistent lock:
John> remove unnecessary spinlock_irqsave() in broadcast interrupt
John> handler
Applied to 4.8/scsi-queue.
--
Martin
Hi Roger
>
> For Mux devices implementing dual-role, the mux device driver _must_ use
> OTG/dual-role core API so that a common ABI is presented to user space for
> OTG/dual-role.
That's the only point we have concern, do dual role switch through
OTG/dual-role core, not do it by itself.
>
> I
On Mon, 06 Jun 2016 14:20:32 -0700, Linus Torvalds said:
> I guess some "concurrent readdir with unlink" load would show that
> behavior, but is it _realistic_? No idea. Let's not worry about it too
> much until somebody shows a reason to worry.
I've seen Makefiles where 'make clean' does a 'find
Hi Heiko,
On 2016/6/7 10:59, Frank Wang wrote:
Hi Heiko & Mark,
On 2016/6/6 20:33, Heiko Stübner wrote:
Am Montag, 6. Juni 2016, 12:27:54 schrieb Mark Rutland:
On Mon, Jun 06, 2016 at 05:20:03PM +0800, Frank Wang wrote:
Signed-off-by: Frank Wang
---
Changes in v3:
- Added 'clocks' and 'c
On Mon, Jun 06, 2016 at 11:54:50AM +0200, Peter Zijlstra wrote:
> > The task groups are changed like this:
> >
> > if (queued)
> > dequeue_task()
> > task_move_group()
> > if (queued)
> > enqueue_task()
> >
> > Unlike the switch to fair class case, if the task is o
For different types of SoC the sensor id and endianness may vary.
"#thermal-sensor-cells" is used to provide sensor id information.
"little-endian" property is to tell the endianness of TMU.
Signed-off-by: Jia Hongtao
---
Changes for V2:
* Remove formatting chnages.
Documentation/devicetree/bin
System workqueues have been able to handle high level of concurrency
for a long time now and there's no reason to use dedicated workqueues
just to gain concurrency. Since aica_queue for AICA sound
driver has workitem dreamcastcard->spu_dma_work (maps to run_spu_dma)
which is involved in aica dma tr
> "Long" == Long Li writes:
Long,
Long> The reason is that, max_sectors already has value at this point,
Long> the default value is SCSI_DEFAULT_MAX_SECTORS
Long> (include/scsi/scsi_host.h). The lower layer host driver can change
Long> this value in its template.
The LLD sets max_hw_sectors
> "Colin" == Colin King writes:
Colin> trivial fix to spelling mistake in printk message
Applied to 4.8/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote:
> This is the start of the stable review cycle for the 3.10.102 release.
> All patches will be posted as a response to this one. If anyone has any
> issue with these being applied, please let me know. If anyone thinks some
> important p
Hi Stefan,
> >> static const struct regmap_config fsl_dcu_regmap_config = {
> >> .reg_bits = 32,
> >> .reg_stride = 4,
> >> .val_bits = 32,
> >> .cache_type = REGCACHE_RBTREE,
> >
> > This needs to be a flat cache. See
> > https://lists.freedesktop.org/archives/dri-devel/2016-Janua
On 06-06-16, 23:09, Rafael J. Wysocki wrote:
> Is there any particular reason why patches [2-7/9] are separate?
I just wanted them to be separately reviewable by platform driver owners.
Nothing else.
Will merge them in next version.
--
viresh
Hi Laxman,
On Monday 06 June 2016 05:14 PM, Laxman Dewangan wrote:
Maxim Semiconductor Max77620 supports alarm interrupts when
its die temperature crosses 120C and 140C. These threshold
temperatures are not configurable.
Add thermal driver to register PMIC die temperature as thermal
zone sensor
On Tue, May 24, 2016 at 7:43 PM, Linus Walleij wrote:
> On Fri, May 13, 2016 at 11:07 PM, Christian Lamparter
> wrote:
>
>> v9 -> v10:
>> - split "gpio: mmio: add DT support for memory-mapped GPIOs"
>> into two parts.
>> - PATCH 1/2 adds the DT infrastructure
>>
On 06/05/2016 02:40 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.72 release.
There are 23 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
iommu/ipmmu-vmsa: Initial r8a7796 support
[PATCH 1/3] iommu/ipmmu-vmsa: Add r8a7796 DT binding
[PATCH 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48
[PATCH 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code
This series adds r8a7796 support to the IPMMU driver. The DT binding
gets u
From: Magnus Damm
Update the IPMMU DT binding documentation to include the r8a7796 compat
string for R-Car M3-W.
Signed-off-by: Magnus Damm
---
Documentation/devicetree/bindings/iommu/renesas,ipmmu-vmsa.txt |1 +
1 file changed, 1 insertion(+)
--- 0001/Documentation/devicetree/bindings/i
From: Magnus Damm
Support the r8a7796 IPMMU by sharing feature flags between
r8a7795 and r8a7796. Also update IOMMU_OF_DECLARE to hook
up the updated compat string.
Signed-off-by: Magnus Damm
---
drivers/iommu/ipmmu-vmsa.c |9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
---
From: Magnus Damm
Bump up the maximum numbers of micro-TLBS to 48.
Each IPMMU device instance get micro-TLB assignment via
the "iommus" property in DT. Older SoCs tend to use a
maximum number of 32 micro-TLBd per IPMMU instance however
newer SoCs such as r8a7796 make use of up to 48 micro-TLBs.
On 06.06.2016 23:41, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Replace the legacy drm_vblank_{get,put}() with the new helper functions.
>
> Signed-off-by: Gustavo Padovan
[...]
> @@ -268,7 +268,7 @@ int amdgpu_crtc_page_flip(struct drm_crtc *crtc,
> return 0;
>
> vblank_clea
On 06/03/2016 11:40 PM, Masami Hiramatsu wrote:
Hi David,
On Thu, 2 Jun 2016 23:26:18 -0400
David Long wrote:
From: Pratyush Anand
Add all function symbols which are called from do_debug_exception under
NOKPROBE_SYMBOL, as they can not kprobed.
I see, but this patch should be applied aft
301 - 400 of 1112 matches
Mail list logo
