From: Akash Gajjar
ROCK Pi 4 is RK3399 based SBC from radxa.com. board has a 1G/2G/4G lpddr4, CSI,
DSI, HDMI, OTG, USB 2.0, USB 3.0, 10/100/1000 RGMII Ethernet Phy, es8316 codec,
POE, WIFI (for Model B only), PCIE M.2 support on board.
This patch enables
- HDMI Display
- Console
- MMC, EMMC
-
On Thu, 27 Dec 2018 09:46:31 +0100,
Jian-Hong Pan wrote:
>
> The headset mic of ASUS laptops like UX533FD, UX433FN and UX333FA, whose
> CODEC is Realtek ALC294 has jack auto detection feature. This patch
> enables the feature.
>
> Signed-off-by: Daniel Drake
> Signed-off-by: Jian-Hong Pan
On Wed, 26 Dec 2018 18:57:47 +0100,
Pierre-Louis Bossart wrote:
>
>
> On 12/25/18 8:29 PM, Kangjie Lu wrote:
> > snd_pcm_lib_malloc_pages() may fail, so let's check its status and
> > return its error code upstream.
>
> Acked-by: Pierre-Louis Bossart
This fixes a potential kernel Oops. Mark,
On Tue, Jan 01, 2019 at 12:12:14PM +0530, Murali Krishna Policharla wrote:
> Store newly configured mtu settings in the netdevice after mtu
> configuration is successful to the dsa switch.
Hi Murali
Please could you give more details. net/dsa/slave.c does not have a
ndo_change_mtu function, so i
On Mon, 24 Dec 2018 09:42:48 +0100,
huang.zijiang wrote:
>
> From: "huang.zijiang"
>
> kmemdup has implemented the function that kmalloc() and memcpy().
>
> Signed-off-by: huang.zijiang
> ---
> sound/pci/emu10k1/emufx.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff
On Wed, 26 Dec 2018 02:40:51 +0100,
Kangjie Lu wrote:
>
> snd_ctl_add() could fail, so let's check its status and issue an error
> message if it indeed fails.
>
> Signed-off-by: Kangjie Lu
The function itself prints the error in most of useful cases, so the
extra error here would be
On Wed, 26 Dec 2018 02:45:32 +0100,
Kangjie Lu wrote:
>
> snd_ctl_add() could fail, so let's check its return value and return its
> error code upstream upon failure.
>
> Signed-off-by: Kangjie Lu
> ---
> sound/isa/sb/sb16_main.c | 10 --
> 1 file changed, 8 insertions(+), 2
I suggested a patch for loading modules from interruptible mode, but
this patch remained unclaimed (
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-August/124851.html
).
For some reason I thought that this patch had been removed and did not
track the fate of this code
On Wed, 26 Dec 2018 04:39:31 +0100,
Kangjie Lu wrote:
>
> The fix checks if snd_card_register() fails, and if so, issues a
> warning.
>
> Signed-off-by: Kangjie Lu
Hmm, you submitted multiple patches doing the similar things but the
error messages are handled completely differently in both
On Wed, 26 Dec 2018 06:12:04 +0100,
Kangjie Lu wrote:
>
> snd_i2c_sendbytes could fail. The fix checks its return value: if it
> fails, issues an error message and returns with its error code.
>
> Signed-off-by: Kangjie Lu
> ---
> sound/pci/ice1712/ews.c | 5 -
> 1 file changed, 4
Board booting logs available at https://paste.ubuntu.com/p/62SYScSRzn/
On 01/01/19 1:38 PM, pragnesh_pa...@mentor.com wrote:
From: Akash Gajjar
ROCK Pi 4 is RK3399 based SBC from radxa.com. board has a 1G/2G/4G lpddr4, CSI,
DSI, HDMI, OTG, USB 2.0, USB 3.0, 10/100/1000 RGMII Ethernet Phy,
Fengguang Wu writes:
> From: Fan Du
>
> When allocate page, DRAM and PMEM node should better not fall back to
> each other. This allows migration code to explicitly control which type
> of node to allocate pages from.
>
> With this patch, PMEM NUMA node can only be used in 2 ways:
> - migrate
Fengguang Wu writes:
> From: Yao Yuan
>
> Signed-off-by: Yao Yuan
> Signed-off-by: Fengguang Wu
> ---
> arch/x86/kvm/mmu.c | 12 +++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> --- linux.orig/arch/x86/kvm/mmu.c 2018-12-26 20:54:48.846720344 +0800
> +++
pstore_rom is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
Why should we need pstore_rom?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a
It is a sample for pstore_rom, using general ram rather than block device.
According to pstore_rom, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
pstore_rom is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
Why should we need pstore_rom?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a
On 01.01.2019 07:42, Murali Krishna Policharla wrote:
> Store newly configured mtu settings in the netdevice after mtu
> configuration is successful to the dsa switch.
>
At first: good that this is fixed, so far each network driver
had to do the "dev->mtu = new_mtu" in its ndo_change_mtu
On 01.01.2019 08:54, Kirill Tkhai wrote:
> On 01.01.2019 09:42, Murali Krishna Policharla wrote:
>> Store newly configured mtu settings in the netdevice after mtu
>> configuration is successful to the dsa switch.
>>
>> Fixes: 2315dc91a5 ("net: make dev_set_mtu() honor notification return code")
>>
Hi Andrew,
Currently net/dsa/slave.c does not have
ndo_change_mtu function. But shortly I will be submitting a separate
patch outside this fix that has ndo_change_mtu function support added to
DSA switch. As part of testing the newly added ndo_change_mtu function
for
Apologies for the delay coming back to this.
Having had a long look at the further implications of this proposed change, I
would like to withdraw the suggested patch.
I agree that is would seem excessive to have to change the PCM core to
accommodate it. Furthermore, the idea only works if is
From: Peng Hao
Fix a style error. Remove redundant space.
Signed-off-by: Peng Hao
---
drivers/misc/sgi-gru/grufault.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/sgi-gru/grufault.c b/drivers/misc/sgi-gru/grufault.c
index 93be82f..2ec5808 100644
---
> Perhaps, you can use SPDX instead of boiler plate license text in the files?
I think we can do this incrementally.
signature.asc
Description: PGP signature
From: Peng Hao
Remove unnecessary semicolon in two functions.
Signed-off-by: Peng Hao
---
drivers/misc/mic/vop/vop_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/mic/vop/vop_main.c b/drivers/misc/mic/vop/vop_main.c
index 3633202..70d4b4d 100644
Hi Pragnesh,
> On 01.01.2019, at 09:08,
> wrote:
>
> From: Akash Gajjar
>
> ROCK Pi 4 is RK3399 based SBC from radxa.com. board has a 1G/2G/4G lpddr4,
> CSI,
> DSI, HDMI, OTG, USB 2.0, USB 3.0, 10/100/1000 RGMII Ethernet Phy, es8316
> codec,
> POE, WIFI (for Model B only), PCIE M.2
Hi Pragnesh, Klaus,
Am Dienstag, 1. Januar 2019, 10:54:55 CET schrieb
klaus.go...@theobroma-systems.com:
> > On 01.01.2019, at 09:08,
> > wrote:
> >
> > From: Akash Gajjar
> >
> > ROCK Pi 4 is RK3399 based SBC from radxa.com. board has a 1G/2G/4G lpddr4,
> > CSI,
> > DSI, HDMI, OTG, USB
Hi,
with the upgrade to 4.19 in Debian sid, I experienced a regression with CIFS
filesystems.
The server is running Debian stretch with samba, the clients are running
Debian sid or stretch. With 4.18 kernels everything is fine, but with 4.19
while the mount succeeds, any read() syscall on a file
Hi all,
Greg K-H suggested to mail you guys.
I installed Linux 4.20.0-rc7 (downloaded, compiled and installed) on a Samsung
NP900X5N laptop and have noticed 3 bugs. 2 of them I found in Bugzilla and
replied on them (i915 and Nouveau issues). I am currently discussing them with
an intel
On 12/21/2018 10:35 AM, Xiaozhou Liu wrote:
> As a simple fix, just print the correct map type.
>
> Signed-off-by: Xiaozhou Liu
Applied to bpf, thanks!
Hi Andrea,
Sorry for late reply,
On Thu, 27 Dec 2018 18:09:34 +0100
Andrea Righi wrote:
> On Tue, Dec 18, 2018 at 06:24:35PM +0100, Andrea Righi wrote:,
> > On Tue, Dec 18, 2018 at 01:50:26PM +0900, Masami Hiramatsu wrote:
> > ...
> > > > Side question: there are certain symbols in
On Tue, Jan 01, 2019 at 10:16:54PM +0900, Masami Hiramatsu wrote:
...
> > > > > Do you see a nice and clean way to blacklist all these functions
> > > > > (something like arch_populate_kprobe_blacklist()), or should we just
> > > > > flag all of them explicitly with NOKPROBE_SYMBOL()?
> > > >
> >
Hi All,
On 20/12/2018 14.40, Vesa Jääskeläinen wrote:
Idea was to define preset colors in device tree as an example when you
are dealing with multi-color LEDs without PWM. In that case you only
have GPIOs to control and then have a problem what does those GPIO's mean.
With preset definitions
Hi Ingo,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e1ef035d272ef4dbfdda98e58699698305138856
commit: ffb61c6346d0f02b2a03377a3edac838c1f09b45 Revert "x86/bug: Macrofy the
BUG table section handling, to work
Hi list,
This patch set updates a few outdated links/sections in the documents of RCU.
Please take a look.
--
Junchang Wang (2):
whatisRCU.txt: correct outdated links
torture.txt: update the list of supported torture types
Documentation/RCU/torture.txt | 15 +++
Fix outdated links in whatisRCU.txt.
Signed-off-by: Junchang Wang
---
Documentation/RCU/whatisRCU.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt
index 4a68543..1ace208 100644
---
Torture types "rcu_bh" and "sched" were removed in commit "c770c82a23".
The name of torture type "rcu_busted" was changed to "busted" in commit
"b3c983142d". Two other types, "srcud" and "busted_srcud" were added in
commits "ca1d51ed98" and "2397d072f7", respectively. This patch updates
On 一, 2018-12-31 at 14:15 -0800, Florian Fainelli wrote:
>
> On 04/12/2018 19:17, Srinath Mannam wrote:
> >
> > Hi,
> >
> > Could you please provide your feedback to this patch series?
> Rui or Eduardo can we get either one of you to review the thermal
> driver
> parts of this patch series? Why
Hi,
Changes since v4:
1. Move helper to get default pattern from led-class.c to led-core.c and
rename it (build issue pointed by kbuild robot).
Changes since v3:
1. Add missing EXPORT_SYMBOL_GPL.
2. Put pattern trigger format into common file - shared between
dt-bindings and sysfs.
3. Use
Document new led-pattern property for initialization of LED triggers.
The property format is trigger-specific (except being array of
integers). For pattern trigger, the explanation of pattern format was
moved to a common file shared with sysfs ABI.
Signed-off-by: Krzysztof Kozlowski
---
Multiple LED triggers might need to access default pattern so add a
helper for that.
Signed-off-by: Krzysztof Kozlowski
---
drivers/leds/led-core.c | 43 +
include/linux/leds.h| 3 +++
2 files changed, 46 insertions(+)
diff --git
Allow initialization of pattern used in pattern trigger from Device Tree
property.
This is especially useful for embedded systems where the pattern trigger
would be used to indicate the process of boot status in a nice,
user-friendly blinking way. This initialization pattern will be used
till
Allow initialization of delays used in oneshot trigger from Device
Tree property.
This is especially useful for embedded systems where the trigger might
be used early, before bringing up user-space.
Signed-off-by: Krzysztof Kozlowski
---
drivers/leds/trigger/ledtrig-oneshot.c | 38
Allow initialization of delays used in timer trigger from Device
Tree property.
This is especially useful for embedded systems where the trigger might
be used early, before bringing up user-space.
Signed-off-by: Krzysztof Kozlowski
---
drivers/leds/trigger/ledtrig-timer.c | 34
Hi Pavel,
On 12/31/18 5:28 PM, Pavel Machek wrote:
Hi!
There is still HSV approach [0] in store. One problem with proposed
implementation is fixed algorithm of RGB <-> HSV color space conversion.
Maybe allowing for some board specific adjustments in DT would add
more flexibility.
[0]
On 12/31/18 8:15 PM, Dan Murphy wrote:
On 12/31/18 9:47 AM, Jacek Anaszewski wrote:
On 12/31/18 4:43 PM, Jacek Anaszewski wrote:
On 12/30/18 6:35 PM, Pavel Machek wrote:
On Sun 2018-12-30 18:09:35, Jacek Anaszewski wrote:
On 12/29/18 8:07 PM, Pavel Machek wrote:
Hi!
With the "color" sysfs
On Mon, Dec 31, 2018 at 12:27:13AM +0100, Christian Brauner wrote:
> On Sun, Dec 30, 2018 at 03:02:45PM -0600, Serge Hallyn wrote:
> > On Sat, Dec 29, 2018 at 11:27:56PM +0100, Christian Brauner wrote:
> > > As suggested by Andrew Morton in [1] add selftests for the new
> > >
Happy new year!
This series make some improments for the kernel latency tracers, especilly
for the wakeup tracers. The latency tracers will show us more useful
information. With this series, the wakeup tracers look like this
when display-graph is enabled:
# tracer: wakeup
#
# wakeup latency
When function_graph is used for latency tracers, relative timestamp
is more straightforward than absolute timestamp as function trace
does. This change adds relative timestamp support to function_graph
and applies to latency tracers (wakeup and irqsoff).
Signed-off-by: Changbin Du
---
This align the behavior of wakeup tracers with irqsoff latency tracer
that we record stacktrace at the beginning and end of waking up. The
stacktrace shows us what is happening in the kernel.
Signed-off-by: Changbin Du
---
kernel/trace/trace_sched_wakeup.c | 4
1 file changed, 4
This add an example about how to use funcgraph with latency tracers.
Signed-off-by: Changbin Du
---
Documentation/trace/ftrace.rst | 51 ++
1 file changed, 51 insertions(+)
diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
index
Add these info fields to funcgraph wakeup tracers:
o Show CPU info since the waker could be on a different CPU.
o Show function duration and overhead.
o Show IRQ markers.
Signed-off-by: Changbin Du
---
kernel/trace/trace_sched_wakeup.c | 5 -
1 file changed, 4 insertions(+), 1
Don't mix context flags with function duration info. Now the output looks
like this:
\# tracer: wakeup
\#
\# wakeup latency trace v1.1.5 on 4.20.0+
\#
\# latency: 593 us, #674/674, CPU#0 | (M:desktop VP:0, KP:0, SP:0 HP:0 #P:4)
Hello Linus,
Please consider pulling from
git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal linus
to receive Thermal-SoC Management updates for v4.21-rc1 with top-most
055ddb633a35845f106fb732a07c90862e0a43e5:
thermal: generic-adc: Fix adc to temp interpolation
On Tue, Jan 01, 2019 at 10:04:39PM +0800, Zhang Rui wrote:
> On 一, 2018-12-31 at 14:15 -0800, Florian Fainelli wrote:
> >
> > On 04/12/2018 19:17, Srinath Mannam wrote:
> > >
> > > Hi,
> > >
> > > Could you please provide your feedback to this patch series?
> > Rui or Eduardo can we get either
On Mon, 2018-12-31 at 16:17 -0500, Mimi Zohar wrote:
> On Sun, 2018-12-30 at 14:22 +0100, Michael Niewöhner wrote:
>
> > > difference is that on a cold boot, the TPM takes longer to initialize.
> >
> > Well, as I said. Waiting for 10, 20 or even 60 seconds in the boot manager
> > does
> > not
On Tue, 2019-01-01 at 17:15 +0100, Michael Niewöhner wrote:
> On Mon, 2018-12-31 at 16:17 -0500, Mimi Zohar wrote:
> > On Sun, 2018-12-30 at 14:22 +0100, Michael Niewöhner wrote:
> >
> > > > difference is that on a cold boot, the TPM takes longer to initialize.
> > >
> > > Well, as I said.
On Tue, 2019-01-01 at 11:38 -0500, Mimi Zohar wrote:
> On Tue, 2019-01-01 at 17:15 +0100, Michael Niewöhner wrote:
> > On Mon, 2018-12-31 at 16:17 -0500, Mimi Zohar wrote:
> > > On Sun, 2018-12-30 at 14:22 +0100, Michael Niewöhner wrote:
> > >
> > > > > difference is that on a cold boot, the TPM
[74011.275028] [ cut here ]
[74011.275031] CPA: called for zero pte. vaddr = 0 cpa->vaddr = 0
[74011.275041] WARNING: CPU: 0 PID: 33 at arch/x86/mm/pageattr.c:1466
__cpa_process_fault+0x365/0x390
[74011.275041] Modules linked in: fuse cmac cifs fscache snd_seq_dummy
I got this message this morning on Kernel 4.20.0 , mind you I have not
done anything differently as the same with kernel 4.19.6. So when this
came up this morning I figured I needed to send this in.
[74011.275028] [ cut here ]
[74011.275031] CPA: called for zero pte.
On Mon, Dec 31, 2018 at 10:50:22AM -0800, Matthew Wilcox wrote:
> On Mon, Dec 31, 2018 at 02:26:38PM +0100, Uladzislau Rezki (Sony) wrote:
> > +#ifdef CONFIG_TEST_VMALLOC_MODULE
> > +EXPORT_SYMBOL(__vmalloc_node_range);
> > +#endif
>
> Definitely needs to be _GPL.
Will upload updated variant.
On Tue, 2019-01-01 at 08:56 +0530, Manivannan Sadhasivam wrote:
> Hi Joe,
Hi Manivannan.
> On Mon, Dec 31, 2018 at 11:12:18AM -0800, Joe Perches wrote:
> > On Tue, 2019-01-01 at 00:25 +0530, Manivannan Sadhasivam wrote:
> > > Add the linux-actions mailing list for Actions Semi SoC architecture.
On Tue, Jan 01, 2019 at 04:07:44PM +0100, Christian Brauner wrote:
> On Mon, Dec 31, 2018 at 12:27:13AM +0100, Christian Brauner wrote:
> > On Sun, Dec 30, 2018 at 03:02:45PM -0600, Serge Hallyn wrote:
> > > On Sat, Dec 29, 2018 at 11:27:56PM +0100, Christian Brauner wrote:
> > > > As suggested by
Hello all,
First of all happy new year. Based on advice of Greg K-H herewith a mail
about my continuous (frustrating) issue with my laptop.
I installed various Kali linux versions up to Linux 4.20.0-rc7
(downloaded, compiled and installed) on a Samsung NP900X5N laptop and
have an issue with
On Mon, Dec 31, 2018 at 10:47:55AM -0700, shuah wrote:
> On 12/31/18 6:26 AM, Uladzislau Rezki (Sony) wrote:
> > Add the test script for the kernel test driver to analyse vmalloc
> > allocator for benchmarking and stressing purposes. It is just a kernel
> > module loader. You can specify and pass
Hi Mark,
On Mon, Dec 31, 2018 at 8:14 PM Mark Brown wrote:
> On Sat, Dec 29, 2018 at 12:13:32PM +0100, Geert Uytterhoeven wrote:
> > > Geert, do you know if anyone vould to test this?
>
> > Thanks, that seems to fix the issue with da9063-rtc.
>
> > I don't know how to trigger an actual
On Thu, Dec 20, 2018 at 07:43:35PM -0800, Florian Fainelli wrote:
> Hi all,
>
> I just painfully learned that perf would segfault when
> CONFIG_KUSER_HELPERS is disabled because it unconditionally makes use of
> it. This patch series adds an ARM test for that by leveraging the
> existing
From: Deepa Dinamani
Date: Thu, 27 Dec 2018 18:55:09 -0800
> Al Viro mentioned (Message-ID
> <20170626041334.gz10...@zeniv.linux.org.uk>)
> that there is probably a race condition
> lurking in accesses of sk_stamp on 32-bit machines.
>
> sock->sk_stamp is of type ktime_t which is always an s64.
On Tue, Jan 01, 2019 at 10:03:19PM +0800, Junchang Wang wrote:
> Fix outdated links in whatisRCU.txt.
>
> Signed-off-by: Junchang Wang
Queued and pushed, thank you!
Thanx, Paul
> ---
> Documentation/RCU/whatisRCU.txt | 4 ++--
> 1 file
On Tue, Jan 01, 2019 at 10:03:20PM +0800, Junchang Wang wrote:
> Torture types "rcu_bh" and "sched" were removed in commit "c770c82a23".
> The name of torture type "rcu_busted" was changed to "busted" in commit
> "b3c983142d". Two other types, "srcud" and "busted_srcud" were added in
> commits
On Mon, Dec 31, 2018 at 02:21:36PM -1000, Joey Pabalinas wrote:
> On Mon, Dec 31, 2018 at 12:08:54PM -0800, Paul E. McKenney wrote:
> > On Sat, Dec 29, 2018 at 09:40:20PM -1000, Joey Pabalinas wrote:
> > > On Sun, Dec 30, 2018 at 08:08:46AM +0100, Willy Tarreau wrote:
> > > > Definitely! Same, I
On Thu, Dec 20, 2018 at 03:55:53PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Dec 20, 2018 at 12:26:01PM -0500, Steven Rostedt escreveu:
> > As strncmp(str, "const", sizeof("const") is exactly the same as
> > strcmp(str, "const") use that instead, otherwise it is confusing.
> >
> >
Jacek
Thanks for the reply!
All
Happy New Year!
On 1/1/19 8:42 AM, Jacek Anaszewski wrote:
> On 12/31/18 8:15 PM, Dan Murphy wrote:
>> On 12/31/18 9:47 AM, Jacek Anaszewski wrote:
>>> On 12/31/18 4:43 PM, Jacek Anaszewski wrote:
On 12/30/18 6:35 PM, Pavel Machek wrote:
> On Sun
On Fri, Dec 21, 2018 at 02:06:18PM +0200, Adrian Hunter wrote:
> In preparation for fixing thread stack processing for the idle task,
> allocate an array of thread stacks.
>
> Signed-off-by: Adrian Hunter
> ---
> tools/perf/util/thread-stack.c | 30 ++
> 1 file
Hi Jason,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e1ef035d272ef4dbfdda98e58699698305138856
commit: 3a6532c9af1a7836da2d597f1aaca73cb16c3b97 RDMA/uverbs: Use
uverbs_attr_bundle to pass udata for write
date:
Kernel 4.19.13
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB
xHCI Controller
Around 400 "unknown event type 37" messages logged in a 2 second span.
*
Jan 01 02:08:07 computername tvheadend[2370]: linuxdvb: Auvitek AU8522
QAM/8VSB Frontend #0 : ATSC-T #0 - poll TIMEOUT
Kernel 4.19.13
*
Jan 01 02:04:20 computername kernel: xhci_hcd :00:14.0: ERROR
unknown event type 37
Jan 01 02:04:20 computername kernel: WARNING: CPU: 2 PID: 2236 at
mm/page_alloc.c:4254 __alloc_pages_nodemask+0xf52/0xfb0
Jan 01 02:04:20 computername kernel: Modules linked in: rfcomm ccm
On Tue, 2019-01-01 at 13:33 +0100, Yves-Alexis Perez wrote:
> Hi,
>
> with the upgrade to 4.19 in Debian sid, I experienced a regression with CIFS
> filesystems.
>
> The server is running Debian stretch with samba, the clients are running
> Debian sid or stretch. With 4.18 kernels everything is
On 1/1/19 3:17 AM, Larry Finger wrote:
On 12/30/18 12:39 PM, Michael Straube wrote:
Commit 6bd082af7e36 ("staging:r8188eu: use lib80211 CCMP decrypt")
is causing hardfreeze whenever the driver tries to connect to my wifi
network. That makes the driver unusable on my system. Reverting the
commit
Band together as a Bloc and take action together. (Bloc revocation).
One practice note: do not send a cease-and-desist before-hand.
Do not let your lawyer send a cease-and-desist before-hand.
If a potential defendant knows that their liberties regarding a
copyrighted work is in question
from
Since commit 89a5e15bcba87d ("gpio/mmc/of: Respect polarity in the device
tree") gpiolib-of parses the "cd-gpios" property and flips the polarity
if "cd-inverted" is also set. This results in the "cd-inverted" property
being evaluated twice, which effectively makes it a no-op:
- first in
As I explained in my original mail [0] I observed that some of my boards
were not detecting their SD card anymore:
- Meson8b Odroid-C1: the one one Kernel CI and another one on my desk
- Meson8b EC-100: on my desk
- Meson GXBB Odroid-C2: on Kernel CI
git bisect pointed to the following commit:
On 1/1/19 10:02 AM, Ivan Safonov wrote:
I suggested a patch for loading modules from interruptible mode, but this patch
remained unclaimed (
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-August/124851.html
).
So with these changes try_then_request_module() would
The GPL is not revocable despite not being a contract. It is a license
to distribute software and you cannot revoke the license on already
existing publications. All you can do is revoke the license on future
publications.
1014527
Without an attached interest you can very well revoke the
Notice the detractors always simply say "NO u can't do this!" or "No u
can't do this because this belongs to this group!".
While I explain where your rights come from, their history, and their
extent.
Detractors say "This is like when Author, after being payed millions,
tries to revoke an
On Wed, Jan 02, 2019 at 02:33:41AM +0800, kbuild test robot wrote:
> Hi Jason,
>
> FYI, the error/warning still remains.
Like binder, DRM, etc, uverbs requires architectures to support 8 byte
get_user/put_user.
For some reason microblaze only supports 8 byte for put_user, so it
fails to
On Mon, Dec 31, 2018 at 6:25 PM Pavel Machek wrote:
>
> On Wed 2018-12-26 10:37:54, Rafael J. Wysocki wrote:
> > On Wed, Dec 26, 2018 at 3:47 AM Kangjie Lu wrote:
> > >
> > > clk_prepare() could fail, so let's check its status, and if it fails,
> > > issue an error message.
> > >
> > >
From: Huazhong Tan
Date: Mon, 31 Dec 2018 10:58:29 +0800
> For HNAE3_DOWN_CLIENT calling hns3_nic_net_stop(), HNAE3_UP_CLIENT
> should call hns3_nic_net_open(), since if the number of queue or
> the map of TC has is changed before HHAE3_UP_CLIENT is called,
> it will cause problem.
>
> Also the
What promise did you rely upon?
It is the right of the property owner to revoke.
You payed the property owner (Linux Programmer 721) nothing for his
code.
He never promised you that he would forgo his right to revoke
(Read the GPLv2, there is no mention of not revoking the license.
Something
On Tue 2019-01-01 21:13:01, Rafael J. Wysocki wrote:
> On Mon, Dec 31, 2018 at 6:25 PM Pavel Machek wrote:
> >
> > On Wed 2018-12-26 10:37:54, Rafael J. Wysocki wrote:
> > > On Wed, Dec 26, 2018 at 3:47 AM Kangjie Lu wrote:
> > > >
> > > > clk_prepare() could fail, so let's check its status, and
Fix __might_sleep warning in tty/n_hdlc.c read due to copy_to_user call while
current is TASK_INTERRUPTIBLE.
This is a false positive since the code path does not depend on current state
remaining TASK_INTERRUPTIBLE.
The loop breaks out and sets TASK_RUNNING after calling copy_to_user.
This
Hi Ben, David and Daniel ,
First of all happy new year. Based on advice of Greg K-H herewith a mail
about a number of Nouveau issues with my laptop.
I installed various Kali linux versions up to Linux 4.20.0-rc7
(downloaded, compiled and installed) on a Samsung NP900X5N laptop and
have an
On Tue, Jan 1, 2019 at 9:21 PM Pavel Machek wrote:
>
> On Tue 2019-01-01 21:13:01, Rafael J. Wysocki wrote:
> > On Mon, Dec 31, 2018 at 6:25 PM Pavel Machek wrote:
> > >
> > > On Wed 2018-12-26 10:37:54, Rafael J. Wysocki wrote:
> > > > On Wed, Dec 26, 2018 at 3:47 AM Kangjie Lu wrote:
> > > >
On Mon, Dec 31, 2018 at 2:45 PM Eric Biggers wrote:
>
> KEYCTL_PKEY_QUERY is still failing basic fuzzing even after Linus' fix that
> changed Opt_err from -1 to 0. The crash is still in
> keyctl_pkey_params_parse():
>
> token = match_token(p, param_keys, args);
>
Looks like this particular issue may have been due to a touchy/finicky
connection.
I removed my tuner from my hub and removed the hub from my
motherboard's USB and put my tuner in directly.
It STILL produced the error, but after I put everything back and
played around a little, the errors
On Tue, Jan 1, 2019 at 4:06 PM Jan Vlietland wrote:
>
> Hi Ben, David and Daniel ,
>
> First of all happy new year. Based on advice of Greg K-H herewith a mail
> about a number of Nouveau issues with my laptop.
>
> I installed various Kali linux versions up to Linux 4.20.0-rc7
> (downloaded,
On Tue, Jan 1, 2019 at 8:05 AM Eduardo Valentin wrote:
>
> Please consider pulling from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
> linus
No.
I pulled and immediately unpulled again.
It doesn't even build cleanly.
Linus
On 1/1/19 3:02 AM, Ivan Safonov wrote:
I suggested a patch for loading modules from interruptible mode, but this patch
remained unclaimed (
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-August/124851.html
).
For some reason I thought that this patch had been removed
On Mon, Dec 24, 2018 at 03:23:13PM +0300, Alexey Budankov wrote:
SNIP
> @@ -2143,6 +2152,8 @@ int cmd_record(int argc, const char **argv)
> if (verbose > 0)
> pr_info("nr_cblocks: %d\n", rec->opts.nr_cblocks);
>
> + pr_debug("affinity: %s\n",
On Mon, Dec 24, 2018 at 03:24:36PM +0300, Alexey Budankov wrote:
>
> Allocate and bind AIO user space buffers to the memory nodes
> that mmap kernel buffers are bound to.
>
> Signed-off-by: Alexey Budankov
> ---
> Changes in v2:
> - implemented perf_mmap__aio_alloc, perf_mmap__aio_free,
On Mon, Dec 24, 2018 at 03:28:33PM +0300, Alexey Budankov wrote:
>
> Implement --affinity=node|cpu option for the record mode defaulting
> to system affinity mask bouncing.
>
> Signed-off-by: Alexey Budankov
> ---
> tools/perf/Documentation/perf-record.txt | 5 +
>
On Mon, Dec 24, 2018 at 03:27:17PM +0300, Alexey Budankov wrote:
SNIP
> diff --git a/tools/perf/util/mmap.c b/tools/perf/util/mmap.c
> index 742fa9a8e498..a2095e4eda4b 100644
> --- a/tools/perf/util/mmap.c
> +++ b/tools/perf/util/mmap.c
> @@ -361,6 +361,7 @@ void perf_mmap__munmap(struct
1 - 100 of 209 matches
Mail list logo
