On Thu, Jul 04, 2019 at 10:13:37AM +, Jose Abreu wrote:
> From: Jesper Dangaard Brouer
>
> > The page_pool DMA mapping cannot be "kept" when page traveling into the
> > network stack attached to an SKB. (Ilias and I have a long term plan[1]
> > to allow this, but you cannot do it ATM).
>
>
Hi,
> > - r = ttm_bo_reserve(&bo->tbo, true, false, NULL);
> > + r = reservation_object_lock_interruptible(bo->gem_base.resv, NULL);
> Can you elaborate a bit about how TTM keeps the BOs alive in, for
> example, virtio_gpu_transfer_from_host_ioctl? In that function, only
> three TTM
On Mon 2019-07-01 16:00:09, Geert Uytterhoeven wrote:
> When using the legacy clock framework, clock pointers are no longer
> printed as IDs, as the !CONFIG_COMMON_CLK case was accidentally
> considered an error case.
>
> Fix this by reverting to the old behavior, which allows to distinguish
> clo
On Thu, Jul 04, 2019 at 11:45:11AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Greg KH writes:
>
> > On Thu, Jul 04, 2019 at 11:25:16AM +0300, Felipe Balbi wrote:
> >>
> >> Hi,
> >>
> >> Pawel Laszczak writes:
> >>
> >> >>
> >> >>Hi,
> >> >>
> >> >>On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
On Thu, Jul 04, 2019 at 12:44:08PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Pawel Laszczak writes:
>
> >>
> >>
> >>Hi,
> >>
> >>Pawel Laszczak writes:
> >>
>
> Hi,
>
> On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
> >
> > On Thu, Jul 04, 2019 at 04:34:58PM +1000, Steph
Hi,
Greg KH writes:
> On Thu, Jul 04, 2019 at 12:44:08PM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Pawel Laszczak writes:
>>
>> >>
>> >>
>> >>Hi,
>> >>
>> >>Pawel Laszczak writes:
>> >>
>>
>> Hi,
>>
>> On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
>> >
>> > On
> > + for (i = 0; i < nents; i++) {
> > + objs->nents = i;
> This line can be moved into the if-block just below.
> > + objs->objs[i] = drm_gem_object_lookup(drm_file, handles[i]);
> > + if (!objs->objs[i]) {
> > + virtio_gpu_arr
> Gesendet: Donnerstag, 04. Juli 2019 um 12:03 Uhr
> Von: "Ran Bi"
> We had implement MT8173 poweroff function in arm-trusted-firmware's PSCI
> plat_system_off() function. MT8173 SoC is using PMIC MT6397. (Ref:
> https://github.com/ARM-software/arm-trusted-firmware/blob/master/plat/mediatek/mt817
> Gesendet: Donnerstag, 04. Juli 2019 um 11:13 Uhr
> Von: "Matthias Brugger"
> It's up to the maintainer but I don't like patches doing clean-ups together
> with
> adding support for new HW, although it's a trivial one here.
i can split again to have clean-up and new functions separated
Hi Arnaldo,
I found this issue has not been fixed in mainline now, please take a glance at
this.
On 2019/5/23 10:50, Namhyung Kim wrote:
> On Wed, May 22, 2019 at 08:08:23AM -0300, Arnaldo Carvalho de Melo wrote:
>> Em Wed, May 22, 2019 at 03:56:10PM +0900, Namhyung Kim escreveu:
>>> On Wed, May
On Thu, 4 Jul 2019 15:39:58 +0900
Masami Hiramatsu wrote:
> Hi Steve,
>
> Would you have any comment on this?
>
Hi Masami,
It's on my todo list. As today is a US holiday, I'll look at this on
Monday.
Thanks for the reminder!
-- Steve
> Thank you,
>
> On Thu, 20 Jun 2019 00:07:09 +0900
>
On 7/4/2019 12:03 PM, Jarkko Sakkinen wrote:
On Mon, 2019-07-01 at 15:15 +0200, Michal Suchanek wrote:
This reverts commit 0b6cf6b97b7ef1fa3c7fefab0cac897a1c4a3400 to avoid
following crash:
Thank you. I think this the right choice for the moment. I fixed
a trivial checkpatch.pl error and added
On Thu, 4 Jul 2019, Alexandre Ghiti wrote:
> On 7/4/19 12:57 AM, Paul Walmsley wrote:
> > On Mon, 1 Jul 2019, Alexandre Ghiti wrote:
> >
> > > - libhugetlbfs testsuite on riscv64/2M:
> > >- brk_near_huge triggers an assert in malloc.c, does not on x86.
> > I was able to reproduce the 2MB mega
Hi,
On 7/3/19 9:22 AM, Subhra Mazumdar wrote:
>
> On 7/2/19 1:54 AM, Patrick Bellasi wrote:
>> Wondering if searching and preempting needs will ever be conflicting?
>> I guess the winning point is that we don't commit behaviors to
>> userspace, but just abstract concepts which are turned into bia
On 04.07.2019 10:43, Jarkko Sakkinen wrote:
Check out tpm_tis_core.c and tpm_tis_spi.c. TPM TIS driver implements
that spec so you should only implement a new physical layer.
I had the same thought. Unfortunately, the I2C-TIS specification
introduces two relevant changes compared to tpm_tis/tp
gcc-9 complains about a blatant uninitialized variable use that
all earlier compiler versions missed:
drivers/iio/adc/rcar-gyroadc.c:510:5: warning: 'ret' may be used uninitialized
in this function [-Wmaybe-uninitialized]
Return -EINVAL instead here.
Cc: sta...@vger.kernel.org
Fixes: 059c53b323
On Mon, 2019-06-24 at 10:46 -0700, Jordan Hand wrote:
> From: Jordan Hand
>
> For TPM2-based systems, retrieve the TCG log from the TPM2 ACPI table.
> The TPM2 ACPI table is defined in section 7.3 of the TCG ACPI
> Specification (see link).
You are claiming here that this applies to all systems I
Commit message title prefix should be "ASoC: wm0010:" not "sound/soc
/codecs:". Take a look at other patches to the same files.
kmemdup is introduced to duplicate a region of memory in a neat way.
Rather than kmalloc/kzalloc + memcpy, which the programmer needs to
write the size twice (sometimes
sched_info_on() is called with unlikely hint, however, the test
is to be true when make defconfig. So replace unlikely with
likely.
Signed-off-by: Yi Wang
---
kernel/sched/stats.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/stats.h b/kernel/sched/stats.
When make defconfig, CONFIG_SCHEDSTATS is set to be y, so
sched_info_on() is 'likely' to be true. However, some functions
invoke this function with unlikely hint or use no hint. Let's
fix this.
Yi Wang (2):
kvm: x86: add likely to sched_info_on()
sched: fix unlikely use of sched_info_on()
ar
The condition to test is likely() to be true when make defconfig.
Add the hint.
Signed-off-by: Yi Wang
---
arch/x86/kvm/cpuid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
index 4992e7c..64fff41 100644
--- a/arch/x86/kvm/cpuid.c
On Thu, 2019-07-04 at 13:28 +0200, Roberto Sassu wrote:
> On 7/4/2019 12:03 PM, Jarkko Sakkinen wrote:
> > On Mon, 2019-07-01 at 15:15 +0200, Michal Suchanek wrote:
> >> This reverts commit 0b6cf6b97b7ef1fa3c7fefab0cac897a1c4a3400 to avoid
> >> following crash:
> >
> > Thank you. I think this the
Hi Arnd,
On Thu, Jul 4, 2019 at 1:38 PM Arnd Bergmann wrote:
> gcc-9 complains about a blatant uninitialized variable use that
> all earlier compiler versions missed:
>
> drivers/iio/adc/rcar-gyroadc.c:510:5: warning: 'ret' may be used
> uninitialized in this function [-Wmaybe-uninitialized]
Ac
> Still missing commit message. Describe here why you need to do that.
ok, added note that headers are reused in power-off-driver
https://github.com/frank-w/BPI-R2-4.14/commits/5.2-poweroff-mainline
> Please check your email setting as discussed offline. Otherwise your patches
> won't get accept
On Thu, Jul 04, 2019 at 10:04:35AM +0200, Jiri Pirko wrote:
> Wed, Jul 03, 2019 at 08:18:51PM CEST, mkube...@suse.cz wrote:
> >On Wed, Jul 03, 2019 at 01:49:33PM +0200, Jiri Pirko wrote:
> >> Tue, Jul 02, 2019 at 01:50:09PM CEST, mkube...@suse.cz wrote:
> >> >+Compact form: nested (bitset) atrribut
On Thu, 4 Jul 2019 10:13:37 +
Jose Abreu wrote:
> From: Jesper Dangaard Brouer
>
> > The page_pool DMA mapping cannot be "kept" when page traveling into the
> > network stack attached to an SKB. (Ilias and I have a long term plan[1]
> > to allow this, but you cannot do it ATM).
>
> The
There were discussions in the past about use cases for
simple_strto() functions and, in some rare cases,
they have a benefit over kstrto() ones.
Update a comment to reduce confusion about special use cases.
Suggested-by: Miguel Ojeda
Signed-off-by: Andy Shevchenko
---
- update comment based on
Like in the commit
8b2303de399f ("serial: core: Fix handling of options after MMIO address")
we may use simple_strtoul() which in comparison to kstrtoul() can do conversion
in-place without additional and unnecessary code to be written.
Signed-off-by: Andy Shevchenko
---
- no change since v2
d
On Wed, 2019-07-03 at 23:32 -0400, Nayna Jain wrote:
> The nr_allocated_banks and allocated banks are initialized as part of
> tpm_chip_register. Currently, this is done as part of auto startup
> function. However, some drivers, like the ibm vtpm driver, do not run
> auto startup during initializat
Hi, patch_realtek.c maintainer:
I see one issue that reboot from windows and boot to ubuntu, the audio
lost from speaker, I suspect there are some bugs in patch_realtek.c drivers,
the device is ALC295 and the device id is 0x10ec0295.
I have done the below experiments:
1. reboot from win
On Thu, 2019-07-04 at 13:52 +0200, Michal Kubecek wrote:
>
> There is still the question if it it should be implemented as a nested
> attribute which could look like the current compact form without the
> "list" flag (if there is no mask, it's a list). Or an unstructured data
> block consisting of
Hi Jesper,
> On Thu, 4 Jul 2019 10:13:37 +
> Jose Abreu wrote:
> > > The page_pool DMA mapping cannot be "kept" when page traveling into the
> > > network stack attached to an SKB. (Ilias and I have a long term plan[1]
> > > to allow this, but you cannot do it ATM).
> >
> > The reason I r
On 5/6/19 6:48 AM, Luca Abeni wrote:
[...]
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index 5b981eeeb944..3436f3d8fa8f 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -1584,6 +1584,9 @@ select_task_rq_dl(struct task_struct *p, int cpu, int
> sd
Hi Peng,
On Wed, Jul 3, 2019 at 11:10 PM Peng Ma wrote:
> So we need this patch, I make some changes,Please help me to test attatchment
> on VF50 board,
You need to change the Subject to something like:
Subject: [PATCH] dmaengine: fsl-edma: Add support for LS1028A
Also, in the commit log, pl
On Wed, 2019-07-03 at 16:37 +0200, Jiri Pirko wrote:
> Wed, Jul 03, 2019 at 03:44:57PM CEST, johan...@sipsolutions.net wrote:
> > On Wed, 2019-07-03 at 13:49 +0200, Jiri Pirko wrote:
> > >
> > > > +Value and mask must have length at least ETHTOOL_A_BITSET_SIZE bits
> > > > rounded up
> > > > +to
On Thu, Jul 04, 2019 at 01:37:47PM +0200, Arnd Bergmann wrote:
> gcc-9 complains about a blatant uninitialized variable use that
> all earlier compiler versions missed:
>
> drivers/iio/adc/rcar-gyroadc.c:510:5: warning: 'ret' may be used
> uninitialized in this function [-Wmaybe-uninitialized]
>
On 04/07/2019 11:49, Dmitry Osipenko wrote:
> 04.07.2019 10:10, Jon Hunter пишет:
>>
>> On 03/07/2019 18:00, Dmitry Osipenko wrote:
>>> 03.07.2019 19:37, Jon Hunter пишет:
On 03/07/2019 02:28, Dmitry Osipenko wrote:
> Tegra's APB DMA engine updates words counter after each transferr
Hi all,
Changes since 20190703:
The pm tree gained build failures for which I applied a fix patch.
The rdma tree still had its build failures so I used the version from
next-20190628.
The net-next tree gained a conflict against the net tree.
The mlx5-next tree gained a conflict against the rdm
Hi Wolfram,
On Thu, Jul 4, 2019 at 2:08 PM Wolfram Sang wrote:
> On Thu, Jul 04, 2019 at 01:37:47PM +0200, Arnd Bergmann wrote:
> > gcc-9 complains about a blatant uninitialized variable use that
> > all earlier compiler versions missed:
> >
> > drivers/iio/adc/rcar-gyroadc.c:510:5: warning: 'ret
ATTENTION:Sir/ Madam,
Your attention is urgently needed for claiming of an Inherited contract,
All paper works and approvals for payment will be made available with
the
contract details stated below:
CONTRACT NUMBER:NNPC/PED/KED-WR/09
JOB LOCATION WARRI/KADUNA
CONTRACT VALUE $15,561.000.00
JOB T
On Thu, Jul 4, 2019 at 12:31 PM Ilias Apalodimas
wrote:
> > On Wed, 3 Jul 2019 12:37:50 +0200
> > Jose Abreu wrote:
> 1. page pool allocs packet. The API doesn't sync but i *think* you don't have
> to
> explicitly since the CPU won't touch that buffer until the NAPI handler kicks
> in. On the
Platform drivers like to add sysfs groups to their device, but right now
they have to do it "by hand". The driver core should handle this for
them, but there is no way to get to the bus-default attribute groups as
all platform devices are "special and unique" one-off drivers/devices.
To combat th
On 04/07/19 13:46, Yi Wang wrote:
> The condition to test is likely() to be true when make defconfig.
> Add the hint.
>
> Signed-off-by: Yi Wang
> ---
> arch/x86/kvm/cpuid.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
> in
Hello,
Thanks all for your feedback!
On Wed, Jul 3, 2019 at 8:11 AM Masami Hiramatsu wrote:
>
> Hi Po-Hsu Lin,
>
> On Tue, 2 Jul 2019 13:22:26 -0600
> shuah wrote:
>
> > Hi Po-Hsu Lin,
> >
> > On 7/2/19 12:23 AM, Po-Hsu Lin wrote:
> > > The ftrace test will need to have CONFIG_FTRACE enabled to
On Thu, Jul 04, 2019 at 02:03:02PM +0200, Johannes Berg wrote:
> On Thu, 2019-07-04 at 13:52 +0200, Michal Kubecek wrote:
> >
> > There is still the question if it it should be implemented as a nested
> > attribute which could look like the current compact form without the
> > "list" flag (if ther
On Thu, Jul 04, 2019 at 07:46:13PM +0800, Yi Wang wrote:
> When make defconfig, CONFIG_SCHEDSTATS is set to be y, so
> sched_info_on() is 'likely' to be true. However, some functions
> invoke this function with unlikely hint or use no hint. Let's
> fix this.
How about remove the hint entirely? lik
On 04/07/19 04:00, wang.y...@zte.com.cn wrote:
> Do you mean we can remove ioapic_debug and apic_debug totally? If so,
> I would like to send a v2 patch to delete these two macros. :-)
>
Yes, please.
Paolo
On Thu, 2019-07-04 at 14:17 +0200, Michal Kubecek wrote:
> On Thu, Jul 04, 2019 at 02:03:02PM +0200, Johannes Berg wrote:
> > On Thu, 2019-07-04 at 13:52 +0200, Michal Kubecek wrote:
> > >
> > > There is still the question if it it should be implemented as a nested
> > > attribute which could look
On 04/07/19 04:11, wang.y...@zte.com.cn wrote:
>> For MMU_DEBUG, the way to go is to add more tracepoints, but then
>> converting all pgprintk occurrences to tracepoints would be wrong. You
>> can only find the "right" tracepoints when debugging MMU code. I do
>> have a couple patches in this are
On 04/07/19 04:11, wang.y...@zte.com.cn wrote:
>> For MMU_DEBUG, the way to go is to add more tracepoints, but then
>> converting all pgprintk occurrences to tracepoints would be wrong. You
>> can only find the "right" tracepoints when debugging MMU code. I do
>> have a couple patches in this are
Various Lantiq (now Intel) SoCs contain one or more PCIe controllers
and PHYs.
This adds a driver for the PCIe PHYs found on the Lantiq VRX200 and
ARX300 SoCs. GRX390 should also be supported as far as I can tell,
but I don't have any of these devices to further verify that.
I have tested this PCI
Add the bindings for the PCIe PHY on Lantiq VRX200 and ARX300 SoCs.
The IP block contains settings for the PHY and a PLL.
The PLL mode is configurable through a dedicated #phy-cell in .dts.
Signed-off-by: Martin Blumenstingl
---
.../bindings/phy/lantiq,vrx200-pcie-phy.yaml | 95
The mainline PCIe PHY driver has it's own devicetree node. Update the
clock alias so the mainline driver finds the clocks.
The first PCIe PHY is located at 0x1f106800 and exists on VRX200, ARX300
and GRX390.
The second PCIe PHY is located at 0x1f700400 and exists on ARX300 and
GRX390.
The third PC
The Lantiq VRX200 SoCs embed a PCIe PHY in the "sram" bus. Unlike most
other IP blocks on this SoC the register values are only 16-bit wide.
Like other IP blocks on this SoC the register values are in big endian.
The PHY embeds a PLL which can be configured in various modes. Only the
36MHz mode is
Unconditionally include the lantiq subdirectory in the phy Makefile.
All drivers in there have their dependencies maintained. One of these
(optional) dependencies is COMPILE_TEST, however this can only be
evaluated when Kconfig scans the lantiq subdirectory.
Signed-off-by: Martin Blumenstingl
--
The patch
ASoC: audio-graph-card: fix use-after-free in graph_for_each_link
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
ASoC: meson: axg-tdm-formatter: add reset to the bindings documentation
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime
Hi all,
This release produces a whole lot (over 200) of this message in my qemu
boot tests:
[1.698497] debugfs: File 'sched' already present!
Introduced by commit
43e23b6c0b01 ("debugfs: log errors when something goes wrong")
from the driver-core tree. I assume that the error(?) was alr
The patch
ASoC: meson: axg-tdm-formatter: add reset
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
regulator: max77650: add MODULE_ALIAS()
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
The patch
regulator: max77620: remove redundant assignment to variable ret
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometim
The patch
regmap: select CONFIG_REGMAP while REGMAP_SCCB is set
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Thu, 2019-07-04 at 09:19 +0200, Boris Brezillon wrote:
> +Kees for the safe-array-iteratio question.
>
> On Wed, 03 Jul 2019 16:26:46 +0200
> Philipp Zabel wrote:
>
> > Hi Ezequiel
> >
> > On Tue, 2019-07-02 at 14:00 -0300, Ezequiel Garcia wrote:
> > > From: ZhiChao Yu
> > >
> > > Introduc
On 24.06.19 11:18:45, Peter Zijlstra wrote:
> While auditing all module notifiers I noticed a whole bunch of fail
> wrt the return value. Notifiers have a 'special' return semantics.
>
> Cc: Robert Richter
> Cc: Steven Rostedt
> Cc: Ingo Molnar
> Cc: Alexei Starovoitov
> Cc: Daniel Borkmann
>
On 7/2/19 2:07 AM, Subhra Mazumdar wrote:
>
Also, systems like POWER9 has sd_llc as a pair of core only. So it
won't benefit from the limits and hence also hiding your code in
select_idle_cpu
behind static keys will be much preferred.
>>> If it doesn't hurt then I don't see
04.07.2019 15:08, Jon Hunter пишет:
>
> On 04/07/2019 11:49, Dmitry Osipenko wrote:
>> 04.07.2019 10:10, Jon Hunter пишет:
>>>
>>> On 03/07/2019 18:00, Dmitry Osipenko wrote:
03.07.2019 19:37, Jon Hunter пишет:
>
> On 03/07/2019 02:28, Dmitry Osipenko wrote:
>> Tegra's APB DMA eng
On Thu, 04 Jul 2019 09:32:13 -0300
Ezequiel Garcia wrote:
> On Thu, 2019-07-04 at 09:19 +0200, Boris Brezillon wrote:
> > +Kees for the safe-array-iteratio question.
> >
> > On Wed, 03 Jul 2019 16:26:46 +0200
> > Philipp Zabel wrote:
> >
> > > Hi Ezequiel
> > >
> > > On Tue, 2019-07-02 at 1
From: Colin Ian King
The variable err is being assigned with a value that is never
read and it is being updated in the next statement with a new value.
The assignment is redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/su
Hi Philipp,
Thanks a lot for reviewing.
On Wed, 2019-07-03 at 16:29 +0200, Philipp Zabel wrote:
> On Tue, 2019-07-02 at 14:00 -0300, Ezequiel Garcia wrote:
> > From: Pawel Osciak
> >
> > Add the parsed VP8 frame pixel format and controls, to be used
> > with the new stateless decoder API for VP
On Thu, Jul 04, 2019 at 10:24:50PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> This release produces a whole lot (over 200) of this message in my qemu
> boot tests:
>
> [1.698497] debugfs: File 'sched' already present!
>
> Introduced by commit
>
> 43e23b6c0b01 ("debugfs: log errors when
Hello Yamada-san
Thanks for your review of this patch. Answers below
On 7/4/2019 2:43 AM, Masahiro Yamada wrote:
CCed a couple of people.
On Mon, Jun 17, 2019 at 3:15 PM Cedric Hombourger
wrote:
Debian-based distributions place libc header files in a machine
specific directory (/usr/include/
On Thu, 4 Jul 2019 13:22:40 +0300
Ivan Khoronzhuk wrote:
> On Wed, Jul 03, 2019 at 07:40:13PM +0200, Jesper Dangaard Brouer wrote:
> >On Wed, 3 Jul 2019 13:18:59 +0300
> >Ivan Khoronzhuk wrote:
> >
> >> First of all, it is an absolute requirement that each RX-queue have
> >> their own page_po
On Thu, Jul 04, 2019 at 07:03:52PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the hmm tree got a conflict in:
>
> include/linux/ioport.h
>
> between commit:
>
> ae9e13d621d6 ("x86/e820, ioport: Add a new I/O resource descriptor
> IORES_DESC_RESERVED")
> 5da0
On Thu, Jul 04, 2019 at 08:01:39PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> drivers/dax/dax-private.h
>
> between commit:
>
> ea31d5859f58 ("device-dax: use the dev_pagemap internal refcount")
>
> from the hmm tre
From: Colin Ian King
The variable 'changed' is being initialized with a value that is never
read and it is being updated later with a new value. The initialization
is redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
sound/pci/hda/patch_ca0132
On Thu, Jul 04, 2019 at 08:09:56PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> include/linux/mm.h
>
> between commit:
>
> 25b2995a35b6 ("mm: remove MEMORY_DEVICE_PUBLIC support")
>
> from the hmm tree and commit:
>
On 25.06.19 09:42:14, Peter Zijlstra wrote:
> On Mon, Jun 24, 2019 at 04:58:10PM -0400, Frank Ch. Eigler wrote:
> > From peterz's comments, the patches, it's not obvious to me how one is
> > to choose between 0 (NOTIFY_DONE) and 1 (NOTIFY_OK) in the case of a
> > routine success.
>
> I'm not sure
On Thu, Jul 04, 2019 at 02:14:28PM +0200, Arnd Bergmann wrote:
> On Thu, Jul 4, 2019 at 12:31 PM Ilias Apalodimas
> wrote:
> > > On Wed, 3 Jul 2019 12:37:50 +0200
> > > Jose Abreu wrote:
>
> > 1. page pool allocs packet. The API doesn't sync but i *think* you don't
> > have to
> > explicitly s
From: Colin Ian King
The variable ret is being initialized with a value that is never
read and it is being updated later with a new value. The
initialization is redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
drivers/infiniband/core/uverbs_c
On Thu, Jul 04, 2019 at 02:21:52PM +0200, Johannes Berg wrote:
> On Thu, 2019-07-04 at 14:17 +0200, Michal Kubecek wrote:
> > On Thu, Jul 04, 2019 at 02:03:02PM +0200, Johannes Berg wrote:
> > > On Thu, 2019-07-04 at 13:52 +0200, Michal Kubecek wrote:
> > > >
> > > > There is still the question if
On Thu, Jul 04, 2019 at 08:55:36PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> mm/memory_hotplug.c
>
> between commit:
>
> 514caf23a70f ("memremap: replace the altmap_valid field with a
> PGMAP_ALTMAP_VALID flag")
>
On Thu, 4 Jul 2019 at 04:10, Peng Ma wrote:
>
> Hi Krzysztof,
>
> I am sorry, It is my mistake to forget about VF50 used EDMA IP with little
> endian.
> The Register(CHCFG0 - CHCFG15) of our platform designed as follows:
> *-
The functions torture_onoff_cleanup, torture_shuffle_cleanup are declared
as static and marked as EXPORT_SYMBOL. It's a bit confusing for an
internal function to be exported. The area of visibility for such function
is its .c file and all other modules. Other *.c files of the same module
can't use
> From: Bartosz Golaszewski
>
> Define a MODULE_ALIAS() in the LED sub-driver for max77650 so that
> the appropriate module gets loaded together with the core mfd driver.
>
> Signed-off-by: Bartosz Golaszewski
ACK.
Pavel
Thank you all for your review comments !
From: Ilias Apalodimas
> That's why i was concerned on what will happen on > 1000b frames and what the
> memory pressure is going to be.
> The trade off here is copying vs mapping/unmapping.
Well, the performance numbers I mentioned are for TSO with def
On 04/07/2019 06:27, Matthew Wilcox wrote:
> On Wed, Jul 03, 2019 at 02:28:41PM -0700, Dan Williams wrote:
<>
>>> +#ifdef CONFIG_XARRAY_MULTI
>>> + unsigned int sibs = xas->xa_sibs;
>>> +
>>> + while (sibs) {
>>> + order++;
>>> + sibs /= 2;
>>> + }
>>
>
On Wed, 2019-07-03 at 13:39 -0400, Nicolas Dufresne wrote:
> Le mardi 02 juillet 2019 à 14:00 -0300, Ezequiel Garcia a écrit :
> > From: Pawel Osciak
> >
> > Add the parsed VP8 frame pixel format and controls, to be used
> > with the new stateless decoder API for VP8 to provide parameters
> > for
Hi Jason,
On Thu, 4 Jul 2019 12:55:43 + Jason Gunthorpe wrote:
>
> On Thu, Jul 04, 2019 at 08:55:36PM +1000, Stephen Rothwell wrote:
> >
> > Today's linux-next merge of the akpm-current tree got a conflict in:
> >
> > mm/memory_hotplug.c
> >
> > between commit:
> >
> > 514caf23a70f ("
On Wed, Jul 03, 2019 at 08:14:30PM -0700, Kris Van Hees wrote:
> +/*
> + * Read the data_head offset from the header page of the ring buffer. The
> + * argument is declared 'volatile' because it references a memory mapped page
> + * that the kernel may be writing to while we access it here.
> + */
On Wed, Jul 03, 2019 at 08:14:30PM -0700, Kris Van Hees wrote:
> +int dt_bpf_attach(int event_id, int bpf_fd)
> +{
> + int event_fd;
> + int rc;
> + struct perf_event_attr attr = {};
> +
> + attr.type = PERF_TYPE_TRACEPOINT;
> + attr.samp
On Thu, 04 Jul 2019 10:00:33 -0300
Ezequiel Garcia wrote:
>
> Oops, this is just an internal note, it seems I forgot to remove this one.
>
> > I am right to think that this is basically the size in bits of the
> > frame header ? Maybe it could be another way to formulate it ? I'm just
> > tryi
Hi Jose,
> Thank you all for your review comments !
>
> From: Ilias Apalodimas
>
> > That's why i was concerned on what will happen on > 1000b frames and what
> > the
> > memory pressure is going to be.
> > The trade off here is copying vs mapping/unmapping.
>
> Well, the performance number
On Thu, 2019-07-04 at 09:43 +0900, Masahiro Yamada wrote:
> CCed a couple of people.
>
> On Mon, Jun 17, 2019 at 3:15 PM Cedric Hombourger
> wrote:
> > Debian-based distributions place libc header files in a machine
> > specific directory (/usr/include/) instead of
> > /usr/include/asm to support
On Thu, 2019-07-04 at 14:53 +0200, Michal Kubecek wrote:
>
> > value: 0b'00xx''
> > mask: 0b'0011''
>
> One scenario that I can see from the top of my head would be user
> running
>
> ethtool -s advertise 0x...
The "0x..." here would
On Wed, 03 Jul 2019 18:32:10 +0200,
Fuqian Huang wrote:
>
> kmemdup is introduced to duplicate a region of memory in a neat way.
> Rather than kmalloc/kzalloc + memcpy, which the programmer needs to
> write the size twice (sometimes lead to mistakes), kmemdup improves
> readability, leads to small
On Thu, 04 Jul 2019 14:44:25 +0200,
Colin King wrote:
>
> From: Colin Ian King
>
> The variable 'changed' is being initialized with a value that is never
> read and it is being updated later with a new value. The initialization
> is redundant and can be removed.
>
> Addresses-Coverity: ("Unused
On 19/06/19 12:31, Paolo Bonzini wrote:
>> I'm a bit unsure if 'bd->last' is always set; it's quite obvious that
>> it's present if set, but what about requests with 'bd->last == false' ?
>> Is there a guarantee that they will _always_ be followed with a request
>> with bd->last == true?
>> And if
On Thu, Jul 4, 2019 at 5:37 AM Fuqian Huang wrote:
>
> Several drivers cast a struct device pointer to a struct
> platform_device pointer only to then call platform_get_drvdata().
> To improve readability, these constructs can be simplified
> by using dev_get_drvdata() directly.
v1 had been appli
On Thu, Jul 04, 2019 at 11:01:33PM +1000, Stephen Rothwell wrote:
> Hi Jason,
>
> On Thu, 4 Jul 2019 12:55:43 + Jason Gunthorpe wrote:
> >
> > On Thu, Jul 04, 2019 at 08:55:36PM +1000, Stephen Rothwell wrote:
> > >
> > > Today's linux-next merge of the akpm-current tree got a conflict in:
>
On Thu, Jul 4, 2019 at 11:47 AM Greg Kroah-Hartman
wrote:
>
> Platform drivers now have the option to have the platform core create
> and remove any needed sysfs attribute files. So take advantage of that
> and do not register "by hand" a lid sysfs file.
>
Acked-by: Andy Shevchenko
> Cc: Darre
201 - 300 of 652 matches
Mail list logo
