Hi Lukasz,
2019년 2월 1일 (금) 오후 11:22, Lukasz Luba 님이 작성:
>
> Hi Chanwoo,
>
> On 2/1/19 9:44 AM, Chanwoo Choi wrote:
> > Hi,
> >
> > On 19. 1. 31. 오후 5:49, Lukasz Luba wrote:
> >> Add new table rate for BPLL for Exynos5422 SoC supporting Dynamic Memory
> >> Controller frequencies for driver's DRAM
The patch titled
`signal: Never allocate siginfo for SIGKILL or SIGSTOP`
created a regression for users of PTRACE_GETSIGINFO needing to
discern signals that were raised via the tgkill syscall.
A notable user of this tgkill+ptrace combination is lldb while
debugging a multithreaded program. Without
Hello!
On 02.02.2019 17:39, Huazhong Tan wrote:
From: Jian Shen
When user disables vlan filter, and adds vlan device, it won't
notify the driver the update the vlan filter. In this case, when
To update, perhaps?
user enables vlan filter again, the packets with new vlan tag
will be filt
On Sat, 2 Feb 2019 20:19:26 -0300
Paul Cercueil wrote:
> Add the backend code for the jz4780-bch driver to support the JZ4740
> SoC from Ingenic.
>
> Signed-off-by: Paul Cercueil
> ---
>
> Changes:
>
> v2: New patch
>
> drivers/mtd/nand/raw/ingenic/Makefile | 2 +-
> drivers/mtd/
Want to retouch your photos? we can help you.
Deep etching or masking for your photos, or even adding clipping path.
Retouching also if needed.
Hopefully to start something for you soon.
Thanks,
Grace
Ingolsdtadt
Nettetal
On Sat, 2 Feb 2019 20:19:21 -0300
Paul Cercueil wrote:
> Add support for probing the jz4780-nand driver on the JZ4740 SoC from
> Ingenic.
>
> Signed-off-by: Paul Cercueil
> ---
>
> Changes:
>
> v2: - Add support for the JZ4740 and not the JZ4725B: they behave the
> same, and JZ4740 is
On Sat, 2 Feb 2019 20:19:23 -0300
Paul Cercueil wrote:
> The Ben Nanonote from Qi Hardware expects a specific OOB layout on its
> NAND. If the "ingenic,oob-layout" device property is set to "qi,lb60",
> this specific OOB layout is used.
I'm really not a big fan of this ingenic,oob-layout proper
On Sat, 2 Feb 2019 20:19:22 -0300
Paul Cercueil wrote:
> The boot ROM of the JZ4725B SoC expects a specific OOB layout on the
> NAND.
>
> Add an optional "ingenic,oob-layout" device property. When set to
> "ingenic,jz4725b", this specific OOB layout is used.
It's a SoC-specific layout, please
On Sat, 2 Feb 2019 20:19:17 -0300
Paul Cercueil wrote:
> Hi,
>
> As requested by Boris, I added a patch to move all the Ingenic NAND
> drivers to their own directory.
>
> In this V2 I added support for the JZ4740 SoC. The combo of the
> jz4780-nemc, jz4780-nand and jz4740-bch now obsolete the
Add documentation to describe Xilinx ZynqMP nvmem driver
bindings.
Signed-off-by: Nava kishore Manne
Reviewed-by: Rob Herring
---
.../bindings/nvmem/xlnx,zynqmp-nvmem.txt | 47 +++
1 file changed, 47 insertions(+)
create mode 100644
Documentation/devicetree/bindings/nvmem
This patch adds zynqmp nvmem firmware driver to access the
SoC revision information from the hardware register.
Signed-off-by: Nava kishore Manne
---
Changes for v2:
-None.
Changes for v1:
-None.
Changes for RFC-V3:
-Changed nvmem_register() to dev
Nava kishore Manne (3):
firmware: xilinx: Add zynqmp_pm_get_chipid() API
dt-bindings: nvmem: Add bindings for ZynqMP nvmem driver
nvmem: zynqmp: Added zynqmp nvmem firmware driver
.../bindings/nvmem/xlnx,zynqmp-nvmem.txt | 47 ++
drivers/firmware/xilinx/zynqmp.c |
This patch adds a new API to provide access to the
hardware related data like soc revision, IDCODE... etc.
Signed-off-by: Nava kishore Manne
---
Changes for v2:
-None.
Changes for v1:
-None.
Changes for RFC-V3:
-corrected typo error in commit msg.
Hello,
I was wondering whether phy-rcar-gen2.c would use dynamically allocated
device nodes? If so, it looks like the following code could cause a
use-after-free, due to not incrementing th reference count:
for_each_child_of_node(dev->of_node, np) {
struct rcar_gen2_chann
The 'pss_locked' field of smaps_rollup was being calculated incorrectly.
It accumulated the current pss everytime a locked VMA was found. Fix
that by adding to 'pss_locked' the same time as that of 'pss' if the vma
being walked is locked.
Fixes: 493b0e9d945f ("mm: add /proc/pid/smaps_rollup")
Cc:
On Thu, Jan 31, 2019 at 04:40:00PM +0100, Johan Hovold wrote:
> On Tue, Jan 29, 2019 at 09:39:28PM -0800, Myungho Jung wrote:
> > tiocmget() and tiocmset() operations are optional and some tty drivers
> > like pty miss the operations. We need NULL check to prevent from
> > dereference.
> >
> > Sig
Thomas Gleixner wrote:
Can you please verify whether the issue is fixed with 4.19.19?
It depends on what you mean by "verify". I looked at the Linux kernel source
code and checked that the "posix-cpu-timers: Unbreak timer rearming" patch is in
4.19.19 (but not 4.19.18) and in 4.20.6 (but not
On Tue, Jan 29, 2019 at 04:52:21PM +0100, Vlastimil Babka wrote:
> On 1/29/19 1:15 AM, Andrew Morton wrote:
> > On Sun, 20 Jan 2019 17:10:49 -0800 Sandeep Patil
> > wrote:
> >
> >> The 'pss_locked' field of smaps_rollup was being calculated incorrectly
> >> as it accumulated the current pss ever
Hi,
02/01/2019 07:31 PM에 Maninder Singh 이(가) 쓴 글:
> Hi,
>
>> On Fri, Feb 01, 2019 at 07:03:26PM +0530, Maninder Singh wrote:
>>> Hi,
>>>
>>>
>>> There is some race condition between tty_port_put and flush_to_ldisc
>>> which lead to use after free case:
>>> (Kernel 4.1)
>>>
>>> [1403.5130] Unable t
This patch gives the reader an intuitive metric of the time cost by
the kernel issuing a filesystem sync during suspend; although developer
can guess by the timestamp of next log or enable the ftrace power event
for manual calculation, this manner is easier to read and benefits the
automatic script
set_termios should not be NULL so return EOPNOTSUPP if tty driver does
not support the operation.
Reported-by: syzbot+a950165cbb86bdd02...@syzkaller.appspotmail.com
Signed-off-by: Myungho Jung
---
drivers/bluetooth/hci_ldisc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --g
From: Colin King
Date: Sat, 2 Feb 2019 11:41:29 +
> From: Colin Ian King
>
> An if statement is indented one level too deep, fix this by removing
> the extra tabs. Also add some spaces to the dev_warn arguments to clean
> up checkpatch warnings.
>
> Signed-off-by: Colin Ian King
Applied
From: Colin King
Date: Sat, 2 Feb 2019 11:45:26 +
> From: Colin Ian King
>
> A return statment is not indented correctly, fix this by adding an
> extra tab.
>
> Signed-off-by: Colin Ian King
Applied.
From: Colin King
Date: Sat, 2 Feb 2019 11:33:51 +
> From: Colin Ian King
>
> The assignment to size is indented too far, fix this and join
> two lines into one.
>
> Signed-off-by: Colin Ian King
Applied.
From: Colin King
Date: Sat, 2 Feb 2019 11:37:07 +
> From: Colin Ian King
>
> The call to bfa_ioc_pf_failed is indented too far, fix this by
> removing a tab.
>
> Signed-off-by: Colin Ian King
Applied.
From: alex.willi...@ettus.com
Date: Thu, 31 Jan 2019 13:33:27 -0800
> From: Alex Williams
>
> The DMA engine is a separate entity altogether, and this allows the DMA
> controller's address to float elsewhere in the FPGA's map.
>
> Signed-off-by: Alex Williams
Applied.
From: alex.willi...@ettus.com
Date: Thu, 31 Jan 2019 13:33:28 -0800
> From: Alex Williams
>
> Now the DMA engine is free to float elsewhere in the system map.
>
> Signed-off-by: Alex Williams
Applied.
Want to retouch your photos? we can help you.
Deep etching or masking for your photos, or even adding clipping path.
Retouching also if needed.
Hopefully to start something for you soon.
Thanks,
Grace
Fuldad
Altednburg
Add __cold to the dev_ logging functions similar to
the use of __cold in the generic printk function.
Using __cold moves all the dev_ logging functions
out-of-line possibly improving code locality and runtime
performance.
Signed-off-by: Joe Perches
---
include/linux/device.h | 20 ++
Add __cold to the netdev_ logging functions similar to
the use of __cold in the generic printk function.
Using __cold moves all the netdev_ logging functions
out-of-line possibly improving code locality and runtime
performance.
Signed-off-by: Joe Perches
---
include/linux/netdevice.h | 16 +
From: Callum Sinclair
Date: Thu, 31 Jan 2019 09:52:09 +1300
>
> -/* Close the multicast socket, and clear the vif tables etc */
> -static void mroute_clean_tables(struct mr_table *mrt, bool all)
> +/* Clear the vif tables */
> +static void mroute_clean_cache(struct mr_table *mrt, bool all)
> {
On Sat, Feb 02, 2019 at 01:15:16PM +0100, Marcel Holtmann wrote:
> Hi Myungho,
>
> > tty_set_termios() should be called with slave side of pty driver. So, If
> > tty driver is pty master, it needs to be switched to ->link.
> >
> > Reported-by: syzbot+a950165cbb86bdd02...@syzkaller.appspotmail.com
Sorry for the delay due to business travel.
On 2019/1/29 2:30, Dan Carpenter wrote:
> On Tue, Jan 29, 2019 at 12:41:55AM +0800, Chao Yu wrote:
>> Hi Dan and Xiang,
>>
>> On 2019-1-28 21:48, Gao Xiang wrote:
>>> Hi Dan,
>>>
>>> On 2019/1/28 21:33, Dan Carpenter wrote:
Hopefully, regular kmallo
On Sat, Feb 2, 2019 at 9:15 AM Oliver Hartkopp wrote:
>
> Hi all,
>
> On 02.02.19 16:34, Deepa Dinamani wrote:
> > Add new socket timeout options that are y2038 safe.
> (..)
> >
> > diff --git a/arch/alpha/include/uapi/asm/socket.h
> > b/arch/alpha/include/uapi/asm/socket.h
> > index 9826d1db71d0
Want to retouch your photos? we can help you.
Deep etching or masking for your photos, or even adding clipping path.
Retouching also if needed.
Hopefully to start something for you soon.
Thanks,
Grace
Pforzdeim
Landau
Want to retouch your photos? we can help you.
Deep etching or masking for your photos, or even adding clipping path.
Retouching also if needed.
Hopefully to start something for you soon.
Thanks,
Grace
Dordmagen
Maindtal
Commit 36c0f7f0f899 ("arch: unexport asm/shmparam.h for all
architectures") is different from the patch I submitted.
My patch is this:
https://lore.kernel.org/lkml/1546904307-11124-1-git-send-email-yamada.masah...@socionext.com/T/#u
The file renaming part:
rename include/{uapi => }/asm-generic
On Thu, Oct 18, 2018 at 4:31 AM Laurent Pinchart
wrote:
> Given that the tolerance is a property of the panel or bridge, I agree with
> Daniel that it should be implemented there, or at least in cooperation with
> drm_panel and drm_bridge.
Clock tolerance is not specified in ANX6345 datasheet.
As Dexuan reports the NVDIMM_FAMILY_HYPERV platform is incompatible with
the existing Linux namespace implementation because it uses
NSLABEL_FLAG_LOCAL for x1-width PMEM interleave sets. Quirk it as an
platform / DIMM that does not provide BLK-aperture access. Allow the
libnvdimm core to assume no
(Adding Chris Metcalf and Rusty Russell.)
If NR_CPUS == 1 due to CONFIG_SMP=n, for_each_cpu(cpu, &has_work) loop does not
evaluate "struct cpumask has_work" modified by cpumask_set_cpu(cpu, &has_work)
at
previous for_each_online_cpu() loop. Guenter Roeck found a problem among three
commits listed
tends to be cluttered because we often put various
sort of unrelated stuff in it. So, we have split out a sensible chunk
of code into a separate header from time to time.
This commit splits out the *_MAX and *_MIN defines.
The standard header contains various MAX, MIN constants
including numeri
The commit log of 44f564a4bf6a ("ipc: add definitions of USHORT_MAX
and others") did not explain why it used (s16) and (u16) instead of
(short) and (unsigned short).
Let's use (short) and (unsigned short), which is more sensible, and
more consistent with the other MAX/MIN defines.
As you see in i
On Sun, Feb 3, 2019 at 1:33 AM Alexey Dobriyan wrote:
>
> On Sun, Feb 03, 2019 at 01:06:24AM +0900, Masahiro Yamada wrote:
> > The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX
> > and others") did not explain why it used (s16) and (u16) instead of
> > (short) and (unsigned short
When releasing socket, it is possible to enter hci_sock_release() and
hci_sock_dev_event(HCI_DEV_UNREG) at the same time in different thread.
The reference count of hdev should be decremented only once from one of
them but if storing hdev to local variable in hci_sock_release() before
detached from
Hi Alexandre,
On 31.01.2019 0:48, Alexandre Belloni wrote:
>> +#endif /* CONFIG_RTC_DRV_ABEOZ9_HWMON */
> This comment is not correct
Thank you for your remarks. Can I add HMON support as Kconfig build option?
Regards,
Artem
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Signed-off-by: Christopher Diaz Riveros
---
drivers/gpu/drm/sun4i/sun8i_hdmi_phy_clk.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/sun4i/sun8i_hdmi_phy_clk.c
b/drivers/gpu/drm/sun4i/sun8i_hdmi_p
Hi,
As requested by Boris, I added a patch to move all the Ingenic NAND
drivers to their own directory.
In this V2 I added support for the JZ4740 SoC. The combo of the
jz4780-nemc, jz4780-nand and jz4740-bch now obsolete the old and dusty
jz4740-nand driver.
To support the only upstream JZ4740-b
Add the backend code for the jz4780-bch driver to support the JZ4740
SoC from Ingenic.
Signed-off-by: Paul Cercueil
---
Changes:
v2: New patch
drivers/mtd/nand/raw/ingenic/Makefile | 2 +-
drivers/mtd/nand/raw/ingenic/jz4740_bch.c | 173 ++
.../mtd/nand/raw/ingen
The jz4780-nand driver uses an API provided by the jz4780-bch driver.
This makes it difficult to support other SoCs in the jz4780-bch driver.
To work around this, we separate the API functions from the SoC-specific
code, so that these API functions are SoC-agnostic.
Signed-off-by: Paul Cercueil
-
Add the backend code for the jz4780-bch driver to support the JZ4725B
SoC from Ingenic.
Signed-off-by: Paul Cercueil
---
Changes:
v2: No changes
drivers/mtd/nand/raw/ingenic/Makefile | 2 +-
drivers/mtd/nand/raw/ingenic/jz4725b_bch.c| 234 ++
.../mtd/nand/raw/ing
Use SPDX license notifiers instead of GPLv2 license text in the headers.
Signed-off-by: Paul Cercueil
Reviewed-by: Boris Brezillon
---
Changes:
v2: No changes
drivers/mtd/nand/raw/ingenic/jz4780_bch.c | 5 +
drivers/mtd/nand/raw/ingenic/jz4780_bch.h | 5 +
drivers/mtd/nand/raw/inge
The boot ROM of the JZ4725B SoC expects a specific OOB layout on the
NAND.
Add an optional "ingenic,oob-layout" device property. When set to
"ingenic,jz4725b", this specific OOB layout is used.
Signed-off-by: Paul Cercueil
---
Changes:
v2: Instead of forcing the OOB layout, leave it to the boa
Add compatible strings to probe the jz4780-nand and jz4780-bch drivers
from devicetree on the JZ4725B and JZ4740 SoCs from Ingenic.
Signed-off-by: Paul Cercueil
---
Changes:
v2: - Change 'ingenic,jz4725b-nand' compatible string to
'ingenic,jz4740-nand' to reflect driver change
- Add '
Add support for probing the jz4780-nand driver on the JZ4740 SoC from
Ingenic.
Signed-off-by: Paul Cercueil
---
Changes:
v2: - Add support for the JZ4740 and not the JZ4725B: they behave the
same, and JZ4740 is fully upstream while JZ4725B is not. The
JZ4725B devicetree will then si
The Ben Nanonote from Qi Hardware expects a specific OOB layout on its
NAND. If the "ingenic,oob-layout" device property is set to "qi,lb60",
this specific OOB layout is used.
Signed-off-by: Paul Cercueil
---
Changes:
v2: New patch
drivers/mtd/nand/raw/ingenic/jz4780_nand.c | 37 +
Before adding support for more SoCs and seeing the number of files for
these drivers grow, we move them to their own subfolder to keep it tidy.
Signed-off-by: Paul Cercueil
---
Changes:
v2: New patch
drivers/mtd/nand/raw/Kconfig | 14 +-
drivers/mtd/nand/raw/Ma
On Tue, Jan 29, 2019 at 07:08:42PM +0800, Li RongQing wrote:
> - XA_BUG_ON(xa, xa_store_index(xa, 1, GFP_KERNEL) != NULL);
> + XA_BUG_ON(xa, xa_store_index(xa, 1, GFP_ATOMIC) != NULL);
Did you try running this change in userspace too? I don't think it'll
work.
I think the right change wo
From: Colin Ian King
There is an earlier null check on pointer dev which implies it may be null,
however the assignment of pointer pref and the call to free_ieee82011 on
a null dev can cause null pointer dereference errors. Fix this by moving
the assignment of priv and the the call to free_ieee8
From: Colin Ian King
Currently the call to cdev_add is missing a check for failure. Fix this by
checking for failure and exiting via a new error path that ensures the
allocated comp_channel struct is kfree'd.
Detected by CoverityScan, CID#1462359 ("Unchecked return value")
Fixes: 9bc79bbcd0c5 (
Dear Linux folks,
On 01.02.19 22:34, Paul Menzel wrote:
[attaching Linux messages, lspci and lsusb output]
On 01.02.19 22:20, Paul Menzel wrote:
When trying to pair a Dell Latitude E7250 running Debian Sid/unstable
with Linux 4.20 and GNOME 3.30 with an LG TV, after starting the
pairing pr
Commit "workqueue: Try to catch flush_work() without INIT_WORK()" added
a warning if flush_work() is called without worker function.
This results in the following tracebacks, typically observed during
system shutdown.
[ cut here ]
WARNING: CPU: 0 PID: 101 at kernel/workqu
When running OMAP1 kernel on QEMU, MMC access is annoyingly noisy:
MMC: CTO of 0xff and 0xfe cannot be used!
MMC: CTO of 0xff and 0xfe cannot be used!
MMC: CTO of 0xff and 0xfe cannot be used!
[ad inf.]
Emulator warnings appear to be valid. The TI document SPRU680
ping?
On 22/12/2018 11:49, Colin King wrote:
> From: Colin Ian King
>
> The comparison css->pipes[pipe].bindex < 0 is always false because
> bindex is an unsigned int. Fix this by using a signed integer for
> the comparison.
>
> Detected by CoverityScan, CID#1476023 ("Unsigned compared against
From: Colin Ian King
Multiplying two unsigned ints leads to an unsigned int result. The
intention is that the result is a unsigned long long, so to fix the
overflow cast the div to an unsigned long long to ensure that the
multiplication is on unsigned long longs to avoid overflow.
Detected by Co
[Just a reminder for the future.]
Hi all,
In commit
2bb10639f12c ("RISC-V: fix bad use of of_node_put")
Fixes tag
Fixes: 94f9bf118f ("RISC-V: Fix of_node_* refcount")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more)
[Just a reminder for the future.]
Hi all,
In commit
85bd6e61f34d ("blk-mq: fix a hung issue when fsync")
Fixes tag
Fixes: bd166ef1 (blk-mq-sched: add framework for MQ capable IO schedulers)
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.
On Fri, Feb 01, 2019 at 02:04:16PM -0800, frowand.l...@gmail.com wrote:
>Include documentation for each *function* in *source*.
> - If no *function* if specified, the documentaion for all functions
> + If no *function* if specified, the documentation for all functions
>and types in the *s
On Sat, Feb 2, 2019 at 11:12 AM Linus Torvalds
wrote:
>
> On Sat, Jan 26, 2019 at 3:31 PM Williams, Dan J
> wrote:
> >
> > Hi Linus, please pull from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> > tags/libnvdimm-fixes-5.0-rc4
>
> Hmm. One more pr-tracker-bot note: goi
On Fri, Feb 01, 2019 at 06:24:24PM +, Dexuan Cui wrote:
> > From: Kimberly Brown
> > Sent: Thursday, January 31, 2019 9:47 AM
> > ...
> > 2) Prevent a deadlock that can occur between the proposed mutex_lock()
> > call in the vmbus_chan_attr_show() function and the sysfs/kernfs functions.
> Hi
Le 2/2/19 à 9:53 AM, Marc Zyngier a écrit :
> Creating a macvtap on a DSA-backed interface results in the following
> splat when lockdep is enabled:
>
> [ 19.638080] IPv6: ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready
> [ 23.041198] device lan0 entered promiscuous mode
> [ 23.043445] dev
On Mon, Jan 28, 2019 at 11:07:34AM -0800, Reinette Chatre wrote:
Hi Sasha,
On 1/28/2019 7:56 AM, Sasha Levin wrote:
From: Babu Moger
[ Upstream commit 723f1a0dd8e26a7523ba068204bee11c95ded38d ]
Fix the messages in rdt_last_cmd_printf() and rdt_last_cmd_puts() to
make them more meaningful and
syzbot has found a reproducer for the following crash on:
HEAD commit:cd984a5be215 Merge tag 'xtensa-20190201' of git://github.c..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1725e4ff40
kernel config: https://syzkaller.appspot.com/x/.config?x=2e0064
On Sat, Jan 26, 2019 at 3:31 PM Williams, Dan J
wrote:
>
> Hi Linus, please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> tags/libnvdimm-fixes-5.0-rc4
Hmm. One more pr-tracker-bot note: going through the pull requests
from the last week, I notice that this one di
On Sat, Feb 2, 2019 at 12:52 AM Hans de Goede wrote:
>
> Hi,
>
> On 1/31/19 8:47 PM, Maxim Mikityanskiy wrote:
> > Hi,
> >
> > On Mon, Sep 24, 2018 at 5:37 PM Hans de Goede wrote:
> >>
> >> We were relying on the interrupt being shared with the ACPI SCI and the
> >> ACPI core calling irq_set_wake
The pull request you sent on Sat, 2 Feb 2019 11:10:06 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
> tags/devicetree-fixes-for-5.0-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/12491ed354d23c0ecbe02459bf4be58b8c772bc8
Thank you!
--
Deet-
The pull request you sent on Fri, 01 Feb 2019 16:06:45 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3cde55ee7921609331178c84cca485491c97df2a
Thank you!
--
Deet-doot-dot, I am a bot.
ht
> +static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev) {
> +struct dma_chan *dma_chan;
> +u32 *dma_buf;
> +dma_addr_t dma_phys;
> +int err = 0;
> +
> +if (!IS_ENABLED(CONFIG_TEGRA20_APB_DMA))
> +
On Fri, Feb 01, 2019 at 06:38:05AM +0100, Hugo Lefeuvre wrote:
> Replace schedule(); try_to_freeze() by freezable_schedule().
>
> Tasks calling freezable_schedule() set the PF_FREEZER_SKIP flag
> before calling schedule(). Unlike tasks calling schedule();
> try_to_freeze() tasks calling freezable_
On Fri, Feb 01, 2019 at 06:06:03PM +0100, Dmitry Vyukov wrote:
> On Fri, Feb 1, 2019 at 5:48 PM Dmitry Vyukov wrote:
> >
> > Hello,
> >
> > The following program creates an unkillable process that eats CPU.
> > /proc/pid/stack is empty, I am not sure what other info I can provide.
> >
> > Tested i
> > This patch adds DMA support for Tegra I2C.
> >
> > Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
> > transfer size of the max FIFO depth and DMA mode is used for transfer
> > size higher than max FIFO depth to save CPU overhead.
> >
> > PIO mode needs full intervention of
Hi Joerg,
I love your patch! Perhaps something to improve:
[auto build test WARNING on swiotlb/linux-next]
[also build test WARNING on v5.0-rc4]
[cannot apply to next-20190201]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://gi
On Fri, 1 Feb 2019, Jiri Olsa wrote:
> >
> > I've just started fuzzing with the patch applied. Often it takes a few
> > hours to trigger the bug.
>
> cool, thanks
I let it run overnight and no crash.
> > Added question about this bug. It appeared that the crash was triggered
> > by the BTS
On 2/2/19 5:05 AM, Mathieu Malaterre wrote:
> Move the static keyword around to remove the following warnings (W=1):
>
> arch/powerpc/platforms/ps3/os-area.c:212:1: error: 'static' is not at
> beginning of declaration [-Werror=old-style-declaration]
> arch/powerpc/platforms/ps3/system-bus.c:4
Creating a macvtap on a DSA-backed interface results in the following
splat when lockdep is enabled:
[ 19.638080] IPv6: ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready
[ 23.041198] device lan0 entered promiscuous mode
[ 23.043445] device eth0 entered promiscuous mode
[ 23.049255]
[ 23.
Hi Bjorn,
> On Jan 28, 2019, at 3:51 PM, Kai Heng Feng
> wrote:
[snipped]
>> If I understand correctly, the bugzilla lspci
>> (https://bugzilla.kernel.org/attachment.cgi?id=280691) was collected
>> at point 8, and it shows PME_Status=1 when it should be 0.
>>
>> If we write a 1 to PME_Status t
There are some new e1000e devices can only be woken up from D3 one time,
by plugging ethernet cable. Subsequent cable plugging does set PME bit
correctly, but it still doesn't get woken up.
Since e1000e connects to the root complex directly, we rely on ACPI to
wake it up. In this case, the GPE fro
On Mon, Jan 28, 2019 at 04:03:41PM -0500, Sean Paul wrote:
On Mon, Jan 28, 2019 at 10:56:29AM -0500, Sasha Levin wrote:
From: Sean Paul
[ Upstream commit c232e9f41b136c141df9938024e521191a7b910d ]
Instead of always re-initializing the variables we need to clean up on
out, move the re-initiali
On Mon, Jan 28, 2019 at 05:56:55PM +0100, Arnd Bergmann wrote:
On Mon, Jan 28, 2019 at 5:07 PM Sasha Levin wrote:
From: Arnaldo Carvalho de Melo
[ Upstream commit 89a0948984896352cac1ebe079cb3d64d6c3adc6 ]
To get the change in:
b7d624ab4312 ("asm-generic: unistd.h: fixup broken macro inc
On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae wrote:
>
> Copy real FS/GSBASE values instead of approximation when FSGSBASE is
> enabled.
>
> Factoring out to save_fsgs() does not result in the same behavior because
> save_base_legacy() does not copy FS/GSBASE when the index is zero.
>
> Signed-off-
On Sat, Feb 02, 2019 at 03:41:21PM +0530, Vinod Koul wrote:
> On 01-02-19, 09:47, Christoph Hellwig wrote:
> > The DMA API generally relies on a struct device to work properly, and
> > only barely works without one for legacy reasons. Pass the easily
> > available struct device from the platform_d
Hi all,
On 02.02.19 16:34, Deepa Dinamani wrote:
Add new socket timeout options that are y2038 safe.
(..)
diff --git a/arch/alpha/include/uapi/asm/socket.h
b/arch/alpha/include/uapi/asm/socket.h
index 9826d1db71d0..0d0fddb7e738 100644
--- a/arch/alpha/include/uapi/asm/socket.h
+++ b/arch/alp
On Fri, 1 Feb 2019 22:57:57 +0100
Tomasz Duszynski wrote:
> Add support for Plantower PMS7003 particulate matter sensor.
>
> Signed-off-by: Tomasz Duszynski
Other than waiting for review of the binding and potentially that minor
change to the gpio naming I suggested, this looks good to me.
Th
On Fri, Feb 1, 2019 at 12:55 PM Chang S. Bae wrote:
>
> GSBASE is used to find per-CPU data in the kernel. But when it is unknown,
> the per-CPU base can be found from the per_cpu_offset table with a CPU NR.
> The CPU NR is extracted from the limit field of the CPUNODE entry in GDT,
> or by the RD
On Fri, Feb 01, 2019 at 03:15:59PM -0800, Darren Hart wrote:
> On Tue, Jan 29, 2019 at 08:34:09AM +0100, Christoph Hellwig wrote:
> > For some odd reason dell_rbu actually seems to want the physical and
> > not a bus address for the allocated buffer. Lets assume that actually
> > is correct given
On Fri, 1 Feb 2019 22:57:59 +0100
Tomasz Duszynski wrote:
> Add device tree support for Plantower PMS7003 particulate matter sensor.
>
> Signed-off-by: Tomasz Duszynski
Hi Tomasz,
Sorry, I clearly didn't look at this in enough detail on earlier versions.
I think the set gpio is rather device
Linus,
Please pull.
Rob
The following changes since commit 75a080cde08d2dcba19ee864f9732094d93fab41:
powerpc: chrp: Use of_node_is_type to access device_type (2019-01-19
10:35:42 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
ta
On Sat, 2 Feb 2019 10:00:03 +0100
Tomasz Duszynski wrote:
> pr_fmt is used by printk wrappers. There are not any in the driver
> code so remove the format specifier.
>
> Signed-off-by: Tomasz Duszynski
Applied to the togreg branch of iio.git and pushed out
as testing for the autobuilders to mo
On Fri, 1 Feb 2019 17:01:38 +0200
Beniamin Bia wrote:
> From: Beniamin Bia
>
> The clock frequency is loaded from device-tree using clock framework
> instead of statically value. The change allow configuration of
> the device via device-trees and better initialization sequence.
> This is part o
Le 2/1/19 à 3:02 PM, Stefan Wahren a écrit :
> Hi Florian,
>
> this is the fixup version (cherry picked the patch with the reference target)
> of the dt-64-next pull request. Please consider this as a replacement for
> the broken dt-64-next pull request.
>
> The following changes since commit bfe
On Fri, 1 Feb 2019 17:01:37 +0200
Beniamin Bia wrote:
> From: Beniamin Bia
>
> The values from platform data were replaced by statically values.
> This was just a intermediate step of taking this driver out of staging and
> load data from device tree.
>
> Signed-off-by: Beniamin Bia
Applied t
1 - 100 of 239 matches
Mail list logo
