On November 21, 2016 1:21:35 PM PST, Linus Torvalds
wrote:
>On Mon, Nov 21, 2016 at 10:26 AM, H. Peter Anvin wrote:
>> On 11/21/16 10:00, Linus Torvalds wrote:
>>>
>>> I'd much rather we go back to just making the "cs" entry explicitly
>>> 16-bit, and have a separate padding entry, the way we us
On Mon, Nov 21, 2016 at 2:17 PM, wrote:
>
> Now, segment loads have always ignored the top 32 bits; it's an issue when
> examined by other kinds of code.
Yes. Particularly ptrace and signal information copying. Need to make
sure those things don't look at (or expose) high bits that may be
stale
On Mon, 21 Nov 2016 14:12:50 -0800
Joel Fernandes wrote:
> Unlike monotonic clock, boot clock as a trace clock will account for
> time spent in suspend useful for tracing suspend/resume. This uses
> earlier introduced infrastructure for using the fast boot clock.
>
> Cc: Steven Rostedt
> Cc: Th
On Mon, Nov 21, 2016 at 09:09:28AM +, Gabriele Paoloni wrote:
> > > +config PCI_HISI_ACPI
> > > + depends on ACPI && ARM64
> > > + bool "HiSilicon Hip05 and Hip06 and Hip07 SoCs ACPI PCIe
> > controllers"
> > > + select PNP
> > > + help
> > > + Say Y here if you want ACPI PCIe controller sup
On Monday, November 21, 2016 10:07:05 AM AceLan Kao wrote:
> The ethernet network fails to work on DELL Latitude 3350 after this commit
>ea7d521 Revert 'Revert "ACPICA: Permanently set _REV to the value '2'."'
>
> dmesg shows
>r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
>r8169
On 2016-11-20 14:30:55 [-0800], Guenter Roeck wrote:
> Install, modprobe, modprobe -r, modprobe,
>
> [24078.179118] [ cut here ]
> [24078.179124] WARNING: CPU: 0 PID: 14 at fs/sysfs/dir.c:31
> sysfs_warn_dup+0x6e/0x80
> [24078.179125] sysfs: cannot create duplicate filenam
A RAS (Reliability, Availability, Serviceability) controller
may be a separate processor running in parallel with OS
execution, and may generate error records for consumption by
the OS. If the RAS controller produces multiple error records,
then they may be overwritten before the OS has consumed th
Currently when a RAS error is reported it is not timestamped.
The ACPI 6.1 spec adds the timestamp field to the generic error
data entry v3 structure. The timestamp of when the firmware
generated the error is now being reported.
Signed-off-by: Jonathan (Zhixiong) Zhang
Signed-off-by: Richard Ruig
When a memory error, CPU error, PCIe error, or other type of hardware error
that's covered by RAS occurs, firmware should populate the shared GHES memory
location with the proper GHES structures to notify the OS of the error.
For example, platforms that implement firmware first handling may impleme
Currently external aborts are unsupported by the guest abort
handling. Add handling for SEAs so that the host kernel reports
SEAs which occur in the guest kernel.
Signed-off-by: Tyler Baicar
---
arch/arm/include/asm/kvm_arm.h | 1 +
arch/arm/include/asm/system_misc.h | 5 +
arch/ar
From: "Jonathan (Zhixiong) Zhang"
Even if an error status block's severity is fatal, the kernel does not
honor the severity level and panic.
With the firmware first model, the platform could inform the OS about a
fatal hardware error through the non-NMI GHES notification type. The OS
should pani
Currently there are trace events for the various RAS
errors with the exception of ARM processor type errors.
Add a new trace event for such errors so that the user
will know when they occur. These trace events are
consistent with the ARM processor error section type
defined in UEFI 2.6 spec section
UEFI spec allows for non-standard section in Common Platform Error
Record. This is defined in section N.2.3 of UEFI version 2.5.
Currently if the CPER section's type (UUID) does not match with
any section type that the kernel knows how to parse, trace event
is not generated for such section. And t
UEFI spec allows for non-standard section in Common Platform Error
Record. This is defined in section N.2.3 of UEFI version 2.5.
Currently if the CPER section's type (UUID) does not match with
one of the section types that the kernel knows how to parse, the
section is skipped. Therefore, user is n
ARM APEI extension proposal added SEA (Synchrounous External
Abort) notification type for ARMv8.
Add a new GHES error source handling function for SEA. If an error
source's notification type is SEA, then this function can be registered
into the SEA exception handler. That way GHES will parse and re
SEA exceptions are often caused by an uncorrected hardware
error, and are handled when data abort and instruction abort
exception classes have specific values for their Fault Status
Code.
When SEA occurs, before killing the process, go through
the handlers registered in the notification list.
Updat
Add support for ARMv8 Common Platform Error Record (CPER).
UEFI 2.6 specification adds support for ARMv8 specific
processor error information to be reported as part of the
CPER records. This provides more detail on for processor error logs.
Signed-off-by: Jonathan (Zhixiong) Zhang
Signed-off-by:
On Tue, Nov 22 2016, Mark Brown wrote:
> [ Unknown signature status ]
> On Thu, Nov 17, 2016 at 05:46:13PM +1100, NeilBrown wrote:
>> On Thu, Nov 17 2016, Mark Brown wrote:
>
>> > To me that's pretty much what's being done here, the code just happens
>> > to sit in USB instead but fundamentally it
On Mon, Nov 21, 2016 at 11:28:56PM +0100, Rafael J. Wysocki wrote:
> On Monday, November 21, 2016 03:45:19 PM Bjorn Helgaas wrote:
> > Since we register pcie_pme_driver only for PCI_EXP_TYPE_ROOT_PORT, the PME
> > driver never claims Root Complex Event Collectors.
> >
> > Remove unused code relate
Hi Joel,
[auto build test ERROR on tip/timers/core]
[also build test ERROR on v4.9-rc6 next-20161117]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Joel-Fernandes/timekeeping-Introduce-a-fast-b
Hi Wim,
On Mon, 14 Nov 2016 16:26:16 +0100 Wim Van Sebroeck wrote:
>
> This has been fixed. Thanks for notifying me about it.
>
> Kind regards,
> Wim.
>
> > Hi Wim,
> >
> > For the past few days (nearly a week, sorry) fetching the watchdog tree
> > (git://www.linux-watchdog.org/linux-watchdog-
On 11/21/2016 03:40 PM, Christopher Covington wrote:
> Hi Wei,
>
> On 11/21/2016 03:24 PM, Wei Huang wrote:
>> From: Christopher Covington
>
> I really appreciate your work on these patches. If for any or all of these
> you have more lines added/modified than me (or using any other better
> me
On Monday, November 21, 2016 04:42:10 PM Bjorn Helgaas wrote:
> On Mon, Nov 21, 2016 at 11:28:56PM +0100, Rafael J. Wysocki wrote:
> > On Monday, November 21, 2016 03:45:19 PM Bjorn Helgaas wrote:
> > > Since we register pcie_pme_driver only for PCI_EXP_TYPE_ROOT_PORT, the PME
> > > driver never cl
On Monday, November 21, 2016 9:57:51 AM CET Linus Torvalds wrote:
>
> - semaphores are "old-fashioned mutexes". A mutex is better than a
> semaphore, but a semaphore is better than just about all the other
> alternatives. There's nothing _wrong_ with using a semaphore per se.
>
> In this case, e
> > +static int ti_ads7950_read_raw(struct iio_dev *indio_dev,
> > + struct iio_chan_spec const *chan,
> > + int *val, int *val2, long m)
> > +{
> > + struct ti_ads7950_state *st = iio_priv(indio_dev);
> > + int ret;
> > +
> > + switch (m) {
From: Rafael J. Wysocki
The definition document of the Hierarchical Properties Extension UUID
for _DSD has been changed recently to allow local references to be
used as sub-node link targets (previously, it only allowed strings to
be used for that purpose).
Update the code in drivers/acpi/proper
Thomas Gleixner writes:
> When entering idle, it's a good oportunity to verify that the TSC_ADJUST
> MSR has not been tampered with (BIOS hiding SMM cycles). If tampering is
> detected, emit a warning and restore it to the previous value.
idle entry is a time critical code path too, because idle
On Mon, Nov 21, 2016 at 2:48 PM, kbuild test robot wrote:
> Hi Joel,
>
> [auto build test ERROR on tip/timers/core]
> [also build test ERROR on v4.9-rc6 next-20161117]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://git
On Mon, Nov 21, 2016 at 11:58:09PM +0100, Rafael J. Wysocki wrote:
> On Monday, November 21, 2016 04:42:10 PM Bjorn Helgaas wrote:
> > On Mon, Nov 21, 2016 at 11:28:56PM +0100, Rafael J. Wysocki wrote:
> > > On Monday, November 21, 2016 03:45:19 PM Bjorn Helgaas wrote:
> > > > Since we register pci
blkcg allocates some per-cgroup data structures with GFP_NOWAIT and
when that fails falls back to operations which aren't specific to the
cgroup. Occassional failures are expected under pressure and falling
back to non-cgroup operation is the right thing to do.
Unfortunately, I forgot to add __GF
Add PCI ID for Intel byt sdio host controller sub-vended by NI.
The controller has different behavior because of the board layout NI
puts it on.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/
On NI 9037 boards the max SDIO frequency is limited by trace lengths
and other layout choices. The max SDIO frequency is stored in an ACPI
table.
The driver reads the ACPI entry MXFQ during sdio_probe_slot and sets the
f_max field of the host.
Signed-off-by: Nathan Sullivan
Reviewed-by: Jaeden A
On some boards, max SDIO frequency is limited by trace lengths and other layout
choices. We would like a way to specify this limitation so the driver can
behave accordingly.
This patch set assumes that the limitation has been reported in an ACPI table
which the driver can check to get the max freq
One Thousand Gnomes wrote:
> You need to filter or lock down kernel module options because a lot of
> modules let you set the I/O port or similar (eg mmio) which means you can
> hack the entire machine with say the 8250 driver just by using it with an
> mmio of the right location to patch the sec
On 11/21, Georgi Djakov wrote:
> The clk_hw_onecell_data struct is missing references to the
> actual clocks. Fix this.
>
> Reported-by: Michael Scott
> Signed-off-by: Georgi Djakov
> ---
> drivers/clk/qcom/clk-smd-rpm.c | 20 +---
> 1 file changed, 9 insertions(+), 11 deletions
On Mon, 2016-11-21 at 22:34 +0100, Thomas Gleixner wrote:
> On Mon, 21 Nov 2016, Pandruvada, Srinivas wrote:
[...]
> Stupid me. I tested putting a socket offline, which works, but did
> not
> check what happens on module removal. Delta fix below. That needs to
> be
> folded into the series as the
Hi Heiko,
Today's linux-next merge of the rockchip tree got a conflict in:
arch/arm64/configs/defconfig
between commit:
a59294b2f7c7 ("ARM64: defconfig: Enable MMC related configs")
from the arm-soc tree and commit:
5295a3157348 ("arm64: defconfig: enable RK808 components")
from the ro
On 2016-11-20 21:54, Sanchayan Maity wrote:
> Current DMA implementation was not handling the continuous selection
> format viz. SPI chip select would be deasserted even between sequential
> serial transfers. Use the cs_change variable and correctly set or
> reset the CONT bit accordingly for case
On 2016-11-20 21:54, Sanchayan Maity wrote:
> Currently dmaengine_prep_slave_single was being called with length
> set to the complete DMA buffer size. This resulted in unwanted bytes
> being transferred to the SPI register leading to clock and MOSI lines
> having unwanted data even after chip sele
On 2016-11-20 21:54, Sanchayan Maity wrote:
> Code cleanup for improving code readability and error path fixes
> and cleanup removing use of devm_kfree.
Two things in one, not very nice. Especially the dma_free_coherent is
really a bug and the other is a cleanup. Can you make a separate patch
for
Hi Catalin,
Today's linux-next merge of the arm64 tree got a conflict in:
arch/arm64/include/asm/cpufeature.h
between commit:
272d01bd790f ("arm64: Fix circular include of asm/lse.h through
linux/jump_label.h")
from Linus' tree and commits:
a4023f682739 ("arm64: Add hypervisor safe hel
Hi,
On Mon, Nov 21, 2016 at 3:19 PM, Stephen Rothwell wrote:
> Hi Heiko,
>
> Today's linux-next merge of the rockchip tree got a conflict in:
>
> arch/arm64/configs/defconfig
>
> between commit:
>
> a59294b2f7c7 ("ARM64: defconfig: Enable MMC related configs")
>
> from the arm-soc tree and co
Neil,
Neil Armstrong writes:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> This commit renames the gxl-s905d-p23x DTSI in a common file for
> S905D p20x and S912 q20x boards.
s/p20x/p23x/ ??
> Then adds a meson-gxm d
Hello Dave,
Thanks for your review.
Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young:
> On 11/10/16 at 01:27am, Thiago Jung Bauermann wrote:
> > powerpc's purgatory.ro has 12 relocation types when built as
> > a relocatable object. To implement support for them requires
> > arch_ke
On 21.11.2016 21:23, Wim Osterholt wrote:
> On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote:
>>
>> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I
>> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now.
>
> Neither 4.8.10, nor 4.8.9 show the b
On 11/20/2016 1:26 PM, Stefan Wahren wrote:
> This patch series fixes several parameter handling issues
> found on bcm2835 in gadget mode. It's based on Felipe's USB next.
>
> Stefan Wahren (5):
> usb: dwc2: Do not set host parameter in peripheral mode
> usb: dwc2: fix dwc2_get_device_property
On 2016.11.17 14:34 Rafael J. Wysocki wrote:
> v2 -> v3:
> The previous iteration didn't work correcty if ondemand was the default
> governor, because it didn't set policy->cur during initialization and
> that caused cpufreq_dbs_governor_start() to return an error (thanks to
> Srinovas for find
On Mon, Nov 21, 2016 at 02:21:40PM +0100, Takashi Iwai wrote:
> The zram hot removal code calls idr_remove() even when zram_remove()
> returns an error (typically -EBUSY). This results in a leftover at
> the device release, eventually leading to a crash when the module is
> reloaded.
>
> As descr
This series updates the device tree for the upcoming V1.1 HW samples.
All changes are purely opportunistic meaning they fix stuff which on
older HW was anyway broken so there should be no backwards
compatibility issues.
Marcel Ziswiler (6):
apalis-tk1: remove spurious new lines
apalis-tk1: t
Configure DP_HPD_PFF0 pin as optional DisplayPort hot-plug detect.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/tegra124-apalis.dtsi
b/arch/arm/boot/dts/tegra124-apalis.dtsi
index
Now with the new V1.1A HW card detect being implemented update resp.
compatibility information.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/tegra124-apalis.dtsi
b/arch/arm/boot/d
Configure Apalis MMC1 D6 GPIO on SDMMC3_CLK_LB_IN as reserved function
without any pull-up/down.
Configure GPIO_PV2 as SD1_CD# according to latest V1.1 HW.
Leave SDMMC3_CLK_LB_OUT muxed as SDMMC3 with output driver enabled aka
not tristated and input driver enabled as well as it features some
mag
Add sd card detect SD1_CD# applicable for V1.1 modules using GPIO_PV2.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-eval.dts | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/arch/arm/boot/dts/tegra124-apalis-eval.dts
b/arch/arm/boot/dts/teg
Pull-up GPIO_PI6 connected to TMP451's ALERT#/THERM2#.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/tegra124-apalis.dtsi
b/arch/arm/boot/dts/tegra124-apalis.dtsi
index 6aa4952
Hi Miklos,
After merging the overlayfs tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
In file included from fs/overlayfs/dir.c:20:0:
fs/overlayfs/dir.c: In function 'ovl_set_redirect':
fs/overlayfs/overlayfs.h:92:6: warning: 'ret' may be used uninitialized in this
Remove some spurious new lines.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-eval.dts | 1 -
arch/arm/boot/dts/tegra124-apalis.dtsi | 12
2 files changed, 13 deletions(-)
diff --git a/arch/arm/boot/dts/tegra124-apalis-eval.dts
b/arch/arm/boot/dts/tegr
CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
However it does not take into account the memmap= parameter passed in from
the kernel commandline. This results in the kernel sometimes being put in
the middle of the user memmap. Check has been added in the kaslr in order
to avoi
On Mon, Nov 21, 2016 at 10:49 PM, Mike Snitzer wrote:
> On Fri, Nov 11 2016 at 7:05am -0500,
> Ming Lei wrote:
>
>> Firstly we have mature bvec/bio iterator helper for iterate each
>> page in one bio, not necessary to reinvent a wheel to do that.
>>
>> Secondly the coming multipage bvecs require
Provide the ability to perform mixed-mode runtime service calls for x86 in
the same way that commit 0a637ee61247bd4bed9b2a07568ef7a1cfc76187 provides
the ability to invoke arbitrary boot services.
Suggested-by: Lukas Wunner
Signed-off-by: David Howells
---
arch/x86/boot/compressed/eboot.c |
Provide the ability to perform mixed-mode runtime service calls for arm in
the same way that commit 0a637ee61247bd4bed9b2a07568ef7a1cfc76187 provides
the ability to invoke arbitrary boot services.
Suggested-by: Lukas Wunner
Signed-off-by: David Howells
---
arch/arm/include/asm/efi.h |1 +
From: Josh Boyer
A user can manually tell the shim boot loader to disable validation of
images it loads. When a user does this, it creates a UEFI variable called
MokSBState that does not have the runtime attribute set. Given that the
user explicitly disabled validation, we can honor that and no
Add the definitions for shim and image security database, both of which
are used widely in various Linux distros.
Signed-off-by: Josh Boyer
Signed-off-by: David Howells
Reviewed-by: Ard Biesheuvel
---
include/linux/efi.h |3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/
Get the firmware's secure-boot status in the kernel boot wrapper and stash
it somewhere that the main kernel image can find.
Signed-off-by: Matthew Garrett
Signed-off-by: David Howells
---
Documentation/x86/zero-page.txt |2 +
arch/x86/boot/compressed/eboot.c |5 ++
From: Josh Boyer
UEFI machines can be booted in Secure Boot mode. Add a EFI_SECURE_BOOT bit
for use with efi_enabled.
Signed-off-by: Josh Boyer
Signed-off-by: David Howells
---
arch/x86/kernel/setup.c |5 +
include/linux/efi.h |1 +
2 files changed, 6 insertions(+)
diff --g
On Sun, 2016-10-30 at 21:40:47 UTC, Christophe Jaillet wrote:
> 'cxl_dev_context_init()' returns an error pointer in case of error, not
> NULL. So test it with IS_ERR.
>
> Signed-off-by: Christophe JAILLET
> Reviewed-by: Andrew Donnellan
> Acked-by: Frederic Barrat
> Acked-by: Ian Munsie
Appl
On Sun, 2016-10-30 at 21:34:51 UTC, Christophe Jaillet wrote:
> 'cxl_dev_context_init()' returns an error pointer in case of error, not
> NULL. So test it with IS_ERR.
>
> Signed-off-by: Christophe JAILLET
> Reviewed-by: Andrew Donnellan
> Acked-by: Frederic Barrat
> Acked-by: Ian Munsie
Appl
On Wed, 2016-09-21 at 14:49:27 UTC, Christophe Leroy wrote:
> MIN_HUGEPTE_SHIFT hasn't been used since commit d1837cba5d5d5
> ("powerpc/mm: Cleanup initialization of hugepages on powerpc")
>
> Signed-off-by: Christophe Leroy
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/c05f
On Sun, 2016-10-30 at 19:35:57 UTC, Christophe Jaillet wrote:
> 'cxl_context_alloc()' does not return an error pointer. It is just a
> shortcut for a call to 'kzalloc' with 'sizeof(struct cxl_context)' as the
> size parameter.
>
> So its return value should be compared with NULL.
> While fixing it
On Mon, Nov 14, 2016 at 09:35:53AM +0800, Peter Chen wrote:
> We have an well-known problem that the device needs to do some power
> sequence before it can be recognized by related host, the typical
> example like hard-wired mmc devices and usb devices.
>
> This power sequence is hard to be descri
From: Archit Taneja
On some adv7511 implementations, we can get some spurious
disconnect signals which can cause monitor probing to fail.
This patch enables HPD (hot plug detect) interrupt support
which allows the monitor to be properly re-initialized when
the spurious disconnect signal goes awa
Secton 4.1 of the adv7511 programming guide advises one waits
200ms after powering on the chip before trying to communicate
with it via i2c. Not doing so can cause reliability issues when
probing the EDID.
See:
http://www.analog.com/media/en/technical-documentation/user-guides/ADV7511_Programming_
I had been seeing some EDID probing issues with the adv7511 driver
on HiKey recently. After talking with Archit and spending some time
reading the programming guide, I put together the following patch
set which seems to resolve the EDID probing issues.
I wanted to send these out for some early rev
In chasing down issues with EDID probing, I found some
duplicated but incomplete logic used to power the chip on and
off.
This patch refactors the adv7511_power_on/off functions, so
they can be used for internal needs, and replaces duplicative
logic that powers the chip on and off around the EDID
This adds a new driver for the TI ADS7950 family of ADC chips. These
communicate using SPI and come in 8/10/12-bit and 4/8/12/16 channel
varieties.
Signed-off-by: David Lechner
---
v3 changes:
* Use spi_async() instead of spi_sync() in ti_ads7950_trigger_handler()
* Fix scaling in ti_ads7950_re
"Kirill A. Shutemov" writes:
> On Wed, Nov 16, 2016 at 11:10:48AM +0800, Huang, Ying wrote:
>> From: Huang Ying
>>
>> This patchset is to optimize the performance of Transparent Huge Page
>> (THP) swap.
>>
>> Hi, Andrew, could you help me to check whether the overall design is
>> reasonable?
>
On Nov 21, 2016, at 8:28 AM, Wolfgang Walter wrote:
>
> Hello,
>
> I'm testing EXT4 with an external journal (data=journal). When writing I
> rather often get
>
> JBD2: Spotted dirty metadata buffer (dev = dm-22, blocknr =
> 1008028301). There's a risk of filesystem corruption in case o
From: Reto Schneider
Date: Mon, 12 Oct 2015 01:44:51 +0200
Subject: [PATCH 2/2] iio: adis16203: Fix copyright year
The copyright year can not be in the future.
Signed-off-by: Reto Schneider
---
drivers/staging/iio/accel/adis16203_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
between commit:
ba1ffd74df74 ("stmmac: fix PTP support for GMAC4")
from the net tree and commit:
38ddc59d65b6 ("net: stmmac: replace all pr_xxx by their netdev_xxx
On Mon, 21 Nov 2016 19:13:55 +
Russell King - ARM Linux wrote:
> On Mon, Nov 21, 2016 at 07:46:44PM +0100, Uwe Kleine-König wrote:
> > Hello,
> >
> > On Mon, Oct 24, 2016 at 05:05:26PM +0200, Arnd Bergmann wrote:
> > > This adds an asm/asm-prototypes.h header for ARM to fix the
> > > broke
On Thu, Nov 18, 2016 at 12:31 PM, Han Xu wrote:
> On Thu, Nov 17, 2016 at 3:14 AM, Yao Yuan wrote:
> > On Thu, Nov 17, 2016 at 06:50:55AM +, Krzeminski, Marcin (Nokia -
> PL/Wroclaw) wrote:
> >> > > > On Thu, Aug 18, 2016 at 2:38 AM, Yunhui Cui
> >> > > >
> >> > > > wrote:
> >> > > > > From:
From: Markus Mayer
This CPUfreq driver provides basic frequency scaling for older Broadcom
STB SoCs that do not use AVS firmware with DVFS support. There is no
support for voltage scaling.
Signed-off-by: Markus Mayer
---
drivers/cpufreq/Kconfig.arm | 12 ++
drivers/cpufreq/Makefile
On 21 November 2016 at 17:06, Markus Mayer wrote:
> From: Markus Mayer
>
> This CPUfreq driver provides basic frequency scaling for older Broadcom
> STB SoCs that do not use AVS firmware with DVFS support. There is no
> support for voltage scaling.
>
> Signed-off-by: Markus Mayer
> ---
I meant
From: Reto Schneider
Date: Sun, 20 Nov 2016 22:11:24 +0100
Subject: [PATCH 1/2] iio: adis1620x: Fix mixed up device descriptions
The module descriptions for the ADIS 16201, 16203 and 16209 drivers do not
match the actual function of the devices. Update them accordingly to fix
this.
Signed-off-by
Hi Rob
> These are v4 of OF graph base simple-card patch-set.
> v3 patch had ALSA SoC side prepare patches as [1/xx] - [5/xx],
> but these are already accepted by Mark, thus, this v4 doesn't
> include these.
> Mainly, v4 solved non-OF case compile error which was reported
> by kbuild.
About "typ
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/net/ethernet/marvell/mvneta_bm.c: In function 'mvneta_bm_construct':
drivers/net/ethernet/marvell/mvneta_bm.c:103:16: warning: cast from pointer to
integer of different size [
Cc Andrew
On (11/22/16 09:11), Minchan Kim wrote:
[..]
> > This patch adds the proper error check in hot_remove_store() not to
> > call idr_remove() unconditionally.
> >
> > Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1010970
> > Reported-and-tested-by: David Disseldorp
> > Reviewed-
Hi Sergey,
On Tue, Nov 22, 2016 at 10:09:30AM +0900, Sergey Senozhatsky wrote:
> Cc Andrew
>
> On (11/22/16 09:11), Minchan Kim wrote:
> [..]
> > > This patch adds the proper error check in hot_remove_store() not to
> > > call idr_remove() unconditionally.
> > >
> > > Bugzilla: https://bugzilla.
On 11/22/2016 02:06 AM, Krzysztof Kozlowski wrote:
> On Mon, Nov 21, 2016 at 04:10:32PM +0900, Jaehoon Chung wrote:
>> Odroid-xu3/4 didn't need to use the cd-gpios for detecting card.
>> Because Host controller has the CDETECT register through SDx_CDN line.
>> Host controller can know whether card
On (11/22/16 10:22), Minchan Kim wrote:
[..]
> > > Acked-by: Minchan Kim
> >
> > Link: lkml.kernel.org/r/20161121132140.12683-1-ti...@suse.de
> > Fixes: 17ec4cd98578 ("zram: don't call idr_remove() from zram_remove()")
> > Cc: [4.5+]
>
> 17ec4cd98578 marked as stable: [4.2+] so we should mar
+Thomas, Gregory,
On 11/21/2016 05:22 PM, Stephen Rothwell wrote:
[snip]
>
> Introduced by commit
>
> a0627f776a45 ("net: marvell: Allow drivers to be built with COMPILE_TEST")
>
> "a few warnings" is a matter of perception. :-(
Thomas, based on our IRC conversation, do you already have pat
On 11/21/16 at 09:49pm, Thiago Jung Bauermann wrote:
> Hello Dave,
>
> Thanks for your review.
>
> Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young:
> > On 11/10/16 at 01:27am, Thiago Jung Bauermann wrote:
> > > powerpc's purgatory.ro has 12 relocation types when built as
> > > a r
On Tue, Nov 22, 2016 at 10:28:12AM +0900, Sergey Senozhatsky wrote:
> On (11/22/16 10:22), Minchan Kim wrote:
> [..]
> > > > Acked-by: Minchan Kim
> > >
> > > Link: lkml.kernel.org/r/20161121132140.12683-1-ti...@suse.de
> > > Fixes: 17ec4cd98578 ("zram: don't call idr_remove() from zram_remove()"
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/i2c/tda998x_drv.c
between commit:
ad975f9364a3 ("drm/i2c: tda998x: group audio functions together")
from the arm tree and commit:
c20ea8fd4986 ("drm/i2c/tda998x: mark symbol static where possible")
fro
801 - 893 of 893 matches
Mail list logo
