Hi Andy and Jonathan,
On Fri, Aug 03, 2018 at 11:09:22PM +0100, Jonathan Cameron wrote:
> On Thu, 2 Aug 2018 22:52:00 +0300
> Andy Shevchenko wrote:
>
> > On Thu, Aug 2, 2018 at 10:15 PM, Marcus Folkesson
> > wrote:
> > > MCP3911 is a dual channel Analog Front End (AFE) containing two
> > > sy
On Fri, 03 Aug 2018 22:52:33 +0200,
Gustavo A. R. Silva wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Notice that in this particular case, I replaced the code comment with
> a proper "fall through" annotation, which
On Fri, 03 Aug 2018 22:53:54 +0200,
Gustavo A. R. Silva wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Warning level 2 was used: -Wimplicit-fallthrough=2
>
> Signed-off-by: Gustavo A. R. Silva
Applied, thanks.
T
Hi Boris,
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Saturday, August 4, 2018 10:49 AM
> Subject: Re: [PATCH v3 1/4] edac: synps: Add platform specific structures for
> ddrc controller
>
> On Thu, Aug 02, 2018 at 06:21:19PM +0530, Manish Narani wrote:
>
On Sat, 4 Aug 2018 14:26:18 +0900
KOBAYASHI Yoshitake wrote:
> This patch is a patch to support TOSHIBA MEMORY CORPORATION BENAND
> memory devices. This use vendor specific command
> (TOSHIBA_NAND_CMD_ECC_STATUS) to know the exact bitflips. However, I
On Sat, 4 Aug 2018 14:25:52 +0900
KOBAYASHI Yoshitake wrote:
> This patch is a patch to support TOSHIBA MEMORY CORPORATION BENAND
> memory devices. Check the status of the built-in ECC with the Read
> Status command without using the vendor specific command. The Read
> Status command only know
This patch is a patch to support TOSHIBA MEMORY CORPORATION BENAND
memory devices. This use vendor specific command
(TOSHIBA_NAND_CMD_ECC_STATUS) to know the exact bitflips. However, I
could not test this patch because I do not have a platform that
supports chip-> exec_op. Therefore, I post this
This patch is a patch to support TOSHIBA MEMORY CORPORATION BENAND
memory devices. Check the status of the built-in ECC with the Read
Status command without using the vendor specific command. The Read
Status command only knows whether there was bitflips above the
threshold and can not get accurat
On Thu, Aug 02, 2018 at 06:21:19PM +0530, Manish Narani wrote:
> This patch adds platform specific structures, so that we can add
"This patch" in a commit message is tautologically redundant.
> different IP support later using quirks.
>
> Signed-off-by: Manish Narani
> ---
> drivers/edac/synop
Hi Linus,
Here's one more patch for 4.18 to fix a coding error in the iomap_bmap
function introduced in -rc1.
This series has been run through a full xfstests run during the week and
through a quick xfstests run against this morning's master, with no
major failures reported.
--D
The following c
2018-08-04 13:47 GMT+09:00 Masahiro Yamada :
> Randy Dunlap reports UML occasionally fails to build with -j and
> O= options.
>
> make[1]: Entering directory '/home/rdunlap/mmotm-2018-0802-1529/UM64'
> UPD include/generated/uapi/linux/version.h
> WRAParch/x86/include/generated/asm
Hi Masami,
On Fri, Aug 3, 2018 at 12:23 AM, Masami Hiramatsu wrote:
> Hi Joel,
>
> Thank you for trying to fix that.
>
> On Thu, 2 Aug 2018 19:57:09 -0700
> Joel Fernandes wrote:
>
>> Hi Masami,
>>
>> On Thu, Aug 2, 2018 at 7:55 AM, Masami Hiramatsu wrote:
>> > Hi Joel,
>> >
>> > I found this c
Now that '%asm-generic' is added to no-dot-config-targets,
'make asm-generic' does not include the kernel configuration.
You can simply do 'make asm-generic' in the recursed top Makefile
without bothering syncconfig.
Signed-off-by: Masahiro Yamada
---
arch/um/Makefile | 8 +---
1 file chan
Randy Dunlap reports UML occasionally fails to build with -j and
O= options.
make[1]: Entering directory '/home/rdunlap/mmotm-2018-0802-1529/UM64'
UPD include/generated/uapi/linux/version.h
WRAParch/x86/include/generated/asm/dma-contiguous.h
WRAParch/x86/include/generated
asm-generic and uapi-asm-generic do not depend on the kernel
configuration. In fact, uapi-asm-generic is the prerequisite of
headers_{install,check}, hence it should not require the .config file.
Signed-off-by: Masahiro Yamada
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
1/3 fixes the build failure reported by Randy.
(I may have seen a similar report before, but I cannot recall it.)
2/3 and 3/3 clean-up the Makefile a bit more.
I'd like to apply this series to kbuild tree.
Ack from UML folks are appreciated.
Masahiro Yamada (3):
um: fix parallel building w
On Wed, 01 Aug 2018 18:26:48 PDT (-0700), zong...@gmail.com wrote:
Palmer Dabbelt 於 2018年8月2日 週四 上午8:38寫道：
On Wed, 20 Jun 2018 18:40:07 PDT (-0700), z...@andestech.com wrote:
> The stvec's value must be 4 byte alignment by specification definition.
> This directive avoids to stvec be set the n
On Wed, 01 Aug 2018 11:55:06 PDT (-0700), t...@linutronix.de wrote:
On Wed, 25 Jul 2018, Christoph Hellwig wrote:
On Wed, Jul 25, 2018 at 12:18:39PM +0100, Marc Zyngier wrote:
> This feels odd. It means that you cannot have the following sequence:
>
>local_irq_disable();
>enable_irq(x)
On Wed, 01 Aug 2018 11:23:43 PDT (-0700), Andrew Waterman wrote:
On Wed, Aug 1, 2018 at 10:55 AM, Palmer Dabbelt wrote:
On Tue, 26 Jun 2018 21:22:26 PDT (-0700), alan...@andestech.com wrote:
This patch adds an option, CONFIG_FPU, to enable/disable floating
procedures. Also, some style issues
Instantiating the sm501 OHCI subdevice results in a kernel warning.
sm501-usb sm501-usb: SM501 OHCI
sm501-usb sm501-usb: new USB bus registered, assigned bus number 1
WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
ohci_init+0x194/0x2d8
Modules linked in:
CPU: 0 PID: 1 Comm: swapper T
2018-08-04 0:41 GMT+09:00 Randy Dunlap :
> On 08/02/2018 05:13 PM, Randy Dunlap wrote:
>> Hi Yamada-san,
>>
>> I see this every few weeks. It's not reproducible (it depends
>> on the moon, Mars, etc.).
>>
>> I'm using O=builddir. The build log is short (below).
>>
>> Do you see a makefile problem
On Fri, Aug 3, 2018 at 2:16 AM, Geliang Tang wrote:
> Fix build error:
>
>fs/pstore/platform.o: In function `zbufsize_zstd':
>>> platform.c:(.text+0x172): undefined reference to `ZSTD_compressBound'
>
> Signed-off-by: Geliang Tang
Thanks! I'll squash this into the original commit.
-Kees
>
From: "Wesley W. Terpstra"
This is used of the HiFive Unleashed development board.
Signed-off-by: Wesley W. Terpstra
Signed-off-by: Palmer Dabbelt
---
drivers/mtd/spi-nor/spi-nor.c | 47 ++-
include/linux/mtd/spi-nor.h | 2 ++
2 files changed, 48 ins
On Wed, 01 Aug 2018 11:26:31 PDT (-0700), r...@kernel.org wrote:
On Wed, Aug 1, 2018 at 1:12 AM Christoph Hellwig wrote:
On Tue, Jul 31, 2018 at 04:46:30PM -0600, Rob Herring wrote:
> Perhaps this should be 'sifive,plic0'
Excepet for the fact this the old name has already been in shipping
har
On Thu, 2018-08-02 at 23:20 +0200, Michal Zylowski wrote:
> Current checkpatch implementation permits notation like:
> } else{
> in kernel code.
> It looks like oversight and inconsistency in checkpatch rules (e.g.
> instruction like 'do' is tested).
>
> Add regex for checking space after 'else' k
On Fri, Aug 3, 2018 at 5:58 PM Mikulas Patocka wrote:
>
>
>
> On Fri, 3 Aug 2018, Richard Earnshaw (lists) wrote:
>
> > Whoa, hold on.
> >
> > Memcpy should never be used on device memory. Period. Memcpy doesn't
> > know anything about what size of access is needed for accessing a device.
> >
>
Add the ability to have an override for the location of the
MAINTAINERS file.
Miscellanea:
o Properly indent a few lines with leading spaces
Suggested-by: Don Zickus
Signed-off-by: Joe Perches
---
scripts/get_maintainer.pl | 48 +--
1 file changed,
On Fri, 3 Aug 2018, Richard Earnshaw (lists) wrote:
> Whoa, hold on.
>
> Memcpy should never be used on device memory. Period. Memcpy doesn't
> know anything about what size of access is needed for accessing a device.
>
> But why is the buffer in device memory rather than some other form of
On Thu, 2 Aug 2018, Dave Hansen wrote:
>
> From: Dave Hansen
>
> The kernel image is mapped into two places in the virtual address
> space (addresses without KASLR, of course):
>
> 1. The kernel direct map (0x8800)
> 2. The "high kernel map" (0x8100)
>
> We
On Thu, 2 Aug 2018, Dave Hansen wrote:
>
> From: Dave Hansen
>
> The x86 code has several places where it frees parts of kernel image:
>
> 1. Unused SMP alternative
> 2. __init code
> 3. The hole between text and rodata
> 4. The hole between rodata and data
>
> We call free_init_pages() to
Quoting Taniya Das (2018-07-24 03:42:49)
> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt
> b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt
> new file mode 100644
> index 000..22d4355
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/cpufreq/
Hi Krzysztof,
On Wed, Jul 25, 2018 at 5:53 PM, Krzysztof Kozlowski wrote:
> In case of Device Tree platforms, even though the Samsung PMIC sec
> device is instantiated from DT, the driver is still matched through I2C
> module alias. That is because I2C core always reports an I2C module
> alias i
On Fri, 3 Aug 2018 11:51:43 +0900 Minchan Kim wrote:
> > Is it legitimate to be altering the bdi capabilities at this level? Or
> > is this hacky?
>
> Most of device's bdi capability seems to be static but there are few drivers
> which can change capability. For example, BDI_CAP_STABLE_WRITES
>
Hi,
On Fri, Aug 03, 2018 at 03:39:24PM +0200, Oleg Nesterov wrote:
> On 08/02, Dmitry Safonov wrote:
> > 2018-07-31 1:56 GMT+01:00 Ivan Delalande :
> > > We were seeing unexplained segfaults in coreutils processes and other
> > > basic utilities that we tracked down to binfmt_elf failing to load
>
On Tue, Jul 31, 2018 at 9:13 AM Georgi Djakov wrote:
>
> On some Qualcomm SoCs, there is a remote processor, which controls some of
> the Network-On-Chip interconnect resources. Other CPUs express their needs
> by communicating with this processor. Add a driver to handle communication
> with this
On Tue, Jul 31, 2018 at 9:13 AM Georgi Djakov wrote:
>
> Add a functionality to provide information about the current constraints
> per each node and provider.
>
> Signed-off-by: Georgi Djakov
> ---
> drivers/interconnect/core.c | 78 +
> 1 file changed, 78 in
On Tue, Jul 31, 2018 at 9:13 AM Georgi Djakov wrote:
>
> Currently we support only platform data for specifying the interconnect
> endpoints. As now the endpoints are hard-coded into the consumer driver
> this may lead to complications when a single driver is used by multiple
> SoCs, which may hav
On Fri, Aug 03, 2018 at 03:51:20PM -0700, Andrew Morton wrote:
> On Fri, 03 Aug 2018 18:36:14 +0300 Kirill Tkhai wrote:
> > The patch introduces a special value SHRINKER_REGISTERING to use instead
> > of list_empty() to detect a semi-registered shrinker.
>
> All this isn't terribly nice. Why can
On Tue, Jul 31, 2018 at 9:13 AM Georgi Djakov wrote:
>
> Add driver for the Qualcomm interconnect buses found in msm8916 based
> platforms.
>
> Signed-off-by: Georgi Djakov
> ---
> drivers/interconnect/Kconfig| 5 +
> drivers/interconnect/Makefile | 1 +
> drivers/interconnect/
On Tue, Jul 31, 2018 at 9:13 AM Georgi Djakov wrote:
>
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the interc
On Fri, 03 Aug 2018 18:36:14 +0300 Kirill Tkhai wrote:
> The patch introduces a special value SHRINKER_REGISTERING to use instead
> of list_empty() to detect a semi-registered shrinker.
>
> This should be clearer for a reader since "list is empty" is not
> an intuitive state of a shrinker), and
On 03.08.2018 22:33, Nick Desaulniers wrote:
> On Fri, Aug 3, 2018 at 12:09 PM John David Anglin
> wrote:
>>
>> On 2018-08-03 2:11 PM, Nick Desaulniers wrote:
>>> But the kernel uses the generic_THIS_IP_ *everywhere*, not parisc's
>>> custom current_text_addr(). So if this did actually break un
On Fri, Aug 03, 2018 at 02:22:57PM -0700, Guenter Roeck wrote:
> Hi,
>
> On Thu, Apr 12, 2018 at 12:13:22PM -0700, Matthew Wilcox wrote:
> > From: Matthew Wilcox
> >
> > __GFP_ZERO requests that the object be initialised to all-zeroes,
> > while the purpose of a constructor is to initialise an o
Quoting skan...@codeaurora.org (2018-08-03 12:52:48)
> On 2018-08-03 12:40, Evan Green wrote:
> > Hi Taniya,
> >
> > On Tue, Jul 24, 2018 at 3:44 AM Taniya Das wrote:
> >>
> >> + if (src)
> >> + c->table[i].frequency = c->xo_rate * lval /
> >> 1000;
> >> +
This adds the display clock controller node to sdm845 based on the
examples in the bindings.
Signed-off-by: Matthias Kaehlcke
---
The dispcc driver and DT bindings landed in the clk-qcom-dispcc-845
branch of the clk tree.
arch/arm64/boot/dts/qcom/sdm845.dtsi | 9 +
1 file changed, 9 ins
On Thu, 2 Aug 2018 16:01:32 +0200
Parthiban Nallathambi wrote:
> Hi Jonathan,
>
> General query, for threshold events and persistence value (period) we
> don't have any direct MACROS similar to IIO_CONST_ATTR_INT_TIME_AVAIL
> as ABI to show the available/range of values.
>
> For most light and
On Fri, 3 Aug 2018, Heiner Kallweit wrote:
> On 03.08.2018 22:00, Thomas Gleixner wrote:
> > On Fri, 3 Aug 2018, Heiner Kallweit wrote:
> >
> >> In case of a domain hierarchy we may miss the IRQCHIP_ONESHOT_SAFE
> >> flag because we look at top of the stack only. See also discussion
> >> here: htt
On Thu, 2 Aug 2018 22:52:00 +0300
Andy Shevchenko wrote:
> On Thu, Aug 2, 2018 at 10:15 PM, Marcus Folkesson
> wrote:
> > MCP3911 is a dual channel Analog Front End (AFE) containing two
> > synchronous sampling delta-sigma Analog-to-Digital Converters (ADC).
> >
> > Signed-off-by: Marcus Folkess
Greetings,
I represent business group in Middle East looking for projects to
fund; we seek any business that will guaranty a safe and secure
return
on investments. Alternative powers, movies, start up companies
etc. We
are also looking for commercial building projects, hotels,
casino,
strip m
Since there's no point in doing anything in this case, immediately exit the
process.
And take the opportunity to improve the error message.
Before:
# ./userfaultfd shmem 10 10
nr_pages: 160, nr_pages_per_cpu: 40
userfaultfd syscall not available in this kernel
# echo $?
1
After:
#
If the userfaultfd test is run on a kernel with CONFIG_USERFAULTFD=n, it
will report that the system call is not available yet go ahead and continue
anyway:
# ./userfaultfd anon 30 1
nr_pages: 480, nr_pages_per_cpu: 120
userfaultfd syscall not available in this kernel
bounces: 0, mode:, re
Hello,
A tester ran the upstream selftest on a distro kernel and sounded the alarm when
it reported failures for features which aren't included in that kernel.
This patch set improves the test behavior in that scenario.
Changes since v1:
- Patch "userfaultfd: selftest: Skip test if userfaultfd(
If userfaultfd runs on a system that doesn't support UFFDIO_ZEROPAGE for
shared memory, it currently ends with error code 1 which indicates test
failure:
# ./userfaultfd shmem 10 10
nr_pages: 160, nr_pages_per_cpu: 80
bounces: 9, mode: rnd poll, unexpected missing ioctl for anon memory
# e
If userfaultfd runs on a system that doesn't support some feature it is
trying to test, it currently ends with error code 1 which indicates
test failure:
# ./userfaultfd anon 10 10
nr_pages: 160, nr_pages_per_cpu: 80
bounces: 9, mode: rnd poll, userfaults: 7 59
bounces: 8, mode: poll, user
On Wed, Aug 1, 2018 at 10:17 AM wrote:
> Yes, in practice what's actually going to happen is that the
> runtime_remaining will be put to 1 by distribute, the cfs_rq will be
> unthrottled, and then when it runs it will go negative immediately and
> hit the negative check in expires, so expires_seq
On Thu, 2 Aug 2018 20:18:59 -0400
Brian Masney wrote:
> This patch adds avago,apds9930 to the tsl2772 bindings.
>
> Signed-off-by: Brian Masney
As before I'll pick up with the rest.
Thanks,
Jonathan
> ---
> Documentation/devicetree/bindings/iio/light/tsl2772.txt | 1 +
> 1 file changed, 1
On Thu, 2 Aug 2018 20:18:58 -0400
Brian Masney wrote:
> The Avago APDS9930 has the same register set as the TAOS/AMS TSL2772 so
> this patch adds the correct bindings and the appropriate LUX table
> values derived from the values in the datasheet. Driver was tested on a
> LG Nexus 5 (hammerhead)
On Thu, 2 Aug 2018 20:18:57 -0400
Brian Masney wrote:
> This patch adds device tree bindings to the tsl2772 driver for the
> regulator framework.
>
> Signed-off-by: Brian Masney
I suspect Rob will tell you this should really have been in the same
patch as the earlier bindings. There is no ne
On Thu, 2 Aug 2018 20:18:56 -0400
Brian Masney wrote:
> This patch adds support for the regulator framework to the tsl2772
> driver. Driver was tested using a LG Nexus 5 (hammerhead) phone with
> the two regulators and on a Raspberry Pi 2 without any regulators
> controlling the power to the sen
On Thu, 2 Aug 2018 20:18:55 -0400
Brian Masney wrote:
> This patch adds the new properties amstaos,proximity-diodes and
> led-max-microamp to the tsl2772 driver. This patch also removes the
> driver from the trivial-devices.txt.
>
> Signed-off-by: Brian Masney
> ---
This and the implementation
Hi!
I know bogomips are supposed to be bogus, but 72000 of them? On
Genuine Intel(R) CPU T2400 @ 1.83GHz ? I could live with
1830 bogomips, or maybe 500, or maybe 6000, but 72k is a bit
much. 32-bit kernel.
(And no, it does not break anything AFAICT, but it looks weird.)
4.18.0-rc5 on
Hi Yixun, thanks for the review
2018-08-03 16:14 GMT+02:00 Yixun Lan :
>> +config MESON_CANVAS
>> + bool "Amlogic Meson Canvas driver"
> shouldn't this a 'tristate'? since you'd make the driver a kernel module..
Yep it should!
I well noted your other feedback and v2 will have fixes for the
On Thu, 2 Aug 2018 20:18:53 -0400
Brian Masney wrote:
> This patch adds device tree bindings for the mpu6515 to the LG Nexus 5
> (hammerhead) phone. Confirmed that the gyroscope / accelerometer
> (mpu6515), magnetometer (ak8963), and temperature / pressure (bmp280)
> sensors are available on the
On Thu, 2 Aug 2018 20:18:52 -0400
Brian Masney wrote:
> This patch adds support for the regulator framework to the mpu6050
> driver.
>
> Signed-off-by: Brian Masney
> Signed-off-by: Jonathan Marek
> Acked-by: Rob Herring
Applied to the togreg branch of iio.git and pushed out as testing
for t
Update the driver to the pci_alloc_irq_vectors API, this allows to get
rid of legacy calls like pci_enable_msi(). Another benefit is that
no driver change would be needed in case the hardware starts
supporting MSI-X.
Signed-off-by: Heiner Kallweit
---
drivers/misc/mei/pci-me.c | 25 +++-
mei_start() prints an error message and returns -ENODEV on failure,
so we don't have to duplicate this in the caller.
Signed-off-by: Heiner Kallweit
---
drivers/misc/mei/pci-me.c | 6 ++
drivers/misc/mei/pci-txe.c | 6 ++
2 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/dr
Usually it's not needed to free and re-request the interrupt in a
suspend / resume cycle, so remove this.
Signed-off-by: Heiner Kallweit
---
drivers/misc/mei/pci-me.c | 20
drivers/misc/mei/pci-txe.c | 27 +--
2 files changed, 1 insertion(+), 46 dele
This series migrates the driver to the pci_alloc_irq_vectors API and
includes also smaller improvements.
MEI_ME was tested on a Zotac CI321. MEI_TXE is compile-tested only.
Heiner Kallweit (3):
mei: Don't free irq when suspending
mei: Migrate to pci_alloc_irq_vectors API
mei: Improve usage
On Fri, 3 Aug 2018 17:35:06 +0530
Himanshu Jha wrote:
> On Fri, Aug 03, 2018 at 12:55:51PM +0100, Colin King wrote:
> > From: Colin Ian King
> >
> > fix spelling mistake in dev_err error message text
> >
> > Signed-off-by: Colin Ian King
>
> Oops! Thanks for the patch Colin.
>
> Reviewed-
On Fri, 3 Aug 2018 16:02:21 +0300
Stefan Popa wrote:
> This patch adds the option for the user to select the filter bandwidth. The
> user can also read the available bandwidths which are always adjusted to be
> at most half of the sampling frequency. Furthermore, the currently selected
> bandwidt
On Fri, 3 Aug 2018 16:02:20 +0300
Stefan Popa wrote:
> This patch adds the option for the user to select the sampling frequency.
> Also, the user can read the available frequencies and read the currently
> set frequency via the read_raw function. The frequency can be set via the
> write_raw funct
On Fri, 3 Aug 2018 16:02:19 +0300
Stefan Popa wrote:
> This patch adds support for the adxl372 FIFO. In order to accomplish this,
> triggered buffers were used.
>
> The number of FIFO samples which trigger the watermark interrupt can be
> configured by using the buffer watermark. The FIFO format
On Fri, 3 Aug 2018 16:02:18 +0300
Stefan Popa wrote:
> From: Crestez Dan Leonard
>
> The regmap API usually assumes that bulk read operations will read a
> range of registers but some I2C/SPI devices have certain registers for
> which a such a read operation will return data from an internal FI
Hi,
On Thu, Apr 12, 2018 at 12:13:22PM -0700, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> __GFP_ZERO requests that the object be initialised to all-zeroes,
> while the purpose of a constructor is to initialise an object to a
> particular pattern. We cannot do both. Add a warning to catch
On Fri, 3 Aug 2018 16:02:17 +0300
Stefan Popa wrote:
> Add the device tree binding documentation for the ADXL372 3-axis digital
> accelerometer.
>
> Signed-off-by: Stefan Popa
> ---
> .../devicetree/bindings/iio/accel/adxl372.txt | 24
> ++
> MAINTAINERS
On Fri, 3 Aug 2018 16:02:16 +0300
Stefan Popa wrote:
> This patch adds basic support for Analog Devices ADXL372 SPI-Bus
> Three-Axis Digital Accelerometer.
>
> The device is probed and configured the with some initial default
> values. With this basic driver, it is possible to read raw accelerat
On 3 August 2018 at 22:44, Matt Sealey wrote:
> On 3 August 2018 at 13:25, Mikulas Patocka wrote:
>>
>>
>> On Fri, 3 Aug 2018, Ard Biesheuvel wrote:
>>
>>> Are we still talking about overlapping unaligned accesses here? Or do
>>> you see other failures as well?
>>
>> Yes - it is caused by overlap
On Fri, 3 Aug 2018 19:36:35 +0200
Parthiban Nallathambi wrote:
> Add support for VCNL4035, which is capable of Ambient light
> sensing (ALS) and proximity function. This patch adds support
> only for ALS function
>
> Signed-off-by: Parthiban Nallathambi
>
> Changelog since v1:
>
> 1. Fixed 0
On 8/3/18 2:07 AM, Michal Hocko wrote:
On Fri 27-07-18 02:10:14, Yang Shi wrote:
When running some mmap/munmap scalability tests with large memory (i.e.
300GB), the below hung task issue may happen occasionally.
INFO: task ps:14018 blocked for more than 120 seconds.
Tainted: G
On Thu, 2 Aug 2018 22:34:14 +0300
Andy Shevchenko wrote:
> On Thu, Aug 2, 2018 at 9:27 PM, Parthiban Nallathambi wrote:
> > Add support for VCNL4035, which is capable of Ambient light
> > sensing (ALS) and proximity function. This patch adds support
> > only for ALS function
>
> > +#include
From: Prasad Sodagudi
When cpu_stop_queue_work() releases the lock for the stopper
thread that was queued into its wake queue, preemption is
enabled, which leads to the following deadlock:
CPU0 CPU1
sched_setaffinity(0, ...)
__set_cpus_allowed_ptr()
stop_one_cpu(0, .
On 03.08.2018 21:40, Thomas Gleixner wrote:
> On Fri, 3 Aug 2018, Heiner Kallweit wrote:
>> On 03.08.2018 16:09, Thomas Gleixner wrote:
>>> On Wed, 1 Aug 2018, Heiner Kallweit wrote:
diff --git a/kernel/irq/msi.c b/kernel/irq/msi.c
index 4ca2fd46..ba6da943 100644
--- a/kernel/irq/msi
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Warning level 2 was used: -Wimplicit-fallthrough=2
Signed-off-by: Gustavo A. R. Silva
---
sound/core/seq/oss/seq_oss_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Notice that in this particular case, I replaced the code comment with
a proper "fall through" annotation, which is what GCC is expecting
to find.
Signed-off-by: Gustavo A. R. Silva
---
s
On 8/3/18 1:53 AM, Michal Hocko wrote:
On Fri 27-07-18 02:10:13, Yang Shi wrote:
Introduces three new helper functions:
* munmap_addr_sanity()
* munmap_lookup_vma()
* munmap_mlock_vma()
They will be used by do_munmap() and the new do_munmap with zapping
large mapping early in the la
On 03.08.2018 22:00, Thomas Gleixner wrote:
> On Fri, 3 Aug 2018, Heiner Kallweit wrote:
>
>> In case of a domain hierarchy we may miss the IRQCHIP_ONESHOT_SAFE
>> flag because we look at top of the stack only. See also discussion
>> here: https://marc.info/?l=linux-kernel&m=153301773524685&w=2
>
On 3 August 2018 at 13:25, Mikulas Patocka wrote:
>
>
> On Fri, 3 Aug 2018, Ard Biesheuvel wrote:
>
>> Are we still talking about overlapping unaligned accesses here? Or do
>> you see other failures as well?
>
> Yes - it is caused by overlapping unaligned accesses inside memcpy. When I
> put "dmb
On Fri, 3 Aug 2018 13:38:17 +0200 (CEST)
Peter Meerwald-Stadler wrote:
> Hello,
>
> > > it is not clear to me why 'white' is needed;
> > > isn't that the default, i.e. unfiltered light?
> >
> > Yes, it is. But devices like vcnl4035 veml7700, White LED data one
> > register and all other sourc
On Fri, Aug 3, 2018 at 12:09 PM John David Anglin wrote:
>
> On 2018-08-03 2:11 PM, Nick Desaulniers wrote:
> > But the kernel uses the generic_THIS_IP_ *everywhere*, not parisc's
> > custom current_text_addr(). So if this did actually break unwinding,
> > you should have noticed by now.
> The u
Linus,
The following changes since commit 28c20cc73b9cc4288c86c2a3fc62af4087de4b19:
Merge tag 'drm-fixes-2018-07-20' of git://anongit.freedesktop.org/drm/drm
(2018-07-19 20:17:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
f
Hi Mike.
On Thu, Aug 02, 2018 at 02:53:53PM +0300, Mike Rapoport wrote:
> The detection and reservation of ramdisk memory were separated to allow
> bootmem bitmap initialization after the ramdisk boundaries are detected.
> Since the bootmem initialization is removed, the reservation of ramdisk
> m
On 02/08/2018 21:33, Peter Shier wrote:
>
>> > The Intel Haswell architecture has an EPT feature whereby the access &
>> > dirty bits in EPT entries are updated without taking a guest exit.
>>
>> Why would this be Haswell specific?
>>
>> Aside of that I don't see what this has to do with exits. Fr
On Fri, Aug 3, 2018 at 8:51 AM Arnaldo Carvalho de Melo wrote:
>
> Em Fri, Aug 03, 2018 at 01:29:55PM +0200, Jiri Olsa escreveu:
> > On Fri, Aug 03, 2018 at 12:28:16AM -0700, Stephane Eranian wrote:
> > > On Tue, Jul 31, 2018 at 2:21 AM Jiri Olsa wrote:
> > > > there's the 'p' key to switch betwe
Hi Mike.
A nice simplification of the arch code - with a potential to do much more.
Some review comments, see the following.
Sam
On Thu, Aug 02, 2018 at 02:53:52PM +0300, Mike Rapoport wrote:
> Each populated sparc_phys_bank is added to memblock.memory. The
> reserve_bootmem() calls are
Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the
devfreq device") initializes df->min/max_freq with the min/max OPP when
the device is added. Later commit f1d981eaecf8 ("PM / devfreq: Use the
available min/max frequency") adds df->scaling_min/max_freq and the
following to the fr
Bart Massey reported what turned out to be a usercopy whitelist false
positive in JFS when symlink contents exceeded 128 bytes. The inline
inode data (i_inline) is actually designed to overflow into the "extended
area" following it when needed. So the whitelist needed to be expanded
to include i_in
Several governors use the user space limits df->min/max_freq to adjust
the target frequency. This is not necessary, since update_devfreq()
already takes care of this. Instead the governor can request the available
min/max frequency by setting the target frequency to DEVFREQ_MIN/MAX_FREQ
and let upd
This series includes miscellaneous changes that were originally part
of the throttler patch series
(https://lore.kernel.org/patchwork/project/lkml/list/?series=357937).
They have been spinned out to facilitate merging them independently
from the throttler changes.
The series is based on
git://git
Currently update_devfreq() is only visible to devfreq governors outside
of devfreq.c. Make it public to allow drivers that adjust devfreq policies
to cause a re-evaluation of the frequency after a policy change.
Signed-off-by: Matthias Kaehlcke
Acked-by: MyungJoo Ham
Reviewed-by: Brian Norris
R
On Fri, 3 Aug 2018, Heiner Kallweit wrote:
> In case of a domain hierarchy we may miss the IRQCHIP_ONESHOT_SAFE
> flag because we look at top of the stack only. See also discussion
> here: https://marc.info/?l=linux-kernel&m=153301773524685&w=2
I think you misunderstood:
> I think the top most c
1 - 100 of 500 matches
Mail list logo
