Hi All,
On 2017/4/7 10:07, Wei.Xu wrote:
This patch series adds Mbigen, NIC, RoCE and SAS nodes for the hip07
SoC and enables the NIC, RoCE and SAS on the hip07 d05 board.
Wei Xu (5):
arm64: dts: hisi: add mbigen nodes for the hip07 SoC
arm64: dts: hisi: add network related nodes for the
On 04/07/2017 03:22 AM, Joerg Roedel wrote:
Can you please send me output of 'lspci -nv' on your system?
I have to figure out how to rebuild the system and find the time to do
it before I can test that patch, but here's the lspci output:
00:00.0 0600: 1022:1576
Subsystem: 1025:1099
Hi Jiancheng,
On 2017/3/29 14:30, Jiancheng Xue wrote:
Add bindings for HiSilicon hi3798cv200 SoC and Poplar Board.
Signed-off-by: Jiancheng Xue
Reviewed-by: Alex Elder
Acked-by: Peter Griffin
Acked-by: Rob Herring
Thanks!
Applied both to the hisilicon arm64 dt tree but added hi3798cv200 s
Hi Xiaoyin,
On 2017/3/30 14:48, Wang Xiaoyin wrote:
Add drive-strength levels of pin for Hi3660 Soc.
Signed-off-by: Wang Xiaoyin
Thanks!
Applied both to the hisilicon arm64 dt tree.
Best Regards,
Wei
---
include/dt-bindings/pinctrl/hisi.h | 15 +++
1 file changed, 15 inserti
Hi Daniel,
On 2017/3/16 22:03, Daniel Lezcano wrote:
The MMC hosts could be left in an unconsistent or uninitialized state from
the firmware. Instead of assuming, the firmware did the right things, let's
reset the host controllers.
This change fixes a bug when the mmc2/sdio is initialized leadi
Right now we have no users of __get_user_unaligned() outside of
arch/* and only 4 users of __put_user_unaligned() outside of arch/*.
All 4 are in compat_sys_getdents64(). For storing
->d_ino and ->d_off in
struct linux_dirent64 {
u64 d_ino;
s64
On Fri, 2017-04-07 at 19:26 -0700, Darren Hart wrote:
> I would like to see more testing because... well... futexes. But, we don't
> have
> a futex torture suite yet, but that is something I'm hoping to be looking into
> in the near future. What testing we do have available has passed between my
On Fri, Apr 7, 2017 at 9:21 PM, Daniel Micay wrote:
>>> Fair enough. However, placing a BUG_ON(!(read_cr0() & X86_CR0_WP))
>>> somewhere sensible should make those "leaks" visible fast -- and their
>>> exploitation impossible, i.e. fail hard.
>>
>> The leaks surely exist and now we'll just add an
On Fri, 2017-04-07 at 21:56 +0300, Michael S. Tsirkin wrote:
> OK. test3 and test4 are now pushed: test3 should fix your hang,
> test4 is trying to fix a crash reported independently.
test3 does not fix the post hibernate hang business that I can easily
reproduce, those are NFS, and at least as o
On Fri, Apr 7, 2017 at 12:58 PM, PaX Team wrote:
> On 7 Apr 2017 at 9:14, Andy Lutomirski wrote:
>
>> On Fri, Apr 7, 2017 at 6:30 AM, Mathias Krause
>> wrote:
>> > On 7 April 2017 at 15:14, Thomas Gleixner wrote:
>> >> On Fri, 7 Apr 2017, Mathias Krause wrote:
>> > Fair enough. However, placing
For endpoints, change pcie_aspm_exit_link_state() so it cleans up
the device's own state and disables ASPM if necessary, but doesn't
remove the parent's link_state.
For bridges, change pcie_aspm_exit_link_state() so it frees the
bridge's own link_state.
Fixes: https://bugzilla.kernel.org/show_bug
Now that we added a hook to be called from device_add, save the
default values from the HW registers early in the boot for further
reuse during hot device add/remove operations.
If the link is down during boot, assume that we want to enable L0s
and L1 following hotplug insertion as well as L1SS if
Split pci_aspm_init() body into pci_aspm_init_upstream()
and pci_aspm_init_downstream() for bridge and endpoint
specific code behavior.
Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=194895
Signed-off-by: Sinan Kaya
---
drivers/pci/pcie/aspm.c | 15 ++-
1 file changed, 14 inserti
For bridges, have pcie_aspm_init_link_state() allocate a link_state,
regardless of whether it currently has any children.
pcie_aspm_init_link_state(): Called for bridges (upstream end of
link) after all children have been enumerated. No longer needs to
check aspm_support_enabled or pdev->has_seco
We need a callback from pci_init_capabilities function for every
single new PCI device that is currently being added.
pci_aspm_init() will be used to save the power on state of the HW.
Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=194895
Signed-off-by: Sinan Kaya
---
drivers/pci/pcie/aspm.
Hello my dear
My name is Rosita I have something to discuss with you please if you
don't mind you can reply me,(rositaadi...@yahoo.com)so that we can
discuss it in full, i will wait for your reply thank you,from Rosita
>> Fair enough. However, placing a BUG_ON(!(read_cr0() & X86_CR0_WP))
>> somewhere sensible should make those "leaks" visible fast -- and their
>> exploitation impossible, i.e. fail hard.
>
> The leaks surely exist and now we'll just add an exploitable BUG.
That didn't seem to matter for landing a
> Not too late to rename it. Scoped write? I think it makes change to
s/change/sense/
> I probably chose the wrong name for this feature (write rarely).
> That's _usually_ true, but "sensitive_write()" was getting rather
> long. The things that we need to protect with this are certainly stuff
> that doesn't get much writing, but some things are just plain
> sensitive (like page tabl
Hi Charles,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.11-rc5 next-20170407]
[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/Charles-Keepax/mfd-arizona-Add-GPIO
Hi Charles,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.11-rc5 next-20170407]
[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/Charles-Keepax/mfd-arizona-Add-GPIO
.S:1011)
[ 21.038901] [ cut here ]
[ 21.039546] kernel BUG at mm/rmap.c:1560!
[ 21.040126] invalid opcode: [#1] SMP DEBUG_PAGEALLOC KASAN
[ 21.040910] Modules linked in:
[ 21.041345] CPU: 6 PID: 1317 Comm: trinity-c62 Tainted: GW
4.11.0-rc5-next-20170407 #7
[
On 06.04.2017 22:25, Jiri Kosina wrote:
> On Thu, 6 Apr 2017, Rafael J. Wysocki wrote:
>
> Your swap partition may be located on an NVDIMM or be encrypted.
An NVDIMM should be considered the same as any other persistent storage.
It may be encrypted, but where's the key stor
On Wed, Mar 22, 2017 at 11:36:00AM +0100, Peter Zijlstra wrote:
> When PREEMPT_RT_FULL does the spinlock -> rt_mutex substitution the PI
> chain code will (falsely) report a deadlock and BUG.
>
> The problem is that we hold hb->lock (now an rt_mutex) while doing
> task_blocks_on_rt_mutex on the fu
>> - trace_seq_printf(s, "#%-5u inner/outer(us): %4llu/%-5llu ts:%ld.%09ld",
>> + trace_seq_printf(s, "#%-5u inner/outer(us): %4llu/%-5llu
>> ts:%lld.%09ld",
>>field->seqnum,
>>field->duration,
>>field->outer_duration,
On Thu, Apr 06, 2017 at 05:54:14PM +0800, Herbert Xu wrote:
> On Mon, Mar 13, 2017 at 07:06:01PM +0200, Krzysztof Kozlowski wrote:
> >
> > I bisected this to commit f1c131b45410 ("crypto: xts - Convert to
> > skcipher"). The s5p-sss driver stays the same... but the xts changes and
> > as a result w
Stm32f769I & stm32f746 are MCUs of stm32f7 family. Here are the major
spces of the two boards:
stm32f769I discovery board:
- Cortex-M7 core @216MHz
- 2MB mcu internal flash
- 512KB internal sram
- 16MB sdram memory
- 64MB qspi flash memory
- 4 inch w
On Fri, 7 Apr 2017 17:57:00 -0700
Deepa Dinamani wrote:
> struct timespec is not y2038 safe on 32 bit machines
> and needs to be replaced by struct timespec64
> in order to represent times beyond year 2038 on such
> machines.
>
> Fix all the timestamp representation in struct trace_hwlat
> and
Use variables to replace fixed defines since the offset
of the status of spm power might be different for some chips
Signed-off-by: Mars Cheng
Signed-off-by: Kevin-CW Chen
---
drivers/soc/mediatek/mtk-scpsys.c | 33 +++--
1 file changed, 27 insertions(+), 6 deletio
On Wed, Mar 22, 2017 at 11:35:59AM +0100, Peter Zijlstra wrote:
> The problem with returning -EAGAIN when the waiter state mismatches is
> that it becomes very hard to proof a bounded execution time on the
prove
> operation. And seeing that this is a RT operation, this is somewhat
an RT
> impor
This adds power dt-bindings for MT6797
Signed-off-by: Mars Cheng
Signed-off-by: Kevin-CW Chen
---
.../devicetree/bindings/soc/mediatek/scpsys.txt|6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/scpsys.txt
b/Documenta
for some chips, there is vdec item in scpsys, this patch adds it.
Signed-off-by: Mars Cheng
---
drivers/soc/mediatek/mtk-scpsys.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/soc/mediatek/mtk-scpsys.c
index eadbf0d..a8ba800 100644
--- a/dr
This adds scpsys support for MT6797
Signed-off-by: Mars Cheng
Signed-off-by: Kevin-CW Chen
---
drivers/soc/mediatek/mtk-scpsys.c| 114 ++
include/dt-bindings/power/mt6797-power.h | 30
2 files changed, 144 insertions(+)
create mode 100644 include
Signed-off-by: Mars Cheng
---
include/dt-bindings/clock/mt6797-clk.h | 281
1 file changed, 281 insertions(+)
create mode 100644 include/dt-bindings/clock/mt6797-clk.h
diff --git a/include/dt-bindings/clock/mt6797-clk.h
b/include/dt-bindings/clock/mt6797-clk.h
This adds dt-binding documentation for Mediatek MT6797. Only
include very basic items, gic, uart timer and cpu.
Signed-off-by: Mars Cheng
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/arm/mediatek.txt |4
.../interrupt-controller/mediatek,sysirq.txt |1 +
.../de
This adds basic chip support for MT6797 SoC.
Signed-off-by: Mars Cheng
---
arch/arm64/boot/dts/mediatek/Makefile |1 +
arch/arm64/boot/dts/mediatek/mt6797-evb.dts | 36 ++
arch/arm64/boot/dts/mediatek/mt6797.dtsi| 182 +++
3 files changed, 219 inserti
From: Kevin-CW Chen
Add MT6797 clock support, include topckgen, apmixedsys, infracfg
and subsystem clocks
Signed-off-by: Kevin-CW Chen
Signed-off-by: Mars Cheng
Tested-by: Matthias Brugger
Acked-by: Stephen Boyd
---
drivers/clk/mediatek/Kconfig | 32 ++
drivers/clk/mediatek/Make
This patch set adds basic SoC support for mediatek's first 10-core
chip, X20, also known as MT6797.
- based on 4.11-rc1
- support common clk framework
- apply patches about intpol just accepted to get full feature support:
http://lists.infradead.org/pipermail/linux-mediatek/2017-March/008371.html
From: Kevin-CW Chen
This patch adds the binding documentation for apmixedsys, imgsys,
infracfg, mmsys, topckgen, vdecsys and vencsys for MT6797.
Signed-off-by: Kevin-CW Chen
Signed-off-by: Mars Cheng
Acked-by: Rob Herring
---
.../bindings/arm/mediatek/mediatek,apmixedsys.txt |1 +
.../b
This adds clk and scp nodes for MT6797
Signed-off-by: Mars Cheng
---
arch/arm64/boot/dts/mediatek/mt6797.dtsi | 71 --
1 file changed, 67 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt6797.dtsi
b/arch/arm64/boot/dts/mediatek/mt6797.dtsi
struct timespec is not y2038 safe on 32 bit machines
and needs to be replaced by struct timespec64
in order to represent times beyond year 2038 on such
machines.
Fix all the timestamp representation in struct trace_hwlat
and all the corresponding implementations.
Signed-off-by: Deepa Dinamani
--
CURRENT_TIME macro is not y2038 safe on 32 bit systems.
The patch replaces all the uses of CURRENT_TIME by
current_time() for filesystem times, and ktime_get_*
functions for others.
struct timespec is also not y2038 safe.
Retain timespec for timestamp representation here as lustre
uses it interna
CURRENT_TIME is not y2038 safe.
Replace it with ktime_get_real_ts64().
Inode time formats are already 64 bit long and
accommodates time64_t.
Signed-off-by: Deepa Dinamani
---
fs/ufs/ialloc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/ufs/ialloc.c b/fs/ufs/ialloc
CURRENT_TIME macro is not y2038 safe on 32 bit systems.
The patch replaces all the uses of CURRENT_TIME by
current_time().
This is also in preparation for the patch that transitions
vfs timestamps to use 64 bit time and hence make them
y2038 safe. current_time() is also planned to be transitioned
btrfs_root_item maintains the ctime for root updates.
This is not part of vfs_inode.
Since current_time() uses struct inode* as an argument
as Linus suggested, this cannot be used to update root
times unless, we modify the signature to use inode.
Since btrfs uses nanosecond time granularity, it c
All uses of CURRENT_TIME_SEC and CURRENT_TIME macros have
been replaced by other time functions. These macros are
also not y2038 safe.
And, all their use cases can be fulfilled by y2038 safe
ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Acked-by: John Stultz
Reviewed-by: Arnd Bergmann
---
All uses of the current_fs_time() function have been
replaced by other time interfaces.
And, its use cases can be fulfilled by current_time()
or ktime_get_* variants.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
---
include/linux/fs.h | 1 -
kernel/time/time.c | 14 --
CURRENT_TIME_SEC is not y2038 safe. current_time() will
be transitioned to use 64 bit time along with vfs in a
separate patch.
There is no plan to transition CURRENT_TIME_SEC to use
y2038 safe time interfaces.
current_time() returns timestamps according to the
granularities set in the inode's supe
CURRENT_TIME is not y2038 safe.
The macro will be deleted and all the references to it
will be replaced by ktime_get_* apis.
struct timespec is also not y2038 safe.
Retain timespec for timestamp representation here as ceph
uses it internally everywhere.
These references will be changed to use stru
CURRENT_TIME macro is not y2038 safe on 32 bit systems.
The patch replaces all the uses of CURRENT_TIME by
current_time() for filesystem times, and ktime_get_*
functions for authentication timestamps and timezone
calculations.
This is also in preparation for the patch that transitions
vfs timesta
struct timespec is not y2038 safe.
Audit timestamps are recorded in string format into
an audit buffer for a given context.
These mark the entry timestamps for the syscalls.
Use y2038 safe struct timespec64 to represent the times.
The log strings can handle this transition as strings can
hold upto
CURRENT_TIME_SEC is not y2038 safe.
Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds
in segment timestamps used by GC algorithm including the
segment mtime timestamps.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
---
fs/f2fs/segment.c | 2 +-
fs/f2fs/segment.h | 5 +++--
The series contains the last unmerged uses of CURRENT_TIME,
CURRENT_TIME_SEC, and current_fs_time().
The series also deletes these apis.
All the patches except [PATCH 9/12] and [PATCH 10/12] are resend patches.
These patches fix new instances of CURRENT_TIME.
cifs and ceph patches have been squash
On Wed, Mar 22, 2017 at 11:35:58AM +0100, Peter Zijlstra wrote:
> By changing futex_lock_pi() to use rt_mutex_*_proxy_lock() we arrive
> at a point where all wait_list modifications are done under both
> hb->lock and wait_lock.
>
> This closes the obvious interleave pattern between futex_lock_pi()
After reading command name from /proc//status,
use ltrim() and rtrim() to strip command name, not using
just while loop, isspace() and etc.
Cc: David Ahern
Cc: Don Zickus
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/util/event.c | 11 ++-
1 file changed, 2
Cc: Andi Kleen
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/util/pmu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
index 362051e..11c7525 100644
--- a/tools/perf/util/pmu.c
+++ b/tools/perf/util
On Fri, Apr 07, 2017 at 12:26:36PM -0700, matthew.gerl...@linux.intel.com wrote:
> From: Matthew Gerlach
>
> The value in the version register of the altera freeze bridge
> controller changed from the beta value of 2 to the
> value of 0xad03 in the official release of the IP.
> This patch sup
When parsing disassemble lines for source line number,
use a stripped line instead of raw line.
Cc: Andi Kleen
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/util/annotate.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/annot
When parsing disassemble lines,
use ltrim() and rtrim() to strip them,
not using just while loop and isspace().
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/util/annotate.c | 42 +++---
1 file changed, 7 insertions(+), 35 deletion
Hi, :)
It is to simply refactor the code about stip strings
with ltrim() and rtrim().
I'd appreciate some feedback on this PATCHset.
The code is avaiable at 'refactor-trim-v2' branch in
git://github.com/taeung/linux-perf
Thanks,
Taeung
v2:
- remove changes unrelated to the main purpose of P
When parsing {fore, back} ground color configs,
use ltrim() instead of just while loop and isspace().
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/ui/browser.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/ui/browser.c b/tools/perf/u
Add support to update the MBA bandwidth values for the domains. The MBA
bandwidth values are specified by updating the schemata.
We do the following to parse the bandwidth(bw) value from
schemata and update the PQOS_MSRS:
1. check the bw to satisfy the minimum and max bandwidth requirements.
Each RDT resource has a separate directory with in the
"/sys/fs/resctrl/info" which has files to display information about the
resource. Currently this list of files is a static list of files
specific to cache resource.
As a preparatory patch to add MBA info files, extend this
implementation suppo
The MBA feature details like minimum bandwidth supported, b/w
granularity etc are obtained via executing CPUID with EAX=10H
,ECX=3.
Setup and initialize the MBA specific extensions to data structures like
global list of RDT resources, RDT resource structure and RDT domain
structure.
Signed-off-by
User updates RDT resource controls by updating the schemata file. OS
then parses these updates and updates the corresponding QOS_MSRs.
However the parsing and MSR update functions are specific to cache
resource type and do not support memory resource type.
Define resource specific function pointer
The files in the info directory for MBA are as follows:
num_closids
The maximum number of CLOSids available for MBA
min_bandwidth
The minimum memory bandwidth percentage value
bandwidth_gran
The granularity of the bandwidth control in percent for the
particu
Lot of data structures and functions are named after cache specific
resources(named after cbm, cache etc). In many cases other non cache
resources may need to share the same data structures/functions.
Generalize such naming to prepare to add more resources like memory
bandwidth.
Signed-off-by: Vi
Sending another version of MBA patch series with changes to V3 version
as per Thomas feedback here:
https://marc.info/?l=linux-kernel&m=149125664024881
Changes:
- Fixed the wrong names in struct document for rdt_domain
- Changed the mba and cache ctrl values to have seperate structs and put
them
Detect MBA feature if CPUID.(EAX=10H, ECX=0):EBX.L2[bit 3] = 1.
Add supporting data structures to detect feature details which is done
in later patch using CPUID with EAX=10H, ECX= 3.
Signed-off-by: Vikas Shivappa
---
arch/x86/include/asm/cpufeatures.h | 2 ++
arch/x86/include/asm/intel_rdt.h
Update the 'intel_rdt_ui' documentation to have Memory bandwidth(b/w)
allocation interface usage.
Signed-off-by: Vikas Shivappa
---
Documentation/x86/intel_rdt_ui.txt | 107 ++---
1 file changed, 87 insertions(+), 20 deletions(-)
diff --git a/Documentation/x86/in
Before we rework the "pmem api" to stop abusing __copy_user_nocache()
for memcpy_to_pmem() we need to fix cases where we may strand dirty data
in the cpu cache. The problem occurs when copy_from_iter_pmem() is used
for arbitrary data transfers from userspace. There is no guarantee that
these transf
The following warning triggers with a new unit test that stresses the
device-dax interface.
===
[ ERR: suspicious RCU usage. ]
4.11.0-rc4+ #1049 Tainted: G O
---
./include/linux/rcupdate.h:521 Illegal context switch in RCU rea
On 04/08/2017 12:04 AM, Arnaldo Carvalho de Melo wrote:
Em Fri, Apr 07, 2017 at 11:24:17PM +0900, Taeung Song escreveu:
When parsing disassemble lines,
use ltrim() and rtrim() to strip them,
not using just while loop and isspace().
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
On Fri, Apr 7, 2017 at 10:41 AM, Kani, Toshimitsu wrote:
> On Thu, 2017-04-06 at 13:59 -0700, Dan Williams wrote:
>> Before we rework the "pmem api" to stop abusing __copy_user_nocache()
>> for memcpy_to_pmem() we need to fix cases where we may strand dirty
>> data in the cpu cache. The problem oc
On 04/07/2017 05:46 PM, Kees Cook wrote:
> On Fri, Apr 7, 2017 at 3:16 PM, Tyler Hicks wrote:
>> On 02/22/2017 12:46 PM, Kees Cook wrote:
>>> On Thu, Feb 16, 2017 at 3:29 PM, Kees Cook wrote:
On Wed, Feb 15, 2017 at 7:24 PM, Andy Lutomirski
wrote:
> On Mon, Feb 13, 2017 at 7:45 PM
On 04/08/2017 12:06 AM, Arnaldo Carvalho de Melo wrote:
Em Fri, Apr 07, 2017 at 11:24:18PM +0900, Taeung Song escreveu:
To strip csv output, use ltrim() instead of
just while loop and isspace() at print_metric_{only}_csv().
Applied.
Thank you!
- Taeung
From: Colin Ian King
The strncasecmp of buff against the literal string RSSI
is using variable length which is zero. This should be instead
using the variable size instead. Also remove the redundant
variable length.
Detected by PVS-Studio, warning: V575
Signed-off-by: Colin Ian King
---
driv
On Fri, Apr 07, 2017 at 04:30:59PM -0700, Darren Hart wrote:
> On Wed, Mar 22, 2017 at 11:35:57AM +0100, Peter Zijlstra wrote:
> > With the ultimate goal of keeping rt_mutex wait_list and futex_q
> > waiters consistent we want to split 'rt_mutex_futex_lock()' into finer
>
> I want to be clear that
From: Colin Ian King
There is a missing comma between the last two literal strings in
array stime, so add it in.
Detected by PVS-Studio, warning: V653
Signed-off-by: Colin Ian King
---
drivers/power/supply/lp8788-charger.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dr
On Wed, Mar 22, 2017 at 11:35:57AM +0100, Peter Zijlstra wrote:
> With the ultimate goal of keeping rt_mutex wait_list and futex_q
> waiters consistent we want to split 'rt_mutex_futex_lock()' into finer
I want to be clear that I understand why this patch is needed - as it actually
moves both the
On 04/07/17 10:09, Rob Herring wrote:
> + Robin, Sricharan
>
> On Fri, Apr 7, 2017 at 12:18 AM, Frank Rowand wrote:
>> On 04/06/17 15:41, Rob Herring wrote:
>>> On Thu, Apr 6, 2017 at 1:37 PM, Frank Rowand wrote:
On 04/06/17 07:03, Rob Herring wrote:
> On Thu, Apr 6, 2017 at 1:18 AM,
From: Colin Ian King
The check for the bad node type of sb->type is checking sa->type
and not sb-type. This looks like a cut and paste error. Fix this.
Detected by PVS-Studio, warning: V581
Signed-off-by: Colin Ian King
---
fs/ubifs/debug.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletio
On Fri, 2017-04-07 at 09:03 -0500, Rob Herring wrote:
> Is this with a serial port? There were some changes to serial_core
> close in 4.9.
It's a combo of serial and hvc actually.
Cheers,
Ben.
On 04/07/17 07:46, Robin Murphy wrote:
> On 06/04/17 20:34, Frank Rowand wrote:
>> On 04/06/17 04:01, Sricharan R wrote:
>>> Hi Frank,
>>>
>>> On 4/6/2017 12:31 PM, Frank Rowand wrote:
On 04/04/17 03:18, Sricharan R wrote:
> Size of the dma-range is calculated as coherent_dma_mask + 1
On 04/06/17 00:01, Frank Rowand wrote:
> On 04/04/17 03:18, Sricharan R wrote:
>> Size of the dma-range is calculated as coherent_dma_mask + 1
>> and passed to arch_setup_dma_ops further. It overflows when
>> the coherent_dma_mask is set for full 64 bits 0x,
>> resulting in size get
If DMA does not support INTERLEAVE, deinterlace_probe() breaks off
initialization, releases dma channel, but returns zero.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/media/platform/m2m-deinterlace.c | 1 +
1 file changed, 1 inser
o1 RK_PC4 IRQ_TYPE_LEVEL_LOW>;
> + rst_gpio_number = <&gpio4 RK_PC6 GPIO_ACTIVE_HIGH>;
> + };
> +
> + rt5640: rt5640@1c {
> + #sound-dai-cells = <0>;
> + compatible = "realtek,rt5640";
> + reg
The mm-of-the-moment snapshot 2017-04-07-15-53 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Fri, Apr 7, 2017 at 3:23 PM, Andrew Morton wrote:
> On Fri, 7 Apr 2017 15:15:36 -0700 Kees Cook wrote:
>
>> On Fri, Apr 7, 2017 at 3:12 PM, Andrew Morton
>> wrote:
>> > On Fri, 7 Apr 2017 14:53:23 -0700 Kees Cook wrote:
>> >
>> >> > Eddie Kovsky (2):
>> >> > module: verify address is read
On Fri, Apr 7, 2017 at 3:16 PM, Tyler Hicks wrote:
> On 02/22/2017 12:46 PM, Kees Cook wrote:
>> On Thu, Feb 16, 2017 at 3:29 PM, Kees Cook wrote:
>>> On Wed, Feb 15, 2017 at 7:24 PM, Andy Lutomirski
>>> wrote:
On Mon, Feb 13, 2017 at 7:45 PM, Tyler Hicks wrote:
> This patch set is th
On Fri, 7 Apr 2017 15:15:36 -0700 Kees Cook wrote:
> On Fri, Apr 7, 2017 at 3:12 PM, Andrew Morton
> wrote:
> > On Fri, 7 Apr 2017 14:53:23 -0700 Kees Cook wrote:
> >
> >> > Eddie Kovsky (2):
> >> > module: verify address is read-only
> >> > extable: verify address is read-only
> >> >
> >>
This patch adds a new driver targeting the T-LBK766SE-BHSB-R. This model
is a 320x240 signature pad communicating via USB HID packets.
Optionally, it can also communicate over RS-232, but this is not
supported in this patch. Enough of the protocol itself is implemented
here in order to blit bitmaps
On 02/22/2017 12:46 PM, Kees Cook wrote:
> On Thu, Feb 16, 2017 at 3:29 PM, Kees Cook wrote:
>> On Wed, Feb 15, 2017 at 7:24 PM, Andy Lutomirski wrote:
>>> On Mon, Feb 13, 2017 at 7:45 PM, Tyler Hicks wrote:
This patch set is the third revision of the following two previously
submitted
On Fri, Apr 7, 2017 at 3:12 PM, Andrew Morton wrote:
> On Fri, 7 Apr 2017 14:53:23 -0700 Kees Cook wrote:
>
>> > Eddie Kovsky (2):
>> > module: verify address is read-only
>> > extable: verify address is read-only
>> >
>> > include/linux/kernel.h | 2 ++
>> > include/linux/module.h | 12 +++
On Fri, 7 Apr 2017 14:53:23 -0700 Kees Cook wrote:
> > Eddie Kovsky (2):
> > module: verify address is read-only
> > extable: verify address is read-only
> >
> > include/linux/kernel.h | 2 ++
> > include/linux/module.h | 12
> > kernel/extable.c | 29
On Fri, Apr 07, 2017 at 05:01:53PM -0500, Rob Herring wrote:
> On Fri, Apr 7, 2017 at 4:55 PM, Linus Walleij
> wrote:
> > It turns out that the Cortina Gemini timer block is just a
> > standard IP block from Faraday Technology named FTTMR010.
> >
> > In order to make things clear and understandab
On Thu, Apr 6, 2017 at 8:55 AM, Oleg Nesterov wrote:
> And this makes me think again that we need to restart this discusion with
> more CC's.
I'm a fan of that; I've not been able to follow this thread as it
seems to have gone far from the original deadlock problem. :) I've
seen issues with ptrac
On Fri, Apr 07, 2017 at 11:55:13PM +0200, Linus Walleij wrote:
> It turns out that the Cortina Gemini timer block is just a
> standard IP block from Faraday Technology named FTTMR010.
>
> In order to make things clear and understandable, we rename the
> bindings with a Faraday compatible as primar
On 08/04/2017 00:01, Rob Herring wrote:
> On Fri, Apr 7, 2017 at 4:55 PM, Linus Walleij
> wrote:
>> It turns out that the Cortina Gemini timer block is just a
>> standard IP block from Faraday Technology named FTTMR010.
>>
>> In order to make things clear and understandable, we rename the
>> bind
On Fri, Apr 7, 2017 at 4:55 PM, Linus Walleij wrote:
> It turns out that the Cortina Gemini timer block is just a
> standard IP block from Faraday Technology named FTTMR010.
>
> In order to make things clear and understandable, we rename the
> bindings with a Faraday compatible as primary and the
1 - 100 of 750 matches
Mail list logo
