> > On Jun 23, 2016 8:27 AM, "Manjeet Pawar" wrote:
>> >
>> > From: Rohit Thapliyal
>> >
>> > swiotlb implementation not required to be enabled in arm and
>> > disabling it reduces uImage size by 16KB.
>> >
>>
>> How so? There are no DMA operations on ARM?
>Xen actively uses the swiotlb on ARM,
On Thu, Jun 16, 2016 at 9:49 AM, Prasun Maiti wrote:
> The two members min_scan_time and max_scan_time of structure
> "mwifiex_ie_types_btcoex_scan_time" are of two bytes each. The values
> are assigned directtly from firmware without endian conversion handling.
> So, wrong datas will get saved in
Hi all,
Changes since 20160623:
The net-next tree gained a conflict against the net tree.
The block tree gained a conflict against the btrfs-kdave tree.
The crypto tree gained a build failure for which I applied a fix patch.
The userns tree gained a conflict against Linus' tree.
Non-
Hi Stephan,
On 06/23/2016 09:38 PM, Stephan Linz wrote:
Cc: Joseph Jezak
Cc: Jörg Sommer
Cc: Mark Rutland
Signed-off-by: Stephan Linz
Acked-by: Rob Herring
Signed-off-by: Jacek Anaszewski
---
Changes in v5:
- Keep documentation for the old 'ide-disk' device tree
binding, but mark a
On Fri, Jun 24, 2016 at 08:39:08AM +0200, Jan Kiszka wrote:
> On 2016-06-24 08:12, Will Deacon wrote:
> > On Thu, Jun 23, 2016 at 07:31:34PM +0200, Jan Kiszka wrote:
> >> On 2016-06-22 08:06, Will Deacon wrote:
> >>> - The probe path seems to have some stateful operations outside of PCI
> >>>
On Thu, Jun 23, 2016 at 04:20:21PM +0200, Marc Kleine-Budde wrote:
> In commit "403567217d3f perf symbols: Do not read symbols/data from
> device files" a check to uninitialzied memory was added. This leads to
> the following valgrind output:
>
> ==24515== Syscall param stat(file_name) points to u
On 06/24/2016 06:06 AM, Vineet Gupta wrote:
On Friday 17 June 2016 03:39 PM, Daniel Lezcano wrote:
The init functions do not return any error. They behave as the following:
- panic, thus leading to a kernel crash while another timer may work and
make the system boot up correctly
On 2016-06-24 08:12, Will Deacon wrote:
> On Thu, Jun 23, 2016 at 07:31:34PM +0200, Jan Kiszka wrote:
>> On 2016-06-22 08:06, Will Deacon wrote:
>>> On Tue, Jun 21, 2016 at 08:07:50PM +0200, Jan Kiszka wrote:
diff --git a/drivers/pci/host/pci-host-common.c
b/drivers/pci/host/pci-host-com
On 22/06/16 00:15, Mel Gorman wrote:
> (sorry for resend, the previous attempt didn't go through fully for
> some reason)
>
> The bulk of the updates are in response to review from Vlastimil Babka
> and received a lot more testing than v6.
>
> Changelog since v6
> o Correct reclaim_idx when dir
Hi Steve,
On Thu, Jun 23, 2016 at 09:37:40AM -0400, Steven Rostedt wrote:
> On Mon, 23 May 2016 00:26:15 +0900
> Namhyung Kim wrote:
>
> > Currently ftrace_graph_ent{,_entry} and ftrace_graph_ret{,_entry} struct
> > can have padding bytes at the end due to alignment in 64-bit data type.
> > As t
On Thu, Jun 23, 2016 at 09:42:09AM +0200, Michael Kerrisk (man-pages) wrote:
> Hi Jann,
>
> Thanks for your further review. Follow-up of one point below.
>
> On 06/23/2016 12:44 AM, Jann Horn wrote:
> >On Wed, Jun 22, 2016 at 09:21:29PM +0200, Michael Kerrisk (man-pages) wrote:
> >>On 06/21/2016
Hi Michael,
Thanks for your comments!
>
> 2<< 30 is 2G but that is not a useful comment.
> pls explain what is the reason for this selection.
>
Will change in the next version.
> > +struct balloon_bmap_hdr {
> > + __virtio32 id;
> > + __virtio32 page_shift;
> > + __virtio64 start_pfn;
Drop redundant include of moduleparam.h
The Coccinelle semantic patch used to make this change is as follows:
@ includesmodule @
@@
#include
@ depends on includesmodule @
@@
- #include
Signed-off-by: Amitoj Kaur Chawla
---
net/caif/chnl_net.c | 1 -
1 file changed, 1 deletion(-)
diff --gi
On Wed, Jun 22, 2016 at 05:56:52PM -0400, Johannes Weiner wrote:
> On Mon, Jun 20, 2016 at 04:42:08PM +0900, Minchan Kim wrote:
> > On Fri, Jun 17, 2016 at 01:01:29PM -0400, Johannes Weiner wrote:
> > > On Fri, Jun 17, 2016 at 04:49:45PM +0900, Minchan Kim wrote:
> > > > On Thu, Jun 16, 2016 at 11:
Drop redundant include of moduleparam.h
The Coccinelle semantic patch used to make this change is as follows:
@ includesmodule @
@@
#include
@ depends on includesmodule @
@@
- #include
Signed-off-by: Amitoj Kaur Chawla
---
sound/soc/codecs/wm8753.c | 1 -
1 file changed, 1 deletion(-)
dif
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
allyesconfig) failed like this:
net/built-in.o: In function `.ecdh_shared_secret':
(.text+0x4ad8d0): multiple definition of `.ecdh_shared_secret'
crypto/built-in.o:(.text+0x113f0): first defined here
net/built-in.o:(.opd
Drop redundant include of moduleparam.h
The Coccinelle semantic patch used to make this change is as follows:
@ includesmodule @
@@
#include
@ depends on includesmodule @
@@
- #include
Signed-off-by: Amitoj Kaur Chawla
---
drivers/w1/w1.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/
On Thu, Jun 23, 2016 at 12:17 PM, Linus Torvalds
wrote:
>
> With the goal being that I'm hoping that we can then actually get rid
> of this (at least on x86-64, even if we leave it in some other
> architectures) in 4.8.
The context here was that we could almost get rid of thread-info
entirely, at
On Wednesday 22 June 2016 10:37 PM, David Lechner wrote:
> On 05/25/2016 06:15 AM, Sekhar Nori wrote:
>> On Tuesday 10 May 2016 10:14 PM, David Lechner wrote:
>>> On 05/10/2016 06:26 AM, Sergei Shtylyov wrote:
On 5/10/2016 2:46 AM, David Lechner wrote:
[...]
> +static struct platform_dev
On Thu, Jun 23, 2016 at 07:31:34PM +0200, Jan Kiszka wrote:
> On 2016-06-22 08:06, Will Deacon wrote:
> > On Tue, Jun 21, 2016 at 08:07:50PM +0200, Jan Kiszka wrote:
> >> diff --git a/drivers/pci/host/pci-host-common.c
> >> b/drivers/pci/host/pci-host-common.c
> >> index 8cba7ab..c0ff4b1 100644
>
On Thu, Jun 23, 2016 at 09:22:56PM -0700, Andy Lutomirski wrote:
> SMP does ECB crypto on stack buffers. This is complicated and
> fragile, and it will not work if the stack is virtually allocated.
>
> Switch to the crypto_cipher interface, which is simpler and safer.
>
> Cc: Marcel Holtmann
>
On 6/23/2016 7:25 PM, Wim Osterholt wrote:
> On Thu, Jun 23, 2016 at 11:45:47AM -0400, Sinan Kaya wrote:
>>>
>>> Sure, let me get a patch for you.
>>
>> Here it is
>
> http://webserver.djo.tudelft.nl/dmesg460+printpatch2
>
Thanks, this was very helpful. I was able to fix the problem by using
the
Am Donnerstag, 23. Juni 2016, 15:55:26 schrieb Tadeusz Struk:
Hi Tadeusz,
> First four patches are a resend algif_akcipher from
> Stephan Mueller, with minor changes after rebase on top of 4.7-rc1.
The first four patches:
Acked-by: Stephan Mueller
Ciao
Stephan
On 2016-5-6 23:31, Amitkumar Karwar wrote:
From: Ganapathi Bhat
This patch implement firmware download feature for
Marvell Bluetooth devices. If firmware is already
downloaded, it will skip downloading.
Signed-off-by: Ganapathi Bhat
Signed-off-by: Amitkumar Karwar
---
v2: Fixed compilation w
From: Luo Yi
Add support for the Bananapi M1 Plus A20 development board from
sinovoip.com.cn . This board is nearly a clone of the Lemaker's
Bananapro, but differ with the wlan chipset connection and i2s pinout.
And I also enable the integrated audio codec on default.
Signed-off-by: Luo Yi
---
On 2016-5-6 23:31, Amitkumar Karwar wrote:
From: Ganapathi Bhat
The hdev struct might not have initialized in protocol receive handler.
This patch adds necessary checks.
Signed-off-by: Ganapathi Bhat
Signed-off-by: Amitkumar Karwar
---
drivers/bluetooth/hci_ldisc.c | 6 --
1 file chan
On Thursday 23 June 2016 06:26 PM, Ivan Khoronzhuk wrote:
>
>
> On 23.06.16 15:36, Grygorii Strashko wrote:
>> TI CPDMA currently uses a bitmap for tracking descriptors alloactions
>> allocations, but The genalloc already handles the same and can be used
>> as with special memory (SRAM) as with D
Hi,
I see a lot of crashes with various architectures in next-20160623.
I bisected mips and sh; both bisect log point to the same patch.
Bisect log is attached. arm, ppc, and x86 images crash as well,
but I did not confirm if the same patch is the culprit there.
I tried to revert the patch, but
On 2016-5-6 23:31, Amitkumar Karwar wrote:
From: Ganapathi Bhat
The new callback is used to prepare the device before HCI becomes
ready. One can use this to download firmware if the download process
doesn't use HCI commands. Also recv_for_prepare callback is
introduced for receiving data from d
On Thursday 23 June 2016 06:06 PM, Grygorii Strashko wrote:
> TI CPDMA currently uses a bitmap for tracking descriptors alloactions
> allocations, but The genalloc already handles the same and can be used
> as with special memory (SRAM) as with DMA cherent memory chank
> (dma_alloc_coherent()). Hen
Hi,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.7-rc4 next-20160623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jongsung-Kim/clk-fixed-factor-add-optional-dt
Hi Rob,
Thank you for your comments.
On 6/20/2016 21:25, Rob Herring wrote:
On Fri, Jun 17, 2016 at 04:57:14PM +0800, Songjun Wu wrote:
DT binding documentation for ISC driver.
Signed-off-by: Songjun Wu
---
Changes in v5:
- Add clock names.
Changes in v4:
- Remove the isc clock nodes.
Cha
Hello, Byungchul,
I guess the review is ongoing yet and maybe it requires more days. Can you let
me know your estimated time for the review if it doesn't bother you?
Thanks,
SeongJae Park
On Fri, Jun 17, 2016 at 3:24 PM, Minchan Kim wrote:
> On Wed, Jun 15, 2016 at 03:47:34PM +0900, SeongJae
On Thu, Jun 23, 2016 at 12:14:11PM -0400, Paul Moore wrote:
> On Thu, Jun 23, 2016 at 2:01 AM, Heiko Carstens
> wrote:
> > On Thu, Jun 23, 2016 at 02:18:14PM +1000, Stephen Rothwell wrote:
> >> Hi Paul,
> >>
> >> Today's linux-next merge of the audit tree got a conflict in:
> >>
> >> arch/s390/k
On Mon, Jun 13, 2016 at 05:47:09PM +0800, Liang Li wrote:
> The implementation of the current virtio-balloon is not very efficient,
> Bellow is test result of time spends on inflating the balloon to 3GB of
> a 4GB idle guest:
>
> a. allocating pages (6.5%, 103ms)
> b. sending PFNs to host (68.3%,
On Thu, 2016-06-23 at 10:59PM, David Miller wrote:
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Thursday, June 23, 2016 10:59 PM
> To: Qiang Zhao
> Cc: o...@buserror.net; linux-kernel@vger.kernel.org; net...@vger.kernel.org;
> Xiaobo Xie
> Subject: Re: [P
The updated ndctl unit tests discovered that if a pfn configuration with
a 4K alignment is read from the namespace, that alignment will be
ignored in favor of the default 2M alignment. The result is that the
configuration will fail initialization with a message like:
dax6.1: bad offset: 0x220
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
> Currently, crashkernel parameter supports the below syntax to parse size
> based on memory range:
>
> crashkernel=:[,:,...]
>
> While such parsing is implemented for crashkernel parameter, it applies to
> other parameters with simila
Current driver assumes that child node channel name is either
"xlnx,axi-vdma-mm2s-channel" or "xlnx,axi-vdma-s2mm-channel"
which is confusing the users of AXI DMA and CDMA.
This patch fixes this issue by using different channel
names for the AXI DMA and AXI CDMA child nodes.
Signed-off-by: Kedares
In the existing vdma driver support for
AXI DMA and CDMA got added so the driver is no
longer VDMA specific.
This patch renames the driver and DT binding doc to xilinx_dma
and updates the Kconfig description for all the DMAS.
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
---> None.
This patch series does the following thing.
---> Add support for AXI DMA Multi-channel DMA mode.
---> Delete AXI DMA binding doc.
---> Rename the driver and update config options.
Kedareswara rao Appana (5):
Documentation: DT: vdma: Update binding doc for multi-channel dma
mode
dmaengine:
This patch updates the device-tree binding doc for
AXI DMA multi channel dma mode.
Acked-by: Rob Herring
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
---> Added Rob Acked-by.
.../devicetree/bindings/dma/xilinx/xilinx_vdma.txt |4
1 files changed, 4 insertions(+), 0 deleti
This patch adds support for AXI DMA multi-channel dma mode
Multichannel mode enables DMA to connect to multiple masters
and slaves on the streaming side.
In Multichannel mode AXI DMA supports 2D transfers.
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
---> Removed mcdma_config as sug
The AXI DMA support is added to the existing AXI VDMA
driver. Device tree binding information also updated
in the VDMA binding doc.
Acked-by: Rob Herring
Signed-off-by: Kedareswara rao Appana
---
--> Added Rob Acked-by.
.../devicetree/bindings/dma/xilinx/xilinx_dma.txt | 65
Hi,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.7-rc4 next-20160623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jongsung-Kim/clk-fixed-factor-add-optional-dt
Hi Alan,
Sorry for late answer.
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: 2016年5月13日 2:11
> To: Yang, Wenyou
> Cc: Greg Kroah-Hartman ; Ferre, Nicolas
> ; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; linux-arm-ker...@lists.infradead
Hi Eric,
Today's linux-next merge of the userns tree got a conflict in:
fs/proc/root.c
between commit:
e54ad7f1ee26 ("proc: prevent stacking filesystems on top")
from Linus' tree and commit:
e94591d0d90c ("proc: Convert proc_mount to use mount_ns")
from the userns tree.
I fixed it up
Hi,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.7-rc4 next-20160623]
[cannot apply to glikely/devicetree/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
On Thu, Jun 23, 2016 at 3:39 PM, John Stultz wrote:
> This patchset enables the pl031 RTC on the Hi6220 SoC.
>
> I'd like to submit it for review and consideration to be merged.
> (But I've not gotten much feedback on it. Do I have the right
> people cc'ed?)
Yes. One issue is the DT header causes
On 06/24/2016 10:25 AM, Shawn Lin wrote:
> Hi Jaehoon,
>
> On 2016/6/23 19:39, Jaehoon Chung wrote:
>> Hi Shawn,
>>
>> On 06/21/2016 04:39 PM, Shawn Lin wrote:
>>> 在 2016/6/21 13:32, Jaehoon Chung 写道:
Hi guys,
On 06/21/2016 11:31 AM, Shawn Lin wrote:
> On 2016/6/21 10:24, Seung-
This avoids pointless races in which another CPU or task might see a
partially populated global pgd entry. These races should normally
be harmless, but, if another CPU propagates the entry via
vmalloc_fault and then populate_pgd fails (due to memory allocation
failure, for example), this prevents
From: Ingo Molnar
So when memory hotplug removes a piece of physical memory from pagetable
mappings, it also frees the underlying PGD entry.
This complicates PGD management, so don't do this. We can keep the
PGD mapped and the PUD table all clear - it's only a single 4K page
per 512 GB of memory
kernel_unmap_pages_in_pgd() is dangerous: if a pgd entry in
init_mm.pgd were to be cleared, callers would need to ensure that
the pgd entry hadn't been propagated to any other pgd.
Its only caller was efi_cleanup_page_tables(), and that, in turn,
was unused, so just delete both functions. This le
From: Herbert Xu
rxkad uses stack memory in SG lists which would not work if stacks
were allocated from vmalloc memory. In fact, in most cases this
isn't even necessary as the stack memory ends up getting copied
over to kmalloc memory.
This patch eliminates all the unnecessary stack memory uses
Since the dawn of time, a kernel stack overflow has been a real PITA
to debug, has caused nondeterministic crashes some time after the
actual overflow, and has generally been easy to exploit for root.
With this series, arches can enable HAVE_ARCH_VMAP_STACK. Arches
that enable it (just x86 for no
SMP does ECB crypto on stack buffers. This is complicated and
fragile, and it will not work if the stack is virtually allocated.
Switch to the crypto_cipher interface, which is simpler and safer.
Cc: Marcel Holtmann
Cc: Gustavo Padovan
Cc: Johan Hedberg
Cc: "David S. Miller"
Cc: linux-blueto
We should account for stacks regardless of stack size, and we need
to account in sub-page units if THREAD_SIZE < PAGE_SIZE. Change the
units to kilobytes and Move it into account_kernel_stack().
Fixes: 12580e4b54ba8 ("mm: memcontrol: report kernel stack usage in cgroup2
memory.stat")
Cc: Vladimi
It's not going to work, because the scheduler will explode if we try
to schedule when running on an IST stack or similar.
This will matter when we let kernel stack overflows (which are #DF)
call die().
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack.c | 3 +++
1 file changed, 3 ins
If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with
vmalloc_node.
Signed-off-by: Andy Lutomirski
---
arch/Kconfig| 29 +
arch/ia64/include/asm/thread_info.h | 2 +-
include/linux/sched.h | 15 +++
kernel/fork.c
If we overflow the stack into a guard page, we'll recursively fault
when trying to dump the contents of the guard page. Use
probe_kernel_address so we can recover if this happens.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack_64.c | 12 ++--
1 file changed, 10 insertions(
If we overflow the stack, print_context_stack will abort. Detect
this case and rewind back into the valid part of the stack so that
we can trace it.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/arch/x8
This allows x86_64 kernels to enable vmapped stacks. There are a
couple of interesting bits.
First, x86 lazily faults in top-level paging entries for the vmalloc
area. This won't work if we get a page fault while trying to access
the stack: the CPU will promote it to a double-fault and we'll die
The comment suggests that show_stack(NULL, NULL) should backtrace
the current context, but the code doesn't match the comment. If
regs are given, start the "Stack:" hexdump at regs->sp.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack_32.c | 4 +++-
arch/x86/kernel/dumpstack_64.c |
If we get a page fault indicating kernel stack overflow, invoke
handle_stack_overflow(). To prevent us from overflowing the stack
again while handling the overflow (because we are likely to have
very little stack space left), call handle_stack_overflow() on the
double-fault stack
Signed-off-by: A
If we call do_exit with a clean stack, we greatly reduce the risk of
recursive oopses due to stack overflow in do_exit, and we allow
do_exit to work even if we OOPS from an IST stack. The latter gives
us a much better chance of surviving long enough after we detect a
stack overflow to write out ou
Currently, NR_KERNEL_STACK tracks the number of kernel stacks in a
zone. This only makes sense if each kernel stack exists entirely in
one zone, and allowing vmapped stacks could break this assumption.
Since frv has THREAD_SIZE < PAGE_SIZE, we need to track kernel stack
allocations in a unit that
If we're using CONFIG_VMAP_STACK and we manage to point an sg entry
at the stack, then either the sg page will be in highmem or sg_virt
will return the direct-map alias. In neither case will the existing
check_for_stack() implementation realize that it's a stack page.
Fix it by explicitly checkin
On Fri, 24 Jun 2016 07:20:38 +0800
Icenowy Zheng wrote:
> In my opinion, return directly PTR_ERR(nfc->reset) is OK here.
> If devm_reset_control_get_optional() return -EPROBE_DEFER, the code here will
> also return it. However, if we get other error, why should it return
> -EPROBE_DEFER again?
On Thu, Jun 23, 2016 at 6:14 PM, Topi Miettinen wrote:
> On 06/23/16 23:46, Andrew Morton wrote:
>> On Thu, 23 Jun 2016 18:07:10 +0300 Topi Miettinen wrote:
>>
>>> There are many basic ways to control processes, including capabilities,
>>> cgroups and resource limits. However, there are far fewer
There is no way to set additional flags for a DT-initialized fixed-
factor-clock, and it can be problematic i.e., when the clock rate
needs to be changed. [1][2]
This patch introduces an optional dt-binding named "clock-flags" to
be used for passing any needed flags from dts.
[1] http://www.spini
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Friday, June 24, 2016 11:37 AM
>
> On Fri, 24 Jun 2016 10:52:58 +0800
> Yongji Xie wrote:
> > On 2016/6/24 0:12, Alex Williamson wrote:
> > > On Mon, 30 May 2016 21:06:37 +0800
> > > Yongji Xie wrote:
> > >> +static void vfio_pc
On Friday 17 June 2016 03:39 PM, Daniel Lezcano wrote:
> The init functions do not return any error. They behave as the following:
>
> - panic, thus leading to a kernel crash while another timer may work and
>make the system boot up correctly
>
> or
>
> - print an error and let the
There is no way to set additional flags for a DT-initialized fixed-
factor-clock, and it can be problematic i.e., when the clock rate
needs to be changed. [1][2]
This patch introduces an optional dt-binding named "clock-flags" to
be used for passing any needed flags from dts.
[1] http://www.spini
On Fri, Jun 24, 2016 at 3:20 AM, wrote:
> From: Ondrej Jirman
>
> Add label to the first cpu so that it can be referenced
> from derived dts files.
>
> Signed-off-by: Ondrej Jirman
> ---
> arch/arm/boot/dts/sun8i-h3.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/
Using functions instead of macros can reduce overall code size
by eliminating unnecessary "KERN_SOH" prefixes from
format strings.
defconfig x86-64:
$ size vmlinux*
textdata bss dec hex filename
10193570 4331464 1105920 15630954 ee826a vmlinux.new
10192623 4335560 1105920 15
On Fri, Jun 24, 2016 at 3:20 AM, wrote:
> From: Ondrej Jirman
>
> SY8106A is I2C attached single output voltage regulator
> made by Silergy.
>
> Signed-off-by: Ondrej Jirman
> ---
> drivers/regulator/Kconfig | 8 +-
> drivers/regulator/Makefile| 2 +-
> drivers/regu
It's confirmed that RAPL works as expected on Ivy Bridge servers.
Tested against processor: Intel(R) Xeon(R) CPU E5-2697 v2 @2.70GHz
Signed-off-by: Xiaolong Wang
---
drivers/powercap/intel_rapl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap
On Fri, 24 Jun 2016 10:52:58 +0800
Yongji Xie wrote:
> On 2016/6/24 0:12, Alex Williamson wrote:
> > On Mon, 30 May 2016 21:06:37 +0800
> > Yongji Xie wrote:
> >> +static void vfio_pci_probe_mmaps(struct vfio_pci_device *vdev)
> >> +{
> >> + struct resource *res;
> >> + int bar;
> >> + struct
On 24/06/16 03:17, Aneesh Kumar K.V wrote:
> Reza Arbab writes:
>
>> These functions are making direct calls to the hash table APIs,
>> leading to a BUG() on systems using radix.
>>
>> Switch them to the vmemmap_{create,remove}_mapping() wrappers, and
>> move to the __meminit section.
>
>
> T
Hi,
On Fri, Jun 24, 2016 at 3:20 AM, wrote:
> From: Ondrej Jirman
>
The subject could read:
thermal: sun8i_ths: Add support for the thermal sensor on Allwinner H3
> This patch adds support for the sun8i thermal sensor on
> Allwinner H3 SoC.
>
> Signed-off-by: Ondřej Jirman
> ---
> driver
Regards,
Ocean He
SW Development Dept.
Beijing Design Center
Enterprise Product Group
Mobile: 18911778926
E-mail: he...@lenovo.com
No.6 Chuang Ye Road, Haidian District, Beijing, China 100085
> -Original Message-
> From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of
> R
Hi Linus,
This is the drm fixes tree for 4.7-rc5. It's a bit larger than normal,
due to fixes for production AMD Polaris GPUs. We only merged support for
these in 4.7-rc1 so it would be good if we got all the fixes into final.
The changes don't hit any other hardware.
Other than the amdgpu Polar
Dear Konrad,
On Thu, 23 Jun 2016 12:06:10 -0400 Konrad Rzeszutek Wilk wrote:
> On June 23, 2016 10:30:34 AM EDT, Catalin Marinas
> wrote:
> >On Thu, Jun 23, 2016 at 05:43:40PM +0530, Manjeet Pawar wrote:
> >> From: Rohit Thapliyal
> >>
> >> swiotlb default size of 64M is too big as
> >> def
While reading the patchset by Kenny Yu, I realised that not having a
field for the "recent" number of failed forks means that userspace would
have trouble accurately deciding whether or not it should increase the
limits.
In addition, by having hits_since, we get to maintain the
on-reset-we-log-fai
This allows users to dynamically adjust their limits based on how many
failed forks happened since they last reset their limits, otherwise they
would have to track (in a racy way) how many limit failures there were
since the last limit change manually. In addition, we log the first
failure since th
So that users know what the interface and meaning of the keyed values
are. In addition, mention that the only time that since=0 is when the
limit was changed.
Signed-off-by: Aleksa Sarai
---
Documentation/cgroup-v1/pids.txt | 18 ++
1 file changed, 18 insertions(+)
diff --git a/
Hi Ondrej,
On Fri, Jun 24, 2016 at 5:21 AM, wrote:
> From: Ondrej Jirman
>
> Xulong Orange Pi One uses GPIO based regulator that
> switches between two voltages: 1.1V and 1.3V. The
> regulator is controlled from the PL6 pin.
>
> Signed-off-by: Ondrej Jirman
> ---
> arch/arm/boot/dts/sun8i-h3-
Hi Ondrej,
On Fri, Jun 24, 2016 at 5:21 AM, wrote:
> From: Ondrej Jirman
>
> PLL1 on H3 requires special factors application algorithm,
> when the rate is changed. This algorithm was extracted
> from the arisc code that handles frequency scaling
> in the BSP kernel.
>
> This commit adds optiona
Hi, Alex
On 2016/6/24 0:12, Alex Williamson wrote:
On Mon, 30 May 2016 21:06:37 +0800
Yongji Xie wrote:
Current vfio-pci implementation disallows to mmap
sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio
page may be shared with other BARs. This will cause some
performance issues
Hi Ondrej,
On Fri, Jun 24, 2016 at 5:21 AM, wrote:
> From: Ondrej Jirman
>
> Xulong Orange Pi One uses GPIO based regulator that
> switches between two voltages: 1.1V and 1.3V. The
> regulator is controlled from the PL6 pin.
>
> Signed-off-by: Ondrej Jirman
> ---
> arch/arm/boot/dts/sun8i-h3-
On Thu, Jun 23, 2016 at 09:21:02AM +0200, Linus Walleij wrote:
> On Thu, Jun 23, 2016 at 12:46 AM, Greg Kroah-Hartman
> wrote:
>
> > 4.6-stable review patch. If anyone has any objections, please let me know.
>
> This should ideally be paired with
> commit 79bb71bd1d93197ce227fa167b450b633f30a52
Hi Guenter
On 06/24/2016 10:10 AM, Guenter Roeck wrote:
Hi Chris,
On Thu, Jun 23, 2016 at 5:34 PM, Chris Zhong wrote:
Hi Guenter
On 06/24/2016 05:47 AM, Guenter Roeck wrote:
Hi Chris,
On Thu, Jun 23, 2016 at 5:51 AM, Chris Zhong wrote:
Add a PHY provider driver for the rk3399 SoC Type-c
From: Kuninori Morimoto
hdmi-codec driver is common HDMI sound driver,
but it doesn't care about multi sound ports.
For example, hdmi-codec driver is supporting 1 I2S and 1 SPDIF ports,
so, we can't use this driver if HDMI has 2 or more I2S ports.
And we would like to use multi detection.
For e
From: Kuninori Morimoto
Current dw-hdmi is supporting sound via AHB bus, but it has
I2S audio feature too. This patch adds I2S audio support to dw-hdmi.
This HDMI I2S is supported by using ALSA SoC common HDMI encoder
driver.
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/bridge/Kconfig
From: Kuninori Morimoto
Current hdmi-codec driver is assuming that it will be registered
from HDMI driver. Because of this assumption, each callback function
has struct device pointer which is parent device (= HDMI).
Then, it can use dev_get_drvdata() to get private data.
OTOH, on some SoC/HDMI
On Thu, Jun 23, 2016 at 11:13:47AM +0200, Florian Westphal wrote:
> Florian Westphal wrote:
> > Greg Kroah-Hartman wrote:
> > > 3.14-stable review patch. If anyone has any objections, please let me
> > > know.
> >
> > I have -- this doesn't work in 3.14 as t->entries (the ruleset blob)
> > is
On Fri, Jun 24, 2016 at 3:20 AM, wrote:
> From: Ondrej Jirman
>
> This patch adds the binding documentation for the sun8i_ths driver
>
> Signed-off-by: Ondřej Jirman
> ---
> .../devicetree/bindings/thermal/sun8i-ths.txt | 31
> ++
> 1 file changed, 31 insertions(+)
>
Hi Mark, Thierry, Russell
These are DesignWare HDMI I2S support patches.
It will use ALSA SoC hdmi-codec driver, but we can't use it as-is.
So, 2), 3) patches modify hdmi-codec style.
Kuninori Morimoto (3):
1) drm: bridge: add DesignWare HDMI I2S audio support
2) ASoC: hdmi-codec: callback f
On Fri, Jun 24, 2016 at 3:20 AM, wrote:
> From: Josef Gajdusek
>
> Add a node describing the Security ID memory to the Allwinner H3 .dtsi file.
>
> Signed-off-by: Josef Gajdusek
> ---
> arch/arm/boot/dts/sun8i-h3.dtsi | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boo
On Thu, Jun 23, 2016 at 06:47:54PM -0700, t...@winchiphead.com wrote:
> The old driver for usb-serial chips ch34x which submitted by kernel volunteer
> Frank A Kingswood is too old to use, and
> the
> driver has bugs when receiving chracters, thus after communicating with the
> author
> we deci
1 - 100 of 926 matches
Mail list logo
