From: Rajan Vaja
Add Xilinx ZynqMP firmware APIs to set suspend mode
and inform firmware that master has initialized its
own power management.
Signed-off-by: Rajan Vaja
Signed-off-by: Jolly Shah
---
drivers/firmware/xilinx/zynqmp.c | 29 +
include/linux/firmwar
From: Rajan Vaja
Add ZynqMP PM driver. PM driver provides power management
support for ZynqMP.
Signed-off-by: Rajan Vaja
Signed-off-by: Jolly Shah
---
drivers/soc/xilinx/Kconfig| 11 +++
drivers/soc/xilinx/Makefile | 1 +
drivers/soc/xilinx/zynqmp_power.c | 178 ++
Add ZynqMP PM driver. PM driver provides power management
support for ZynqMP.
v5:
- Added Reviewed tag for dt bindings
v4:
- Minor fixes to address v3 review comments
v3:
- Updated DT bindings as per v2 review comments
v2:
- Rebased on top of latest firmware driver patch series
- Updated
From: Rajan Vaja
Add documentation to describe Xilinx ZynqMP power management
bindings.
Signed-off-by: Rajan Vaja
Signed-off-by: Jolly Shah
Reviewed-by: Rob Herring
---
.../bindings/power/reset/xlnx,zynqmp-power.txt | 25 ++
1 file changed, 25 insertions(+)
create mo
On 1/14/2019 1:54 PM, Mike Kravetz wrote:
> On 1/14/19 7:35 AM, Steven Sistare wrote:
>> On 1/11/2019 6:28 PM, Mike Kravetz wrote:
>>> On 1/11/19 1:55 PM, Kirill A. Shutemov wrote:
On Fri, Jan 11, 2019 at 08:10:03PM +, Mike Kravetz wrote:
> At LPC last year, Boaz Harrosh asked why he h
On 1/13/19, 2:39 PM, "Andrew Jeffery" wrote:
Hi Vijay,
Sorry for providing an opinion so late, however:
On Sat, 12 Jan 2019, at 11:03, Vijay Khemka wrote:
> Joel,
> Please merge these patches as it is required by facebook platform.
>
> Regards
> -Vija
On Mon, Jan 14, 2019 at 2:22 AM Peter Zijlstra wrote:
>
> On Thu, Jan 10, 2019 at 02:07:18PM -0800, Suren Baghdasaryan wrote:
> > +/*
> > + * psi_update_work represents slowpath accounting part while
> > + * psi_group_change represents hotpath part.
> > + * There are two potential races between th
On Wed, Jan 09, 2019 at 12:47:26PM +0100, Sebastian Andrzej Siewior wrote:
> fpu__clear() only initializes the `state' if the FPU is present. This
> initialisation is also required for the FPU-less system and takes place
"in math_emulate()."
> math_emulate(). Since fpu__initialize() only performs
On Tue, Jan 15, 2019 at 5:25 AM Steven Rostedt wrote:
>
> The swap_lock used by sbitmap has a chain with locks taken from
> softirq, but the swap_lock is not protected from being preempted by
> softirqs.
>
> A chain exists of:
>
> sbq->ws[i].wait -> dispatch_wait_lock -> swap_lock
>
> Where the s
[+ BenH and MPE]
On Mon, Jan 14, 2019 at 07:21:08PM +, Koenig, Christian wrote:
> Am 14.01.19 um 20:13 schrieb Will Deacon:
> > On Mon, Jan 14, 2019 at 07:07:54PM +, Koenig, Christian wrote:
> >> Am 14.01.19 um 18:32 schrieb Ard Biesheuvel:
> >> - The reason remapping the CPU
- Original Message -
> On Mon, Jan 14, 2019 at 01:58:32PM -0500, Dave Anderson wrote:
> > Preferably it would be left as-is. The crash utility has a "crash
> > --osrelease vmcore"
> > option that only looks at the dumpfile header, and just dump the string.
> > With respect
> > to compr
* Mathieu Desnoyers:
> - On Jan 14, 2019, at 10:55 AM, Florian Weimer fwei...@redhat.com wrote:
>
>> * Mathieu Desnoyers:
>>
>>> Therefore, both symbols will end up in
>>> sysdeps/unix/sysv/linux/Versions.
>>
>> I'm not sure what you mean by that. The physical location in the
>> directory t
User process can involve dealing with big buffer sizes, and also passing
buffers from one compute context bank to other compute context bank for
complex dsp algorithms.
This patch adds support to fastrpc to make it a proper dmabuf exporter
to avoid making copies of buffers.
Co-developed-by: Thier
The FastRPC driver implements an IPC (Inter-Processor Communication)
mechanism that allows for clients to transparently make remote method
invocations across DSP and APPS boundaries. This enables developers
to offload tasks to the DSP and free up the application processor for
other tasks.
Co-devel
Thanks for reviewing the v2, here is new version addressing the
comments from v2.
This patchset adds support to Qualcomm FastRPC driver which implements
an IPC (Inter-Processor Communication) mechanism that allows for clients
to transparently make remote method invocations across processor boundari
This patch adds basic driver model for qualcomm fastrpc.
Each DSP rpmsg channel is represented as fastrpc channel context and
is exposed as a character driver for userspace interface.
Each compute context bank is represented as fastrpc-session-context,
which are dynamically managed by the channel c
This patch adds support to create or attach remote shell process.
The shell process called fastrpc_shell_0 is usually loaded on the DSP
when a user process is spawned.
Most of the work is derived from various downstream Qualcomm kernels.
Credits to various Qualcomm authors who have contributed to
This patch adds support to compute context invoke method
on the remote processor (DSP).
This involves setting up the functions input and output arguments,
input and output handles and mapping the dmabuf fd for the
argument/handle buffers.
Most of the work is derived from various downstream Qualcom
On Mon, Jan 14, 2019 at 11:30:12AM -0800, Suren Baghdasaryan wrote:
> On Mon, Jan 14, 2019 at 2:22 AM Peter Zijlstra wrote:
> >
> > On Thu, Jan 10, 2019 at 02:07:18PM -0800, Suren Baghdasaryan wrote:
> > > +/*
> > > + * psi_update_work represents slowpath accounting part while
> > > + * psi_group_
Current GPIO code in cp210x fails to take USB autosuspend into account,
making it practically impossible to use GPIOs with autosuspend enabled
without user configuration. Fix this like for ftdi_sio in a previous patch.
Tested on a CP2102N.
Signed-off-by: Karoly Pados
---
drivers/usb/serial/cp210
On 1/14/19 10:14 AM, Steven Rostedt wrote:
> It was brought to my attention (by this creating a splat in the RT tree
> too) this code:
>
> static inline bool sbitmap_deferred_clear(struct sbitmap *sb, int index)
> {
> unsigned long mask, val;
> unsigned long __maybe_unused flags;
>
Several drivers didn't have a specific maintainer (other than the
subsystem maintainer). Add some generic regex patterns to capture most
qcom drivers in the list of supported drivers. For the rest, add
explicit filenames.
Sort the entries, while we're at it.
Signed-off-by: Amit Kucheria
---
MAI
Add support for parsing "firmware-name" dt bindings which specifies
the relative paths of mba/modem/pas image as strings. Fallback to
the default paths for mba/modem/pas image on -EINVAL.
Signed-off-by: Sibi Sankar
---
v3:
* Fixed minor code style issues
* Add comments for firmware blob name g
On 1/11/19 3:28 PM, Safford, David (GE Global Research) wrote:
-Original Message-
From: linux-integrity-ow...@vger.kernel.org On Behalf Of Stefan Berger
Sent: Wednesday, January 09, 2019 5:11 PM
To: linux-integr...@vger.kernel.org; jarkko.sakki...@linux.intel.com
Cc: linux-security-mod..
On Mon, Jan 14, 2019 at 10:50:24AM -0800, Todd Kjos wrote:
> On Mon, Jan 14, 2019 at 10:33 AM Joel Fernandes wrote:
> >
> > On Mon, Jan 14, 2019 at 09:10:21AM -0800, Todd Kjos wrote:
> > > To allow servers to verify client identity, allow a node
> > > flag to be set that causes the sender's securi
From: Zhikang Zhang
[delete "extern" from prototype --adobriyan]
Signed-off-by: Zhikang Zhang
Signed-off-by: Alexey Dobriyan
---
fs/proc/base.c |2 +-
fs/proc/internal.h |2 +-
fs/proc/root.c |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--- a/fs/proc/base.c
++
Help gcc generate better code:
$ ./scripts/bloat-o-meter ../vmlinux-000 ../vmlinux-001
add/remove: 2/2 grow/shrink: 0/1 up/down: 92/-142 (-50)
Function old new delta
get_iowait_time.isra - 46
On Mon, Jan 14, 2019 at 02:36:47PM -0500, Dave Anderson wrote:
> There's no reading of the dumpfile's memory involved, and that being the case,
> the vmlinux file is not utilized. That's the whole point of the crash
> option, i.e.,
> taking a vmcore file, and trying to determine what kernel shoul
On Thu, Jan 10, 2019 at 05:11:27PM -0600, Alexandru Gagniuc wrote:
> _HPX Type 3 is intended to be more generic and allow configuration of
> settings not possible with Type 2 tables. For example, FW could ensure
> that the completion timeout value is set accordingly throughout the PCI
> tree; some
Hi,
On 1/12/19 4:42 AM, Himanshu Jha wrote:
On Fri, Jan 11, 2019 at 03:53:58PM -0500, Sebastien Bourdelin wrote:
This commit allow the driver to work with device-tree.
Signed-off-by: Sebastien Bourdelin
---
I get the following compilation failure:
Below I have `allyesconfig` except 'BME680'
Hi,
On 1/12/19 1:22 PM, Jonathan Cameron wrote:
On Fri, 11 Jan 2019 15:53:58 -0500
Sebastien Bourdelin wrote:
This commit allow the driver to work with device-tree.
Signed-off-by: Sebastien Bourdelin
Minor stuff inline.
J
---
v1 -> v2:
- add missing of.h header in bme680_spi.c
---
d
Compilers like to transform loops like
for (i = 0; i < n; i++) {
[use p[i]]
}
into
for (p = p0; p < end; p++) {
...
}
Do it by hand, so that it results in overall simpler loop
and smaller code.
Space savings:
$ ./scripts/b
seq_printf() without format specifiers == faster seq_puts()
Signed-off-by: Alexey Dobriyan
---
fs/proc/array.c | 16
fs/proc/base.c |2 +-
fs/proc/task_nommu.c |2 +-
3 files changed, 10 insertions(+), 10 deletions(-)
--- a/fs/proc/array.c
+++ b/fs/proc/ar
- Original Message -
> On Mon, Jan 14, 2019 at 02:36:47PM -0500, Dave Anderson wrote:
> > There's no reading of the dumpfile's memory involved, and that being the
> > case,
> > the vmlinux file is not utilized. That's the whole point of the crash
> > option, i.e.,
> > taking a vmcore
On Mon, Jan 14, 2019 at 08:17:10PM +0100, Harald Arnesen wrote:
> Sean Christopherson [14.01.2019 19:33]:
>
> > On Mon, Jan 14, 2019 at 06:04:27PM +0100, Harald Arnesen wrote:
> >> Qemu with KVM acceleration fails with kernel 5.0-rc1 and 5.0-rc2.
> >> It works fine with 4.20.
>
> > Can you test t
Hi Fenghua/Sai/Arshiya,
Few comments on this patch below. Sorry for the late comment.
On 12/21/18 6:20 PM, Fenghua Yu wrote:
> From: Arshiya Hayatkhan Pathan
>
> Cache Allocation Technology (CAT) selftest allocates a portion of
> last level cache and starts a benchmark to read each cache
> line
On Tue, Jan 08, 2019 at 07:33:19PM -0200, Thiago Jung Bauermann wrote:
> Alexey Dobriyan writes:
> > --- a/tools/testing/selftests/proc/proc-loadavg-001.c
> > +++ b/tools/testing/selftests/proc/proc-loadavg-001.c
> > @@ -30,7 +30,7 @@ int main(void)
> >
> > if (unshare(CLONE_NEWPID) == -1) {
>
Hi Dan,
On 1/14/19 1:27 PM, Dan Murphy wrote:
Jacek
On 1/12/19 1:48 PM, Jacek Anaszewski wrote:
Hi Dan,
On 1/12/19 6:09 PM, Dan Murphy wrote:
Jacek
On 1/11/19 3:52 PM, Jacek Anaszewski wrote:
Dan,
On 1/11/19 1:38 PM, Dan Murphy wrote:
Jacek
Sorry I missed some replies
On 1/10/19 4:03 P
On Sun, Jan 13, 2019 at 6:41 PM H. Peter Anvin wrote:
>
> On 1/13/19 6:31 PM, H. Peter Anvin wrote:
> >
> > static cpumask_t text_poke_cpumask;
> >
> > static void text_poke_sync(void)
> > {
> > smp_wmb();
> > text_poke_cpumask = cpu_online_mask;
> > smp_wmb(); /* Should be
GCC supports -mcpu=G4
This patch gives the opportunity to select ALTIVEC for this variant.
Signed-off-by: Mathieu Malaterre
---
arch/powerpc/platforms/Kconfig.cputype | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/powerpc/platforms/Kconfig.cputype
b/arch/powerpc/platforms/Kconf
Jacek
On 1/14/19 2:11 PM, Jacek Anaszewski wrote:
> Hi Dan,
>
> On 1/14/19 1:27 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 1/12/19 1:48 PM, Jacek Anaszewski wrote:
>>> Hi Dan,
>>>
>>> On 1/12/19 6:09 PM, Dan Murphy wrote:
Jacek
On 1/11/19 3:52 PM, Jacek Anaszewski wrote:
> Dan,
>>
This fixes autoloading the module by the OF compatible string.
Fixes: 813e18b18a87f31c5b216ea7546127deac3ae1ae
Cc: sta...@vger.kernel.org # v4.19+
Signed-off-by: Lubomir Rintel
---
drivers/usb/host/ehci-mv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/ehci-mv.c b/drivers
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
security/keys/request_key.c:293:7: warning: this statement may fall through
[-Wimplicit-fallthrough=]
security/keys/re
On Mon, Jan 14, 2019 at 03:07:33PM -0500, Dave Anderson wrote:
> That's what it *does* utilize -- it takes a standalone vmcore dumpfile, and
> pulls out the OSRELEASE string from it, so that a user can determine what
> vmlinux file should be used with that vmcore for normal crash analysis.
And th
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warning:
security/keys/process_keys.c:380:7: warning: this statement may fall through
[-Wimplicit-fallthrough=]
security/keys/pr
On 1/12/19 1:28 PM, Jonathan Cameron wrote:
On Fri, 11 Jan 2019 15:53:59 -0500
Sebastien Bourdelin wrote:
BME680 is a pressure/temperature/humidity/voc sensor.
Signed-off-by: Sebastien Bourdelin
Hmm. We could add the VDD and VDIO regulators perhaps.
Driver assumes they are on currently bu
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
security/keys/keyring.c:248:10: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
-
On Sun, Jan 13, 2019 at 10:34 AM Michal Hocko wrote:
>
> On Fri 11-01-19 14:54:32, Shakeel Butt wrote:
> > Hi Johannes,
> >
> > On Fri, Jan 11, 2019 at 12:59 PM Johannes Weiner wrote:
> > >
> > > Hi Shakeel,
> > >
> > > On Thu, Jan 10, 2019 at 09:44:32AM -0800, Shakeel Butt wrote:
> > > > If a me
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
lib/siphash.c:71:12: warning: this statement may fall through
[-Wimplicit-fallthrough=]
lib/siphash.c:72:12: warning:
On Mon, Jan 14, 2019 at 01:20:45PM -0500, Michael S. Tsirkin wrote:
> I don't think so - the issue is really that DMA API does not yet handle
> the SEV case 100% correctly. I suspect passthrough devices would have
> the same issue.
The DMA API handles the SEV case perfectly. Its just that virtio_
BME680 is a pressure/temperature/humidity/voc sensor.
Signed-off-by: Sebastien Bourdelin
---
v2 -> v3:
- change i2c address to 0x76 as it seems more reliable: Suggested by Himanshu
Jha
- rebase on master
---
.../devicetree/bindings/iio/chemical/bme680.txt | 11 +++
1 file cha
This commit allow the driver to work with device-tree.
Signed-off-by: Sebastien Bourdelin
---
v2 -> v3:
- remove of_match_ptr: Suggested by Jonathan Cameron
- minor style fixup
- rebase on master
v1 -> v2:
- add missing of.h header in bme680_spi.c
---
drivers/iio/chemical/bme680_i2c.c |
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
lib/cmdline.c:137:7: warning: this statement may fall through
[-Wimplicit-fallthrough=]
lib/cmdline.c:140:7: warning:
On Mon, Jan 14, 2019 at 07:12:08PM +, Robin Murphy wrote:
> Now, in theory, yes, the real issue at hand is not unique to virtio-blk nor
> SEV - any driver whose device has a sufficiently large DMA segment size and
> who manages to get sufficient physically-contiguous memory could
> technical
Hi Xiang,
> -Original Message-
> From: xiang xiao
> Sent: samedi 12 janvier 2019 19:29
> To: Loic PALLARDY
> Cc: bjorn.anders...@linaro.org; o...@wizery.com; linux-
> remotep...@vger.kernel.org; linux-kernel@vger.kernel.org; Arnaud
> POULIQUEN ; benjamin.gaign...@linaro.org; s-
> a...@ti
On Mon 14 Jan 09:36 PST 2019, Christoph Hellwig wrote:
> On Mon, Jan 14, 2019 at 09:30:51AM -0800, Bjorn Andersson wrote:
> > The problem here is that the capability bit states that the controller
> > itself claim to be able to deal with 64-bit addresses, which is probably
> > true. The thing that
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
lib/assoc_array.c:1110:3: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
li
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
lib/asn1_decoder.c:386:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
lib/asn1_decoder.c:449:6:
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
drivers/gpu/drm/radeon/evergreen_cs.c:1301:11: warning: this statement may
fall through [-Wimplicit-fallthrough=]
Signed-off-by: Mathi
- Original Message -
> On Mon, Jan 14, 2019 at 03:07:33PM -0500, Dave Anderson wrote:
> > That's what it *does* utilize -- it takes a standalone vmcore dumpfile, and
> > pulls out the OSRELEASE string from it, so that a user can determine what
> > vmlinux file should be used with that vm
- On Jan 14, 2019, at 2:37 PM, Florian Weimer fwei...@redhat.com wrote:
> * Mathieu Desnoyers:
>
>> - On Jan 14, 2019, at 10:55 AM, Florian Weimer fwei...@redhat.com wrote:
>>
>>> * Mathieu Desnoyers:
>>>
Therefore, both symbols will end up in
sysdeps/unix/sysv/linux/Versions.
Dan,
On 1/14/19 9:14 PM, Dan Murphy wrote:
[...]
One last question I am going to add the LP5036 and 30 which have the same
technology but slightly different register maps.
Should I rename the driver to LP5036.c as the 30, 24 and 18 would technically
be subsets?
How about leds-lp50xx.c ? You
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
include/linux/compiler.h:77:22: warning: this statement may fall through
[-Wimplicit-fallthrough=]
include/asm-generic
Hello everyone,
first of all thanks to Marek for looking into this.
@Robin: This works for me. The drivers now probe and bind correctly again.
With best wishes,
Tobias
Robin Murphy wrote:
> On 14/01/2019 16:09, Thierry Reding wrote:
>> On Mon, Jan 14, 2019 at 02:22:40PM +0100, Marek Szyprowski
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case change put the fall through comment on a single
line so as to match the regular expression expected by GCC.
This commit remove the following warning:
ker
On Mon, Jan 14, 2019 at 07:12:08PM +, Robin Murphy wrote:
> On 14/01/2019 18:20, Michael S. Tsirkin wrote:
> > On Mon, Jan 14, 2019 at 08:41:37PM +0800, Jason Wang wrote:
> > >
> > > On 2019/1/14 下午5:50, Christoph Hellwig wrote:
> > > > On Mon, Jan 14, 2019 at 05:41:56PM +0800, Jason Wang wrot
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warnings (W=1).
This commit remove the following warning:
kernel/bpf/cgroup.c:719:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
Jacek
On 1/14/19 2:28 PM, Jacek Anaszewski wrote:
> Dan,
>
> On 1/14/19 9:14 PM, Dan Murphy wrote:
> [...]
>> One last question I am going to add the LP5036 and 30 which have the
>> same technology but slightly different register maps.
>> Should I rename the driver to LP5036.c as the
There is a plan to build the kernel with -Wimplicit-fallthrough and
thise place in the code produced a warnings (W=1).
In this particular case change a ‘:’ with a ‘,’ so as to match the
regular expression expected by GCC.
This commit remove the following warning:
net/core/filter.c:5310:6: warn
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
kernel/trace/trace_events_filter.c:494:8: warning: this statement may fall
through [-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Ma
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
kernel/trace/trace_probe.c:302:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
kernel/trace/blktrace.c:725:9: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
--
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
kernel/irq/manage.c:725:3: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
k
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
kernel/sys.c:1748:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
kernel/
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 to enabling
-Wimplicit-fallthrough
Signed-off-by: Gustavo A. R. Silva
---
fs/adfs/dir_f.c |
On Mon, Jan 14, 2019 at 03:26:32PM -0500, Dave Anderson wrote:
> No. It needs *both* the vmlinux file and the vmcore file in order to read
> kernel
> virtual memory, so just having a kernel virtual address is insufficient.
>
> So it's a chicken-and-egg situation. This particular --osrelease opt
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
kernel/signal.c:795:13: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
kern
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
ipc/sem.c:1683:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
ipc/sem.c
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
kernel/events/core.c:8945:11: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case add a ‘-’ so as to match the regular expression
expected by GCC.
This commit remove the following warning:
kernel/irq/handle.c:167:4: warning: this state
On Thu, Jan 3, 2019 at 4:50 AM Myungho Jung wrote:
> I reproduced on vm using syzkaller utils and verified the fix by syzbot.
Hi Myungho,
I think this might be a better fix:
diff --git a/net/ceph/messenger.c b/net/ceph/messenger.c
index d5718284db57..c5f5313e3537 100644
--- a/net/ceph/messenger
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
fs/signalfd.c:178:7: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
fs/sign
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
fs/seq_file.c:319:10: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
---
fs/seq
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case remove a ‘:’ so as to match the regular
expression expected by GCC.
This commit remove the following warning:
fs/locks.c:1473:16: warning: this statement
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
fs/libfs.c:148:11: warning: this statement may fall through
[-Wimplicit-fallthrough=]
fs/libfs.c:150:7: warning: this
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case change a ‘:’ with a ‘-’ so as to match the
regular expression expected by GCC.
This commit remove the following warning:
fs/fcntl.c:770:7: warning: this
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the problem
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
fs/ext4/indirect.c:1182:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
fs/ext4/indirect.c:1188:
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
fs/ext4/hash.c:233:15: warning: this statement may fall through
[-Wimplicit-fallthrough=]
fs/ext4/hash.c:246:15: warni
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warnings:
drivers/video/fbdev/offb.c:211:5: warning: this statement may fall through
[-Wimplicit-fallthrough=]
drivers/video/fbd
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
This commit remove the following warning:
drivers/tty/vt/vt.c:2112:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
drivers/tty/vt/vt.c:2237
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case change a ‘:’ with a ‘,’ so as to match the
regular expression expected by GCC.
This commit remove the following warning:
drivers/pci/quirks.c:2138:6: war
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.
In this particular case change a ‘:’ with either a ‘-’ or a ‘,’
so as to match the regular expression expected by GCC.
This commit remove the following warnings:
d
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case rewrote the comment to start with the string "fall
through", so as to match the regular expression expected by GCC. Truncate
the comment slightly to fit the
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case add a ‘-’ so as to match the regular expression
expected by GCC.
This commit remove the following warning:
/drivers/firewire/core-device.c: In function 'se
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
In this particular case rewrote the comment to start with the string "fall
through", so as to match the regular expression expected by GCC.
This commit remove the following warning
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
drivers/firewire/core-topology.c:69:23: warning: this statement may fall
through [-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Mala
Incoroporate ssdd into the rt-tests build
Signed-off-by: John Kacur
---
Makefile | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 06f399cc629d..16cd2f9bdd03 100644
--- a/Makefile
+++ b/Makefile
@@ -16,7 +16,8 @@ sources = cyclictest.c \
There is a plan to build the kernel with -Wimplicit-fallthrough and
this place in the code produced a warning (W=1).
This commit remove the following warning:
drivers/char/generic_nvram.c:83:3: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Signed-off-by: Mathieu Malaterre
On Mon, Jan 14, 2019 at 11:42 AM Johannes Weiner wrote:
>
> On Mon, Jan 14, 2019 at 11:30:12AM -0800, Suren Baghdasaryan wrote:
> > On Mon, Jan 14, 2019 at 2:22 AM Peter Zijlstra wrote:
> > >
> > > On Thu, Jan 10, 2019 at 02:07:18PM -0800, Suren Baghdasaryan wrote:
> > > > +/*
> > > > + * psi_upd
701 - 800 of 1164 matches
Mail list logo
