On Tue, 15 Jan 2019 at 09:49, Jae Hyun Yoo wrote:
> >> + /**
> >> +* We check that the regmap works on this very first access,
> >> +* but as this is an MMIO-backed regmap, subsequent regmap
> >> +* access is not going to fail and we skip error checks from
> >> +
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo entry[];
};
instance =
On Tue, Jan 15, 2019 at 05:58:34PM +0800, Kairui Song wrote:
> When efi=noruntime or efi=oldmap is used, EFI services won't be available
> in the second kernel, therefore the second kernel will not be able to get
> the ACPI RSDP address from firmware by calling EFI services and won't
> boot.
We are already checking in phy_detach() that the PHY driver is of
generic kind (1G or 10G) and we are going to make use of that in the SFP
layer as well for 1000BaseT SFP modules, so expose helper functions to
return that information.
Signed-off-by: Florian Fainelli
---
This patch uses the information conveyed by perf_event::attr::config2
to select a sink to use for the session. That way a sink can easily be
selected to be used by more than one source, something that isn't currently
possible with the sysfs implementation.
Signed-off-by: Mathieu Poirier
---
The communication of sink information for a trace session doesn't work when
more than on CPU is involved in the scenario due to the static nature of
sysfs. As such communicate the sink information to each event by using the
perf_event::attr:config2 attribute. The information sent to the kernel
From: linaro
Moving definition of EVENT_SOURCE_DEVICE_PATH to pmu.h so that it can be
used by other files than pmu.c
Signed-off-by: linaro
---
tools/perf/util/pmu.c | 2 --
tools/perf/util/pmu.h | 1 +
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/perf/util/pmu.c
Add a "sinks" directory entry so that users can see all the sinks
available in the system in a single place. Individual sink are added
as they are registered with the coresight bus.
Signed-off-by: Mathieu Poirier
---
.../hwtracing/coresight/coresight-etm-perf.c | 43 +++
When pmu::setup_aux() is called the coresight PMU needs to know which
sink to use for the session by looking up the information in the
event's attr::config2 field.
As such simply replace the cpu information by the complete perf_event
structure and change all affected customers.
Signed-off-by:
On Tuesday, January 15, 2019 11:43:05 PM CET Stephen Rothwell wrote:
> Hi Rafael,
>
> On Tue, 15 Jan 2019 23:13:16 +0100 "Rafael J. Wysocki"
> wrote:
> >
> > On Tuesday, January 15, 2019 9:55:40 PM CET Stephen Rothwell wrote:
> > > [I am experimenting with checking the Fixes tags in commits in
Now that event's config2 attribute is used to communicate sink selection
to the kernel, remove the old set_drv_config() implementation since it
is no longer needed.
Signed-off-by: Mathieu Poirier
---
tools/perf/arch/arm/util/cs-etm.c | 54 ---
CoreSight was the only client of the PMU's set_drv_config() API. Now
that it is no longer needed by CoreSight remove it from the code base.
Signed-off-by: Mathieu Poirier
---
tools/perf/builtin-record.c | 10 -
tools/perf/builtin-stat.c | 9
tools/perf/builtin-top.c | 13
From: "Mathieu Poirier]"
This set is a refurbished version of this one [1]. I dropped the version
count and changed the name because a new approach is taken.
The end result is the same though, that is to allow multiple sources to
select the same sink for a session which is a prerequisite for
b53 and mv88e6xxx support passing platform_data, and now that we have
split the platform_data portion from the main net/dsa.h header file,
include only the relevant parts.
Signed-off-by: Florian Fainelli
---
include/linux/platform_data/b53.h | 2 +-
include/linux/platform_data/mv88e6xxx.h
Now that we have split the DSA platform data structures from the main
net/dsa.h header file, include only the relevant header file.
Signed-off-by: Florian Fainelli
---
arch/arm/mach-orion5x/common.c | 2 +-
arch/arm/mach-orion5x/rd88f5181l-fxo-setup.c | 2 +-
Hi all,
This patch series decouples the DSA platform data structures from
net/dsa.h which was getting used for all sorts of DSA related
structures.
It would probably make sense for this series to go via David's net-next
tree to avoid conflicts on the ARM part, since we cannot obviously
include a
Instead of having net/dsa.h contain both the internal switch tree/driver
structures, split the relevant platform_data parts into
include/linux/platform_data/dsa.h and make that header be included by
net/dsa.h in order not to break any setup. A subsequent set of patches
will update code including
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct foo {
int stuff;
void *entry[];
};
instance = kzalloc(sizeof(struct
On 1/15/19 4:54 PM, Jason Gunthorpe wrote:
> On Tue, Jan 15, 2019 at 12:00:48AM -0600, Gustavo A. R. Silva wrote:
>> Replace kzalloc() function with its 2-factor argument form, kcalloc().
>>
>> This patch replaces cases of:
>>
>> kzalloc(a * b, gfp)
>>
>> with:
>> kcalloc(a, b, gfp)
Using the batch API from the interconnect driver sometimes leads to a
KASAN error due to an access to freed memory. This is easier to trigger
with threadirqs on the kernel commandline.
BUG: KASAN: use-after-free in rpmh_tx_done+0x114/0x12c
Read of size 1 at addr fff51414ad84 by task
On Tue, Jan 15, 2019 at 12:00:48AM -0600, Gustavo A. R. Silva wrote:
> Replace kzalloc() function with its 2-factor argument form, kcalloc().
>
> This patch replaces cases of:
>
> kzalloc(a * b, gfp)
>
> with:
> kcalloc(a, b, gfp)
>
> This code was detected with the help of
Dan Williams writes:
> Changes since v2 [1]:
> * Don't allow ND_CMD_CALL to bypass dsm_mask restrictions (Jeff)
>
> [1]: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019498.html
>
> ---
>
> One last resend to make sure all the last bits of thrash have settled.
LGTM.
Thanks!
Jeff
On Tue, Jan 15, 2019 at 05:37:07PM +0100, Federico Vaga wrote:
> Hi there,
>
> I just want to ask if there has been any update about this patchset that I'm
> not aware off. Thanks
I don't think so. Peter, what is the status of this series?
signature.asc
Description: PGP signature
On Tue, Oct 30, 2018 at 02:09:11PM -0700, Jae Hyun Yoo wrote:
> In multi-master environment, this driver's master cannot know
> exactly when a peer master sends data to this driver's slave so a
> case can be happened that this master tries to send data through
> the master_xfer function but slave
The _DSM function number validation only happens to succeed when the
generic Linux command number translation corresponds with a
DSM-family-specific function number. This breaks NVDIMM-N
implementations that correctly implement _LSR, _LSW, and _LSI, but do
not happen to publish support for DSM
Changes since v2 [1]:
* Don't allow ND_CMD_CALL to bypass dsm_mask restrictions (Jeff)
[1]: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019498.html
---
One last resend to make sure all the last bits of thrash have settled.
Quote patch2 changelog:
The _DSM function number
In preparation for using function number 0 as an error value, prevent it
from being considered a valid function value by acpi_nfit_ctl().
Cc:
Cc: stuart hayes
Fixes: e02fb7264d8a ("nfit: add Microsoft NVDIMM DSM command set...")
Reported-by: Jeff Moyer
Reviewed-by: Jeff Moyer
Signed-off-by:
Hi Sinan,
On Tue, 15 Jan 2019 16:10:07 -0500 Sinan Kaya wrote:
>
> Interesting, can you add this to the checkpatch.pl script so that it doesn't
> happen again?
Probably a good idea ... (cc'ing Paul G :-))
--
Cheers,
Stephen Rothwell
pgpEWRXRehsRY.pgp
Description: OpenPGP digital signature
There is not currently way to infer the port number through sysfs that
is being used as the CPU port number. Overlay a ndo_get_phys_port_name()
operation onto the DSA master network device in order to retrieve that
information.
Signed-off-by: Florian Fainelli
---
include/net/dsa.h | 5 +
> All errors (new ones prefixed by >>):
>
> >> ERROR: "at91_init_twi_bus_slave" [drivers/i2c/busses/i2c-at91.ko]
> >> undefined!
> >> ERROR: "at91_twi_probe_slave" [drivers/i2c/busses/i2c-at91.ko] undefined!
That needs to be fixed. Rest looks good to me!
signature.asc
Description: PGP
Hi Rafael,
On Tue, 15 Jan 2019 23:13:16 +0100 "Rafael J. Wysocki"
wrote:
>
> On Tuesday, January 15, 2019 9:55:40 PM CET Stephen Rothwell wrote:
> > [I am experimenting with checking the Fixes tags in commits in linux-next.
> > Please let me know if you think I am being too strict.]
> >
> > Hi
On 1/14/2019 5:15 PM, Kees Cook wrote:
On Sat, Jan 12, 2019 at 7:29 AM Willy Tarreau wrote:
From: Silvio Cesare
Change snprintf to scnprintf. There are generally two cases where using
snprintf causes problems.
1) Uses of size += snprintf(buf, SIZE - size, fmt, ...)
In this case, if
On Tue, Jan 15, 2019 at 11:06:17AM -0800, Sean Christopherson wrote:
> > I can see there are five options to solve it.
> >
> > 1) always inline vmx_vcpu_run()
> > 2) always noinline vmx_vcpu_run()
> > 3) add -fdiable-ipa-fnsplit option to Makefile for vmx.o
> > 4) let STACK_FRAME_NON_STANDARD
On 13.01.2019 17:14, Russell King - ARM Linux wrote:
> On Sun, Jan 13, 2019 at 04:41:52PM +0100, Stefan Agner wrote:
>> Hi,
>>
>> On 12.01.2019 02:01, Jeremy Fertic wrote:
>> > I'm having a problem with the ftrace function graph tracer on a 32 bit arm
>> > board (orangepi pc). A bisect points to
On Tue, Jan 15, 2019 at 1:29 PM David Miller wrote:
>
> From: Arnd Bergmann
> Date: Tue, 15 Jan 2019 22:19:27 +0100
>
> > The correct check appears to be
> >
> > #if defined(__sparc__) && defined(__arch64__)
>
> That is correct.
OK. Deepa, could you please send me a fixup as I already pushed
Greetings
My name is Miss Alizata Aron. It give me a great pleasure to write you, it
attracts me to write to you so that we can be friends if you will have the
desire as me. i will be very happy to be in communication with you so that we
can get to know each other better and see what
We report a bug in linux-4.20.2: "UBSAN: Undefined behaviour in
fs/f2fs/extent_cache.c"
kernel config: https://kt0755.github.io/etc/config_v4.20_stable
repro: https://kt0755.github.io/etc/repro.4a3e7.c (f2fs is mounted on
/mnt/f2fs/)
This arose in f2fs_update_extent_tree_range
Hi Gustavo,
On Mon, 14 Jan 2019 14:35:07 -0600 "Gustavo A. R. Silva"
wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts
(2018-12-05 16:12:32 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20190115
for you to fetch changes up to 5b0e7310a2a33c06edc7eb81ffc521af9b2c5610:
selinux: fix GPF on invalid policy (2019-01-10 20:23:05
[-cc stable]
On Mon, Jan 14, 2019 at 11:07:27PM -0500, Michael S. Tsirkin wrote:
> On Thu, Dec 20, 2018 at 05:36:03PM -0500, Michael S. Tsirkin wrote:
> > On Thu, Dec 20, 2018 at 04:31:58PM -0600, Bjorn Helgaas wrote:
> > > On Thu, Dec 20, 2018 at 04:26:54PM -0500, Michael S. Tsirkin wrote:
> > >
Hi!
> >+The 24-bit RGB value passed in follows the pattern 0xXXRRGGBB
> >+XX - Do not care ignored by the driver
> >+RR - is the 8 bit Red LED value
> >+GG - is the 8 bit Green LED value
> >+BB - is the 8 bit Blue LED value
> >+
> >+Example:
> >+LED module output 4 of the LP5024 will be a yellow
Hi Rob.
> > +
> > +Optional property:
> > +- quartz-load-femtofarads: The capacitive load of the quartz(x-tal),
>
> Probably should put this in rtc.txt so it can be shared.
Good point - will do and respin the patchset.
>
> > + expressed in femto Farad (fF). Valid values are 7000 and 12500.
>
On 1/15/19 3:49 PM, Chuck Lever wrote:
On Jan 15, 2019, at 4:11 PM, Gustavo A. R. Silva wrote:
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that
On Tuesday, January 15, 2019 9:55:40 PM CET Stephen Rothwell wrote:
> [I am experimenting with checking the Fixes tags in commits in linux-next.
> Please let me know if you think I am being too strict.]
>
> Hi Rafael,
>
> Commits
>
> 62b33d57c534 ("drivers: thermal: int340x_thermal: Make PCI
Hi Eugen.
Patch looks good, but a small improvement proposal.
On Mon, Jan 14, 2019 at 09:43:31AM +, eugen.hris...@microchip.com wrote:
> From: Eugen Hristev
>
> PDA 91-00156-A0 5.0 is a 5.0" WVGA TFT LCD panel.
> This panel with backlight is found in PDA 5" LCD screen (TM5000 series or
>
On Tue, 15 Jan 2019 22:41:21 +0100,
Chuck Lever wrote:
>
> Hi Stephen-
>
> On Jan 15, 2019, at 4:38 PM, Stephen Rothwell wrote:
>
> > [I am experimenting with checking the Fixes tags in commits in linux-next.
> > Please let me know if you think I am being too strict.]
> >
> > Hi all,
> >
> >
On Tue, Jan 15, 2019 at 01:56:51PM -0800, John Hubbard wrote:
> On 1/15/19 9:15 AM, Jerome Glisse wrote:
> > On Tue, Jan 15, 2019 at 09:07:59AM +0100, Jan Kara wrote:
> >> On Mon 14-01-19 12:21:25, Jerome Glisse wrote:
> >>> On Mon, Jan 14, 2019 at 03:54:47PM +0100, Jan Kara wrote:
> On Fri
Hi,
On Mon, Jan 14, 2019 at 1:19 PM Bjorn Andersson
wrote:
>
> DMA memory allocations for devices on the soc bus must be constrained to
> the 36 address bits that the bus provides, which without IOMMU is taken
> care of by the addresses being direct physical allocations.
The above confuses me
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
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
Hi,
This is v12 of the hist trigger snapshot and onchange additions
patchset.
It addresses some comments from Namhyung regarding the 'tracing: Add
alternative synthetic event trace action syntax' patch to remove
parens and change the documentation to emphasize the trace()
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 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 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
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
Add a test case verifying the basic functionality of the
hist:snapshot() action.
Signed-off-by: Tom Zanussi
Acked-by: Masami Hiramatsu
---
.../inter-event/trigger-snapshot-action-hist.tc| 43 ++
1 file changed, 43 insertions(+)
create mode 100644
Hi Eugen.
On Mon, Jan 14, 2019 at 09:43:26AM +, eugen.hris...@microchip.com wrote:
> From: Eugen Hristev
>
> Precision Design Associates, Inc. (PDA) manufactures standard and custom
> capacitive touch screens, LCD's embedded controllers and custom embedded
> software. They specialize in
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
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 verifying the basic functionality of the
hist:onchange($var) handler.
Signed-off-by: Tom Zanussi
Acked-by: Masami Hiramatsu
---
.../inter-event/trigger-onchange-action-hist.tc| 28 ++
1 file changed, 28 insertions(+)
create mode
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
Since we now have a str_has_prefix() that returns the length, we can
use that instead of explicitly calculating it.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
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
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
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
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
One of the more common cases of allocation size calculations is finding the
size of a structure that has a zero-sized array at the end, along with memory
for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo entry[];
};
instance =
On Tue, Jan 15, 2019 at 09:48:01AM +0800, Wei Hu (Xavier) wrote:
>
>
> On 2019/1/15 6:06, Jason Gunthorpe wrote:
> > On Sat, Jan 12, 2019 at 03:55:31PM +0800, Wei Hu (Xavier) wrote:
> >>
> >> On 2019/1/12 5:34, Jason Gunthorpe wrote:
> >>> On Thu, Jan 10, 2019 at 09:57:41PM +0800, Wei Hu
Hello,
On Fri, Jan 11, 2019 at 01:52:44PM +0530, Yash Shah wrote:
> Adds a PWM driver for PWM chip present in SiFive's HiFive Unleashed SoC.
>
> Signed-off-by: Wesley W. Terpstra
> [Atish: Various fixes and code cleanup]
> Signed-off-by: Atish Patra
> Signed-off-by: Yash Shah
> ---
>
On Wed, Jan 9, 2019 at 10:30 AM Steve Longerbeam wrote:
>
> Also add an example pipeline for unconverted capture with interweave
> on SabreAuto.
>
> Cleanup some language in various places in the process.
>
> Signed-off-by: Steve Longerbeam
> Reviewed-by: Philipp Zabel
> ---
> Changes since v4:
On 1/15/19 9:15 AM, Jerome Glisse wrote:
> On Tue, Jan 15, 2019 at 09:07:59AM +0100, Jan Kara wrote:
>> On Mon 14-01-19 12:21:25, Jerome Glisse wrote:
>>> On Mon, Jan 14, 2019 at 03:54:47PM +0100, Jan Kara wrote:
On Fri 11-01-19 19:06:08, John Hubbard wrote:
> On 1/11/19 6:46 PM, Jerome
Hi Alex,
On 1/15/19 12:04 AM, Alex Williamson wrote:
> On Mon, 14 Jan 2019 21:48:06 +0100
> Auger Eric wrote:
>
>> Hi Alex,
>>
>> On 1/12/19 12:58 AM, Alex Williamson wrote:
>>> On Tue, 8 Jan 2019 11:26:30 +0100
>>> Eric Auger wrote:
>>>
This patch adds a new 64kB region aiming to
Hi,
On Tue, Jan 15, 2019 at 04:03:32PM +0200, Laurentiu Tudor wrote:
> If the dma controller is not yet probed, defer i2c probe.
> The error path in probe was slightly modified (no functional change)
> to avoid triggering this WARN_ON():
> "cg-pll0-div1 already disabled
> WARNING: CPU: 1 PID: 1
On some architectures, it is possible to have nested NMIs taking
spinlocks nestedly. Even though the chance of having more than 4 nested
spinlocks with contention is extremely small, there could still be a
possibility that it may happen some days leading to system panic.
What we don't want is a
The addresses within a single page are always contiguous, so it's
not so necessary to allocate one single page from CMA area. Since
the CMA area has a limited predefined size of space, it might run
out of space in some heavy use case, where there might be quite a
lot CMA pages being allocated for
On Jan 15, 2019, at 4:11 PM, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
>
Hi Da,
Thank you for the v2.
I have some remarks below.
On 1/14/19 10:17 PM, Dan Murphy wrote:
Introduce the LP5036/30/24/18 RGB LED driver.
The difference in these parts are the number of
LED outputs where the:
LP5036 can control 36 LEDs
LP5030 can control 30 LEDs
LP5024 can control 24 LEDs
On Tue, Jan 15, 2019 at 09:41:38PM +, Mark Brown wrote:
> On Tue, Jan 15, 2019 at 03:16:57PM -0600, Pierre-Louis Bossart wrote:
>
> > > Maybe the defer card probe logic needs to be extended to also check if
> > > dai_link_name had already been registered (either cpu or cpu_dai_name
> > >
One of the more common cases of allocation size calculations is finding the
size of a structure that has a zero-sized array at the end, along with memory
for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo entry[];
};
instance =
Hi Dan,
Thank you for the patch.
Seeing the mess with regs and led-modules I think
it will be better to abide by the regs alone.
Please see below how I would structure that.
On 1/14/19 10:17 PM, Dan Murphy wrote:
Introduce the bindings for the Texas Instruments LP5036, LP5030, LP5024 and the
On Tue, Jan 15, 2019 at 03:16:57PM -0600, Pierre-Louis Bossart wrote:
> > Maybe the defer card probe logic needs to be extended to also check if
> > dai_link_name had already been registered (either cpu or cpu_dai_name
> > needs to be set), not 100% sure which problem the defer card probe patch
>
Hi Stephen-
On Jan 15, 2019, at 4:38 PM, Stephen Rothwell wrote:
> [I am experimenting with checking the Fixes tags in commits in linux-next.
> Please let me know if you think I am being too strict.]
>
> Hi all,
>
> Commit
>
> deaa5c96c2f7 ("SUNRPC: Address Kerberos performance/behavior
On Fri, 11 Jan 2019 06:22:40 +, Anson Huang wrote:
> Add i.MX7ULP system integration module (SIM) binding.
>
> Signed-off-by: Anson Huang
> ---
> .../bindings/arm/freescale/fsl,imx7ulp-sim.txt | 16
>
> 1 file changed, 16 insertions(+)
> create mode 100644
>
On 1/15/19 4:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 786e1048e7f4 ("pvcalls-front: fix potential null dereference")
>
> has a malformed Fixes tag:
>
> Fixes: 9f51c05dc41a ("pvcalls-front: Avoid get_free_pages(GFP_KERNEL)
> under spinlock")
>
> It should not be split over 2
On 1/15/19 12:34 AM, Jan Kara wrote:
> On Mon 14-01-19 11:09:20, John Hubbard wrote:
>> On 1/14/19 9:21 AM, Jerome Glisse wrote:
[...]
>
>> For example, the following already survives a basic boot to graphics mode.
>> It requires a bunch of callsite conversions, and a page flag (neither of
On Tue, 15 Jan 2019 22:37:01 +0200
"Joel Nider" wrote:
> Jonathan Corbet wrote on 01/15/2019 08:08:54 PM:
> > The intent behind the user-space API manual is to document the user-space
> > API; it's meant to be read by people writing applications and such.
> > Perhaps they find it with a web
[I am experimenting with checking the Fixes tags in commits in linux-next.
Please let me know if you think I am being too strict.]
Hi all,
Commit
deaa5c96c2f7 ("SUNRPC: Address Kerberos performance/behavior regression")
has problem with this Fixes tag:
Fixes: 918f3c1fe83c ("SUNRPC:
One of the more common cases of allocation size calculations is finding the
size of a structure that has a zero-sized array at the end, along with memory
for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo entry[];
};
instance =
On Thu, 10 Jan 2019 17:04:29 +0200, Roger Quadros wrote:
> The AM654 SoC from TI contains a DWC3 controller. Add
> support for it.
>
> Signed-off-by: Roger Quadros
> ---
> Documentation/devicetree/bindings/usb/keystone-usb.txt | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
Hi Alex,
On 1/11/19 11:50 PM, Alex Williamson wrote:
> On Tue, 8 Jan 2019 11:26:16 +0100
> Eric Auger wrote:
>
>> From: "Liu, Yi L"
>>
>> This patch adds VFIO_IOMMU_SET_PASID_TABLE ioctl which aims at
>> passing the virtual iommu guest configuration to the VFIO driver
>> downto to the iommu
[I am experimenting with checking the Fixes tags in commits in linux-next.
Please let me know if you think I am being too strict.]
Hi all,
Commit
b488517b28a4 ("clk: socfpga: stratix10: fix naming convention for the
fixed-clocks")
has a malformed Fixes tag:
Fixes: 07afb8db7340 ("clk:
On Wed, 9 Jan 2019 18:43:42 +0200, Tomer Maimon wrote:
> Added device tree binding documentation for Nuvoton BMC
> NPCM Analog-to-Digital Converter(ADC).
>
> Signed-off-by: Tomer Maimon
> ---
> .../bindings/iio/adc/nuvoton,npcm-adc.txt | 35
> ++
> 1 file changed,
From: Arnd Bergmann
Date: Tue, 15 Jan 2019 22:19:27 +0100
> The correct check appears to be
>
> #if defined(__sparc__) && defined(__arch64__)
That is correct.
Hi Jean,
On 1/11/19 12:06 PM, Jean-Philippe Brucker wrote:
> On 10/01/2019 18:45, Jacob Pan wrote:
>> On Tue, 8 Jan 2019 11:26:26 +0100
>> Eric Auger wrote:
>>
>>> From: Jacob Pan
>>>
>>> Device faults detected by IOMMU can be reported outside IOMMU
>>> subsystem for further processing. This
On 12/16/2018 02:37 PM, Linus Torvalds wrote:
> On Fri, Dec 14, 2018 at 1:53 PM Waiman Long wrote:
>> This patchset addresses 2 issues found in the dentry code and adds a
>> new nr_dentry_negative per-cpu counter to track the total number of
>> negative dentries in all the LRU lists.
> The series
[ 300.403269] [ cut here ]
[ 300.403271] CPA: called for zero pte. vaddr = 0 cpa->vaddr = 0
[ 300.403281] WARNING: CPU: 0 PID: 33 at arch/x86/mm/pageattr.c:1466
__cpa_process_fault+0x365/0x390
[ 300.403282] Modules linked in: cmac cifs fscache snd_seq_dummy
snd_seq_oss
On Tue, Jan 15, 2019 at 09:58:55PM +0100, Martin Sperl wrote:
> Maybe a bigger change to the reduce the complexity of
> the state machine would solve that problem and also
> reduce code complexity...
Yeah, that's where I was getting to with that test patch I posted.
> I may find some time over
On Tue, Jan 15, 2019 at 02:17:26PM +, Thomas Hellstrom wrote:
> Hi, Christoph,
>
> On Mon, 2019-01-14 at 10:48 +0100, Christoph Hellwig wrote:
> > On Thu, Jan 10, 2019 at 04:42:18PM -0700, Jason Gunthorpe wrote:
> > > > Changes since the RFC:
> > > > - Rework vmwgfx too [CH]
> > > > - Use a
On Tue, Jan 15, 2019 at 5:36 PM Geert Uytterhoeven wrote:
> On Tue, Jan 15, 2019 at 4:19 PM Arnd Bergmann wrote:
> > On Tue, Jan 15, 2019 at 4:01 PM Arnd Bergmann wrote:
> > > On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman
> > > wrote:
> > > > Arnd Bergmann writes:
> > > > >
Hi,
On 01/15/2019 01:50 PM, Stefan Wahren wrote:
Hi Jeremy,
Jeremy Linton hat am 10. Januar 2019 um 00:55
geschrieben:
Arm64 machines should be displaying a human readable
vulnerability status to speculative execution attacks in
/sys/devices/system/cpu/vulnerabilities
This series enables
201 - 300 of 1184 matches
Mail list logo
