ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/net/lcs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/scsi/zfcp_ccw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/virtio/virtio_ccw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, 15 Aug 2017 16:45:34 +0800
Kemi Wang wrote:
> Each page allocation updates a set of per-zone statistics with a call to
> zone_statistics(). As discussed in 2017 MM submit, these are a substantial
^^ should be "summit"
> source of overhead i
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/net/ctcm_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/char/tape_34xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/block/dasd_fba.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/block/dasd_eckd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.66 release.
There are 16 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.83 release.
There are 23 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Tue, Jul 25, 2017 at 08:10:39PM +0800, Shaokun Zhang wrote:
> This patch adds support for L3C PMU driver in HiSilicon SoC chip, Each
> L3C has own control, counter and interrupt registers and is an separate
> PMU. For each L3C PMU, it has 8-programable counters and supports 0x60
> events, event
From: Jonathan Corbet
> Sent: 12 August 2017 15:55
...
> > + Chapter 20: Put values on initialisers without exception
> > +
> > +When declaring variables on functions must put values:
>
> Thanks for sending a patch for the kernel's documentation.
> Unfortunately, I can't accept this patc
On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.12.8 release.
There are 65 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Tue, 15 Aug 2017, Ingo Molnar wrote:
> * Willy Tarreau wrote:
>
> > Nowadays we could use similar methods using RDTSC providing more accurate
> > counting. This doesn't provide a lot of entropy of course, given that a
> > 2 GHz machine will at most count 31 bits there. But I tend to think that
On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.44 release.
There are 41 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 2017-08-14 14:38, Bhumika Goyal wrote:
> Make this const as it is only passed as the 2nd argument to the
> function devm_snd_soc_register_platform, which is of type
On Mon, Aug 14, 2017 at 04:17:35PM -0700, Khuong Dinh wrote:
[...]
> >> +static acpi_status acpi_create_msi_device(acpi_handle handle, u32 Level,
> >> + void *context, void **retval)
> >> +{
> >> + struct acpi_device *device = NULL;
> >> + int type = AC
The revision 0x300 generic error data entry is different
from the old version, but currently iterating through the
GHES estatus blocks does not take into account this difference.
This will lead to failure to get the right data entry if GHES
has revision 0x300 error data entry.
Update the GHES esta
On Tue, Aug 15, 2017 at 11:31:57AM +0100, Punit Agrawal wrote:
> I'd seen the link between acpi_pci_root_init() and acpi_hest_init() but
> didn't want to open another can of worms... :)
>
> $SUBJECT was my attempt (small) at improving the situation but I guess I
> didn't go far enough.
Well, one
Masahiro-san,
I have a question about make *config. In scripts/kconfig/Makefile, there
is following statement:
$(obj)/zconf.tab.o: $(obj)/zconf.lex.c $(obj)/zconf.hash.c
and the $(obj)/zconf.{tab,hash,lex}.c match the rule in Makefile.lib:
$(obj)/%: $(src)/%_shipped
$(call cmd,shipped)
On Tuesday, August 15, 2017 1, Nicolas Pitre wrote:
> I was able to reproduce. The following patch on top should partially fix
> it. I'm trying to figure out how to split a vma and link it properly in
> the case the vma cannot be mapped entirely. In the mean time shared libs
> won't be XIP.
>
>
On Tue, Jul 25, 2017 at 08:10:40PM +0800, Shaokun Zhang wrote:
> +/* HHA register definition */
> +#define HHA_INT_MASK 0x0804
> +#define HHA_INT_STATUS 0x0808
> +#define HHA_INT_CLEAR0x080C
> +#define HHA_PERF_CTRL0x1E00
> +#define HHA_EVENT_CT
Introducing USB charger type and state definition can help
to support USB charging which will be added in USB phy core.
Signed-off-by: Baolin Wang
---
include/uapi/linux/usb/charger.h | 31 +++
1 file changed, 31 insertions(+)
create mode 100644 include/uapi/linux/
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not b
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
Signed-off-
This patch introduces the usb charger support based on usb phy that
makes an enhancement to a power driver. The basic conception of the
usb charger is that, when one usb charger is added or removed by
reporting from the extcon device state change, the usb charger will
report to power user to set th
Commit-ID: 84393817db09bb436e934f8f8cc981cbca9ea4dc
Gitweb: http://git.kernel.org/tip/84393817db09bb436e934f8f8cc981cbca9ea4dc
Author: Thomas Gleixner
AuthorDate: Tue, 15 Aug 2017 13:03:47 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 15 Aug 2017 13:03:47 +0200
x86/mtrr: Prevent CP
On Mon, Aug 07, 2017 at 07:36:05PM +0100, Mark Rutland wrote:
> diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> index e5aa866..44a27c3 100644
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
> @@ -72,6 +72,37 @@
> .macro kernel_ventrylabel
> .
Hi Felipe,
On 15 August 2017 at 17:53, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>>> Currently the Linux kernel does not provide any standard integration of this
>>> feature that integrates the USB subsystem with the system power regulation
>>> provided by PMICs meaning that either ven
On Tue, 15 Aug 2017 16:05:44 +0530
Arvind Yadav wrote:
> ccw_device_id are not supposed to change at runtime. All functions
> working with ccw_device_id provided by work with
> const ccw_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/s390/vi
Julia Lawall writes:
> Normally the values in the resource field and the argument to ARRAY_SIZE
> in the num_resources are the same. In this case, the value in the reousrce
> field is the same as the one in the previous platform_device structure, and
> appears to be a copy-paste error. Replace
On Tue, Aug 15, 2017 at 12:00 PM, Oleksandr Shamray
wrote:
> + case JTAG_IOCXFER:
> + if (copy_from_user(&xfer, varg, sizeof(struct jtag_xfer)))
> + return -EFAULT;
> +
> + if (xfer.length >= JTAG_MAX_XFER_DATA_LEN)
> +
On Tue, Aug 15, 2017 at 12:10:32PM +0100, Catalin Marinas wrote:
> On Mon, Aug 07, 2017 at 07:36:05PM +0100, Mark Rutland wrote:
> > diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> > index e5aa866..44a27c3 100644
> > --- a/arch/arm64/kernel/entry.S
> > +++ b/arch/arm64/kernel/e
platform_device_id are not supposed to change at runtime. All functions
working with platform_device_id provided by
work with const platform_device_id. So mark the non-const structs as
const.
Signed-off-by: Arvind Yadav
---
drivers/media/platform/omap3isp/isp.c | 2 +-
1 file changed, 1 inserti
platform_device_id are not supposed to change at runtime. All functions
working with platform_device_id provided by
work with const platform_device_id. So mark the non-const structs as
const.
Signed-off-by: Arvind Yadav
---
drivers/media/platform/davinci/vpbe_osd.c | 2 +-
drivers/media/platfo
platform_device_id are not supposed to change at runtime. All functions
working with platform_device_id provided by
work with const platform_device_id. So mark the non-const structs as const.
Arvind Yadav (3):
[PATCH 1/3] [media] coda: constify platform_device_id
[PATCH 2/3] [media] davinci:
platform_device_id are not supposed to change at runtime. All functions
working with platform_device_id provided by
work with const platform_device_id. So mark the non-const structs as
const.
Signed-off-by: Arvind Yadav
---
drivers/media/platform/coda/coda-common.c | 2 +-
1 file changed, 1 ins
On 11.08.2017 05:41, Lu Baolu wrote:
Xhci driver handles USB transaction errors on transfer events,
but transaction errors are possible on address device command
completion events as well.
The xHCI specification (section 4.6.5) says: A USB Transaction
Error Completion Code for an Address Device
When forcing a signal, SIGNAL_UNKILLABLE is removed to prevent recursive
faults, but this is undesirable when tracing. For example, debugging an
init process (whether global or namespace), hitting a breakpoint and
SIGTRAP will force SIGTRAP and then remove SIGNAL_UNKILLABLE.
Everything continues f
On Tue, Aug 15, 2017 at 04:05:31PM +0530, Arvind Yadav wrote:
> ccw_device_id are not supposed to change at runtime. All functions
> working with ccw_device_id provided by work with
> const ccw_device_id. So mark ccw_device_id member of struct ccw driver
> as const. And change all driver relativel
Hi Dave,
more fixes to net tree for 4.13. More info in the signed tag below,
please let me know if there are any problems.
Kalle
The following changes since commit 5f5d03143de5e0c593da4ab18fc6393c2815e108:
brcmfmac: fix memleak due to calling brcmf_sdiod_sgtable_alloc() twice
(2017-07-27 14:
4.13 contains a number of updates to the core IRQ code to deal with
things like the effective affinity. This series attempts to fix a
number of small things that are now breaking:
1) The core code assumes that CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK
being defined implies that *all* interrupts hav
If CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK is defined, but that the
interrupt is not single target, the effective affinity reported in
/proc/irq/x/effective_affinity will be empty, which is not the truth.
Instead, use the accessor to report the affinity, which will pick
the right mask.
Signed-off-b
The GICv3 ITS driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/irq-gic-v3-its.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-
The xtensa-mx driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/Kconfig | 1 +
drivers/irqchip/irq-xtensa-mx.c | 6 +-
2 files changed, 6 insertions(+), 1 deletion
The MIPS GIC driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/Kconfig| 1 +
drivers/irqchip/irq-mips-gic.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/driv
The HIP04 driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
arch/arm/mach-hisi/Kconfig | 1 +
drivers/irqchip/irq-hip04.c | 3 +++
2 files changed, 4 insertions(+)
diff --git a/arch/arm/mac
The BCM 7038-L1 driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/Kconfig | 1 +
drivers/irqchip/irq-bcm7038-l1.c | 3 +++
2 files changed, 4 insertions(+)
diff --gi
The metag-ext driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
arch/metag/Kconfig | 1 +
drivers/irqchip/irq-metag-ext.c | 4
2 files changed, 5 insertions(+)
diff --git a
On Fri 2017-08-11 09:31:28, Helge Deller wrote:
> On 11.08.2017 02:15, Sergey Senozhatsky wrote:
> > On (08/10/17 19:35), Helge Deller wrote:
> >> Sometimes people seems unclear when to use the %pS or %pF printk format.
> >> Adding some examples may help to avoid such mistakes.
> >>
> >> See for ex
On 2017-08-12 00:26, Stephen Boyd wrote:
> Quoting Peter Rosin (2017-08-08 05:46:30)
>> On 2017-08-08 03:51, Stephen Boyd wrote:
>>
>>> It looked like we paired the start/stop ops with
>>> each other so that the mux is properly managed across these ops.
>>
>> Yes, it *looks* ok
The BCM 6345-L1 driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/Kconfig | 1 +
drivers/irqchip/irq-bcm6345-l1.c | 3 +++
2 files changed, 4 insertions(+)
diff --gi
The Armada 370 XP driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/Kconfig | 1 +
drivers/irqchip/irq-armada-370-xp.c | 3 +++
2 files changed, 4 insertions(+)
d
The GICv3 driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/Kconfig | 1 +
drivers/irqchip/irq-gic-v3.c | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/ir
The GIC driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.
Signed-off-by: Marc Zyngier
---
drivers/irqchip/Kconfig | 1 +
drivers/irqchip/irq-gic.c | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/irqchip/Kc
On Tue, 2017-08-15 at 16:53 +0530, Arvind Yadav wrote:
> platform_device_id are not supposed to change at runtime. All
> functions
> working with platform_device_id provided by
> work with const platform_device_id. So mark the non-const structs as
> const.
>
> Signed-off-by: Arvind Yadav
Acked-
Just because CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK is selected
doesn't mean that all the interrupts are using the effective
affinity mask. For a number of them, this mask is likely to
be empty.
In order to deal with this, let's restrict the use of the
effective affinity mask to these interrupts th
Marcel,
Am Dienstag, 15. August 2017, 12:22:27 CEST schrieb Marcel Holtmann:
> > Is this known?
>
> It is not known, but it is also unclear why this happens. Basically the card
> looses power and thus ends up in bootloader mode.
>
Hm, maybe a BIOS issue?
Thanks,
//richard
--
sigma star gmbh
On Sun, Aug 13, 2017 at 02:24:44PM +0530, Arvind Yadav wrote:
> usb_device_id are not supposed to change at runtime. All functions
> working with usb_device_id provided by work with
> const usb_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
Acked-by: Sean You
On 2017/8/15 11:22, Jaegeuk Kim wrote:
> On 08/15, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2017/8/11 8:42, Jaegeuk Kim wrote:
>>> If we set CP_ERROR_FLAG in roll-forward error, f2fs is no longer to proceed
>>> any IOs due to f2fs_cp_error(). But, for example, if some stale data is
>>> involved
>>>
Hi,
thanks for reviewing.
On 2017-08-15 12:03, Felipe Balbi wrote:
Hi,
Danilo Krummrich writes:
udc_stop needs to be called before gadget driver unbind. Otherwise it
might happen that udc drivers still call into the gadget driver (e.g.
to reset gadget after OTG event). If this happens it is
On Tue, Aug 15, 2017 at 05:09:14PM +0800, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> add dt-binding document for MediaTek MT6380 PMIC
Please use subject lines reflecting the style for the subsystem.
signature.asc
Description: PGP signature
On 08/14/2017 07:55 PM, Edward Cree wrote:
State of a register doesn't matter if it wasn't read in reaching an exit;
a write screens off all reads downstream of it from all explored_states
upstream of it.
This allows us to prune many more branches; here are some processed insn
counts for so
On Tue, Aug 15, 2017 at 04:07:02PM +0800, Ryder Lee wrote:
> This patch update interrupt property since we only use ASYS IRQ
> in the driver, and this may confuse people.
> - interrupts = ,
> - ;
> + interrupts = ;
What harm does having the extra
On Thu 2017-08-10 13:36:35, Kees Cook wrote:
> This reverts commit 68c4a4f8abc60c9440ede9cd123d48b78325f7a3, with
> various conflict clean-ups.
>
> With the default root directory mode set to 0750 now, the capability
> check was redundant.
>
> Suggested-by: Nick Kralevich
> Signed-off-by: Kees C
From: Markus Elfring
Date: Tue, 15 Aug 2017 13:43:21 +0200
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (5):
Delete an error message for a failed memory allocation in five functions
Improve 19 size determinations
Add a jump target in p9_c
From: Markus Elfring
Date: Tue, 15 Aug 2017 08:25:41 +0200
Omit an extra message for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
net/9p/client.c | 7 ++-
net/9p/trans_fd.c | 6 ++
On Tuesday, August 15, 2017 4:56:18 AM CEST Sergey Senozhatsky wrote:
> It's not always possible/safe to wake_up() printk kernel
> thread. For example, late suspend/early resume may printk()
> while timekeeping is not initialized yet, so calling into the
> scheduler may result in recursive warnings
From: Markus Elfring
Date: Tue, 15 Aug 2017 09:36:20 +0200
Replace the specification of data structures by variable references
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
From: Markus Elfring
Date: Tue, 15 Aug 2017 10:07:22 +0200
Replace a variable assignment by a goto statement so that an extra check
will be avoided at the end of this function.
Signed-off-by: Markus Elfring
---
net/9p/client.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --
On Tue, 15 Aug 2017, Marc Zyngier wrote:
> Just because CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK is selected
> doesn't mean that all the interrupts are using the effective
> affinity mask. For a number of them, this mask is likely to
> be empty.
>
> In order to deal with this, let's restrict the use
From: Markus Elfring
Date: Tue, 15 Aug 2017 11:17:23 +0200
Adjust jump labels so that the function implementation becomes smaller.
Delete an extra variable assignment and a check (at the end of
this function).
Signed-off-by: Markus Elfring
---
net/9p/client.c | 18 +++---
1 file c
Hi,
Danilo Krummrich writes:
> thanks for reviewing.
np :-)
> On 2017-08-15 12:03, Felipe Balbi wrote:
>> Hi,
>>
>> Danilo Krummrich writes:
>>> udc_stop needs to be called before gadget driver unbind. Otherwise it
>>> might happen that udc drivers still call into the gadget driver (e.g.
>>>
From: Markus Elfring
Date: Tue, 15 Aug 2017 11:25:31 +0200
The local variable "err" will eventually be set to an appropriate value
a bit later. Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
net/9p/client.c | 2 +-
1 file changed, 1 insertion(+), 1 de
On 2017/8/15 11:45, Jaegeuk Kim wrote:
> On 08/07, Chao Yu wrote:
>> From: Chao Yu
>>
>> Commit d618ebaf0aa8 ("f2fs: enable small discard by default") enables
>> f2fs to issue 4K size discard in real-time discard mode. However, issuing
>> smaller discard may cost more lifetime but releasing less f
On Tuesday, August 15, 2017 4:56:19 AM CEST Sergey Senozhatsky wrote:
> We need to switch to emergency printk mode in kernel_kexec(). One
> kernel_kexec() branch calls kernel_restart_prepare(), which updates
> `system_state', however, the other one, when user requested to
> ->preserve_context, does
On Tue, 15 Aug 2017 10:09:54 +0200,
Julia Lawall wrote:
>
> These snd_rawmidi_ops structures are only passed as the third
> argument of snd_rawmidi_set_ops. This argument is const, so the
> snd_rawmidi_ops structures can be const too.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Jul
To use this driver with 32 bit userspace applications on 64 bit
kernels a compat_ioctl is needed.
Signed-off-by: Lars Poeschel
---
drivers/tty/n_gsm.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
index 2afe5fce68e3..0a3c9665e015 10064
On Tue, Aug 15, 2017 at 10:05:46AM +0200, Ingo Molnar wrote:
> > > * Willy Tarreau wrote:
> > > >
> > > > Nowadays we could use similar methods using RDTSC providing more
> > > > accurate
> > > > counting. This doesn't provide a lot of entropy of course, given that a
> > > > 2 GHz machine will a
On 2017/8/15 15:41, Yunlong Song wrote:
> The usage message shows a wrong message for ovp option, so fix it.
>
> Signed-off-by: Yunlong Song
> ---
> mkfs/f2fs_format_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mkfs/f2fs_format_main.c b/mkfs/f2fs_format_main.c
On Mon, Aug 14, 2017 at 03:42:54PM -0700, David Rientjes wrote:
> On Mon, 14 Aug 2017, Roman Gushchin wrote:
> > +
> > +static long oom_evaluate_memcg(struct mem_cgroup *memcg,
> > + const nodemask_t *nodemask)
> > +{
> > + struct css_task_iter it;
> > + struct task_str
On 15/08/17 13:01, Thomas Gleixner wrote:
> On Tue, 15 Aug 2017, Marc Zyngier wrote:
>
>> Just because CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK is selected
>> doesn't mean that all the interrupts are using the effective
>> affinity mask. For a number of them, this mask is likely to
>> be empty.
>>
>>
On Mon, Aug 14, 2017 at 02:01:36PM -0700, John Stultz wrote:
> Fixes the following build warning:
> freq-step.c: In function ‘main’:
> freq-step.c:271:1: warning: control reaches end of non-void function
> [-Wreturn-type]
> @@ -268,4 +268,6 @@ int main(int argc, char **argv)
> ksft_
> On Mon, 14 Aug 2017, Elena Reshetova wrote:
>
> > atomic_as_refcounter.cocci script allows detecting
> > cases when refcount_t type and API should be used
> > instead of atomic_t.
> >
> > Signed-off-by: Elena Reshetova
> > ---
> > scripts/coccinelle/api/atomic_as_refcounter.cocci | 148
> +
If (quirks & QUIRK_SEC_DAI == 0) then samsung_i2s_probe() doesn't allocate
sec_dai and pri_dai->sec_dai remains Null, but samsung_i2s_remove()
performs pri_dai->sec_dai dereference in any case.
The patch removes useless reinitialization of sec_dai at
samsung_i2s_remove(), because resources are und
On 08/15/2017 10:15 PM, Roman Gushchin wrote:
Generally, oom_score_adj should have a meaning only on a cgroup level,
so extending it to the system level doesn't sound as a good idea.
But wasn't the original purpose of oom_score (and oom_score_adj) to work
on a system level, aka "normal" OOM? I
Use api pair of request_mem_region and release_mem_region
instead of release_resource.
Found by Linux Driver Verification project (linuxtesting.
Signed-off-by: Anton Vasilyev
---
v1: Fix commit based on Boris Brezillon review
---
drivers/mtd/maps/plat-ram.c | 4 ++--
1 file changed, 2 insertion
On Tue 15-08-17 19:06:28, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Tue 15-08-17 07:51:02, Tetsuo Handa wrote:
> > > Michal Hocko wrote:
> > [...]
> > > > Were you able to reproduce with other filesystems?
> > >
> > > Yes, I can reproduce this problem using both xfs and ext4 on
> > > 4.11.
On Mon 14-08-17 23:12:16, Dan Williams wrote:
> The mmap syscall suffers from the ABI anti-pattern of not validating
> unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a
> mechanism to define new behavior that is known to fail on older kernels
> without the feature. Use the fact
On Mon 07-08-17 13:38:37, Michal Hocko wrote:
> Hi,
> there are two issues this patch series attempts to fix. First one is
> something that has been broken since MMF_UNSTABLE flag introduction
> and I guess we should backport it stable trees (patch 1). The other
> issue has been brought up by Wenwe
On Tuesday, August 15, 2017 11:59:00 AM CEST Zheng, Lv wrote:
> Hi,
>
> > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> > Subject: Re: [PATCH 1/3] ACPICA: Dispatch active GPEs at init time
> >
> > On Friday, August 11, 2017 7:40:56 AM CEST Zheng, Lv wrote:
> > > Hi, Rafael
> > >
> > > > F
On Tuesday, August 15, 2017 4:12:24 AM CEST Zheng, Lv wrote:
> Hi, Rafael
>
> > From: linux-acpi-ow...@vger.kernel.org
> > [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J.
> > Wysocki
> > Subject: [PATCH 3/3] ACPI / scan: Enable GPEs before scanning the namespace
> >
> > From: Ra
On Tuesday, August 15, 2017 7:42:19 AM CEST Chen-Yu Tsai wrote:
> On Mon, Jul 24, 2017 at 7:46 PM, Rafael J. Wysocki wrote:
> > On Monday, July 24, 2017 02:23:49 PM Viresh Kumar wrote:
> >> On 23-07-17, 18:27, Icenowy Zheng wrote:
> >> > Some new Allwinner SoCs get supported in the kernel after th
On 2017/8/13 12:34, Jaegeuk Kim wrote:
> We need to check HOT_DATA to truncate any previous data block when doing
> roll-forward recovery.
>
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
> ---
> fs/f2fs/recovery.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/f
On 2017/8/14 16:52, Yunlong Song wrote:
> Signed-off-by: Yunlong Song
Reviewed-by: Chao Yu
> ---
> fs/f2fs/segment.h | 5 -
> 1 file changed, 5 deletions(-)
>
> diff --git a/fs/f2fs/segment.h b/fs/f2fs/segment.h
> index 7f700e5..b9b4f85 100644
> --- a/fs/f2fs/segment.h
> +++ b/fs/f2fs/seg
在 2017-08-15 20:25，Rafael J. Wysocki 写道：
On Tuesday, August 15, 2017 7:42:19 AM CEST Chen-Yu Tsai wrote:
On Mon, Jul 24, 2017 at 7:46 PM, Rafael J. Wysocki
wrote:
> On Monday, July 24, 2017 02:23:49 PM Viresh Kumar wrote:
>> On 23-07-17, 18:27, Icenowy Zheng wrote:
>> > Some new Allwinner SoCs
On Tue, Aug 15, 2017 at 8:25 PM, Rafael J. Wysocki wrote:
> On Tuesday, August 15, 2017 7:42:19 AM CEST Chen-Yu Tsai wrote:
>> On Mon, Jul 24, 2017 at 7:46 PM, Rafael J. Wysocki
>> wrote:
>> > On Monday, July 24, 2017 02:23:49 PM Viresh Kumar wrote:
>> >> On 23-07-17, 18:27, Icenowy Zheng wrote:
On Tue 15-08-17 01:19:16, Chen Yu wrote:
[...]
> @@ -2561,8 +2562,10 @@ void mark_free_pages(struct zone *zone)
> unsigned long i;
>
> pfn = page_to_pfn(page);
> - for (i = 0; i < (1UL << order); i++)
> + for (i =
On Mon 14-08-17 23:12:22, Dan Williams wrote:
> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> index ff151814a02d..73fdc0ada9ee 100644
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -306,6 +306,7 @@ struct vm_area_struct {
> struct mm_struct *vm_mm;
On Thu, 10 Aug 2017 19:35:33 +0200
Helge Deller wrote:
> Sometimes people seems unclear when to use the %pS or %pF printk format.
> Adding some examples may help to avoid such mistakes.
>
> See for example commit 51d96dc2e2dc ("random: fix warning message on ia64 and
> parisc") which fixed such
301 - 400 of 848 matches
Mail list logo
