On Fri, 2019-01-11 at 08:54 -0800, Matthew Wilcox wrote:
> On Fri, Jan 11, 2019 at 08:41:43AM -0800, James Bottomley wrote:
> > On Fri, 2019-01-11 at 16:46 +0100, Hannes Reinecke wrote:
> > > > - asc_sg_head = kzalloc(sizeof(asc_scsi_q-
> > > > >sg_head)
> > > > +
> > > > -
From: Bartosz Golaszewski
The timer interrupts specified in commit 3652e2741f42 ("ARM: dts:
da850: Add clocks") are wrong but since the current timer code
hard-codes them, the bug was never spotted.
This patch must go into stable since, once we introduce a proper
clocksource driver, devices
From: Bartosz Golaszewski
Currently the timer code checks if the clock pointer passed to it is
good (!IS_ERR(clk)). The new clocksource driver expects the clock to
be functional and doesn't perform any checks so emit a warning if
clk_get() fails.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
Currently the timer code checks if the clock pointer passed to it is
good (!IS_ERR(clk)). The new clocksource driver expects the clock to
be functional and doesn't perform any checks so emit a warning if
clk_get() fails.
Signed-off-by: Bartosz Golaszewski
---
> On Jan 11, 2019, at 8:07 AM, Josh Poimboeuf wrote:
>
> On Fri, Jan 11, 2019 at 03:48:59PM +, Nadav Amit wrote:
>>> I liked the idea, BUT, how would it work for callee-saved PV ops? In
>>> that case there's only one clobbered register to work with (rax).
>>
>> That’s would be more tricky.
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm365.c | 30 +++---
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm644x.c | 36 ++
1 file changed, 23 insertions(+), 13 deletions(-)
diff --git
From: Bartosz Golaszewski
Currently the timer code checks if the clock pointer passed to it is
good (!IS_ERR(clk)). The new clocksource driver expects the clock to
be functional and doesn't perform any checks so emit a warning if
clk_get() fails.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
Currently the timer code checks if the clock pointer passed to it is
good (!IS_ERR(clk)). The new clocksource driver expects the clock to
be functional and doesn't perform any checks so emit a warning if
clk_get() fails.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
Currently the timer code checks if the clock pointer passed to it is
good (!IS_ERR(clk)). The new clocksource driver expects the clock to
be functional and doesn't perform any checks so emit a warning if
clk_get() fails.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da830.c | 56 ++-
1 file changed, 29 insertions(+), 27 deletions(-)
diff --git
From: Bartosz Golaszewski
Boards from the dm* family rely on register offset definitions from
arch/arm/mach-davinci/include/mach/time.h. We'll be removing this file
soon, so move the required defines to davinci.h where the rest of such
constants live.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm646x.c | 36 ++
1 file changed, 23 insertions(+), 13 deletions(-)
diff --git
From: Bartosz Golaszewski
All platforms have now been switched to the new clocksource driver.
Remove the old code and various no longer needed bits and pieces.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/Makefile | 3 +-
arch/arm/mach-davinci/devices-da8xx.c
From: Bartosz Golaszewski
This series removes the legacy timer code from mach-davinci in favor of
a new clocksource driver it introduces.
The first patch fixes a device tree bug that's been around for a while.
Unfortunately any systems shipped with the buggy device will stop booting
once they
From: Bartosz Golaszewski
Currently the timer code checks if the clock pointer passed to it is
good (!IS_ERR(clk)). The new clocksource driver expects the clock to
be functional and doesn't perform any checks so emit a warning if
clk_get() fails.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da850.c | 56 ++-
1 file changed, 22 insertions(+), 34 deletions(-)
diff --git
From: Bartosz Golaszewski
Currently the clocksource and clockevent support for davinci platforms
lives in mach-davinci. It hard-codes many things, used global variables,
implements functionalities unused by any platform and has code fragments
scattered across many (often unrelated) files.
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm355.c | 36 ++-
1 file changed, 23 insertions(+), 13 deletions(-)
diff --git
binvxDX550k5S.bin
Description: PGP/MIME version identification
encrypted.asc
Description: OpenPGP encrypted message
On Fri, Jan 11, 2019 at 1:19 AM Masahiro Yamada
wrote:
>
> Add hostld_flags and hostld_libs shorthands. No function change.
>
> Signed-off-by: Masahiro Yamada
Acked-by: Kees Cook
-Kees
> ---
>
> scripts/Makefile.host | 23 +--
> 1 file changed, 13 insertions(+), 10
On Fri, Jan 11, 2019 at 1:19 AM Masahiro Yamada
wrote:
>
> GCC-plugin is the only user of the shared library build rules in
> scripts/Makefile.host. Hence, those rules do not need to be treewide
> available.
>
> The build rules in scripts/Makefile.host are written in a too generic
> way. I guess
On Fri, Jan 11, 2019 at 11:51:45AM -0500, Qian Cai wrote:
> A GFP was reported,
>
> kasan: CONFIG_KASAN_INLINE enabled
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#1] SMP KASAN
> kasan_die_handler.cold.22+0x11/0x31
>
binTOtB0Q7U_6.bin
Description: PGP/MIME version identification
encrypted.asc
Description: OpenPGP encrypted message
On Thu, 10 Jan 2019 11:35:01 PST (-0800), Alistair Francis wrote:
Enable generic PCIe by default in the RISC-V defconfig, this allows us
to use QEMU's PCIe support out of the box.
Signed-off-by: Alistair Francis
---
arch/riscv/configs/defconfig | 3 +++
1 file changed, 3 insertions(+)
diff
On Thu, 3 Jan 2019 23:40:22 -0200, Otavio Salvador wrote:
> Add elgin vendor definition as 'Elgin S/A.'
>
> Signed-off-by: Otavio Salvador
> ---
>
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
Hi Linus,
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-5.0-rc2
for you to fetch changes up to
On Fri, 2019-01-11 at 17:55 +0100, Peter Zijlstra wrote:
> On Fri, Jan 11, 2019 at 07:55:03AM -0800, Bart Van Assche wrote:
> > On Fri, 2019-01-11 at 13:48 +0100, Peter Zijlstra wrote:
> > > I spotted this new v6 in my inbox and have rebased to it.
> >
> > Thanks!
> >
> > > On Wed, Jan 09, 2019
The pull request you sent on Thu, 10 Jan 2019 15:31:31 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
> tags/pci-v5.0-fixes-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/de6629eb262e0dc52a2367db38e3d2780cff5427
Thank you!
--
On 08/01/2019 10:26, Eric Auger wrote:
> Implement IOMMU_INV_TYPE_TLB invalidations. When
> nr_pages is null we interpret this as a context
> invalidation.
>
> Signed-off-by: Eric Auger
>
> ---
>
> The user API needs to be refined to discriminate context
> invalidations from NH_VA
On 01/11/2019 12:06 AM, Zhenzhong Duan wrote:
>
>
> On 2019/1/10 22:43, Waiman Long wrote:
>> On 01/10/2019 03:02 AM, Zhenzhong Duan wrote:
>>> Hi Maintainer,
>>>
>>>
>>> There is a question confused me for days. Appreciate an answer.
>>>
>>> In below code, the comment says we never have more than
On Fri, Jan 11, 2019 at 05:46:36PM +0100, Alexandre Chartre wrote:
>
>
> On 01/11/2019 04:28 PM, Josh Poimboeuf wrote:
> > On Fri, Jan 11, 2019 at 01:10:52PM +0100, Alexandre Chartre wrote:
> > > To avoid any issue with live patching the call instruction, what about
> > > toggling between two
The current version of the VMCI device only supports 32 bit PPNs,
so check whether we are truncating PPNs, and fail the operation
if we do. One such check did exist, but was wrong. Another
check was missing.
Testing through code modification: constructed PPN not representable
by 32-bit and
On Fri, Jan 11, 2019 at 07:55:03AM -0800, Bart Van Assche wrote:
> On Fri, 2019-01-11 at 13:48 +0100, Peter Zijlstra wrote:
> > I spotted this new v6 in my inbox and have rebased to it.
>
> Thanks!
>
> > On Wed, Jan 09, 2019 at 01:01:48PM -0800, Bart Van Assche wrote:
> >
> > > The changes
On Fri, Jan 11, 2019 at 08:41:43AM -0800, James Bottomley wrote:
> On Fri, 2019-01-11 at 16:46 +0100, Hannes Reinecke wrote:
> > > - asc_sg_head = kzalloc(sizeof(asc_scsi_q->sg_head)
> > > +
> > > - use_sg * sizeof(struct asc_sg_list),
> > > GFP_ATOMIC);
> > > +
On Thu, Jan 10, 2019 at 06:59:31PM -0800, John Hubbard wrote:
> On 1/3/19 6:44 AM, Jerome Glisse wrote:
> > On Thu, Jan 03, 2019 at 10:26:54AM +0100, Jan Kara wrote:
> >> On Wed 02-01-19 20:55:33, Jerome Glisse wrote:
> >>> On Wed, Dec 19, 2018 at 12:08:56PM +0100, Jan Kara wrote:
> On Tue
A GFP was reported,
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN
kasan_die_handler.cold.22+0x11/0x31
notifier_call_chain+0x17b/0x390
atomic_notifier_call_chain+0xa7/0x1b0
On 01/11/2019 04:28 PM, Josh Poimboeuf wrote:
On Fri, Jan 11, 2019 at 01:10:52PM +0100, Alexandre Chartre wrote:
To avoid any issue with live patching the call instruction, what about
toggling between two call instructions: one would be the currently active
call, while the other would
On Sat 12-01-19 00:37:05, Tetsuo Handa wrote:
> On 2019/01/12 0:07, Michal Hocko wrote:
> > On Fri 11-01-19 23:31:18, Tetsuo Handa wrote:
> >> The OOM killer invoked by [ T9694] called printk() but didn't kill
> >> anything.
> >> Instead, SIGINT from Ctrl-C killed all thread groups sharing
On Fri, 2019-01-11 at 16:46 +0100, Hannes Reinecke wrote:
> On 1/4/19 10:22 PM, Gustavo A. R. Silva wrote:
> > One of the more common cases of allocation size calculations is
> > finding the
> > size of a structure that has a zero-sized array at the end, along
> > with memory
> > for some number
On Fri, Jan 11, 2019 at 08:53:00AM +0100, Roberto Sassu wrote:
> On 1/10/2019 6:38 PM, Jarkko Sakkinen wrote:
> > On Mon, Jan 07, 2019 at 11:06:33AM +0100, Roberto Sassu wrote:
> > > On 12/22/2018 1:03 AM, Jarkko Sakkinen wrote:
> > > > On Fri, Dec 21, 2018 at 10:40:09AM +0100, Roberto Sassu
imx274_read_reg() is not used since commit ca017467c78b ("media:
imx274: add helper to read multibyte registers").
Signed-off-by: Luca Ceresoli
---
drivers/media/i2c/imx274.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/drivers/media/i2c/imx274.c
Em Thu, Jan 10, 2019 at 04:19:25PM -0800, Song Liu escreveu:
> This set catches symbol for all bpf programs loaded/unloaded
> before/during/after perf-record run PERF_RECORD_KSYMBOL and
> PERF_RECORD_BPF_EVENT.
>
> PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT includes key information
> of a bpf
On Thu, Jan 10, 2019 at 11:36 PM Dave Chinner wrote:
>
> > It's only that single page that *matters*. That's the page that the
> > probe reveals the status of - but it's also the page that the probe
> > then *changes* the status of.
>
> It changes the state of it /after/ we've already got the
Hi Namhyung,
On Fri, 2019-01-11 at 15:07 +0900, Namhyung Kim wrote:
> On Wed, Jan 09, 2019 at 01:49:17PM -0600, Tom Zanussi wrote:
> > From: Tom Zanussi
> >
> > Add a 'trace(synthetic_event_name, params)' alternative to
> > synthetic_event_name(params).
> >
> > Currently, the syntax used for
On Fri, Jan 11, 2019 at 7:59 AM Keith Busch wrote:
>
> On Fri, Jan 11, 2019 at 11:32:38AM +, Jonathan Cameron wrote:
> > On Thu, 10 Jan 2019 10:30:17 -0700
> > Keith Busch wrote:
> > > I am not aware of a real platform that has an initiator-target pair with
> > > better latency but worse
On Fri, 11 Jan 2019 22:07:29 +0900
Sergey Senozhatsky wrote:
> On (01/11/19 13:45), Petr Mladek wrote:
> > The sysrq header line is printed with an increased loglevel
> > to provide users some positive feedback.
> >
> > The original loglevel is not restored when the sysrq operation
> > is
To allow servers to verify client identity, allow a node
flag to be set that causes the sender's security context
to be delivered with the transaction. The BR_TRANSACTION
command is extended in BR_TRANSACTION_SEC_CTX to
contain a pointer to the security context string.
Signed-off-by: Todd Kjos
The sysrq header line is printed with an increased loglevel
to provide users some positive feedback.
The original loglevel is not restored when the sysrq operation
is disabled. This bug was introduced in 2.6.12 (pre-git-history)
by the commit ("Allow admin to enable only some of the Magic-Sysrq
People are sometimes confused that they do not see any output
on the console when trying to get some debugging information
using SysRq.
The messages are filtered by the current console_loglevel.
It makes some sense because a very long output might cause
troubles with a slow console.
Fortunately,
The commit 97f5f0cd8cd0a0544 ("Input: implement SysRq as a separate input
handler") added pr_fmt() definition. It caused a duplicated message
prefix in the sysrq header messages, for example:
[ 177.053931] sysrq: SysRq : Show backtrace of all active CPUs
[ 742.864776] sysrq: SysRq : HELP :
The first two patches are simple bug fixes.
The last one is RFC to fix a bug report. It is not obvious
why sysrq debug operations show only the sysrq header on
the console. The filtering by console_loglevel makes
some sense. The level can actually be set by sysrq.
The solution implemented in the
On Thu, 3 Jan 2019 14:47:05 +0100, Christian Hohnstaedt wrote:
> Add input voltage configuration options
>
> Signed-off-by: Christian Hohnstaedt
> ---
> .../devicetree/bindings/regulator/tps65218.txt | 22
> ++
> 1 file changed, 22 insertions(+)
>
Reviewed-by: Rob
On Fri, 2019-01-11 at 16:07 +0530, Kohli, Gaurav wrote:
>
> On 1/7/2019 11:26 PM, Oleg Nesterov wrote:
> > pr_crit("XXX: %ld %d\n", current->state, current->on_rq);
>
> Can we also add flags, this may help to know the path of problem:
>
> pr_crit("XXX: %ld %d 0x%x\n", current->state,
Hi Neil,
On Fri, 11 Jan 2019 at 19:10, Neil Armstrong wrote:
>
> Hi Anand,
>
> On 11/01/2019 10:22, Anand Moon wrote:
> > Add missing vin-supply 5V regulator node on usb_phy nodes needed
> > to power usb bus ports. Override the dr_mode from "host" to "peripheral"
> > for initialization of dwc2
On Thu, Jan 03, 2019 at 11:40:04AM +, james qian wang (Arm Technology
China) wrote:
> From: "james qian wang (Arm Technology China)"
>
> Add DT bindings documentation for the ARM display processor D71 and later
> IPs.
>
> Changes in v4:
> - Deleted unnecessary address-cells, size-cells
Bits are usually numbered starting from zero, so 4 should be bit 2, not
bit 3.
Suggested-by: Matthew Wilcox
Signed-off-by: Vincent Whitchurch
---
Documentation/sysctl/vm.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/sysctl/vm.txt
On Fri, 2019-01-11 at 21:43 +0800, Dave Young wrote:
[snip]
> Personally I would like to see platform key separated from integrity.
> But for the kexec_file part I think it is good at least it works with
> this fix.
>
> Acked-by: Dave Young
The original "platform" keyring patches that Nayna
On Wed, 2 Jan 2019 12:57:52 -0800, Sowjanya Komatineni wrote:
> Add pinctrl for 3V3 and 1V8 pad drive strength configuration for
> Tegra210 sdmmc which has pad configuration registers in the pinmux
> reigster domain.
> Pad drive strengths for Tegra186 and Later are
> part of SDMMC device node
On Fri, Jan 11, 2019 at 5:36 AM Thomas Gleixner wrote:
>
> The recent commit which prevented a division by 0 issue in the alarm timer
> code broke posix CPU timers as an unwanted side effect.
>
> The reason is that the common rearm code checks for timer->it_interval
> being 0 now. What went
On Wed, Jan 02, 2019 at 10:09:52PM +0800, Henry Chen wrote:
> Document the binding for enabling DVFSRC on MediaTek SoC.
>
> Signed-off-by: Henry Chen
> ---
> .../devicetree/bindings/soc/mediatek/dvfsrc.txt| 26
> ++
> include/dt-bindings/soc/mtk,dvfsrc.h |
From: Guo Ren
C-SKY CPU 8xx's _PAGE_GLOBAL is BIT(0), but 610's _PAGE_GLOBAL is
BIT(6). Use _PAGE_GLOBAL macro instead of bad magic number.
Signed-off-by: Guo Ren
---
arch/csky/include/asm/pgtable.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Thu, Jan 10, 2019 at 01:36:15PM -0800, Andy Lutomirski wrote:
> > Does it even matter if just leave EINITTOKENKEY attribute unprivileged
> > given that Linux requires that MSRs are writable? Maybe I'll just
> > whitelist that attribute to any enclave?
> >
>
> I would at least make it work like
Den 11.01.2019 11.25, skrev Daniel Vetter:
> On Fri, Jan 11, 2019 at 05:49:15PM +0800, CK Hu wrote:
>> Hi, Daniel:
>>
>> On Fri, 2019-01-11 at 10:20 +0100, Daniel Vetter wrote:
>>> On Fri, Jan 11, 2019 at 11:20:09AM +0800, CK Hu wrote:
Hi, Daniel:
On Thu, 2019-01-10 at 21:02
On Fri, Jan 11, 2019 at 03:48:59PM +, Nadav Amit wrote:
> > I liked the idea, BUT, how would it work for callee-saved PV ops? In
> > that case there's only one clobbered register to work with (rax).
>
> That’s would be more tricky. How about using a per-CPU trampoline code to
> hold a direct
On Fri, 11 Jan 2019 15:18:22 +0100
David Hildenbrand wrote:
> When calling smp_call_ipl_cpu() from the IPL CPU, we will try to read
> from pcpu_devices->lowcore. However, due to prefixing, that will result
> in reading from absolute address 0 on that CPU. We have to go via the
> actual lowcore
On Wed, Jan 09, 2019 at 10:34:42AM -0800, Andy Lutomirski wrote:
> I suppose I should go read the 2.0 spec. I’ve read the 1.2 spec, but I
> always assumed that 2.0 was essentially a superset of 1.2
> functionality.
They are essentially different protocols. No real compatibility.
> Can the
Hi Eric,
On 08/01/2019 10:26, Eric Auger wrote:
> To allow nested stage support, we need to store both
> stage 1 and stage 2 configurations (and remove the former
> union).
>
> arm_smmu_write_strtab_ent() is modified to write both stage
> fields in the STE.
>
> We add a nested_bypass field to
On Fri, Jan 11, 2019 at 11:32:38AM +, Jonathan Cameron wrote:
> On Thu, 10 Jan 2019 10:30:17 -0700
> Keith Busch wrote:
> > I am not aware of a real platform that has an initiator-target pair with
> > better latency but worse bandwidth than any different initiator paired to
> > the same
On 09.01.2019 18:24, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding the
> size of a structure that has a zero-sized array at the end, along with memory
> for some number of elements for that array. For example:
>
> struct foo {
> int
On 1/11/19 3:01 PM, Juergen Gross wrote:
> On 11/01/2019 14:12, Hans van Kranenburg wrote:
>> Hi,
>>
>> On 1/11/19 1:08 PM, Juergen Gross wrote:
>>> Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable'
>>> sched_clock() interface") broke Xen guest time handling across
>>>
Hello,
syzbot found the following crash on:
HEAD commit:b19bce0335e2 net: ethernet: mediatek: fix warning in phy_s..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=168e0b9f40
kernel config: https://syzkaller.appspot.com/x/.config?x=7308e68273924137
On Wed, Jan 09, 2019 at 10:53:54PM +0100, Daniel Vetter wrote:
> On Tue, Jan 08, 2019 at 08:29:35PM +0100, Sam Ravnborg wrote:
> > drmP.h is an relic from the days when there was a single header file.
> > To enable the removal of drmP.h from all users drop include
> > of drmP.h from
Hi Peter,
bpf_perf_event_open() already returns a value, but if
perf_event_output's output_begin (mostly perf_output_begin) fails,
the only way to know about that is looking before/after the rb->lost,
right?
For ring buffer users that is ok, we'll get a PERF_RECORD_LOST,
etc, but
On Fri, 2019-01-11 at 13:48 +0100, Peter Zijlstra wrote:
> I spotted this new v6 in my inbox and have rebased to it.
Thanks!
> On Wed, Jan 09, 2019 at 01:01:48PM -0800, Bart Van Assche wrote:
>
> > The changes compared to v5 are:
> > - Modified zap_class() such that it doesn't try to free a
On Mon, Jan 07, 2019 at 11:49:16AM +0100, Daniel Vetter wrote:
> On Fri, Jan 04, 2019 at 09:56:10AM +0100, Paul Kocialkowski wrote:
> > When drivers pass non-empty lists of modifiers for initializing their
> > planes, we can infer that they allow framebuffer modifiers and set the
> > driver's
On Thu, Jan 10, 2019 at 02:11:55AM +0800, joeyli wrote:
> > Well, I think here, if we were actually trying to solve the problem of
> > proving the hibernated image were the same one we would need to prove
> > some log of the kernel operation came to a particular value *after* the
> > hibernated
On Fri, Dec 14, 2018 at 08:16:32AM -0800, Eric Anholt wrote:
> Paul Kocialkowski writes:
>
> > Despite what the HVS documentation indicates, the VC4 does not actually
> > support SAND tiling modes for any RGB format and only semiplanar YUV420
> > formats (NV12/NV21) can be used in these tiling
Hello,
syzbot found the following crash on:
HEAD commit:1bdbe2274920 Merge tag 'vfio-v5.0-rc2' of git://github.com..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=177ce96f40
kernel config: https://syzkaller.appspot.com/x/.config?x=edf1c3031097c304
On 11/01/2019 13:58, Loic Pallardy wrote:
> Domain translate function is needed to recover irq
> configuration parameters from DT node
>
> Signed-off-by: Loic Pallardy
Surely this fixes something, right? Can you please add a Fixes: tag?
> ---
> drivers/irqchip/irq-stm32-exti.c | 18
On Fri, 11 Jan 2019, Paul Elder wrote:
> On Wed, Jan 09, 2019 at 02:06:31PM -0500, Alan Stern wrote:
> > On Wed, 9 Jan 2019, Paul Elder wrote:
> >
> > > A usb gadget function driver may or may not want to delay the status
> > > stage of a control OUT request. An instance where it might want to
> On Jan 11, 2019, at 7:15 AM, Josh Poimboeuf wrote:
>
> On Fri, Jan 11, 2019 at 01:47:01AM +, Nadav Amit wrote:
>> Here is an alternative idea (although similar to Steven’s and my code).
>>
>> Assume that we always clobber R10, R11 on static-calls explicitly, as anyhow
>> should be done by
Embedded systems often connect to sensors or other multimedia
subdevices directly. Currently, to be able to select such a
subdevice (e.g. CONFIG_VIDEO_OV5640) disabling of the auto-
select config option is needed (CONFIG_MEDIA_SUBDRV_AUTOSELECT).
This is inconvenient as the ancillary drivers for
On Fri, 11 Jan 2019 15:18:22 +0100
David Hildenbrand wrote:
> When calling smp_call_ipl_cpu() from the IPL CPU, we will try to read
> from pcpu_devices->lowcore. However, due to prefixing, that will result
> in reading from absolute address 0 on that CPU. We have to go via the
> actual lowcore
I have got a HP EX900 NVMe SSD with the SM2263XT controller. Whenever I
perform fstrim on this device, I get the appended error message. Maybe
something can be made out of that.
DMAR: DRHD: handling fault status reg 3
DMAR: [DMA Read] Request device [04:00.0] fault addr f98eb000 [fault reason 06]
On 1/4/19 10:22 PM, Gustavo A. R. Silva wrote:
One of the more common cases of allocation size calculations is finding the
size of a structure that has a zero-sized array at the end, along with memory
for some number of elements for that array. For example:
struct foo {
int stuff;
On Fri, Jan 11, 2019 at 10:39:45PM +0800, Qu Wenruo wrote:
>
>
> On 2019/1/11 下午10:03, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: 05a37c48604c19b50873fd9663f9140c150469d1 ("btrfs: volumes: Make
> > sure no dev extent is beyond device
On Fri, Jan 11, 2019 at 10:23:15AM -0500, Mike Snitzer wrote:
> On Fri, Jan 11 2019 at 10:17am -0500,
> Greg Kroah-Hartman wrote:
>
> > On Fri, Jan 11, 2019 at 10:06:05AM -0500, Mike Snitzer wrote:
> > > On Fri, Jan 11 2019 at 9:35am -0500,
> > > Greg Kroah-Hartman wrote:
> > >
> > > > On
On 1/11/19 2:14 AM, Rohit kumar wrote:
From: Ajit Pandey
soc_find_component() may lead to null pointer exception if both
arguments i.e of_node and name is NULL. Add NULL check before
calling soc_find_component(). Also fix some typos.
Thanks for the overnight fix. This update fixes the
Hello Al,
Have you had the opportunity to review our patch?
Cheers,
Alex
On 17.12.18 09:28, Jan Kara wrote:
> On Fri 14-12-18 11:55:52, Alexander Lochmann wrote:
>>
>> file_remove_privs() might be called for non-regular files, e.g.
>> blkdev inode. There is no reason to do its job on things
>>
Hi Michael,
On Sun, 2018-11-11 at 19:50 +0100, Michael Niewöhner wrote:
> Well, there are at least two implementations I know of:
> For my Lenovo X260 I can choose between Infineon TPM 1.2 or Intel PTT TPM 2.0
> This here is my ThinkStation P320 which can choose between PTT 1.2, PTT 2.0,
>
Use the gpiod interface instead of the deprecated old non-descriptor
interface while continuing to ignore gpio flags from device tree in
"svc_reset_onoff()" for now.
Reviewed-by: Johan Hovold
Signed-off-by: Nishad Kamdar
---
Changes in v6:
- Make error messages consistent.
Changes in v5:
-
On 01/10, Andrew Morton wrote:
>
> > Fixes: 7c8bd2322c7f ("exit: ptrace: shift "reap dead" code from
> > exit_ptrace() to forget_original_parent()")
> >
> > Cc: "Eric W. Biederman"
> > Cc: Andrew Morton
> > Signed-off-by: Oleg Nesterov
> > Signed-off-by: Andrei Vagin
>
> Does this warrant a
Use the gpiod interface instead of the deprecated old non-descriptor
interface while continuing to ignore gpio flags from device tree in
functions "deassert_reset()" and "assert_reset()" for now.
Reviewed-by: Johan Hovold
Signed-off-by: Nishad Kamdar
---
Changes in v6:
- Remove some
On 2019/01/12 0:07, Michal Hocko wrote:
> On Fri 11-01-19 23:31:18, Tetsuo Handa wrote:
>> The OOM killer invoked by [ T9694] called printk() but didn't kill anything.
>> Instead, SIGINT from Ctrl-C killed all thread groups sharing current->mm.
>
> I still do not get it. Those other processes are
This patch series converts uses of the old GPIO API to the GPIO
descriptor API. It also converts the GPIO driver to use the
GPIO irqchip library GPIOLIB_IRQCHIP instead of repimplementing
the same.
Changes in v6:
- Patchset now contains two patches as the patch
1 has been accepted.
- Changes
On Fri 2019-01-11 22:07:29, Sergey Senozhatsky wrote:
> On (01/11/19 13:45), Petr Mladek wrote:
> > The sysrq header line is printed with an increased loglevel
> > to provide users some positive feedback.
> >
> > The original loglevel is not restored when the sysrq operation
> > is disabled. This
Remove linux/poll.h which is included more than once
Signed-off-by: Sabyasachi Gupta
---
fs/coda/psdev.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/coda/psdev.c b/fs/coda/psdev.c
index c5234c2..f2bb798 100644
--- a/fs/coda/psdev.c
+++ b/fs/coda/psdev.c
@@ -39,7 +39,6 @@
#include
On 19.10.2018 15:52, Luis Oliveira wrote:
> Add bindings for Synopsys DesignWare MIPI CSI-2 host.
>
> Signed-off-by: Luis Oliveira
> ---
> Changelog
> v2-V3
> - removed IPI settings
>
> .../devicetree/bindings/media/snps,dw-csi-plat.txt | 52
> ++
> 1 file changed, 52
On Fri, 2019-01-11 at 16:02 +0200, Jarkko Sakkinen wrote:
> On Tue, Jan 08, 2019 at 05:43:53PM -0800, Andy Lutomirski wrote:
> > (Also, do we have a sensible story of how the TPM interacts with
> > hibernation at all? Presumably we should at least try to replay
> > the PCR operations that have
401 - 500 of 1414 matches
Mail list logo
