On Tue, 11 Dec 2018, at 10:35, Nathan Chancellor wrote:
> Clang does not support this option:
>
> warning: unknown warning option '-Woverride-init'; did you mean
> '-Woverride-module'? [-Wunknown-warning-option]
> 1 warning generated.
>
> Signed-off-by: Nathan Chancellor
Acked-by: Andrew
Clang does not support this option:
warning: unknown warning option '-Woverride-init'; did you mean
'-Woverride-module'? [-Wunknown-warning-option]
1 warning generated.
Signed-off-by: Nathan Chancellor
---
drivers/pinctrl/aspeed/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, Dec 04, 2018 at 02:24:29PM -0800, Anthony Yznaga wrote:
> Because kpagecount_read() fakes success if map counts are not being
> collected, clamp the page count passed to it by walk_pfn() to the pages
> value returned by the preceding call to kpageflags_read().
>
> Fixes: 7f1d23e60718
From: Tom Zanussi
The action/handler code refactoring didn't change the action/handler
syntax, but did generalize it - the Documentation should reflect that.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 56 ++-
1 file changed, 43
From: Tom Zanussi
Add support for a hist:onchange($var) handler, similar to the onmax()
handler but triggering whenever there's any change in $var, not just a
max.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.c | 3 ++-
kernel/trace/trace_events_hist.c | 58
From: Tom Zanussi
Add Documentation for the hist:onchange($var) handler.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 98 +++
1 file changed, 98 insertions(+)
diff --git a/Documentation/trace/histogram.rst
From: Tom Zanussi
Add a test case verifying the basic functionality of the
hist:onchange($var) handler.
Signed-off-by: Tom Zanussi
---
.../inter-event/trigger-onchange-action-hist.tc| 28 ++
1 file changed, 28 insertions(+)
create mode 100644
From: Tom Zanussi
Add support for hist:handlerXXX($var).snapshot(), which will take a
snapshot of the current trace buffer whenever handlerXXX is hit.
As a first user, this also adds snapshot() action support for the
onmax() handler i.e. hist:onmax($var).snapshot().
Also, the hist trigger key
From: Tom Zanussi
The action refactor code allowed actions and handlers to be separated,
but the existing onmax handler and save action code is still not
flexible enough to handle arbitrary coupling. This change generalizes
them and in the process makes additional handlers and actions easier
to
From: Tom Zanussi
Add a 'trace(synthetic_event_name, params)' alternative to
synthetic_event_name(params).
Currently, the syntax used for generating synthetic events is to
invoke synthetic_event_name(params) i.e. use the synthetic event name
as a function call.
Users requested a new form that
From: Tom Zanussi
Add a test case for the alternative trace(
---
.../inter-event/trigger-trace-action-hist.tc | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-trace-action-hist.tc
diff
From: Tom Zanussi
Have create_var_ref() manage the hist trigger's var_ref list, rather
than having similar code doing it in multiple places. This cleans up
the code and makes sure var_refs are always accounted properly.
Also, document the var_ref-related functions to make what their
purpose
On Mon, Dec 10, 2018 at 02:35:13PM -0800, Anthony Yznaga wrote:
> Certain pages that are never mapped to userspace have a type
> indicated in the page_type field of their struct pages (e.g. PG_buddy).
> page_type overlaps with _mapcount so set the count to 0 and avoid
> calling page_mapcount() for
From: Tom Zanussi
Since all the variable reference hist_fields are collected into
hist_data->var_refs[] array, there's no need to go through all the
fields looking for them, or in separate arrays like synth_var_refs[],
which will be going away soon anyway.
This also allows us to get rid of some
From: Tom Zanussi
track_data->var_ref->var_ref_idx can be used instead of
track_data.var_ref_idx, so remove it.
Also, hist_field.var_idx is completely unused, so remove it too.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 7 +--
1 file changed, 1 insertion(+), 6
From: Tom Zanussi
Add a test case verifying that basic action combinations fail as
expected.
Signed-off-by: Tom Zanussi
---
.../inter-event/trigger-action-hist-xfail.tc | 30 ++
1 file changed, 30 insertions(+)
create mode 100644
From: Tom Zanussi
All var_refs are now handled uniformly and there's no reason to treat
the synth_refs in a special way now, so remove them and associated
functions.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 18 --
1 file changed, 18 deletions(-)
diff
From: Tom Zanussi
Add a few comments to help clarify how variable and variable reference
fields are used in the code.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 36
1 file changed, 36 insertions(+)
diff --git
From: Tom Zanussi
Since every var ref for a trigger has an entry in the var_ref[] array,
use that to destroy the var_refs, instead of piecemeal via the field
expressions.
This allows us to avoid having to keep and treat differently separate
lists for the action-related references, which future
From: Tom Zanussi
Currently, tracing snapshots are context-free - they capture the ring
buffer contents at the time the tracing_snapshot() function was
invoked, and nothing else. Additionally, they're always taken
unconditionally - the calling code can decide whether or not to take a
snapshot,
From: Tom Zanussi
Add a test case verifying the basic functionality of the
hist:snapshot() action.
Signed-off-by: Tom Zanussi
---
.../inter-event/trigger-snapshot-action-hist.tc| 43 ++
1 file changed, 43 insertions(+)
create mode 100644
From: Tom Zanussi
Add Documentation for the hist:handlerXXX($var).snapshot() action.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 110 ++
1 file changed, 110 insertions(+)
diff --git a/Documentation/trace/histogram.rst
From: Tom Zanussi
Apparently this directory was missed in the license cleanup process -
add the missing identifiers to the trigger/inter-event test cases.
Signed-off-by: Tom Zanussi
---
.../ftrace/test.d/trigger/inter-event/trigger-extended-error-support.tc | 1 +
From: Tom Zanussi
Hi,
This is v8 of the hist trigger snapshot and onchange additions
patchset. It makes testcase changes suggested by Masami, and does a
bit of refactoring and cleanup as suggested by Namhyung. It also adds
a bunch of comments mainly to the variable and variable reference code
From: Tom Zanussi
Currently, the onmatch action data binds the onmatch action to data
related to synthetic event generation. Since we want to allow the
onmatch handler to potentially invoke a different action, and because
we expect other handlers to generate synthetic events, we need to
From: Tom Zanussi
Add abbreviated documentation for handlers and actions to README.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 911470ad9e94..1abde13a7eab
From: Tom Zanussi
The hist trigger action code currently implements two essentially
hard-coded pairs of 'actions' - onmax(), which tracks a variable and
saves some event fields when a max is hit, and onmatch(), which is
hard-coded to generate a synthetic event.
These hardcoded pairs (track
On Thu 2018-11-29 11:11:50, Linus Torvalds wrote:
> On Thu, Nov 29, 2018 at 11:08 AM Linus Torvalds
> wrote:
> >
> > What you can do then is basically add a single-byte prefix to the
> > "call" instruction that does nothing (say, cs override), and then
> > replace *that* with a 'int3'
Hi,
On Mon, Nov 12, 2018 at 12:02 AM Bjorn Andersson
wrote:
> + aoss_qmp: qmp@c30 {
> + compatible = "qcom,sdm845-aoss-qmp";
> + reg = <0x0c30 0x10>;
drive-by nit: s/0x0c30/0xc30
...another random suggestion is that I think Rob H. has been
requesting that
Hi!
> These patches are related to two similar patch sets from Ard and Steve:
>
> - https://lkml.kernel.org/r/20181005081333.15018-1-ard.biesheu...@linaro.org
> - https://lkml.kernel.org/r/20181006015110.653946...@goodmis.org
>
> The code is also heavily inspired by the jump label code, as some
Clang warns:
drivers/scsi/pcmcia/nsp_cs.c:1137:27: warning: equality comparison with
extraneous parentheses [-Wparentheses-equality]
if ((tmpSC->SCp.Message == MSG_COMMAND_COMPLETE)) {
~~~^~~
On Fri, Dec 07, 2018 at 05:25:17PM +, Will Deacon wrote:
> On Thu, Dec 06, 2018 at 04:47:17PM +, Andrew Murray wrote:
> > Many PMU drivers do not have the capability to exclude counting events
> > that occur in specific contexts such as idle, kernel, guest, etc. These
> > drivers indicate
Clang warns:
drivers/scsi/nsp32.c:2444:14: warning: explicitly assigning value of
variable of type 'unsigned char' to itself [-Wself-assign]
offset = offset;
~~ ^
Signed-off-by: Nathan Chancellor
---
drivers/scsi/nsp32.c | 1 -
1 file changed, 1 deletion(-)
diff
Clang warns when one enumerated type is implicitly converted to another:
drivers/crypto/ux500/hash/hash_core.c:169:4: warning: implicit
conversion from enumeration type 'enum dma_data_direction' to different
enumeration type 'enum dma_transfer_direction' [-Wenum-conversion]
Clang warns when one enumerated type is implicitly converted to another:
drivers/crypto/ux500/cryp/cryp_core.c:559:5: warning: implicit
conversion from enumeration type 'enum dma_data_direction' to different
enumeration type 'enum dma_transfer_direction' [-Wenum-conversion]
* Nishanth Menon [181210 12:07]:
> I really am curious how Arnd / Tony actually pull this one off.. If they
> have continous cron job for checking if your patch is ready... I doubt
> it..
The only way that works in a distributed manner is for the patch
authors to resend after the dependencies
When building an allyesconfig build with Clang, the kernel fails to link
arch/x86/platform/efi/efi_64.o because of a failed BUILD_BUG_ON:
ld: arch/x86/platform/efi/efi_64.o: in function `efi_sync_low_kernel_mappings':
(.text+0x8e5): undefined reference to `__compiletime_assert_277'
Since there
Hi Maciej,
On Mon, Dec 10, 2018 at 11:32:46PM +, Maciej W. Rozycki wrote:
> On Mon, 10 Dec 2018, Paul Burton wrote:
>
> > And I realise that undoing that but keeping n64 in our own filenames &
> > macros is another type of inconsistency, but something imperfect is
> > unavoidable at this
Hi!
> Documentation/admin-guide/kernel-parameters.txt | 56 ++
> Documentation/userspace-api/spec_ctrl.rst |9
Could we name this speculation.rst instead? _ is inconsistent, and
spec could be shorthand for other stuff, too...
This patchset implements bpffs pretty printing for cgroup local storage maps.
v2->v1:
- fixed size checks in cgroup_storage_check_btf(),
based on input from Yonghong and Martin
- implemented and used btf_type_is_reg_int(), suggested by Martin
Roman Gushchin (3):
bpf: pass struct btf
If key_type or value_type are of non-trivial data types
(e.g. structure or typedef), it's not possible to check them without
the additional information, which can't be obtained without a pointer
to the btf structure.
So, let's pass btf pointer to the map_check_btf() callbacks.
Signed-off-by:
Implement bpffs pretty printing for cgroup local storage maps
(both shared and per-cpu).
Output example (captured for tools/testing/selftests/bpf/netcnt_prog.c):
Shared:
$ cat /sys/fs/bpf/map_2
# WARNING!! The output is for debug purpose only
# WARNING!! The output format will change
Add btf annotations to cgroup local storage maps (per-cpu and shared)
in the network packet counting example.
Signed-off-by: Roman Gushchin
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
---
tools/testing/selftests/bpf/netcnt_prog.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
Clang warns when an expression that equals zero is used as a null
pointer constant (in lieu of NULL):
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4435:3:
warning: expression which evaluates to zero treated as a null pointer
constant of type 'const enum color_transfer_func *'
It seems that your patch is addressing the same bug. I will see if
that works for our failure scenarios.
Why don't you make it upstream?
On Sun, Dec 9, 2018 at 6:22 AM Nitzan Carmi wrote:
>
> Hi,
> We encountered similar issue.
> I think that the problem is that error_recovery might not even be
Without this, cpumask_t and bool are not defined:
In file included from drivers/media/pci/ddbridge/ddbridge-ci.c:19:
In file included from drivers/media/pci/ddbridge/ddbridge.h:22:
./arch/arm/include/asm/irq.h:35:50: error: unknown type name 'cpumask_t'
extern void
On 03/12/2018 12:47:36+0100, Lubomir Rintel wrote:
> The example should follow the practice or using a generic node name
> instead of the precise programming model, as recommended by the DTSpec.
>
> Signed-off-by: Lubomir Rintel
> ---
> Documentation/devicetree/bindings/rtc/rtc-ds1307.txt | 2
On Mon, Dec 10, 2018 at 03:25:04PM -0800, Alexander Duyck wrote:
> On Mon, 2018-12-10 at 11:22 -0800, Luis Chamberlain wrote:
> > On Wed, Dec 05, 2018 at 09:25:13AM -0800, Alexander Duyck wrote:
> > > This patch set provides functionality that will help to improve the
> > > locality of the
On 12/10/18 9:39 AM, Carlos O'Donell wrote:
> On 12/10/18 11:27 AM, Jonathan Corbet wrote:
>> On Sat, 8 Dec 2018 20:38:56 -0800
>> Randy Dunlap wrote:
>>
>>> On 11/12/18 8:08 AM, Jonathan Corbet wrote:
On Sun, 11 Nov 2018 18:36:30 -0800
Greg KH wrote:
> We should have a
On Tue, Dec 11, 2018 at 10:18:31AM +1100, Oliver wrote:
> On Tue, Dec 11, 2018 at 8:52 AM Arnd Bergmann wrote:
> >
> > For this use case, completions and semaphores are equivalent,
> > but semaphores are an awkward interface that should generally
> > be avoided, so use the completion instead.
>
From: Colin Ian King
Variable 'status' is declared but not used, remove it.
Cleans up warning:
warning: unused variable ‘status’ [-Wunused-variable]
Signed-off-by: Colin Ian King
---
drivers/scsi/qla2xxx/qla_os.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, 10 Dec 2018, Paul Burton wrote:
> And I realise that undoing that but keeping n64 in our own filenames &
> macros is another type of inconsistency, but something imperfect is
> unavoidable at this point given that the engineers way back when decided
> to use "ABI64" for n64.
My feeling
Hi Takashi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 40e020c129cfc991e8ab4736d2665351ffd1468d
commit: d99501b8575dc1248bacf1b58d2241cb4b265d49 ALSA: hda/ca0132 - Call
pci_iounmap() instead of iounmap()
date:
On Mon, Dec 10, 2018 at 03:21:37PM -0800, Sean Christopherson wrote:
> At that point I realized it's a hell of a lot easier to simply provide
> an IOCTL via /dev/sgx that allows userspace to register a per-process
> ENCLU exception handler. At a high level, the basic idea is the same
> as the
On Mon, 2018-12-10 at 11:22 -0800, Luis Chamberlain wrote:
> On Wed, Dec 05, 2018 at 09:25:13AM -0800, Alexander Duyck wrote:
> > This patch set provides functionality that will help to improve the
> > locality of the async_schedule calls used to provide deferred
> > initialization.
> >
> > This
Hi all,
Today's linux-next merge of the ubifs tree got a conflict in:
fs/ubifs/Kconfig
between commit:
6956097c429a ("fscrypt: remove filesystem specific build config option")
from the fscrypt tree and commit:
1341551f1e2a ("ubifs: CONFIG_UBIFS_FS_AUTHENTICATION should depend on
On Mon, 10 Dec 2018 17:22:41 +0530, Jagan Teki wrote:
> Allwinner A64 CSI has single channel time-multiplexed BT.656
> CMOS sensor interface like H3 but work by lowering clock than
> default mod clock.
>
> Add a compatible string for it.
>
> Signed-off-by: Jagan Teki
> ---
>
On Mon, Dec 10, 2018 at 07:11:19AM +, Anson Huang wrote:
> According to datasheet, the isl29018 has "vddd/vdda" power
> supply, and isl29023/isl29035 ONLY has "vdd" power supply,
> update the power supply name with "vdd" and "vdda" according
> to datasheet to cover all devices and avoid
On Tue, 2018-12-11 at 02:11 +0300, Darya Litvintseva wrote:
> Signed-off-by: Darya Litvintseva
Hello.
Most maintainers want some patch description
and not a blank commit message.
Whitespace only changes are sometimes not taken.
First kernel patches are best done in drivers/staging.
And some
On Mon, 10 Dec 2018 11:27:39 +1300, Darwin Dingel wrote:
> When a serial port continuously experiences input overrun from
> (1) continuous receive characters from remote and or (2) hardware
> issues, its interrupt handler can preempt other tasks especially
> when the system is busy (ie. boot up
Intel Software Guard Extensions (SGX) SGX introduces a new CPL3-only
enclave mode that runs as a sort of black box shared object that is
hosted by an untrusted normal CPL3 process.
Enclave transitions have semantics that are a lovely blend of SYCALL,
SYSRET and VM-Exit. In a non-faulting
Intel Software Guard Extensions (SGX) introduces a new CPL3-only
"enclave" mode that runs as a sort of black box shared object that is
hosted by an untrusted "normal" CPl3 process.
Entering an enclave can only be done through SGX-specific instructions,
EENTER and ERESUME, and is a non-trivial
Call fixup_sgx_enclu_exception() in all trap flows that generate
signals to userspace immediately prior to generating any such signal.
If the exception is fixed, return cleanly and don't generate a signal.
Cc: Andy Lutomirski
Cc: Jarkko Sakkinen
Cc: Dave Hansen
Cc: Josh Triplett
Call fixup_sgx_enclu_exception() in the SIGSEGV and SIGBUS paths of
the page fault handler immediately prior to signaling. If the fault
is fixed, return cleanly and do not generate a signal.
In the SIGSEGV flow, make sure the error code passed to userspace has
been sanitized.
Cc: Andy
This is effectively v3 of the "x86: Add vDSO exception fixup for SGX"
series, but as you might of noticed, there are no vDSO changes here.
Andy's comment on Spectre/retpoline[1] and Jethro's comment on making
the vDSO as barebones as possible[2] got me wondering if we could let
userspace
From: Colin Ian King
Currently, in the unlikely case when the dyn_event_ops_list list is
empty then ret is never assigned a value and the function will return
with a uninitialized garbage return value from ret. Fix this corner
case by setting ret to zero.
Fixes: 5448d44c3855 ("tracing: Add
On Tue, Dec 11, 2018 at 8:52 AM Arnd Bergmann wrote:
>
> For this use case, completions and semaphores are equivalent,
> but semaphores are an awkward interface that should generally
> be avoided, so use the completion instead.
IIRC Sam has been reworking the locking used inside of EEH so this
On Thu, 6 Dec 2018 14:26:32 -0500, Sven Van Asbroeck wrote:
> The imx-weim driver was patched to allow correct WEIM configuration
> when multiple address ranges are used in a child node.
> Update the dt-bindings to reflect this.
>
> Signed-off-by: Sven Van Asbroeck
> ---
>
On Thu, 6 Dec 2018 13:41:30 +, =?utf-8?B?Vm9rw6HEjSBNaWNoYWw=?= wrote:
> Output of the PWM block on i.MX SoCs is always low when the block is
> disabled. This can cause issues when inverted PWM polarity is needed.
> With inverted polarity a duty cycle = 0% corresponds to high level on
> the
On Tue, 4 Dec 2018 20:17:27 +0100, Miquel Raynal wrote:
> Current file describe COMPHY bindings for the IP available on the
> CP110 of Armada 7k/8k. Bindings are very close (and serve the same
> purpose) as the new Armada 3700 COMPHY driver so update this file to
> describe both. Also add an
Hi all,
Today's linux-next merge of the f2fs tree got a conflict in:
fs/f2fs/dir.c
between commit:
848a010287e6 ("f2fs: use IS_ENCRYPTED() to check encryption status")
from the fscrypt tree and commit:
4e240d1bab1e ("f2fs: check memory boundary by insane namelen")
from the f2fs tree.
On Mon, Dec 10, 2018 at 09:27:04AM +0100, Pavel Machek wrote:
> On Sun 2018-12-09 23:47:17, Josh Triplett wrote:
> > On Sun, Dec 09, 2018 at 09:06:00PM +0100, Pavel Machek wrote:
> > ...
> > > > > > The default permissions for the device are 600.
> > > > >
> > > > > Good. This does not belong to
Signed-off-by: Darya Litvintseva
---
net/ethernet/eth.c | 23 ---
1 file changed, 8 insertions(+), 15 deletions(-)
diff --git a/net/ethernet/eth.c b/net/ethernet/eth.c
index fd8faa0dfa61..3b430e245d58 100644
--- a/net/ethernet/eth.c
+++ b/net/ethernet/eth.c
@@ -90,9 +90,7 @@
On 12/7/2018 8:13 AM, Jeffrey Hugo wrote:
On 12/7/2018 7:23 AM, Marc Gonzalez wrote:
On 06/12/2018 23:11, Jeffrey Hugo wrote:
Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
for clients to vote on.
Signed-off-by: Jeffrey Hugo
---
v2
-fix compatible ordering nits per
On Mon, Dec 10, 2018 at 04:53:01PM +0800, Leo Yan wrote:
> The exception packet appears as one element with 'elem_type' ==
> OCSD_GEN_TRC_ELEM_EXCEPTION or OCSD_GEN_TRC_ELEM_EXCEPTION_RET,
> which present for exception entry and exit respectively. The decoder
> set packet fields 'packet->exc' and
On Mon, Dec 10, 2018 at 04:53:00PM +0800, Leo Yan wrote:
> If decoder outputs EO_TRACE element, it means the end of the trace
> buffer; this is a discontinuity and in this case the end of trace data
> needs to be saved.
>
> This patch generates CS_ETM_DISCONTINUITY packet for EO_TRACE element
>
On Mon, Dec 10, 2018 at 04:25:15PM -0500, Steven Rostedt wrote:
On Mon, 10 Dec 2018 21:09:20 +
Sasha Levin wrote:
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: .
The bot has tested the following trees: v4.19.8,
On Mon, Dec 10, 2018 at 10:16:03PM +0100, Thomas Gleixner wrote:
On Mon, 10 Dec 2018, Sasha Levin wrote:
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.19.8,
On Mon, Dec 10, 2018 at 04:52:59PM +0800, Leo Yan wrote:
> CoreSight tracer driver might insert barrier packet between different
> buffers, thus the decoder can spot the boundaries based on the barrier
> packet; the decoder is possible to hit a barrier packet and emit a
> NO_SYNC element, then the
On Mon, Dec 10, 2018 at 10:36:40PM +0100, Rafael J. Wysocki wrote:
> On Mon, Dec 10, 2018 at 1:21 PM Peter Zijlstra wrote:
> > One question on this; why is this tracked unconditionally?
>
> Because I didn't quite see how to make that conditional in a sensible way.
Something like:
if
Hi Leo,
On Mon, Dec 10, 2018 at 04:52:58PM +0800, Leo Yan wrote:
> TRACE_ON element is used at the beginning of trace, it also can be
> appeared in the middle of trace data to indicate discontinuity; for
> example, it's possible to see multiple TRACE_ON elements in the trace
> stream if the trace
On Mon, Dec 10, 2018 at 04:52:57PM +0800, Leo Yan wrote:
> At the end of trace buffer handling, function cs_etm__flush() is invoked
> to flush any remaining branch stack entries. As a side effect, it also
> generates branch sample, because the 'etmq->packet' doesn't contains any
> new coming
On Fri, Dec 07, 2018 at 07:37:35PM -0800, Yonghong Song wrote:
>
>
> On 12/7/18 4:53 PM, Roman Gushchin wrote:
> > Implement bpffs pretty printing for cgroup local storage maps
> > (both shared and per-cpu).
> > Output example (captured for tools/testing/selftests/bpf/netcnt_prog.c):
> >
> >
From: Rob Herring
Convert Rockchip SoC bindings to DT schema format using json-schema.
Cc: Mark Rutland
Cc: Heiko Stuebner
Cc: devicet...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-rockc...@lists.infradead.org
Signed-off-by: Rob Herring
[move to per-board entries and
On Mon, Dec 10, 2018 at 2:24 PM Alexander Duyck
wrote:
>
> On Mon, 2018-12-10 at 13:23 -0800, Dan Williams wrote:
> > On Mon, Dec 10, 2018 at 1:15 PM Dan Williams
> > wrote:
> > >
> > > On Mon, Dec 10, 2018 at 12:58 PM Alexander Duyck
> > > wrote:
> >
> > [..]
> > > > Also the context for the
Added ADC and other sensor devices in Facebook Tiogapass device tree.
Signed-off-by: Vijay Khemka
---
.../dts/aspeed-bmc-facebook-tiogapass.dts | 33 +--
1 file changed, 31 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed-bmc-facebook-tiogapass.dts
Please ignore this patch as it is duplicate. It is included in list of 2
patches I have sent just before.
On 12/10/18, 12:08 PM, "Vijay Khemka" wrote:
Added kcs device support for lpc BMC.
Signed-off-by: Vijay Khemka
---
arch/arm/boot/dts/aspeed-g5.dtsi | 29
GNU linker's -z common-page-size's default value is based on the target
architecture. arch/sparc/vdso/Makefile sets it to the architecture
default, which is implicit and redundant. Drop it.
Link: https://lkml.kernel.org/r/20181206191231.192355-1-ndesaulni...@google.com
Signed-off-by: Nick
On Sun, Dec 9, 2018 at 2:38 AM Russell King - ARM Linux
wrote:
>
> On Sun, Dec 09, 2018 at 06:28:11PM +0800, kbuild test robot wrote:
> > Hi Ard,
> >
> > I love your patch! Perhaps something to improve:
>
> Hi,
>
> This looks to me like a false warning - how can a patch touching arch
> code
Certain pages that are never mapped to userspace have a type
indicated in the page_type field of their struct pages (e.g. PG_buddy).
page_type overlaps with _mapcount so set the count to 0 and avoid
calling page_mapcount() for these pages.
Signed-off-by: Anthony Yznaga
Acked-by: Matthew Wilcox
On Tue, Dec 04, 2018 at 05:52:48PM +0100, Kamil Konieczny wrote:
> Add imem clocks for exynos5433. This will enable to use crypto Security
> SubSystem (in short SSS) and SlimSSS IP blocks.
>
> Signed-off-by: Kamil Konieczny
> ---
> drivers/clk/samsung/clk-exynos5433.c | 193
rdt_find_domain() returns an ERR_PTR() that is generated from a provided
domain id when the value is negative.
Care needs to be taken when creating an ERR_PTR() from this value because
a subsequent check using IS_ERR() expects the error to be within the
MAX_ERRNO range. By using an invalid domain
GNU linker's -z common-page-size's default value is based on the target
architecture. arch/arm/vdso/Makefile sets it to the architecture
default, which is implicit and redundant. Drop it.
Link: https://lkml.kernel.org/r/20181206191231.192355-1-ndesaulni...@google.com
Signed-off-by: Nick
On Tue, 4 Dec 2018 09:52:28 +, wrote:
> This patch describes the compatible and the device tree
> bindings necessary for the MCP16502 PMIC.
>
> Signed-off-by: Andrei Stefanescu
> ---
> .../bindings/regulator/mcp16502-regulator.txt | 143
> +
> 1 file changed, 143
GNU linker's -z common-page-size's default value is based on the target
architecture. arch/x86/entry/vdso/Makefile sets it to the architecture
default, which is implicit and redundant. Drop it.
Link: https://lkml.kernel.org/r/20181206191231.192355-1-ndesaulni...@google.com
Signed-off-by: Nick
On Mon, 3 Dec 2018 18:35:02 +0800, Xiaowei Bao wrote:
> Add the documentation for the Device Tree binding for the layerscape PCIe
> controller with EP mode.
>
> Signed-off-by: Xiaowei Bao
> ---
> v2:
> - Add the SoC specific compatibles.
> v3:
> - modify the commit message.
>
>
The Video Engine (VE) embedded in the Aspeed AST2400 and AST2500 SOCs
can capture and compress video data from digital or analog sources. With
the Aspeed chip acting a service processor, the Video Engine can capture
the host processor graphics output.
Add a V4L2 driver to capture video data and
From: Eddie James
The Video Engine (VE) embedded in the Aspeed AST2400 and AST2500 SOCs
can capture and compress video data from digital or analog sources. With
the Aspeed chip acting as a service processor, the Video Engine can
capture the host processor graphics output.
This series adds a
Document the bindings.
Signed-off-by: Eddie James
Reviewed-by: Rob Herring
---
.../devicetree/bindings/media/aspeed-video.txt | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/aspeed-video.txt
diff --git
On Mon, Dec 10, 2018 at 2:11 PM Enric Balletbo Serra
wrote:
>
> Missatge de Guenter Roeck del dia dl., 10 de des.
> 2018 a les 22:50:
> >
> > On Mon, Dec 10, 2018 at 1:27 PM Enric Balletbo Serra
> > wrote:
> > >
> > > Missatge de Guenter Roeck del dia dl., 10 de des.
> > > 2018 a les 19:34:
>
201 - 300 of 1203 matches
Mail list logo
