On Wed, Oct 10, 2018 at 07:09:30PM +0200, Lubomir Rintel wrote:
> There seem to be SSP2, SSP4 and perhaps SSP5 too, but Marvel keeps their
> base addresses secret.
>
> The SSP1 and SSP3 addresses were taken from OLPC 1.75, OpenFirmware and
> kernel respectively.
Sorry for the delay. Love your
On Wed, Oct 10, 2018 at 07:09:30PM +0200, Lubomir Rintel wrote:
> There seem to be SSP2, SSP4 and perhaps SSP5 too, but Marvel keeps their
> base addresses secret.
>
> The SSP1 and SSP3 addresses were taken from OLPC 1.75, OpenFirmware and
> kernel respectively.
Sorry for the delay. Love your
Contact Allstate Funding Corporation ® for small and large loans amount. We
give out loan all kinds of loan at 2% interest rate. We also give out from.
$5000 thousand Dollars to 20 million Dollars for individuals and companies, the
credit is open to all regardless of nationality.
NOTE: All
Hi Ming
On 10/29/18 10:49 AM, Ming Lei wrote:
> On Sat, Oct 27, 2018 at 12:01:09AM +0800, Jianchao Wang wrote:
>> Merge blk_mq_try_issue_directly and __blk_mq_try_issue_directly
>> into one interface which is able to handle the return value from
>> .queue_rq callback. Due to we can only issue
Contact Allstate Funding Corporation ® for small and large loans amount. We
give out loan all kinds of loan at 2% interest rate. We also give out from.
$5000 thousand Dollars to 20 million Dollars for individuals and companies, the
credit is open to all regardless of nationality.
NOTE: All
Hi Ming
On 10/29/18 10:49 AM, Ming Lei wrote:
> On Sat, Oct 27, 2018 at 12:01:09AM +0800, Jianchao Wang wrote:
>> Merge blk_mq_try_issue_directly and __blk_mq_try_issue_directly
>> into one interface which is able to handle the return value from
>> .queue_rq callback. Due to we can only issue
Hi Rob,
On Fri, Oct 26, 2018 at 9:07 AM Rob Herring wrote:
>
> Linus,
>
> Please pull DT updates for 4.20. A bit bigger than normal as I've been
> busy this cycle. There's a few things with dependencies and a few
> things subsystem maintainers didn't pick up, so I'm taking them thru
> my tree.
Hi Rob,
On Fri, Oct 26, 2018 at 9:07 AM Rob Herring wrote:
>
> Linus,
>
> Please pull DT updates for 4.20. A bit bigger than normal as I've been
> busy this cycle. There's a few things with dependencies and a few
> things subsystem maintainers didn't pick up, so I'm taking them thru
> my tree.
Hi Alan,
Thanks for the review.
I will update the patch accordingly and send out v2.
On 10/28/2018 10:48 PM, Alan Stern wrote:
>
> On Sat, 27 Oct 2018, Cherian, George wrote:
>
>> Implement workaround for ThunderX2 Errata-129 (documented in
>> CN99XX Known Issues" available at Cavium support
Hi Alan,
Thanks for the review.
I will update the patch accordingly and send out v2.
On 10/28/2018 10:48 PM, Alan Stern wrote:
>
> On Sat, 27 Oct 2018, Cherian, George wrote:
>
>> Implement workaround for ThunderX2 Errata-129 (documented in
>> CN99XX Known Issues" available at Cavium support
On Tue, Sep 25, 2018 at 02:03:25PM +0200, Michal Hocko wrote:
> From: Andrea Arcangeli
>
> THP allocation might be really disruptive when allocated on NUMA system
> with the local node full or hard to reclaim. Stefan has posted an
> allocation stall report on 4.12 based SLES kernel which
On Tue, Sep 25, 2018 at 02:03:25PM +0200, Michal Hocko wrote:
> From: Andrea Arcangeli
>
> THP allocation might be really disruptive when allocated on NUMA system
> with the local node full or hard to reclaim. Stefan has posted an
> allocation stall report on 4.12 based SLES kernel which
From: Miles Chen
The kbuf used by page owner is allocated by kmalloc(), which means it
can use only normal memory and there might be a "out of memory"
issue when we're out of normal memory.
To solve this problem, use kvmalloc() to allocate kbuf
from normal/highmem. But there is one problem
From: Miles Chen
The kbuf used by page owner is allocated by kmalloc(), which means it
can use only normal memory and there might be a "out of memory"
issue when we're out of normal memory.
To solve this problem, use kvmalloc() to allocate kbuf
from normal/highmem. But there is one problem
On Sun, Oct 28, 2018 at 06:20:42PM -0700, Paul E. McKenney wrote:
> On Mon, Oct 29, 2018 at 12:10:03AM +0100, Andrea Parri wrote:
> > Hopefully, with Paul's proper email address this time,
> >
> > Andrea
> >
> > On Mon, Oct 29, 2018 at 12:06:27AM +0100, Andrea Parri wrote:
> > > Hi,
> > >
> >
On Sun, Oct 28, 2018 at 06:20:42PM -0700, Paul E. McKenney wrote:
> On Mon, Oct 29, 2018 at 12:10:03AM +0100, Andrea Parri wrote:
> > Hopefully, with Paul's proper email address this time,
> >
> > Andrea
> >
> > On Mon, Oct 29, 2018 at 12:06:27AM +0100, Andrea Parri wrote:
> > > Hi,
> > >
> >
When I have time I’ll have to read a few books and dig into the latest kernel
to really understand what the Linux kernel is, but during that procrastination
I want to rewrite the Linux scheduler using my code, it’s basically a binary
tree with a bunch of fixed variables with a rotating DMA
When I have time I’ll have to read a few books and dig into the latest kernel
to really understand what the Linux kernel is, but during that procrastination
I want to rewrite the Linux scheduler using my code, it’s basically a binary
tree with a bunch of fixed variables with a rotating DMA
Hi Al, David,
These have returned, so I have disabled CONFIG_SAMPLE_VFS again.
On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell
wrote:
>
> After merging the vfs tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> samples/vfs/test-fsinfo.c: In function 'fsinfo':
>
Hi Al, David,
These have returned, so I have disabled CONFIG_SAMPLE_VFS again.
On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell
wrote:
>
> After merging the vfs tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> samples/vfs/test-fsinfo.c: In function 'fsinfo':
>
On Sun, 28 Oct 2018, Anatoly Trosinenko wrote:
> Hello,
>
> When reading a file from a fuzzed cramfs image, unhandled kernel
> paging request occurs.
Hmmm... It doesn't show up on my test system.
> How to reproduce with kvm-xfstests:
> 1) Checkout the v4.19 tag, copy x86_64-config-4.14 to
On Sun, 28 Oct 2018, Anatoly Trosinenko wrote:
> Hello,
>
> When reading a file from a fuzzed cramfs image, unhandled kernel
> paging request occurs.
Hmmm... It doesn't show up on my test system.
> How to reproduce with kvm-xfstests:
> 1) Checkout the v4.19 tag, copy x86_64-config-4.14 to
Hi Geert,
On Sat, 27 Oct 2018 at 20:17, Geert Uytterhoeven wrote:
>
> Hi Firoz,
>
> On Fri, Oct 26, 2018 at 7:06 AM Firoz Khan wrote:
> > The purpose of this patch series is, we can easily add/modify/delete
> > system call table support by changing entry in syscall.tbl file
> > instead of
Hi Geert,
On Sat, 27 Oct 2018 at 20:17, Geert Uytterhoeven wrote:
>
> Hi Firoz,
>
> On Fri, Oct 26, 2018 at 7:06 AM Firoz Khan wrote:
> > The purpose of this patch series is, we can easily add/modify/delete
> > system call table support by changing entry in syscall.tbl file
> > instead of
On Mon, 2018-10-29 at 11:04 +0800, Biao Huang wrote:
> The mt2712 Ethernet IP is from Synopsys, so extend stmmac to support mt2712.
>
sorry, I forgot to add detail descriptions for these patches.
changes in v2:
--since STMMAC driver applied to most Synopsys ip Ethernet, I add
dwmac-mediatek.c to
On Mon, 2018-10-29 at 11:04 +0800, Biao Huang wrote:
> The mt2712 Ethernet IP is from Synopsys, so extend stmmac to support mt2712.
>
sorry, I forgot to add detail descriptions for these patches.
changes in v2:
--since STMMAC driver applied to most Synopsys ip Ethernet, I add
dwmac-mediatek.c to
Hi all,
Today's linux-next merge of the drivers-x86 tree got a conflict in:
drivers/platform/x86/intel_telemetry_debugfs.c
between commit:
f2c4db1bd807 ("x86/cpu: Sanitize FAM6_ATOM naming")
from Linus' tree and commit:
1a7938a632ce ("platform/x86: intel_telemetry: Get rid of custom
Hi all,
Today's linux-next merge of the drivers-x86 tree got a conflict in:
drivers/platform/x86/intel_telemetry_debugfs.c
between commit:
f2c4db1bd807 ("x86/cpu: Sanitize FAM6_ATOM naming")
from Linus' tree and commit:
1a7938a632ce ("platform/x86: intel_telemetry: Get rid of custom
This patch updates license to use SPDX-License-Identifier
instead of verbose license text.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index
This patch updates license to use SPDX-License-Identifier
instead of verbose license text.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index
move pvpanic.c from drivers/platform/x86 to drivers/misc.
following patches will use pvpanic device in arm64.
Signed-off-by: Peng Hao
---
drivers/misc/Kconfig | 7 +++
drivers/misc/Makefile | 1 +
drivers/misc/pvpanic.c | 124
Add dt-bindings document for "qemu:pvpanic-mmio".
Signed-off-by: Peng Hao
---
.../devicetree/bindings/misc/pvpanic-mmio.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/misc/pvpanic-mmio.txt
diff --git
move pvpanic.c from drivers/platform/x86 to drivers/misc.
following patches will use pvpanic device in arm64.
Signed-off-by: Peng Hao
---
drivers/misc/Kconfig | 7 +++
drivers/misc/Makefile | 1 +
drivers/misc/pvpanic.c | 124
Add dt-bindings document for "qemu:pvpanic-mmio".
Signed-off-by: Peng Hao
---
.../devicetree/bindings/misc/pvpanic-mmio.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/misc/pvpanic-mmio.txt
diff --git
By default, when ACPI tables and FDT coexist for ARM64,
current kernel takes precedence over FDT to get device information.
Virt machine in qemu provides both FDT and ACPI table. This patch
increases the way to get information through FDT.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 63
On some architectures (e.g. arm64), it's preferable to use MMIO, since
this can be used standalone. Add MMIO support to the pvpanic driver.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git
By default, when ACPI tables and FDT coexist for ARM64,
current kernel takes precedence over FDT to get device information.
Virt machine in qemu provides both FDT and ACPI table. This patch
increases the way to get information through FDT.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 63
On some architectures (e.g. arm64), it's preferable to use MMIO, since
this can be used standalone. Add MMIO support to the pvpanic driver.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git
Hi Linus,
Can you please pull the m68knommu git tree, for-next branch.
Only a single change to fix an out of bounds array access when
parsing boot command line.
Regards
Greg
The following changes since commit 35a7f35ad1b150ddf59a41dcac7b2fa32982be0e:
Linux 4.19-rc8 (2018-10-15
On Sun, Oct 28, 2018 at 7:46 PM David Miller wrote:
>
> Please pull, thanks a lot!
Pulled,
Linus
Hi Linus,
Can you please pull the m68knommu git tree, for-next branch.
Only a single change to fix an out of bounds array access when
parsing boot command line.
Regards
Greg
The following changes since commit 35a7f35ad1b150ddf59a41dcac7b2fa32982be0e:
Linux 4.19-rc8 (2018-10-15
On Sun, Oct 28, 2018 at 7:46 PM David Miller wrote:
>
> Please pull, thanks a lot!
Pulled,
Linus
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 1326bd52888a..94747eeff0fa 100644
--- a/drivers/w1/w1.c
+++ b/drivers/w1/w1.c
@@ -1196,7 +1196,7 @@ int w1_process(void *data)
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 1326bd52888a..94747eeff0fa 100644
--- a/drivers/w1/w1.c
+++ b/drivers/w1/w1.c
@@ -1196,7 +1196,7 @@ int w1_process(void *data)
Among improving the readability of the struct declarations,
this fixes a warning about incorrect brace placement
raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1_netlink.h | 28 +---
1 file changed, 13 insertions(+), 15 deletions(-)
diff
Among improving the readability of the struct declarations,
this fixes a warning about incorrect brace placement
raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1_netlink.h | 28 +---
1 file changed, 13 insertions(+), 15 deletions(-)
diff
Hi,
This is my first series of patches for the Linux kernel.
I started by familiarizing myself with coding style and
satisfying my inner OCD by cleaning the 1-wire subsystem.
Cheers,
Steffen
---
Changes since v1:
- addressed comments from Joe Perches:
- re-ran checkpatch.pl in --strict
Get size of allocation based on pointer not type.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 2 +-
drivers/w1/w1_int.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 4cbe1849fbfc..87094d99ccbe 100644
---
Hi,
This is my first series of patches for the Linux kernel.
I started by familiarizing myself with coding style and
satisfying my inner OCD by cleaning the 1-wire subsystem.
Cheers,
Steffen
---
Changes since v1:
- addressed comments from Joe Perches:
- re-ran checkpatch.pl in --strict
Get size of allocation based on pointer not type.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 2 +-
drivers/w1/w1_int.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 4cbe1849fbfc..87094d99ccbe 100644
---
This satisfies a checkpatch warning
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 23 +++
drivers/w1/w1_netlink.c | 7 +++
2 files changed, 30 insertions(+)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 6b3cdc5a09fb..48c20639f75f 100644
---
This satisfies a checkpatch warning
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 23 +++
drivers/w1/w1_netlink.c | 7 +++
2 files changed, 30 insertions(+)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 6b3cdc5a09fb..48c20639f75f 100644
---
This satisfies a checkpatch warning and is the preferred
method for notating the license.
The SPDX identifier is a legally binding shorthand, which
can be used instead of the full boiler plate text.
Signed-off-by: Steffen Vogel
---
drivers/w1/masters/ds1wm.c | 5 +
These changes fix several warnings emitted by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 38 +++---
drivers/w1/w1_family.c | 2 +-
drivers/w1/w1_io.c | 40 +---
This satisfies a checkpatch warning and is the preferred
method for notating the license.
The SPDX identifier is a legally binding shorthand, which
can be used instead of the full boiler plate text.
Signed-off-by: Steffen Vogel
---
drivers/w1/masters/ds1wm.c | 5 +
These changes fix several warnings emitted by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 38 +++---
drivers/w1/w1_family.c | 2 +-
drivers/w1/w1_io.c | 40 +---
Some SoC share one irq number between DSPI controllers.
For example, on the LX2160 board, DSPI0 and DSPI1 share one irq number.
In this case, only one DSPI controller can register successfully,
and others will fail.
Signed-off-by: Chuanhua Han
---
drivers/spi/spi-fsl-dspi.c | 4 ++--
1 file
Hi,Daniel:
On Fri, 2018-10-26 at 12:21 +0200, Daniel Vetter wrote:
> On Fri, Oct 26, 2018 at 03:22:03PM +0800, CK Hu wrote:
> > After adding dma_dev in struct drm_device and
> > drm_gem_cma_dumb_create_no_kmap(), drm_gem_cma_object could replace
> > mtk_drm_gem_obj, so use drm_gem_cma_object
Some SoC share one irq number between DSPI controllers.
For example, on the LX2160 board, DSPI0 and DSPI1 share one irq number.
In this case, only one DSPI controller can register successfully,
and others will fail.
Signed-off-by: Chuanhua Han
---
drivers/spi/spi-fsl-dspi.c | 4 ++--
1 file
Hi,Daniel:
On Fri, 2018-10-26 at 12:21 +0200, Daniel Vetter wrote:
> On Fri, Oct 26, 2018 at 03:22:03PM +0800, CK Hu wrote:
> > After adding dma_dev in struct drm_device and
> > drm_gem_cma_dumb_create_no_kmap(), drm_gem_cma_object could replace
> > mtk_drm_gem_obj, so use drm_gem_cma_object
The mt2712 Ethernet IP is from Synopsys, so extend stmmac to support mt2712.
The mt2712 Ethernet IP is from Synopsys, so extend stmmac to support mt2712.
The commit adds the device tree binding documentation for the MediaTek DWMAC
found on MediaTek MT2712.
Signed-off-by: Biao Huang
---
.../devicetree/bindings/net/mediatek-dwmac.txt | 49
1 file changed, 49 insertions(+)
create mode 100644
The commit adds the device tree binding documentation for the MediaTek DWMAC
found on MediaTek MT2712.
Signed-off-by: Biao Huang
---
.../devicetree/bindings/net/mediatek-dwmac.txt | 49
1 file changed, 49 insertions(+)
create mode 100644
Add Ethernet support for MediaTek SoCs from the mt2712 family
Signed-off-by: Biao Huang
---
drivers/net/ethernet/stmicro/stmmac/Kconfig|8 +
drivers/net/ethernet/stmicro/stmmac/Makefile |1 +
.../net/ethernet/stmicro/stmmac/dwmac-mediatek.c | 364
3
Add Ethernet support for MediaTek SoCs from the mt2712 family
Signed-off-by: Biao Huang
---
drivers/net/ethernet/stmicro/stmmac/Kconfig|8 +
drivers/net/ethernet/stmicro/stmmac/Makefile |1 +
.../net/ethernet/stmicro/stmmac/dwmac-mediatek.c | 364
3
This satifies a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 184df1fe216b..a8ead2350521 100644
--- a/drivers/w1/w1.c
This fixes a warning raised by the checkpatch tool
Signed-off-by: Steffen Vogel
---
drivers/w1/w1_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/w1_io.c b/drivers/w1/w1_io.c
index 688778cccf65..65384b332a5a 100644
--- a/drivers/w1/w1_io.c
+++
Furthermore indentation of broken lines has been fixed.
This fixes several warnings raised by the checkpatch.pl script.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 160 +++-
drivers/w1/w1_family.c | 2 +-
drivers/w1/w1_int.c |
This fixes a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 7 +--
drivers/w1/w1_int.c | 6 +-
2 files changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index a8ead2350521..cbfc3f7012de 100644
---
This satifies a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 184df1fe216b..a8ead2350521 100644
--- a/drivers/w1/w1.c
This fixes a warning raised by the checkpatch tool
Signed-off-by: Steffen Vogel
---
drivers/w1/w1_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/w1_io.c b/drivers/w1/w1_io.c
index 688778cccf65..65384b332a5a 100644
--- a/drivers/w1/w1_io.c
+++
Furthermore indentation of broken lines has been fixed.
This fixes several warnings raised by the checkpatch.pl script.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 160 +++-
drivers/w1/w1_family.c | 2 +-
drivers/w1/w1_int.c |
This fixes a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 7 +--
drivers/w1/w1_int.c | 6 +-
2 files changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index a8ead2350521..cbfc3f7012de 100644
---
This fixes a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 5 +++--
drivers/w1/w1_int.c | 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index cbfc3f7012de..4cbe1849fbfc 100644
---
As indicated by checkpatch.pl script.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 87094d99ccbe..1326bd52888a 100644
--- a/drivers/w1/w1.c
+++ b/drivers/w1/w1.c
@@ -636,7 +636,7 @@
This fixes a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 5 +++--
drivers/w1/w1_int.c | 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index cbfc3f7012de..4cbe1849fbfc 100644
---
As indicated by checkpatch.pl script.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index 87094d99ccbe..1326bd52888a 100644
--- a/drivers/w1/w1.c
+++ b/drivers/w1/w1.c
@@ -636,7 +636,7 @@
On Sat, Oct 27, 2018 at 12:01:09AM +0800, Jianchao Wang wrote:
> Merge blk_mq_try_issue_directly and __blk_mq_try_issue_directly
> into one interface which is able to handle the return value from
> .queue_rq callback. Due to we can only issue directly w/o io
> scheduler, so remove the
On Sat, Oct 27, 2018 at 12:01:09AM +0800, Jianchao Wang wrote:
> Merge blk_mq_try_issue_directly and __blk_mq_try_issue_directly
> into one interface which is able to handle the return value from
> .queue_rq callback. Due to we can only issue directly w/o io
> scheduler, so remove the
1) GRO overflow entries are not unlinked properly, resulting in list poison
pointers being dereferenced.
2) Fix bridge build with ipv6 disabled, from Nikolay Aleksandrov.
3) Direct packet access and other fixes in BPF from Daniel Borkmann.
4) gred_change_table_def() gets passed the wrong
1) GRO overflow entries are not unlinked properly, resulting in list poison
pointers being dereferenced.
2) Fix bridge build with ipv6 disabled, from Nikolay Aleksandrov.
3) Direct packet access and other fixes in BPF from Daniel Borkmann.
4) gred_change_table_def() gets passed the wrong
Hi,
I am using network device pass through mode with qemu x86(-device
vfio-pci,host=:xx:yy.z)
and “intel_iommu=on” in host kernel command line, and it shows the whole guest
memory
were pinned(vfio_pin_pages()), viewed by the “top” RES memory output. I
understand it is due
to device can DMA
Hi,
I am using network device pass through mode with qemu x86(-device
vfio-pci,host=:xx:yy.z)
and “intel_iommu=on” in host kernel command line, and it shows the whole guest
memory
were pinned(vfio_pin_pages()), viewed by the “top” RES memory output. I
understand it is due
to device can DMA
-Original Message-
From: Li Yang
Sent: 2018年10月27日 4:29
To: Xiaowei Bao
Cc: Arnd Bergmann ; Rob Herring ; Bjorn Helgaas
; Mark Rutland ; Shawn Guo
; kis...@ti.com; lorenzo.pieral...@arm.com; Greg
Kroah-Hartman ; M.h. Lian ;
Mingkai Hu ; Roy Zang ; Kate Stewart
;
-Original Message-
From: Li Yang
Sent: 2018年10月27日 4:29
To: Xiaowei Bao
Cc: Arnd Bergmann ; Rob Herring ; Bjorn Helgaas
; Mark Rutland ; Shawn Guo
; kis...@ti.com; lorenzo.pieral...@arm.com; Greg
Kroah-Hartman ; M.h. Lian ;
Mingkai Hu ; Roy Zang ; Kate Stewart
;
On Mon, Oct 29, 2018 at 10:16:43AM +0800, miles.c...@mediatek.com wrote:
> The kbuf used by page owner is allocated by kmalloc(), which means it
> can use only normal memory and there might be a "out of memory"
> issue when we're out of normal memory.
>
> Use kvmalloc() so we can also allocate
On Mon, Oct 29, 2018 at 10:16:43AM +0800, miles.c...@mediatek.com wrote:
> The kbuf used by page owner is allocated by kmalloc(), which means it
> can use only normal memory and there might be a "out of memory"
> issue when we're out of normal memory.
>
> Use kvmalloc() so we can also allocate
>> Hi
>> We are working for running android in container, but we found that binder
>> is
>> not isolated by ipc namespace. Since binder is a form of IPC and therefore
>> should
>> be tied to ipc namespace. With this patch, we can run more than one android
>> container on one host.
>> This
>> Hi
>> We are working for running android in container, but we found that binder
>> is
>> not isolated by ipc namespace. Since binder is a form of IPC and therefore
>> should
>> be tied to ipc namespace. With this patch, we can run more than one android
>> container on one host.
>> This
On Thu, Oct 18, 2018 at 12:35 AM Icenowy Zheng wrote:
>
> This patchset brings the support for Analogix ANX6345 RGB-(e)DP bridge,
> which is used by some Allwinner A64 laptops, such as Pinebook and Olimex
> TERES-I.
>
> It reuses some definitions from the ANX78xx driver that already exists
> in
On Thu, Oct 18, 2018 at 12:35 AM Icenowy Zheng wrote:
>
> This patchset brings the support for Analogix ANX6345 RGB-(e)DP bridge,
> which is used by some Allwinner A64 laptops, such as Pinebook and Olimex
> TERES-I.
>
> It reuses some definitions from the ANX78xx driver that already exists
> in
From: Rasmus Villemoes
Date: Fri, 26 Oct 2018 23:22:59 +0200
> Building with -Wformat-nonliteral, gcc complains
>
> drivers/ptp/ptp_clock.c: In function ‘ptp_clock_register’:
> drivers/ptp/ptp_clock.c:239:26: warning: format not a string literal and no
> format arguments [-Wformat-nonliteral]
From: Rasmus Villemoes
Date: Fri, 26 Oct 2018 23:22:59 +0200
> Building with -Wformat-nonliteral, gcc complains
>
> drivers/ptp/ptp_clock.c: In function ‘ptp_clock_register’:
> drivers/ptp/ptp_clock.c:239:26: warning: format not a string literal and no
> format arguments [-Wformat-nonliteral]
From: Linus Torvalds
Date: Sun, 28 Oct 2018 15:45:16 -0700
> On Sun, Oct 28, 2018 at 3:35 PM Stephen Rothwell
> wrote:
>>
>> After merging the origin tree, today's linux-next build (powerpc
>> ppc64_defconfig) failed like this:
>
> linux-next is back! Wheee..
>
>> 5a2de63fd1a5 ("bridge: do
From: Linus Torvalds
Date: Sun, 28 Oct 2018 15:45:16 -0700
> On Sun, Oct 28, 2018 at 3:35 PM Stephen Rothwell
> wrote:
>>
>> After merging the origin tree, today's linux-next build (powerpc
>> ppc64_defconfig) failed like this:
>
> linux-next is back! Wheee..
>
>> 5a2de63fd1a5 ("bridge: do
From: Miles Chen
The kbuf used by page owner is allocated by kmalloc(), which means it
can use only normal memory and there might be a "out of memory"
issue when we're out of normal memory.
Use kvmalloc() so we can also allocate kbuf from
normal/hihghmem on 32bit kernel.
Clamp the kbuf size to
From: Miles Chen
The kbuf used by page owner is allocated by kmalloc(), which means it
can use only normal memory and there might be a "out of memory"
issue when we're out of normal memory.
Use kvmalloc() so we can also allocate kbuf from
normal/hihghmem on 32bit kernel.
Clamp the kbuf size to
Could anyone give some clues to address count of rx_fw_discards increasing
issue?
On 2018/10/26 11:15, maowenan wrote:
> Hi，
>
> After I update version of bnx2 driver from 2.2.1 to 2.2.6, I find BCM5716
> sporadically drops packets, which
> shows in rx_fw_discards.
> C36-141-5:~ # ethtool -S
Could anyone give some clues to address count of rx_fw_discards increasing
issue?
On 2018/10/26 11:15, maowenan wrote:
> Hi，
>
> After I update version of bnx2 driver from 2.2.1 to 2.2.6, I find BCM5716
> sporadically drops packets, which
> shows in rx_fw_discards.
> C36-141-5:~ # ethtool -S
1 - 100 of 520 matches
Mail list logo
