Some of the Broadcom iProc SoCs have FlexRM ring manager
which provides a ring-based programming interface to various
offload engines (e.g. RAID, Crypto, etc).
This patch adds a common mailbox driver for Broadcom FlexRM
ring manager which can be shared by various offload engine
drivers (implemente
From: Arnd Bergmann
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 950eabbd6ddedc1b08350b9169a6a51b130ebaaf upstream.
With some gcc versions, we get a warning about the eicon driver,
and that currently shows up as the only remaining warning
From: Einar Jón
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit c97c52be78b8463ac5407f1cf1f22f8f6cf93a37 upstream.
The priv->device pointer for c_can_pci is never set, but it is used
without a NULL check in c_can_start(). Setting it in c_can_
From: Francesco Ruggeri
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 07a5d38453599052aff0877b16bb9c1585f08609 upstream.
dst_release should not access dst->flags after decrementing
__refcnt to 0. The dst_entry may be in dst_busy_list and
ds
From: Kinglong Mee
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit c929ea0b910355e1876c64431f3d5802f95b3d75 upstream.
After removing sunrpc module, I get many kmemleak information as,
unreferenced object 0x88003316b1e0 (size 544):
comm
On 2-3-2017 17:38, Arnd Bergmann wrote:
> The wlc_phy_table_write_nphy/wlc_phy_table_read_nphy functions always put an
> object
> on the stack, which will each require a redzone with KASAN and lead to
> possible
> stack overflow:
>
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:
The DMA_PREP_FENCE is to be used when preparing Tx descriptor if output
of Tx descriptor is to be used by next/dependent Tx descriptor.
The DMA_PREP_FENSE will not be set correctly in do_async_gen_syndrome()
when calling dma->device_prep_dma_pq() under following conditions:
1. ASYNC_TX_FENCE not s
The raid6_gfexp table represents {2}^n values for 0 <= n < 256. The
Linux async_tx framework pass values from raid6_gfexp as coefficients
for each source to prep_dma_pq() callback of DMA channel with PQ
capability. This creates problem for RAID6 offload engines (such as
Broadcom SBA) which take dis
The Broadcom stream buffer accelerator (SBA) provides offloading
capabilities for RAID operations. This SBA offload engine is
accessible via Broadcom SoC specific ring manager.
This patch adds Broadcom SBA RAID driver which provides one
DMA device with RAID capabilities using one or more Broadcom
This patch adds the DT bindings document for newly added Broadcom
SBA RAID driver.
Acked-by: Rob Herring
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Signed-off-by: Anup Patel
---
.../devicetree/bindings/dma/brcm,iproc-sba.txt | 29 ++
1 file changed, 29 insertions(
On old perf, when using perf probe -d to delete an inexistent event,
it return errno, eg,
-bash-4.3# perf probe -d xxx || echo $?
Info: Event "*:xxx" does not exist.
Error: Failed to delete events.
255
But now perf_del_probe_events() will always set ret = 0, different
from previous del_perf_pr
On Sun, Mar 5, 2017 at 6:36 PM, Dmitry Vyukov wrote:
> On Sun, Mar 5, 2017 at 4:08 PM, Dmitry Vyukov wrote:
>> Hello,
>>
>> I am getting the following deadlock reports while running syzkaller
>> fuzzer on net-next/8d70eeb84ab277377c017af6a21d0a337025dede:
>>
>> ===
On 06.03.2017 05:40, NeilBrown wrote:
> On Fri, Mar 03 2017, Jack Wang wrote:
>>
>> Thanks Neil for pushing the fix.
>>
>> We can optimize generic_make_request a little bit:
>> - assign bio_list struct hold directly instead init and merge
>> - remove duplicate code
>>
>> I think better to squash
The Broadcom SBA RAID is a stream-based device which provides
RAID5/6 offload.
It requires a SoC specific ring manager (such as Broadcom FlexRM
ring manager) to provide ring-based programming interface. Due to
this, the Broadcom SBA RAID driver (mailbox client) implements
DMA device having one DMA
On Sun, Mar 5, 2017 at 8:18 PM, Al Viro wrote:
> On Sun, Mar 05, 2017 at 06:33:18PM +0100, Dmitry Vyukov wrote:
>
>> Added more debug output.
>>
>> name_to_handle_at(r4, &(0x7f003000-0x6)="2e2f62757300",
>> &(0x7f003000-0xd)={0xc, 0x0, "cd21"}, &(0x7f002000)=0x0,
>> 0x1000)
>>
>> actua
This patch adds device tree bindings document for the FlexRM
ring manager found on Broadcom iProc SoCs.
Acked-by: Rob Herring
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Signed-off-by: Anup Patel
---
.../bindings/mailbox/brcm,iproc-flexrm-mbox.txt| 59 ++
1 file ch
On Mar 01 2017 or thereabouts, Joe Perches wrote:
> Use a more common logging style and remove the unnecessary
> OOM messages as there is default dump_stack when OOM.
>
> Miscellanea:
>
> o Hoist an assignment in an if
> o Realign arguments
> o Realign a deeply indented if descendent above a prin
> On Mon, 20 Feb 2017 13:29:46 +0200 Elena Reshetova
> wrote:
>
> > Now when new refcount_t type and API are finally merged
> > (see include/linux/refcount.h), the following
> > patches convert various refcounters in the ipc susystem from atomic_t
> > to refcount_t. By doing this we prevent inten
On 2017년 03월 06일 16:24, Krzysztof Kozlowski wrote:
> On Mon, Mar 6, 2017 at 4:52 AM, Brian Kim wrote:
>> The power button on Odroid XU3/4 is connected with the PWRON pin of
>> s2mps11 PMIC. The s2mps11 sends low signal to GPIO input in exynos 5422
>> via ONOB pin.
>>
>> This patch adds devicetree
On Tuesday 07 February 2017 08:25 AM, Masami Hiramatsu wrote:
> On Thu, 2 Feb 2017 16:41:38 +0530
> Ravi Bangoria wrote:
>
>> The v5 patchset for sdt marker argument support for x86 [1] has
>> couple of issues. For example, it still has x86 specific code
>> in general code. It lacks support fo
Hello,
I've got the following use-after-free report while running syzkaller
fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. Note that the task
is freed right in copy_process due to some error, but it's referenced
by another thread in perf subsystem.
===
Hi,
On 3/3/2017 9:27 PM, Peter Senna Tschudin wrote:
The video processing pipeline on the second output on the GE B850v3:
Host -> LVDS|--(STDP4028)--|DP -> DP|--(STDP2690)--|DP++ -> Video output
Each bridge has a dedicated flash containing firmware for supporting the
custom design. The resul
Hi Xie XiuQi,
On 03/03/17 10:39, Xie XiuQi wrote:
> ARM APEI extension proposal added SEI (asynchronous SError interrupt)
> notification type for ARMv8.
>
> Add a new GHES error source handling function for SEI. In firmware
> first mode, if an error source's notification type is SEI. Then GHES
>
On 06/03/17 08:38, Peter De Schrijver wrote:
> On Thu, Mar 02, 2017 at 05:56:49PM +, Jon Hunter wrote:
>>
>> On 28/02/17 15:19, Peter De Schrijver wrote:
>>> This is needed to make the JTAG debugging interface work.
>>>
>>> Signed-off-by: Peter De Schrijver
>>> ---
>>> drivers/clk/tegra/clk-
Cc += LinusW
On Mon, Mar 06, 2017 at 10:53:27AM +0100, Geert Uytterhoeven wrote:
> On Mon, Mar 6, 2017 at 10:30 AM, Uwe Kleine-König
> wrote:
> > On Mon, Mar 06, 2017 at 10:09:50AM +0100, Geert Uytterhoeven wrote:
> >> On Mon, Mar 6, 2017 at 9:58 AM, Uwe Kleine-König
> >> wrote:
> >> > On Mon, M
The aux port does not get detected without noloop quirk, so external PS/2
mouse cannot work as result.
The PS/2 mouse can work with this quirk.
BugLink: https://bugs.launchpad.net/bugs/1591053
Signed-off-by: Kai-Heng Feng
---
drivers/input/serio/i8042-x86ia64io.h | 7 +++
1 file changed, 7
Hi Uwe,
On Mon, Mar 6, 2017 at 10:30 AM, Uwe Kleine-König
wrote:
> On Mon, Mar 06, 2017 at 10:09:50AM +0100, Geert Uytterhoeven wrote:
>> On Mon, Mar 6, 2017 at 9:58 AM, Uwe Kleine-König
>> wrote:
>> > On Mon, Mar 06, 2017 at 09:49:39AM +0100, Geert Uytterhoeven wrote:
>> >> > Given that mctrl-g
On Fri, Feb 10, 2017 at 5:41 PM, Mylène Josserand
wrote:
> Update the driver to use SND_SOC_DAPM_AIF_IN instead of
> SND_SOC_DAPM_DAC.
>
> Set the route names so it must be updated on the device tree too.
>
> Signed-off-by: Mylène Josserand
> ---
> arch/arm/boot/dts/sun8i-a33.dtsi | 4 ++--
Thi
On Mon, Mar 06, 2017 at 10:24:24AM +0100, Dmitry Vyukov wrote:
> On Sun, Mar 5, 2017 at 7:47 PM, Paul E. McKenney
> wrote:
> > On Sun, Mar 05, 2017 at 11:50:39AM +0100, Dmitry Vyukov wrote:
> >> On Sat, Mar 4, 2017 at 9:40 PM, Paul E. McKenney
> >> wrote:
> >> > On Sat, Mar 04, 2017 at 05:01:19PM
Add support for HS400ES mode to Cadence SDHCI driver.
Signed-off-by: Piotr Sroka
---
Changes in v2:
- Modify enhanced strobe function to handle disabling
enhanced strobe inside the function.
Do no relay on that mmc_set_ios() is called
immediately after host->ops->hs400_enhanced_strobe(ho
Hi,
On Mon, Mar 06, 2017 at 12:45:35AM +0800, Icenowy Zheng wrote:
> Response Timeout is very usual: it will happen when trying to run some
> commands that do not belong to the card; it will happen when some SDIO
> card transfer beyond its SDIO bandwidth; and when the MMC controller is
> set to po
On Fri, Mar 03, 2017 at 10:20:44PM +0100, Harald Geyer wrote:
> I don't know whether the binding document or the implementation is wrong,
> so can't propose a fix for this. Sorry.
The documentation for the fixed and GPIO regulators needs to be updated,
it the property is optional for general regu
On Fri, Mar 03, 2017 at 06:05:15PM +, Jose Abreu wrote:
> Hi Alexey,
>
>
> On 03-03-2017 13:27, Alexey Brodkin wrote:
> >
> > So if I understood you correct here what I really need is just to get rid
> > of existing check,
> > right? I.e. the following is to be in v2 respin:
> >
On Sat, Mar 04, 2017 at 04:37:17PM +0200, Andy Shevchenko wrote:
> On Sat, Mar 4, 2017 at 3:09 PM, James Hogan wrote:
> > Commit 6a171b299379 ("serial: 8250_dw: Allow hardware flow control to be
> > used") recently broke the 8250_dw driver on platforms which don't select
> > HAVE_CLK, as dw8250_se
On Mon, Mar 6, 2017 at 11:07 AM, Paul E. McKenney
wrote:
> On Mon, Mar 06, 2017 at 10:24:24AM +0100, Dmitry Vyukov wrote:
>> On Sun, Mar 5, 2017 at 7:47 PM, Paul E. McKenney
>> wrote:
>> > On Sun, Mar 05, 2017 at 11:50:39AM +0100, Dmitry Vyukov wrote:
>> >> On Sat, Mar 4, 2017 at 9:40 PM, Paul E.
Hi,
On Friday 17 February 2017 10:45 PM, Christoph Hellwig wrote:
> I'm commenting on the configfs layout here instead of the patch with the
> code as the issues are easier to explain that way. I think the layout
> is a bit confusing and could be cleaner by making use of pre-created
> entries and
Am Freitag, den 03.03.2017, 20:27 +0100 schrieb Mats Karrman:
> On 2017-03-03 13:59, Heikki Krogerus wrote:
>
> >
> > On Fri, Mar 03, 2017 at 08:29:18AM +0100, Mats Karrman wrote:
> >
>
> >
> > How would something like that sound to you guys?
>
> Complicated... Need to marinate on that fo
Signed-off-by: Geert Uytterhoeven
---
arch/m68k/include/asm/unistd.h | 2 +-
arch/m68k/include/uapi/asm/unistd.h | 1 +
arch/m68k/kernel/syscalltable.S | 1 +
3 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/m68k/include/asm/unistd.h b/arch/m68k/include/asm/unistd.h
ind
zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using
the NVMe over Fabrics loopback target which potentially sends a huge bulk of
pages attached to the bio's bvec this results in a kernel panic because of
array out of bounds accesses in zram_decompress_page().
Signed-off-by
On 03/06/2017 11:23 AM, Johannes Thumshirn wrote:
> zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using
> the NVMe over Fabrics loopback target which potentially sends a huge bulk of
> pages attached to the bio's bvec this results in a kernel panic because of
> array out of
On Sun, Mar 5, 2017 at 7:47 PM, Paul E. McKenney
wrote:
> On Sun, Mar 05, 2017 at 11:50:39AM +0100, Dmitry Vyukov wrote:
>> On Sat, Mar 4, 2017 at 9:40 PM, Paul E. McKenney
>> wrote:
>> > On Sat, Mar 04, 2017 at 05:01:19PM +0100, Dmitry Vyukov wrote:
>> >> Hello,
>> >>
>> >> Paul, you wanted bugs
Hi, Paul,
I understand the current situation.
We have three devices that have ID: E7=73 03 28.
DELL: Normal Pad type (There are Left and right button below Touchpad.)
ID: E7=73 03 28, EC=73 01 13
ID: E7=73 03 28, EC=73 01 22
TOSHIBA: Button Pad type
ID: E7=73 03 28, EC=73 01 14
I think Nick men
On 2017/3/3 2:55, Jaegeuk Kim wrote:
> On 03/02, Chao Yu wrote:
>> There is no CP_CRC_RECOVERY_FLAG tagged in checkpoint pack, calculate
>> cp_version as old format.
>>
>> Signed-off-by: Chao Yu
>> ---
>> fs/f2fs/node.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git
From: Michal Hocko
alloc_ila_locks seemed to c&p from alloc_bucket_locks allocation
pattern which is quite unusual. The default allocation size is 320 *
sizeof(spinlock_t) which is sub page unless lockdep is enabled when the
performance benefit is really questionable and not worth the subtle code
From: Michal Hocko
alloc_bucket_locks allocation pattern is quite unusual. We are
preferring vmalloc when CONFIG_NUMA is enabled. The rationale is that
vmalloc will respect the memory policy of the current process and so the
backing memory will get distributed over multiple nodes if the requester
From: Michal Hocko
Using kmalloc with the vmalloc fallback for larger allocations is a
common pattern in the kernel code. Yet we do not have any common helper
for that and so users have invented their own helpers. Some of them are
really creative when doing so. Let's just add kv[mz]alloc and make
From: Michal Hocko
vhost code uses __GFP_REPEAT when allocating vhost_virtqueue resp.
vhost_vsock because it would really like to prefer kmalloc to the
vmalloc fallback - see 23cc5a991c7a ("vhost-net: extend device
allocation to vmalloc") for more context. Michael Tsirkin has also
noted:
"
__GFP_
Hi,
this has been previously posted here [1]. Based on the discussion I have
dropped "[PATCH 9/9] net, bpf: use kvzalloc helper" and added "[PATCH]
xattr: zero out memory copied to userspace in getxattr". I have rebased
the series on top of 4.11-rc1. I hope there are no further obstacles to
have t
On Fri, Mar 03, 2017 at 11:52:40PM +0900, Ryan Lee wrote:
> Signed-off-by: Ryan Lee
> ---
> Some register values in 'max98927_reg_map' table was not physical default.
> Random mix of strangely formatted #defines and numbers was fixed.
> Reclassified register definition in 'max98927.h' for better l
From: Michal Hocko
fq_alloc_node, alloc_netdev_mqs and netif_alloc* open code kmalloc
with vmalloc fallback. Use the kvmalloc variant instead. Keep the
__GFP_REPEAT flag based on explanation from Eric:
"
At the time, tests on the hardware I had in my labs showed that
vmalloc() could deliver pages
Hi Tyler,
On 28/02/17 19:43, Baicar, Tyler wrote:
> On 2/24/2017 3:42 AM, James Morse wrote:
>> On 21/02/17 21:22, Tyler Baicar wrote:
>>> Currently external aborts are unsupported by the guest abort
>>> handling. Add handling for SEAs so that the host kernel reports
>>> SEAs which occur in the gu
From: Michal Hocko
copy_params uses kmalloc with vmalloc fallback. We already have a helper
for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't
been converted with many others by previous patches. All we need to
achieve this semantic is to use the scope memalloc_noio_{save,re
From: Michal Hocko
bcache_device_init uses kmalloc for small requests and vmalloc for those
which are larger than 64 pages. This alone is a strange criterion.
Moreover kmalloc can fallback to vmalloc on the failure. Let's simply
use kvmalloc instead as it knows how to handle the fallback properly
From: Michal Hocko
There are many code paths opencoding kvmalloc. Let's use the helper
instead. The main difference to kvmalloc is that those users are usually
not considering all the aspects of the memory allocator. E.g. allocation
requests <= 32kB (with 4kB pages) are basically never failing an
On 2017-03-03 18:07, Ansuel Smith wrote:
This patch add support for 2 Linksys router model
(shelby and rango). With this we now support all
the mvebu board on the market.
Signed-off-by: Imre Kaloz
Signed-off-by: Álvaro Fernández Rojas
Signed-off-by: Ansuel Smith
---
arch/arm/boot/dts/armada
On Fri, Mar 03, 2017 at 10:46:03AM -0800, Laura Abbott wrote:
> On 03/03/2017 08:39 AM, Laurent Pinchart wrote:
> > Hi Daniel,
> >
> > On Friday 03 Mar 2017 10:56:54 Daniel Vetter wrote:
> >> On Thu, Mar 02, 2017 at 01:44:38PM -0800, Laura Abbott wrote:
> >>> Now that we call dma_map in the dma_bu
On Fri, Mar 03, 2017 at 11:52:39PM +0900, Ryan Lee wrote:
> From: Ryan Lee
>
> Signed-off-by: Ryan Lee
> ---
>
> Initial release of ALSA SoC MAX98927 driver.
The rest of this patch series appears to be bug fixes to this driver.
Please don't submit things like this, if there are problems with c
Am 05.03.2017 um 23:17 schrieb Wanpeng Li:
> Reported by syzkaller:
>
> WARNING: CPU: 1 PID: 27742 at arch/x86/kvm/vmx.c:11029
> nested_vmx_vmexit+0x5c35/0x74d0 arch/x86/kvm/vmx.c:11029
> CPU: 1 PID: 27742 Comm: a.out Not tainted 4.10.0+ #229
> Hardware name: QEMU Standard PC (i440
On Fri, Mar 03, 2017 at 06:45:40PM +0200, Laurent Pinchart wrote:
> - I haven't seen any proposal how a heap-based solution could be used in a
> generic distribution. This needs to be figured out before committing to any
> API/ABI.
Two replies from my side:
- Just because a patch doesn't solve
Hi Jaegeuk,
On 2017/3/3 3:10, Jaegeuk Kim wrote:
> Hi Chao,
>
> On 03/01, Chao Yu wrote:
>> Both nat_bits cache and free_nid_bitmap cache provide same functionality
>> as a intermediate cache between free nid cache and disk, but with
>> different granularity of indicating free nid range, and diff
On Mon, Mar 06, 2017 at 07:31:38AM +0800, Icenowy Zheng wrote:
> From: Andre Przywara
>
> The Orange Pi PC 2 is a typical single board computer using the
> Allwinner H5 SoC. Apart from the usual suspects it features three
> separately driven USB ports and a Gigabit Ethernet port.
> Also it has a
On Tue, Jan 3, 2017 at 6:52 PM, Geert Uytterhoeven wrote:
> mm/filemap.c: In function ‘clear_bit_unlock_is_negative_byte’:
> mm/filemap.c:933: warning: passing argument 2 of ‘test_bit’ discards
> qualifiers from pointer target type
>
> Make the bitmask pointed to by the "vaddr" parameter volatile
Hello, any new update need for this or new comments? :)
On Wed, Feb 08, 2017 at 11:09:37AM +0800, changbin...@intel.com wrote:
> From: Changbin Du
>
> While I am searching something in menuconfig, I hope if I can jump to
> interested
> items directly. I even try to add this feature. When I chec
On 03/03/2017 06:22 PM, Jose Abreu wrote:
> Hi Neil,
>
>
> On 03-03-2017 16:42, Neil Armstrong wrote:
>>
>> Sure, I was meaning the *input* format the controller receives from the
>> pixel encoder, I'm quite sure the format is strict.
>>
>
> Hmm, not quite following you here. As far as the contr
On Sat, Nov 26, 2016 at 7:05 PM, Dmitry Vyukov wrote:
> Hello,
>
> I am hitting the following BUG while running syzkaller fuzzer:
>
> kernel BUG at net/unix/garbage.c:149!
> invalid opcode: [#1] SMP DEBUG_PAGEALLOC KASAN
> Dumping ftrace buffer:
>(ftrace buffer empty)
> Modules linked in:
Patch to export SIER bits to userspace via
perf_mem_data_src and perf_sample_data struct.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Sukadev Bhattiprolu
Cc: Daniel Axtens
Cc: Andrew Donnellan
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/perf/power9-pmu.c | 2 ++
1 file changed
From: Michal Hocko
getxattr uses vmalloc to allocate memory if kzalloc fails. This is
filled by vfs_getxattr and then copied to the userspace. vmalloc,
however, doesn't zero out the memory so if the specific implementation
of the xattr handler is sloppy we can theoretically expose a kernel
memory
From: Sukadev Bhattiprolu
perf_mem_data_src is an union that is initialized via the ->val field
and accessed via the bitmap fields. For this to work on big endian
platforms, we also need a big-endian represenation of perf_mem_data_src.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de
Power8/Power9 Perforence Monitoring Unit (PMU) supports
different sampling modes (SM) such as Random Instruction
Sampling (RIS), Random Load/Store Facility Sampling (RLS)
and Random Branch Sampling (RBS). Sample mode RLS updates
Sampled Instruction Event Register [SIER] bits with memory
hierarchy i
Threshold feature when used with MMCRA [Threshold Event Counter Event],
MMCRA[Threshold Start event] and MMCRA[Threshold End event] will update
MMCRA[Threashold Event Counter Exponent] and MMCRA[Threshold Event
Counter Multiplier] with the corresponding threshold event count values.
Patch to export
On Fri, Mar 03, 2017 at 10:50:20AM -0800, Laura Abbott wrote:
> On 03/03/2017 08:41 AM, Laurent Pinchart wrote:
> > Hi Laura,
> >
> > Thank you for the patch.
> >
> > On Thursday 02 Mar 2017 13:44:42 Laura Abbott wrote:
> >> When CMA was first introduced, its primary use was for DMA allocation
>
The LDST field and DATA_SRC in SIER identifies the memory hierarchy level
(eg: L1, L2 etc), from which a data-cache miss for a marked instruction
was satisfied. Use the 'perf_mem_data_src' object to export this
hierarchy level to user space.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Thom
On Wed, Mar 01, 2017 at 12:26:28PM +, Liviu Dudau wrote:
> Without this I am getting the following messages at boot on my Trimslice:
>tlv320aic23-codec 2-001a: Control not supported for path LLINEIN -> [NULL]
> -> Line Input
Please use subject lines matching the style for the subsystem.
On (03/06/17 11:23), Johannes Thumshirn wrote:
> zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using
> the NVMe over Fabrics loopback target which potentially sends a huge bulk of
> pages attached to the bio's bvec this results in a kernel panic because of
> array out of bo
On Mon, Mar 06, 2017 at 08:42:59AM +0100, Michal Hocko wrote:
> On Fri 03-03-17 09:37:55, Laura Abbott wrote:
> > On 03/03/2017 05:29 AM, Michal Hocko wrote:
> > > On Thu 02-03-17 13:44:32, Laura Abbott wrote:
> > >> Hi,
> > >>
> > >> There's been some recent discussions[1] about Ion-like framework
On 03/06/2017 03:21 AM, Wenyou Yang wrote:
> Enables the transmission of CAN FD frames on M_CAN IP core >= v3.1.x
> and with the bit rate switching.
>
> Tested on M_CAN IP 3.1.0 (CREL = 0x31040730) of SAMA5D2 SoC.
Does this patch work still with the old version of the silicon?
Marc
--
Pengutro
Commit-ID: f2853308b6409b97799b0beceacd9da43a82fe43
Gitweb: http://git.kernel.org/tip/f2853308b6409b97799b0beceacd9da43a82fe43
Author: Andy Shevchenko
AuthorDate: Mon, 6 Mar 2017 10:57:48 +0200
Committer: Thomas Gleixner
CommitDate: Mon, 6 Mar 2017 11:47:43 +0100
x86/build/x86_64_defco
Commit-ID: 3b3e78552d3077ec70d2640e629e07e3ab416a6a
Gitweb: http://git.kernel.org/tip/3b3e78552d3077ec70d2640e629e07e3ab416a6a
Author: Matjaz Hegedic
AuthorDate: Sun, 5 Mar 2017 19:16:44 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 6 Mar 2017 11:47:43 +0100
x86/reboot/quirks: Add
On Mon, Mar 06, 2017 at 06:03:06PM +0800, Kai-Heng Feng wrote:
> The aux port does not get detected without noloop quirk, so external PS/2
> mouse cannot work as result.
>
> The PS/2 mouse can work with this quirk.
>
> BugLink: https://bugs.launchpad.net/bugs/1591053
> Signed-off-by: Kai-Heng Fen
Hello,
I've got the following crash while running syzkaller fuzzer on
net-next/8d70eeb84ab277377c017af6a21d0a337025dede:
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked
On Mon, Mar 6, 2017 at 10:16 AM, Arend Van Spriel
wrote:
> On 2-3-2017 17:38, Arnd Bergmann wrote:
>> The wlc_phy_table_write_nphy/wlc_phy_table_read_nphy functions always put an
>> object
>> on the stack, which will each require a redzone with KASAN and lead to
>> possible
>> stack overflow:
>>
Hi Alexey,
On 03-03-2017 19:24, Alexey Brodkin wrote:
>
> Correct. Otherwise we'll get some modes and devices that
> don't work.
>
> Remember our saga with 74.25 vs 74.40 MHz?
>
> With our PLLs on AXS and HSDK boards we may generate 74.25 MHz clock
> which satisfy some monitors especially those w
On Mon, Mar 06, 2017 at 11:40:41AM +0100, Daniel Vetter wrote:
> No one gave a thing about android in upstream, so Greg KH just dumped it
> all into staging/android/. We've discussed ION a bunch of times, recorded
> anything we'd like to fix in staging/android/TODO, and Laura's patch
> series here
On Mon, Mar 6, 2017 at 6:46 PM, Icenowy Zheng wrote:
>
>
> 06.03.2017, 18:35, "Maxime Ripard" :
>> Hi,
>>
>> On Mon, Mar 06, 2017 at 07:31:33AM +0800, Icenowy Zheng wrote:
>>> The skeleton.dtsi file is now deprecated, and do not exist in ARM64
>>> environment.
>>>
>>> Since we will soon reuse m
On 6-3-2017 11:38, Arnd Bergmann wrote:
> On Mon, Mar 6, 2017 at 10:16 AM, Arend Van Spriel
> wrote:
>> On 2-3-2017 17:38, Arnd Bergmann wrote:
>>> The wlc_phy_table_write_nphy/wlc_phy_table_read_nphy functions always put
>>> an object
>>> on the stack, which will each require a redzone with KASA
Hi James,
Thanks for your comments.
On 2017/3/6 18:00, James Morse wrote:
> Hi Xie XiuQi,
>
> On 03/03/17 10:39, Xie XiuQi wrote:
>> ARM APEI extension proposal added SEI (asynchronous SError interrupt)
>> notification type for ARMv8.
>>
>> Add a new GHES error source handling function for SEI.
The patch
spi: sc18is602: Add OF device ID table
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus durin
The patch
ASoC: es7134: add dt-bindings for the es7134 dac
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent t
On Fri, Mar 03, 2017 at 12:47:06PM +0100, Ulf Hansson wrote:
> On 6 February 2017 at 14:39, Jan Glauber wrote:
> > Add description of Cavium Octeon and ThunderX SOC device tree bindings.
> >
> > CC: Ulf Hansson
> > CC: Rob Herring
> > CC: Mark Rutland
> > CC: devicet...@vger.kernel.org
> >
> >
Hi,
On Sun 05-03-17 10:21:11, Wu Fengguang wrote:
> FYI next-20170303 is good while mainline is bad with this error.
> The attached reproduce-* may help reproduce the issue.
Thanks for report! So from the stacktrace we are in the path testing
removal of a device immediately after it has been prob
Hi,
On Mon, Mar 06, 2017 at 07:31:33AM +0800, Icenowy Zheng wrote:
> The skeleton.dtsi file is now deprecated, and do not exist in ARM64
> environment.
>
> Since we will soon reuse most part of H3 DTSI for H5, which is an ARM64
> chip, drop skeleton.dtsi inclusion now.
>
> Signed-off-by: Icenowy
On Mon, Mar 06, 2017 at 12:01:51AM +0100, Pavel Machek wrote:
> Hi!
>
> > > mplayer stopped working after a while. Dmesg says:
> > >
> > > [ 3000.266533] cdc_ether 2-1.2:1.0 usb0: register 'cdc_ether' at
>
> Now I'm pretty sure it is a regression in v4.11-rc0. Any ideas what to
> try? Bisect wil
On Mon, Mar 6, 2017 at 12:02 PM, Arend Van Spriel
wrote:
> On 6-3-2017 11:38, Arnd Bergmann wrote:
>> On Mon, Mar 6, 2017 at 10:16 AM, Arend Van Spriel
>> wrote:
>>> On 2-3-2017 17:38, Arnd Bergmann wrote:
The wlc_phy_table_write_nphy/wlc_phy_table_read_nphy functions always put
an obj
The patch
ASoC: es7134: add es7134 DAC driver
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus durin
On Wed, 1 Mar 2017, David Miller wrote:
> > @@ -1066,6 +1066,7 @@ hfsc_change_class(struct Qdisc *sch, u32 classid, u32
> > parentid,
> > &pfifo_qdisc_ops, classid);
> > if (cl->qdisc == NULL)
> > cl->qdisc = &noop_qdisc;
> > + qdisc_hash_add(cl
On Mon, Mar 06, 2017 at 04:13:08PM +0530, Madhavan Srinivasan wrote:
> From: Sukadev Bhattiprolu
>
> perf_mem_data_src is an union that is initialized via the ->val field
> and accessed via the bitmap fields. For this to work on big endian
> platforms, we also need a big-endian represenation of p
Create device tree bindings documentation.
Signed-off-by: Ramiro Oliveira
---
.../devicetree/bindings/media/i2c/ov5647.txt | 35 ++
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt
diff --git a/Documentation/de
Dave noticed that after fixing MADV_DONTNEED vs. numa balancing race the
last pmdp_huge_get_and_clear_notify() user is gone.
Let's drop the helper.
Signed-off-by: Kirill A. Shutemov
Cc: Dave Hansen
---
include/linux/mmu_notifier.h | 13 -
1 file changed, 13 deletions(-)
diff --git
Hello,
This patchset adds support for the Omnivision OV5647 sensor.
At the moment it only supports 640x480 in RAW 8.
This is the tenth version of the OV5647 camera driver patchset.
v10:
- Add more error info to model check
- Remove empty callback
Suggested-by: Sakari Ailus
- Change error me
As we're about to introduce a new workaround that is specific to
Cortex-A73, let's define the coresponding MIDR.
Acked-by: Mark Rutland
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/cputype.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/include/asm/cputype.h b/arch/
201 - 300 of 1037 matches
Mail list logo
