Hi Masahiro,
Masahiro Yamada wrote on Tue, 12 Mar
2019 20:07:27 +0900:
> Hi Miquel,
>
>
> On Tue, Mar 12, 2019 at 7:54 PM Miquel Raynal
> wrote:
> >
> > Hi Masahiro,
> >
> > Masahiro Yamada wrote on Tue, 12 Mar
> > 2019 19:51:21 +0900:
> >
> > > On Tue, Mar 12, 2019 at 7:28 PM Miquel
On Tue, 12 Mar 2019 02:24:08 +, Anson Huang wrote:
> Freescale MMDC (Multi Mode DDR Controller) driver is supported
> since i.MX6Q, but not yet documented, this patch adds binding
> doc for MMDC module driver.
>
> Signed-off-by: Anson Huang
> ---
> Changes since V4:
> - update mmdc1
Am Donnerstag, 7. März 2019, 09:41:53 CET schrieb Christoph Muellner:
> The rockchip-emmc PHY can be configured with different
> drive impedance values. Currenlty a value of 50 Ohm is
> hard coded into the driver.
>
> This patch introduces the DTS property 'drive-impedance-ohm'
> for the
> On 12.03.2019, at 13:52, Heiko Stuebner wrote:
>
> Hi Christoph,
>
> Am Donnerstag, 7. März 2019, 09:41:54 CET schrieb Christoph Muellner:
>> This patch documents the new proprty drive-impedance-ohm for
>> Rockchip's eMMC PHY node.
>>
>> Signed-off-by: Christoph Muellner
>> Signed-off-by:
> > Do you have a Fixes tag for this?
> >
>
> Fixes: aeb068c57214858b638d5ee627bb4a831f98771e ("i2c: i2c-stm32f7: add
> driver")
>
> Will you change the commit message or do you want me to resend the patch?
I'll fix it. Thanks for this info!
signature.asc
Description: PGP signature
On 2019-03-11 19:35, Andrey Smirnov wrote:
On Mon, Mar 11, 2019 at 2:35 PM Angus Ainslie (Purism)
wrote:
These are the TMU nodes from the NXP vendor kernel
Hey Angus,
TMU block supports multiple thermal zones and vendor kernel doesn't
really account for that (see below). Latest version of
On 2/8/19 11:05 AM, Patrick Bellasi wrote:
[...]
+config UCLAMP_BUCKETS_COUNT
+ int "Number of supported utilization clamp buckets"
+ range 5 20
+ default 5
+ depends on UCLAMP_TASK
+ help
+ Defines the number of clamp buckets to use. The range of each
Hi Christoph,
Am Donnerstag, 7. März 2019, 09:41:54 CET schrieb Christoph Muellner:
> This patch documents the new proprty drive-impedance-ohm for
> Rockchip's eMMC PHY node.
>
> Signed-off-by: Christoph Muellner
> Signed-off-by: Philipp Tomsich
> ---
>
On Fri, Mar 08, 2019 at 12:56:28PM -0800, Nick Desaulniers wrote:
> On Fri, Mar 8, 2019 at 4:37 AM Greg KH wrote:
> >
> > On Tue, Mar 05, 2019 at 01:47:58PM -0800, Nick Desaulniers wrote:
> > > On Tue, Mar 5, 2019 at 2:30 AM Kieran Bingham
> > > wrote:
> > > >
> > > > From: Jackie Liu
> > > >
>
On Mon, Mar 11, 2019 at 05:27:43PM -0700, James Bottomley wrote:
> On Mon, 2019-03-11 at 16:54 -0700, Calvin Owens wrote:
> > e're having lots of problems with TPM commands timing out, and we're
> > seeing these problems across lots of different hardware (both v1/v2).
> >
> > I instrumented the
On Thu, 7 Mar 2019 13:52:51 +0100, =?UTF-8?q?Marek=20Beh=C3=BAn?= wrote:
> This patch adds documentation of the device tree bindings for GPIOs
> on the devices connected via Moxtet bus.
>
> Signed-off-by: Marek Behún
> Cc: Rob Herring
> Cc: devicet...@vger.kernel.org
> ---
>
On Mon, Mar 11, 2019 at 10:29:31AM +0800, Gao Xiang wrote:
> commit 419d6efc50e94bcf5d6b35cd8c71f79edadec564 upstream.
>
> As Al pointed out, "
> ... and while we are at it, what happens to
> unsigned int nameoff = le16_to_cpu(de[mid].nameoff);
> unsigned int matched = min(startprfx,
Hi, Kirill,
On Tue, Mar 12, 2019 at 10:49:51AM +0300, Kirill A. Shutemov wrote:
> On Mon, Mar 11, 2019 at 05:36:58PM +0800, Peter Xu wrote:
> > Hi,
> >
> > (The idea comes from Andrea, and following discussions with Mike and
> > other people)
> >
> > This patchset introduces a new sysctl flag
Hi Marc,
Thanks for the patch!
On 3/11/19 4:56 PM, Marc Gonzalez wrote:
> Some chips report an incorrect device class. Override the incorrect
> value using a quirk, instead of code in the read function.
>
> Signed-off-by: Marc Gonzalez
> ---
> FWIW, this quirk is no longer required on recent
On Mon 2019-03-11 19:54:11, Sergey Senozhatsky wrote:
> On (03/07/19 10:53), John Ogness wrote:
> > Since all current console drivers are already irq safe, I'm
> > wondering if using irq_work to handle the emergency printing for console
> > drivers without write_atomic() would help. (If the printk
On 24/02/2019 04:53, Bjorn Andersson wrote:
> On Sat 23 Feb 10:37 PST 2019, Marc Zyngier wrote:
>
>> On Sat, 23 Feb 2019 18:12:54 +, Bjorn Andersson wrote:
>>>
>>> On Mon 11 Feb 06:59 PST 2019, Marc Zyngier wrote:
>>>
On 11/02/2019 14:29, AngeloGioacchino Del Regno wrote:
>
On Mon, Mar 11, 2019 at 04:54:04PM -0700, Calvin Owens wrote:
> We're having lots of problems with TPM commands timing out, and we're
> seeing these problems across lots of different hardware (both v1/v2).
>
> I instrumented the driver to collect latency data, but I wasn't able to
> find any
The hist__account_cycles is executed when the hist_iter__branch_callback
is called. But it looks it's not necessary. In hist__account_cycles, it
already walks on all branch entries.
This patch moves the hist__account_cycles out of callback, now the data
processing is much faster than before.
For
On Tue, Mar 12, 2019 at 09:01:47AM +0200, Mike Rapoport wrote:
> Hi Peter,
>
> On Mon, Mar 11, 2019 at 05:36:58PM +0800, Peter Xu wrote:
> > Hi,
> >
> > (The idea comes from Andrea, and following discussions with Mike and
> > other people)
> >
> > This patchset introduces a new sysctl flag to
On Tue, Mar 12, 2019 at 4:16 AM Jiaxun Yang wrote:
>
> Add devicetree skeleton for ls1b and ls1c
>
> Signed-off-by: Jiaxun Yang
> ---
> arch/mips/boot/dts/loongson/Makefile | 6 ++
> arch/mips/boot/dts/loongson/ls1b.dts | 21 +
> arch/mips/boot/dts/loongson/ls1c.dts | 25 ++
>
On Sat, Mar 09, 2019 at 07:26:34AM +0530, Manivannan Sadhasivam wrote:
> For the AMBA Primecell devices having the reset lines wired, it is
> necessary to take them out of reset before reading the pid and cid values.
> Earlier we were dependent on the bootloader to do this but a more cleaner
>
On Tue, Mar 12, 2019 at 08:58:30AM +0200, Mike Rapoport wrote:
[...]
> > +config USERFAULTFD_UNPRIVILEGED_DEFAULT
> > +string "Default behavior for unprivileged userfault syscalls"
> > +depends on USERFAULTFD
> > +default "disabled"
> > +help
> > + Set
Hi,
Please pull these apparmor bugfixes for v5.1
Thanks!
- John
The following changes since commit 43aa09fee2f08c8d90a4f35d4c8c711362afcaee:
apparmor: Fix warning about unused function apparmor_ipv6_postroute
(2018-11-14 11:42:18 -0800)
are available in the Git repository at:
This patch series we add support for wcn3998 BT chip set. This new chipset
is based from the wcn3990 with minimal power numbers. So here in this patch
The major difference between wcn3990 and wcn3998 is only power numbers. where
as init process and fw download is same with wcn3990.So we add new
On Tue, Mar 12, 2019 at 11:12:02AM +0100, Volker Haspel wrote:
> Changes since v1:
> * use devm_spi_register_controller() instead of calling
>spi_unregister_controller() in the remove function
Please don't send cover letters for single patches, if there is anything
that needs saying put it
Added new compatible for wcn3998 and corresponding voltage
and current values to wcn3998 compatible.
Changed driver code to support wcn3998
Signed-off-by: Harish Bandi
---
changes in v3:
- updated to latest code base.
---
drivers/bluetooth/btqca.c | 4 ++--
drivers/bluetooth/btqca.h | 3
This patch enables regulators for the Qualcomm Bluetooth wcn3998
controller.
Signed-off-by: Harish Bandi
---
changes in v3:
- updated to latest code base.
---
.../devicetree/bindings/net/qualcomm-bluetooth.txt| 15 +++
1 file changed, 15 insertions(+)
diff --git
On 11/03/2019 09:54, Erin Lo wrote:
> From: Ben Ho
>
> Add basic chip support for Mediatek 8183, include
> uart node with correct uart clocks, pwrap device
>
> Add clock controller nodes, include topckgen, infracfg,
> apmixedsys and subsystem.
>
> Signed-off-by: Ben Ho
> Signed-off-by:
Introduce the Texas Instruments LM3532 White LED driver.
The driver supports ALS configurability or manual brightness
control.
The driver also supports associating LED strings with specific
control banks in a group or as individually controlled strings.
Signed-off-by: Dan Murphy
---
v3 -
Update the properties for the lm3532 device node for droid4.
With this change the backlight LED string and the keypad
LED strings will be controlled separately.
Signed-off-by: Dan Murphy
---
v3 - updated keypad label on v1 comment -
https://lore.kernel.org/patchwork/patch/1049023/
v2 - Fixed
Add the lm3532 device tree documentation.
Remove lm3532 device tree reference from the ti_lmu devicetree
documentation.
With the addition of the dedicated lm3532 documentation the device
can be removed from the ti_lmu.txt.
The reason for this is that the lm3532 dt documentation now defines
the
Remove the LM3532 backlight driver references from the ti-lmu
code as dedicated driver support is available.
Signed-off-by: Dan Murphy
---
v3 - No changes - https://lore.kernel.org/patchwork/patch/1049025/
v2 - Removed LM3532 register definitions from ti-lmu-register -
Hi Nick,
On 11/3/19 16:58, Nick Crews wrote:
> Before, ec->data_buffer could be written to from multiple
> contexts at the same time. Since the ec is shared data,
> it needs to be inside the mutex as well.
>
Probably you're missing a fixes tag here.
> Signed-off-by: Nick Crews
> ---
>
On Tue, Mar 12, 2019 at 10:17:39AM +0100, Uwe Kleine-König wrote:
> Hello,
>
> there are just a few minor things left I commented below.
>
> On Tue, Mar 12, 2019 at 01:41:29PM +0530, Yash Shah wrote:
> > +#define div_u64_round(a, b) \
> > + ({typeof(b) __b = b; div_u64((a) + __b / 2, __b); })
Building with W=1 reports (among other things)
CC [M] drivers/staging/rtl8712/rtl871x_ioctl_linux.o
drivers/staging/rtl8712/rtl871x_ioctl_linux.c:1106: warning: Cannot understand
*
on line 1106 - I thought it was a doc line
CC [M] drivers/staging/rtl8712/os_intfs.o
On Wed, Mar 6, 2019 at 11:40 AM Balakrishna Godavarthi
wrote:
>
>
> Hi,
>
> The following changes since commit
> 54b0a748c8966c93aaa8726402e0b69cb51cd5d2:
>
>WHENCE: Correct errant entries (2019-02-21 07:21:45 -0500)
>
> are available in the Git repository at:
>
>
On Tue, 12 Mar 2019 11:41:02 +0100
LABBE Corentin wrote:
> On Mon, Dec 10, 2018 at 05:52:35PM +0300, Sergei Shtylyov wrote:
> > Hello!
> >
> > On 12/10/2018 04:46 PM, Corentin Labbe wrote:
> >
> > > When playing with a virtual SPARC machine with qemu, I found that the
> > > IDE emulated
On Tue, Mar 12, 2019 at 10:27:18AM +0530, Viresh Kumar wrote:
> At boot up, CPUfreq core performs a sanity check to see if the system is
> running at a frequency defined in the frequency table of the CPU. If so,
> we try to find a valid frequency (lowest frequency greater than the
> currently
On Tue, Mar 12, 2019 at 02:29:29PM +0800, maowenan wrote:
> ping...
>
> On 2019/3/9 11:26, Mao Wenan wrote:
What? You got an automated email from my patch system saying that I can
not do anything with this patch until after 5.1-rc1 is out, due to the
merge window. Why did that not answer the
This fixes following Smatch errors:
hfi_parser.c:103 parse_profile_level() error: memcpy() 'proflevel'
too small (8 vs 128)
hfi_parser.c:129 parse_caps() error: memcpy() 'cap'
too small (16 vs 512)
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/hfi_parser.c | 12
On 3/12/19 7:20 AM, Steven Rostedt wrote:
On Fri, 8 Mar 2019 15:16:18 +0530
Neeraj Upadhyay wrote:
Update the code to match the comment that self wakeup of
grace period kthread is allowed from interrupt handler, and
softirq handler, running in the grace period kthread's
context. Present
Building with W=1 reports (among other things):
CC drivers/tty/tty_jobctrl.o
drivers/tty/tty_jobctrl.c:317: warning: Cannot understand *
on line 317 - I thought it was a doc line
Fix up the non-kerneldoc comment. (other warnings to be cleaned up in separate
patch)
Signed-off-by Valdis
Hi Linus,
The following changes since commit 2137397c92aec3713fa10be3c9b830f9a1674e60:
Merge tag 'sound-5.0' of
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound (2019-02-20 09:42:52
-0800)
are available in the Git repository at:
On 12-03-19, 10:04, Pavel Machek wrote:
> On Tue 2019-03-12 08:58:02, Viresh Kumar wrote:
> > On 11-03-19, 13:05, Rafael J. Wysocki wrote:
> > > On Friday, March 8, 2019 10:53:11 AM CET Viresh Kumar wrote:
> > > > wakeup_source_remove() is the counterpart of wakeup_source_add() helper
> > > > and
On Mon, Mar 11, 2019 at 07:55:21PM +0100, Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/gpio/gpio-zynq.c | 4 +---
> 1 file
Building with C=2 W=1 reports:
CHECK drivers/ras/debugfs.c
drivers/ras/debugfs.c:3:15: warning: symbol 'ras_debugfs_dir' was not declared.
Should it be static?
drivers/ras/debugfs.c:7:5: warning: symbol 'ras_userspace_consumers' was not
declared. Should it be static?
On Mon, Mar 11, 2019 at 07:55:17PM +0100, Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> this driver deserves a bit more cleanup, to get rid of the global
> variable giu_base, which makes it
On Mon, Mar 11, 2019 at 07:55:12PM +0100, Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/gpio/gpio-tegra.c | 4 +---
> 1
On Mon, Mar 11, 2019 at 07:55:05PM +0100, Enrico Weigelt, metux IT consult
wrote:
> a tab sneaked in, where it shouldn't be.
Pedantic nitpick: "pendantic" -> "pedantic" in the subject, and start
the commit message with a capital letter: "A tab sneaked in [...]".
Thierry
signature.asc
Building with W=1 complains:
CC [M] drivers/platform/x86/dell-rbtn.o
drivers/platform/x86/dell-rbtn.c:345:5: warning: no previous prototype for
'dell_rbtn_notifier_register' [-Wmissing-prototypes]
345 | int dell_rbtn_notifier_register(struct notifier_block *nb)
|
On Tue, Mar 12, 2019 at 10:33:44AM +0100, Enrico Weigelt, metux IT consult
wrote:
> On 12.03.19 10:17, Ben Dooks wrote:
> > On 11/03/2019 18:54, Enrico Weigelt, metux IT consult wrote:
> >> don't need the temporary variable "dev", directly use >dev
> >>
> >> Signed-off-by: Enrico Weigelt, metux
On Mon, Mar 11, 2019 at 07:54:51PM +0100, Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/gpio/gpio-grgpio.c | 4 +---
> 1
On Mon, Mar 11, 2019 at 07:54:49PM +0100, Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/gpio/gpio-ep93xx.c | 7 ++-
> 1
On Mon, Mar 11, 2019 at 07:54:42PM +0100, Enrico Weigelt, metux IT consult
wrote:
> We already have the struct device* pointer in a local variable,
> so we can write this a bit shorter.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/gpio/gpio-amdpt.c | 10 +-
> 1
On 11/03/2019 19:54, Enrico Weigelt, metux IT consult wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/gpio/gpio-mt7621.c | 3 +--
> 1 file changed, 1
On Mon, Mar 11, 2019 at 08:52:22PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> When a sample doesn't have a time stamp (e.g. from --no-time),
> show the beginning of the trace for res samples instead of generating
> an impossible time range that errors out.
>
> Signed-off-by: Andi Kleen
On Mon, Mar 11, 2019 at 08:52:23PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Pass on -f to the child perf script, so that it can read the perf.data
> file if it's owned by a different user.
>
> Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
thanks,
jirka
> ---
>
On 03/12/19 11:07, Qais Yousef wrote:
> eBPF tools like bcc-tools have hard time figuring out when features like
> raw_tracepoint are supported in the kernel on which we are running. At
> the moment a fragile mechanism of matching bpf_find_raw_tracepoint()
> function in /proc/kallsyms is used to
On Mon, Mar 11, 2019 at 08:52:24PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> In hierarchy mode the res samples need to be cloned from the parent
> entry. Copy them in this case. This fixes res sample browsing
> with --hierarchy.
>
> Signed-off-by: Andi Kleen
> ---
>
Hi Miquel,
On Tue, Mar 12, 2019 at 7:54 PM Miquel Raynal wrote:
>
> Hi Masahiro,
>
> Masahiro Yamada wrote on Tue, 12 Mar
> 2019 19:51:21 +0900:
>
> > On Tue, Mar 12, 2019 at 7:28 PM Miquel Raynal
> > wrote:
> > >
> > > Hi Masahiro,
> > >
> > > Masahiro Yamada wrote on Tue, 12 Mar
> > >
On Mon, Mar 11, 2019 at 4:47 PM Michal Hocko wrote:
>
> On Fri 01-03-19 15:38:54, Yafang Shao wrote:
> > If we want to know the zone type, we have to check whether
> > CONFIG_ZONE_DMA, CONFIG_ZONE_DMA32 and CONFIG_HIGHMEM are set or not,
> > that's not so convenient.
> >
> > We'd better show the
Hi Masahiro,
Masahiro Yamada wrote on Tue, 12 Mar
2019 19:51:21 +0900:
> On Tue, Mar 12, 2019 at 7:28 PM Miquel Raynal
> wrote:
> >
> > Hi Masahiro,
> >
> > Masahiro Yamada wrote on Tue, 12 Mar
> > 2019 17:44:43 +0900:
> >
> > > The Denali IP adopts the syndrome page layout (payload and
On Tue, Mar 12, 2019 at 7:28 PM Miquel Raynal wrote:
>
> Hi Masahiro,
>
> Masahiro Yamada wrote on Tue, 12 Mar
> 2019 17:44:43 +0900:
>
> > The Denali IP adopts the syndrome page layout (payload and ECC are
> > interleaved). The *_page_raw() and *_oob() callbacks are complicated
> > because they
Am Freitag, 8. März 2019, 19:12:02 CET schrieb Jagan Teki:
> FriendlyElec NanoPi NEO4 is known to be a revision 4 based
> NanoPi4 series of boards.
>
> Most of know peripherals are shared between Nanopi M4 vs NEO4, except
> - 1GB DDR3
> - USB Host ports
> - Missing DSI port
> - USB 2.0 Host with
Am Sonntag, 10. März 2019, 13:00:45 CET schrieb Jonas Karlman:
> This patch fixes definition of several clock gate and select register
> that is wrong for rk3328 referring to the TRM and vendor kernel.
> Also use correct number of softrst registers.
>
> Fix clock definition for:
> - clk_crypto
>
On 03/12/2019 01:41 PM, LABBE Corentin wrote:
>>> When playing with a virtual SPARC machine with qemu, I found that the
>>> IDE emulated device was not probing with the ata/pata_oldpiix driver.
>>
>>Correctly, it should probe with ata_piix,
>>
>>> But with the old ide/piix, it was probed.>
On 12/03/2019 11:32, Neil Armstrong wrote:
> The OX820 compatible is wrong is the driver, fix it.
>
> Fixes: 2ea3401e2a84 ("clocksource/drivers/oxnas: Add OX820 compatible")
> Reported-by: Daniel Golle
> Signed-off-by: Neil Armstrong
> ---
> drivers/clocksource/timer-oxnas-rps.c | 2 +-
> 1
Building with W=1 reports:
CC drivers/extcon/devres.o
drivers/extcon/devres.c:208: warning: bad line: -
Resource-managed extcon_unregister_notifier()
Give the line the asterisk it wanted.
Signed-off-by: Valdis Kletnieks
diff --git a/drivers/extcon/devres.c
On Mon, Mar 11, 2019 at 06:01:13PM -0700, Andrew Morton wrote:
> On Fri, 8 Mar 2019 09:31:00 +0100 Linus Walleij
> wrote:
>
> > On Sun, Mar 3, 2019 at 8:47 AM William Breathitt Gray
> > wrote:
> >
> > > This macro iterates for each 8-bit group of bits (clump) with set bits,
> > > within a
On Mon, Dec 10, 2018 at 05:52:35PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 12/10/2018 04:46 PM, Corentin Labbe wrote:
>
> > When playing with a virtual SPARC machine with qemu, I found that the
> > IDE emulated device was not probing with the ata/pata_oldpiix driver.
>
>Correctly, it
Am Montag, 11. März 2019, 16:03:30 CET schrieb Jagan Teki:
> It is always better practice to follow regulator naming conventions
> as per the schematics for future references.
>
> So, rename vcc_sys into vcc5v0_sys as per rk3399 power diagram of
> rock960 schematics.
>
> Signed-off-by: Jagan
The OX820 compatible is wrong is the driver, fix it.
Fixes: 2ea3401e2a84 ("clocksource/drivers/oxnas: Add OX820 compatible")
Reported-by: Daniel Golle
Signed-off-by: Neil Armstrong
---
drivers/clocksource/timer-oxnas-rps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Restrict kdump to only reserve crashkernel below 64TB. Since the kdump
jumping may be from 5-level to 4-level, and the kdump kernel is put
above 64TB in 5-level kernel, then the jumping will fail. And the
crashkernel reservation is done during the 1st kernel bootup, there's
no way to detect the
On Mon, Mar 11, 2019 at 01:24:36PM -0700, Andi Kleen wrote:
> Mostly unrelated to each other, so can be picked'n'chosed.
>
> - Fix perf stat --no-scale
> - Support --reltime in perf script
> - Fix crashes with stat -r
> - Handle JITed code better in perf report
> - Allow to limit rotated
This is v3 post.
The original v1 post can be found here:
http://lkml.kernel.org/r/20180829141624.13985-1-...@redhat.com
Later a v1 RESEND version:
http://lkml.kernel.org/r/20190125022817.29506-1-...@redhat.com
V2 post is here:
http://lkml.kernel.org/r/20190312005004.19182-1-...@redhat.com
This
In relocate_kernel() CR4.LA57 flag is set before kexec jumping if
the kernel has 5-level paging enabled. Then in boot/compressed/head_64.S,
it will check if the booting kernel is in 4-level or 5-level paging
mode, and handle accordingly. However, the old kernel which doesn't
contain the 5-level
On Mon, Mar 11, 2019 at 01:24:41PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Show all the supported sort keys in the command line help output,
> so that it's not needed to refer to the manpage.
>
> The output is not line wrapped, so it can be fairly long.
>
> Before:
>
> % perf report
On Mon, Mar 11, 2019 at 01:24:40PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> The help description for --switch-output looks like there
> are multiple comma separated fields. But it's actually a choice
> of different options. Make it clear and less confusing.
>
> Before:
>
> % perf report
On Mon 2019-03-11 11:51:49, John Ogness wrote:
> On 2019-03-07, Sergey Senozhatsky wrote:
> > I don't really understand the role of loglevel anymore.
>
> "what the kernel considers" is a configuration option of the
> administrator. The administrator can increase the verbocity of the
> console
Add two bits XLF_5LEVEL and XLF_5LEVEL_ENABLED for 5-level kernel.
Bit XLF_5LEVEL indicates if 5-level related code is contained
in this kernel.
Bit XLF_5LEVEL_ENABLED indicates if CONFIG_X86_5LEVEL=y is set.
They are being used in later patch to check if kexec/kdump kernel
is loaded in right
Hi!
On Tue, Mar 12, 2019 at 4:59 PM Neil Armstrong wrote:
> [...]
> BTW, do you know if it's possible to have a sample of the Phicomm N1
> in order to be added in kernelci ?
It's easy to purchase one in China and second-handed ones are dirt
cheap, but I don't think it's available worldwide.
I'm
Hi Masahiro,
Masahiro Yamada wrote on Tue, 12 Mar
2019 17:44:43 +0900:
> The Denali IP adopts the syndrome page layout (payload and ECC are
> interleaved). The *_page_raw() and *_oob() callbacks are complicated
> because they must hide the underlying layout used by the hardware,
> and always
From: Philippe Schenker
Add the stmpe-adc DT node as found on Toradex T30 modules
Signed-off-by: Philippe Schenker
---
arch/arm/boot/dts/tegra30-apalis-v1.1.dtsi | 22 ++
arch/arm/boot/dts/tegra30-apalis.dtsi | 22 ++
CC security/keys/request_key.o
security/keys/request_key.c:35: warning: Function parameter or member 'authkey'
not described in 'complete_request_key'
security/keys/request_key.c:35: warning: Excess function parameter 'auth_key'
description in 'complete_request_key'
Fix it up to match
CC fs/fhandle.o
fs/fhandle.c:259: warning: Function parameter or member 'flags' not described
in 'sys_open_by_handle_at'
fs/fhandle.c:259: warning: Excess function parameter 'flag' description in
'sys_open_by_handle_at'
Fix apparent typo in the kerneldoc
Signed-off-by: Valdis Kletnieks
On Mär 12 2019, Yash Shah wrote:
> This patch series adds a PWM driver and DT documentation
> for HiFive Unleashed board. The patches are mostly based on
> Wesley's patch.
Heartbeat trigger still doesn't work for me.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint =
On 03/12/19 at 12:48pm, Kirill A. Shutemov wrote:
> > #ifdef CONFIG_X86_32
> > # define CRASH_ADDR_LOW_MAX(512 << 20)
> > # define CRASH_ADDR_HIGH_MAX (512 << 20)
> > #else
> > # define CRASH_ADDR_LOW_MAX(896UL << 20)
> > -# define CRASH_ADDR_HIGH_MAX MAXMEM
> > +#
Changes since v1:
* use devm_spi_register_controller() instead of calling
spi_unregister_controller() in the remove function
Thanks
Volker
Volker Haspel (1):
spi: spi-fsl-qspi: use devm_spi_register_controller
drivers/spi/spi-fsl-qspi.c | 2 +-
1 file changed, 1 insertion(+), 1
The driver does not clearly unregister the spi controller.
Therefore calling an unbind and bind again will end up in a
Kernel crash.
The function devm_spi_register_controller will automatically
be unregister the SPI device.
Signed-off-by: Volker Haspel
Signed-off-by: John Ogness
---
Am Samstag, 9. März 2019, 17:10:12 CET schrieb Tomohiro Mayama:
> This patch makes USB ports functioning again.
>
> Suggested-by: Robin Murphy
> Signed-off-by: Tomohiro Mayama
> Tested-by: Katsuhiro Suzuki
added Fixes and Cc-stable tags and applied as fix for 5.1
Thanks
Heiko
On 12/03/2019 09:19, Enrico Weigelt, metux IT consult wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/ata/ahci_tegra.c | 13 +
> 1 file changed,
On Mon, 11 Mar 2019 at 13:03, Rafael J. Wysocki wrote:
>
> On Tuesday, March 5, 2019 1:55:26 PM CET Ulf Hansson wrote:
> > In a step to consolidate code around fetching the runtime PM active/suspend
> > time for a device, let's re-factor the existing pm_runtime_suspended_time()
> > and add a new
When the CONFIG_HOTPLUG_CPU is not set, there won't be a "hotplug"
directory in /sys/devices/system/cpu/. Make use of this fact to check
if we need to skip this test.
Signed-off-by: Po-Hsu Lin
---
tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh | 5 +
1 file changed, 5 insertions(+)
On (03/11/19 11:51), John Ogness wrote:
> > In new printk design the tasks are still affected by printing floods.
> > Tasks have to line up and (busy) wait for each other, regardless of
> > contexts.
>
> They only line up and busy wait is to add the informational message to
> the ring buffer. The
On Sat, Mar 09, 2019 at 10:10:19PM -0800, h...@zytor.com wrote:
> >@@ -47,8 +50,18 @@ static unsigned long find_trampoline_pla
> > * This code is based on reserve_bios_regions().
> > */
> >
> >-ebda_start = *(unsigned short *)0x40e << 4;
> >-bios_start = *(unsigned short *)0x413
On Tue, Mar 12, 2019 at 6:03 PM Boris Brezillon
wrote:
>
> On Tue, 12 Mar 2019 17:44:45 +0900
> Masahiro Yamada wrote:
>
>
> > +
> > +static int denali_exec_instr(struct nand_chip *chip,
> > + const struct nand_op_instr *instr)
> > +{
> > + struct denali_nand_info
On Tue, Mar 12, 2019 at 08:50:04AM +0800, Baoquan He wrote:
> Restrict kdump to only reserve crashkernel below 64TB. Since the kdump
> jumping may be from 5-level to 4-level, and the kdump kernel is put
> above 64TB in 5-level kernel, then the jumping will fail. And the
> crashkernel reservation
On 12/03/2019 01:10, Max Filippov wrote:
[...]
>
> Acked-by: Max Filippov
>
Thanks!
Hi,
On 11/03/2019 23:13, David Miller wrote:
[...]
>
> We must re-evaluate the %tstate value stored in ptregs, you cannot
> make this change.
>
That's the one I was the less sure about, thanks for clearing it up and
sorry for the noise.
Hi All,
Please ignore this, has re-sent it adding lost Reviewed-by tag.
Thanks,
Zhiqiang
> -Original Message-
> From: Z.q. Hou
> Sent: 2019年3月11日 17:33
> To: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
>
1001 - 1100 of 1231 matches
Mail list logo
