Allocate a temporary cgroup storage to use for bpf program test runs.
Because the test program is not actually attached to a cgroup,
the storage is allocated manually just for the execution
of the bpf program.
If the program is executed multiple times, the storage is not zeroed
on each run, emula
On Thu, Aug 02, 2018 at 06:16:48PM +0200, Christoph Hellwig wrote:
> On Thu, Aug 02, 2018 at 05:08:38PM +0100, Al Viro wrote:
> > On Thu, Aug 02, 2018 at 06:08:16PM +0200, Christoph Hellwig wrote:
> > > On Thu, Aug 02, 2018 at 05:00:32PM +0100, Al Viro wrote:
> > > > BTW, what happens if we insert
Alan Jenkins wrote:
> Another closely-related limitation of `mount`, is that it can't atomically set
> the propagation type at mount time.
I want to add a mount_setattr() too at some point:
fd = open_tree(..., OPEN_TREE_CLONE);
mount_setattr(fd, ...);
move_mount(fd, ...)
This implements the worst-case compression size querying interface for
lz4hc, based on the logic originally used by pstore.
Signed-off-by: Kees Cook
---
crypto/lz4hc.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/crypto/lz4hc.c b/crypto/lz4hc.c
index
Now that the crypto compression API has a zbufsize interface, use that
instead, so pstore doesn't need to keep getting updated for each new
compression algo that gets added to the kernel. This reorganizes the
code slightly at initialization time (since we must allocate the algo
first now), but othe
This implements the worst-case compression size querying interface for
zstd, based on the logic originally used by pstore.
Signed-off-by: Kees Cook
---
crypto/zstd.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/crypto/zstd.c b/crypto/zstd.c
index 9a7
On Thu 02 Aug 14:21 PDT 2018, Jacek Anaszewski wrote:
> On 08/01/2018 11:01 AM, Baolin Wang wrote:
[..]
> > diff --git a/drivers/leds/trigger/ledtrig-pattern.c
> > b/drivers/leds/trigger/ledtrig-pattern.c
[..]
> > +static ssize_t pattern_trig_store_pattern(struct device *dev,
> > +
On Wed, Aug 1, 2018, 4:26 PM Rishabh Bhatnagar
wrote:
> When calling request_firmware_into_buf() with the FW_OPT_NOCACHE flag
> it is expected that firmware is loaded into buffer from memory.
> But inside alloc_lookup_fw_priv every new firmware that is loaded is
> added to the firmware cache (fwc
On 08/02/2018 03:19 AM, Alexey Brodkin wrote:
> Otherwise kernel uses random MAC which is not very conveniet.
Curious what exactly is the issue - why does the user care what MAC is assigned
?
> With that change in place use might set desired MAC in U-Boot
> with "setenv ethaddr 11:22:33:44:55:66
Greg Kurz wrote on Thu, Aug 02, 2018:
> > @@ -443,9 +444,9 @@ static int rdma_request(struct p9_client *client,
> > struct p9_req_t *req)
> > **/
> > if (unlikely(atomic_read(&rdma->excess_rc) > 0)) {
> > if ((atomic_sub_return(1, &rdma->excess_rc) >= 0)) {
> > -
On 2018/07/31 14:09, Michal Hocko wrote:
> On Tue 31-07-18 06:01:48, Tetsuo Handa wrote:
>> On 2018/07/31 4:10, Michal Hocko wrote:
>>> Since should_reclaim_retry() should be a natural reschedule point,
>>> let's do the short sleep for PF_WQ_WORKER threads unconditionally in
>>> order to guarantee
On 8/2/18 4:50 AM, Christoph Hellwig wrote:
From: Palmer Dabbelt
This patch adds documentation for the platform-level interrupt
controller (PLIC) found in all RISC-V systems. This interrupt
controller routes interrupts from all the devices in the system to each
hart-local interrupt controller.
Hi all,
Today's linux-next merge of the dma-mapping tree got a conflict in:
arch/nios2/Kconfig
between commit:
17c46a6aff5c ("kconfig: remove duplicate SWAP symbol defintions")
from the kbuild tree and commit:
25622e045a6a ("nios2: use generic dma_noncoherent_ops")
from the dma-mapping
Dmitry Vyukov via V9fs-developer wrote on Wed, Jul 18, 2018:
> >> Btw, I see that p9_client_rpc uses wait_event_killable, why wasn't it
> >> killed along with the whole process?
> >>
> >
> > wait_event_killable() would return -ERESTARTSYS if got SIGKILL.
> > But if (c->status == Connected) && (type
On 8/2/18 4:50 AM, Christoph Hellwig wrote:
From: Palmer Dabbelt
Follow the updated DT specs and read the timebase-frequency from the
CPU 0 node.
However, the DT in the HighFive Unleashed has the entry at the wrong place.
Even the example in github also at wrong place.
https://github.com/ri
From: RAFAEL J. WYSOCKI
Date: Wed, Aug 1, 2018 at 2:21 PM
Subject: Re: [PATCH] dd: Invoke one probe retry cycle after every
initcall level
To: Rishabh Bhatnagar
Cc: "Rafael J. Wysocki" , Greg Kroah-Hartman
, Linux Kernel Mailing List
, ckad...@codeaurora.org,
ts...@codeaurora.org, Vikram Mulukut
Hello RT Folks!
This is the RT stable review cycle of patch 3.18.117-rt105-rc1.
In addition to the applicable stable-rt patches not yet in the 3.18-rt
kernel, this set includes some patches needed to fix cross-compilation
build failures.
Please scream at me if I messed something up. Please test
From: Peter Zijlstra
It's unused:
$ git grep "\" | wc -l
1
And dangerous, kill the bugger.
Cc: stable...@vger.kernel.org
Acked-by: Thomas Gleixner
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Sebastian Andrzej Siewior
(cherry picked from commit ffb940123ed607f1cba0d1f7c281ca92feac97
From: Sebastian Andrzej Siewior
NEON in kernel mode is used by the crypto algorithms and raid6 code.
While the raid6 code looks okay, the crypto algorithms do not: NEON
is enabled on first invocation and may allocate/free/map memory before
the NEON mode is disabled again.
This needs to be changed
From: Sebastian Andrzej Siewior
On RT the timer can be preempted while running and therefore we wait
with timer_wait_for_callback() for the timer to complete (instead of
busy looping). The RCU-readlock is held to ensure that this posix timer
is not removed while we wait on it.
If the timer is rem
From: Sebastian Andrzej Siewior
If alarm_try_to_cancel() requires a retry, then depending on the
priority setting the retry loop might prevent timer callback completion
on RT. Prevent that by waiting for completion on RT, no change for a
non RT kernel.
Cc: stable...@vger.kernel.org
Signed-off-by
From: Sebastian Andrzej Siewior
During the stable update the arm architecture did not compile anymore
due to missing definition of u16/32.
Cc: stable...@vger.kernel.org
Signed-off-by: Sebastian Andrzej Siewior
(cherry picked from commit 1289b06974d64f244a26455fab699c6a1332f4bc)
Signed-off-by: T
From: Julia Cartwright
The mainline implementation of read_seqbegin() orders prior loads w.r.t.
the read-side critical section. Fixup the RT writer-boosting
implementation to provide the same guarantee.
Also, while we're here, update the usage of ACCESS_ONCE() to use
READ_ONCE().
Fixes: e69f15
From: Philipp Schrader
With PREEMPT_RT and most of the lockdep-related options enabled I
encountered this splat when booting our DRA7 evaluation module:
[0.055073]
[0.055076] ===
[0.055079] [ INFO: suspicious RCU usage. ]
[0.055084] 4.1.6+ #2 Not taint
This reverts commit 3b5cf23e6b87a938522eb074baeb034e66dc9cb3.
Similar to commit d5bc2c7b2cc0 Revert "fs: jbd2: pull your plug when
waiting for space", according to Sebastian Siewior: this "is the same
thing but for ext3/jbd. The code was removed at some point so I did
not revert in my tree."
>Fr
From: Julia Cartwright
Currently, the squashfs multi_cpu decompressor makes use of
get_cpu_ptr()/put_cpu_ptr(), which unconditionally disable preemption
during decompression.
Because the workload is distributed across CPUs, all CPUs can observe a
very high wakeup latency, which has been seen to
From: Sebastian Andrzej Siewior
In commit ("net: move xmit_recursion to per-task variable on -RT") the
recursion level was changed to be per-task since we can get preempted in
BH on -RT. The lock owner should consequently be recorded as the task
that holds the lock and not the CPU. Otherwise we t
The mm-of-the-moment snapshot 2018-08-02-15-29 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
Quoting Amit Nischal (2018-07-30 04:28:56)
> On 2018-07-25 12:28, Stephen Boyd wrote:
> >
> > Ok. Sounds good! Is the rate range call really needed? It can't be
> > determined in the PLL code with some table or avoided by making sure
> > GPU
> > uses OPP table with only approved frequencies?
> >
From: Dave Hansen
When chunks of the kernel image are freed, free_init_pages()
is used directly. Consolidate the three sites that do this.
Also update the string to give an incrementally better
description of that memory versus what was there before.
Signed-off-by: Dave Hansen
Cc: Kees Cook
The fixes for the problem Hugh reported took a bit more surgery
than I would have liked, but they do appear to work. Note that
the last two patches are unnecessary cleanups that could be removed
from backports.
Changes from v1:
* Modify set_memory_np() to avoid messing with the direct map
b
From: Dave Hansen
This is a cleanup. There should be functional changes in this patch.
The pageattr code has the ability to find and change aliases
mappings. It does this for requests by default unless the
page protections being modified contain only the NX bit.
But, this behavior is rather
From: Dave Hansen
The kernel image starts out with the Global bit set across the entire
kernel image. The bit is cleared with set_memory_nonglobal() in the
configurations with PCIDs where we do not need the performance
benefits of the Global bit.
However, this is fragile. It means that we ar
Em Tue, 24 Jul 2018 11:35:59 +0200
Arnd Bergmann escreveu:
> Without the MFD driver, we run into a link error:
Weird... I'm not seeing this driver at the media tree... was it merged via
some other tree?
>
> drivers/media/platform/cros-ec-cec/cros-ec-cec.o: In function
> `cros_ec_cec_transmit'
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 do this. Strangely, we convert the
symbol addresses to ker
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 actually execute out of #2. If we get the address of
From: Dave Hansen
This is a cleanup. There should be functional changes in this patch.
change_page_attr_set/clear() take an 0/1 argument to indicate whether
CPA_ARRAY should be passed down to change_page_attr_set/clear().
Rather than having a 0/1 argument to turn a single flag on/off, just
pa
From: Dave Hansen
free_reserved_area() takes pointers as arguments to show which
addresses should be freed. However, it does this in a
somewhat ambiguous way. If it gets a kernel direct map address,
it always works. However, if it gets an address that is
part of the kernel image alias mappin
On 8/2/18 4:51 AM, Christoph Hellwig wrote:
Adds a driver for the SiFive implementation of the RISC-V Platform Level
Interrupt Controller (PLIC). The PLIC connects global interrupt sources
to the local interrupt controller on each hart.
This driver is based on the driver in the RISC-V tree from
Hi Chanwoo,
On Thu, Aug 02, 2018 at 10:58:59AM +0900, Chanwoo Choi wrote:
> Hi Matthias,
>
> On 2018년 08월 02일 02:08, Matthias Kaehlcke wrote:
> > Hi Chanwoo,
> >
> > On Wed, Aug 01, 2018 at 10:22:16AM +0900, Chanwoo Choi wrote:
> >> On 2018년 08월 01일 04:39, Matthias Kaehlcke wrote:
> >>> On Mon,
On 8/2/18 4:51 AM, Christoph Hellwig wrote:
From: Palmer Dabbelt
The RISC-V ISA defines a per-hart real-time clock and timer, which is
present on all systems. The clock is accessed via the 'rdtime'
pseudo-instruction (which reads a CSR), and the timer is set via an SBI
call.
Contains various
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/Kconfig
between commit:
1572497cb0e6 ("kconfig: include common Kconfig files from top-level Kconfig")
from the kbuild tree and commit:
6c359eb1dcdb ("MIPS: Allow auto-dection of ARCH_PFN_OFFSET & PHYS_OFFSET"
On Mon, Jul 30, 2018 at 11:34 AM Tomer Maimon wrote:
> Add get_set_inv_dir and get_set_multiple_inv_dir I/O functions
> to call the data register when the dirction is input and
> set register when the direction is output.
> the functions will linked to the I/O get functions if the user set
> BGPI
Hi Chanwoo,
this patch and "PM / devfreq: Fix handling of min/max_freq == 0"
address issues not directly related with the throttler. It seems it
could still take a while for the throttler to move forward, do you
want me to spin out these two patches so that they can get merged
independently from t
Dear Friend,
Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in
getting the fund $29.6Million transferred under the co-operation of a new
partner from Dubai, Presently I'm in Dubai for investment projects with my own
share of the total sum. Meanwhile,I didn't forget
On 02/08/18 22:51, David Howells wrote:
Alan Jenkins wrote:
Another closely-related limitation of `mount`, is that it can't atomically set
the propagation type at mount time.
I want to add a mount_setattr() too at some point:
fd = open_tree(..., OPEN_TREE_CLONE);
mount_setatt
On Thu, Aug 02, 2018 at 04:13:43PM -0700, Matthias Kaehlcke wrote:
> Hi Chanwoo,
>
> On Thu, Aug 02, 2018 at 10:58:59AM +0900, Chanwoo Choi wrote:
> > Hi Matthias,
> >
> > On 2018년 08월 02일 02:08, Matthias Kaehlcke wrote:
> > > Hi Chanwoo,
> > >
> > > On Wed, Aug 01, 2018 at 10:22:16AM +0900, Cha
Hi Matthias,
On 2018년 08월 03일 08:13, Matthias Kaehlcke wrote:
> Hi Chanwoo,
>
> On Thu, Aug 02, 2018 at 10:58:59AM +0900, Chanwoo Choi wrote:
>> Hi Matthias,
>>
>> On 2018년 08월 02일 02:08, Matthias Kaehlcke wrote:
>>> Hi Chanwoo,
>>>
>>> On Wed, Aug 01, 2018 at 10:22:16AM +0900, Chanwoo Choi wrote
The file r8192U_dm.h defines the structure DM_RxPathSelTable as being
external. The structure is however declared in r8192U_dm.c and only
used locally in that file.
As a result the external definition has been removed and the declaration
in r8192U_dm.c changed to being of type static.
This is a c
The structure 'dig' defines a member variable
'initialgain_lowerbound_state', which although initialised to false,
is never used in the code. As a result this unused member variable
has been removed.
This is a coding style change which should not impact runtime code
execution.
Signed-off-by: John
This series of patches is a clean up of the file:
drivers/staging/rtl8192u/r8192U_dm.h
Whilst I consider all the changes to be coding style changes some have
removed structure member variables which were not implementing any
logic, which required them to be a member of a structure. The first
patch
The structure dynamic_rx_path_sel defines a member variable 'Enable'
which is initialised and later tested. The variable is however never
changed to the test is redundant and the member variable is then never
used.
The member variable, initialisation and test have all been removed.
This is a codi
Two structures, (struct dig and struct dynamic_rx_path_sel) contain
a u8 member variable representing debug setting. In the file r8192U_dm.c
these member variables, for both structures, are initialised to an
enumerated constant 'DM_DBG_OFF'. The member variables are never
assigned another value, ot
Rename the member variable disabledRF to disabled_rf. This change
resolves the checkpatch issue with CamelCase naming.
The change is purely a coding style change which should have no impact
on runtime code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r8192U_dm.c | 10 +++
The member variable diff_TH is assigned a constant value and then used
in a comparison. The variable is never changed so the comparison can
as easily be performed directly with the defined constant.
The member variable has been removed and the defined constant
RxPathSelection_diff_TH renamed to RX
The constant RateAdaptiveTH_High causes a checkpatch issue with respect
to CamelCase naming. As a result the constant has been renamed to
RATE_ADAPTIVE_TH_HIGH.
This is purely a coding style change which should have no impact on
runtime code execution.
Signed-off-by: John Whitmore
---
drivers/s
The four register constants, 'Current_Tx_Rate_Reg',
'Initial_Tx_Rate_Reg', 'Tx_Retry_Count_Reg' and 'RegC38_TH' all cause
checkpatch issue with CamelCase naming. The three have been renamed to
'CURRENT_TX_RATE_REG', 'INITIAL_TX_RATE_REG', 'TX_RETRY_COUNT_REG' and
'REG_C38_TH' respectively.
These a
The two constants, RateAdaptiveTH_Low_20M and RateAdaptiveTH_Low_40M
generate a checkpatch warning about CamelCase naming. The two have been
renamed to clear this issue. RATE_ADAPTIVE_TH_LOW_20M and
RATE_ADAPTIVE_TH_LOW_40M
This is a coding style change which should have no impact on runtime
code
The constant DM_DIG_MIN_Netcore causes a checkpatch issue with CamelCase
naming so has been renamed to DM_DIG_MIN_NETCORE.
This is a simple coding style change which should have no impact on
runtime code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r8192U_dm.c | 2 +-
dr
The structure DCMD_TXCMD_T is declared with a typedef, which causes a
checkpatch issue with defining new types. As a result the typedef has
been removed.
The structure's name DCMD_TXCMD_T, as a type, is meant to be lowercase
so has been renamed to tx_config_cmd.
The structures three members, (Op,
Multiple blank line, which cause an issue with checkpath, have been
removed and the spacing of definitions have been aligned to look
cleaner.
These are coding style changes which should have no impact on
runtime code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r8192U_dm
The constants 'VeryLowRSSI' and 'CTSToSelfTHVal' generate warnings from
checkpatch due to the use of CamelCase naming. The two constants have
been renamed to 'VERY_LOW_RSSI' and 'CTS_TO_SELF_TH_VAL' respectively.
These are coding style changes which should have no impact on runtime
code execution.
Hi Matthias,
On 2018년 08월 03일 08:36, Matthias Kaehlcke wrote:
> Hi Chanwoo,
>
> this patch and "PM / devfreq: Fix handling of min/max_freq == 0"
> address issues not directly related with the throttler. It seems it
> could still take a while for the throttler to move forward, do you
> want me to
The structure dynamic_rx_path_sel contains a u8 member variable called
reserved. This member variable is never actually used in the code.
The naming suggests that the sizeof the structure is significant but
the only use of the structure is a local static in r8192U_dm.c:
static struct dynamic_rx_p
The structure 'dig' defines a member variable, (rx_gain_range_max)
which is initialised to the value 'DM_DIG_MAX', (a defined constant).
The variable is then used to test and set another variable. Since
the member rx_gain_range_max is never assigned any other value then
the constant 'DM_DIG_MAX' th
Rename the two constants defined in the enumerated type enum
cck_rx_path_method so that they are both uppercase, as suggested by
the coding style.
This is purely a coding style change and should have no impact on
runtime code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/
The member variable SS_TH_low is assigned a constant and then used
in a comparison. This member variable is redundant as the constant
can be used directly for the comparison.
In addition the constant RxPathSelection_SS_TH_low has been renamed
to RX_PATH_SELECTION_SS_TH_LOW, to clear the checkpatch
Rename the member variable cck_Rx_path to cck_rx_path. This clears
the checkpatch issue with CamelCase naming.
This is a coding style change which should have no impact one runtime
code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r8192U_dm.c | 8
drivers/stagin
Hi Matthias,
On 2018년 07월 12일 17:38, Chanwoo Choi wrote:
> Hi Matthias,
>
> On 2018년 07월 07일 02:07, Matthias Kaehlcke wrote:
>> Hi,
>>
>> On Wed, Jul 04, 2018 at 11:51:30AM +0900, Chanwoo Choi wrote:
>>> Hi,
>>>
>>> On 2018년 07월 04일 08:46, Matthias Kaehlcke wrote:
Move variables related with
Hi Tomer,
this is starting to look really good!
Please try this with my patch and drop the new DIR_INV flag that I think
we do not need anymore after that.
Other small bits:
On Mon, Jul 30, 2018 at 1:04 PM Tomer Maimon wrote:
> +/* Structure for register banks */
> +struct npcm7xx_gpio {
> +
Hi Matthias,
On 2018년 08월 03일 08:48, Matthias Kaehlcke wrote:
> On Thu, Aug 02, 2018 at 04:13:43PM -0700, Matthias Kaehlcke wrote:
>> Hi Chanwoo,
>>
>> On Thu, Aug 02, 2018 at 10:58:59AM +0900, Chanwoo Choi wrote:
>>> Hi Matthias,
>>>
>>> On 2018년 08월 02일 02:08, Matthias Kaehlcke wrote:
Hi Ch
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 here? (nothing to do with mmotm;
I see it more frequently with linux-next since I do many daily
builds wit
This patch set adds support for the gyroscope / accelerometer
(mpu6515), magnetometer (ak8963), temperature / pressure (bmp280), and
proximity / ALS (tsl2772) sensors to the LG Nexus 5 (hammerhead) phone.
Changes since v2:
- Updated dt property names for tsl2772: amstaos,proximity-diodes and
led
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
---
I got a Reviewed-by: Rob Herring on my last series but
didn't include it due to the new file ts
This patch adds device tree bindings for the tsl2772 ALS / proximity
sensor for the LG Nexus 5 (hammerhead) phone.
Signed-off-by: Brian Masney
Signed-off-by: Jonathan Marek
---
.../qcom-msm8974-lge-nexus5-hammerhead.dts| 27 +++
arch/arm/boot/dts/qcom-msm8974.dtsi
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) phone.
avago,apds9930 datasheet:
https://www.mouser.com/datashe
This patch adds support for optionally reading the proximity led diode
and current settings from device tree. This was tested using a LG
Nexus 5 (hammerhead) which requires a different diode than the driver
default for the IR LED.
Signed-off-by: Brian Masney
---
drivers/iio/light/tsl2772.c | 81
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 sensor.
Signed-off-by: Brian Masney
---
drivers/iio/light/tsl2772
This patch adds avago,apds9930 to the tsl2772 bindings.
Signed-off-by: Brian Masney
---
Documentation/devicetree/bindings/iio/light/tsl2772.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iio/light/tsl2772.txt
b/Documentation/devicetree/bindings/iio/lig
This patch adds device tree bindings to the tsl2772 driver for the
regulator framework.
Signed-off-by: Brian Masney
---
Documentation/devicetree/bindings/iio/light/tsl2772.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/iio/light/tsl2772.txt
b/Docum
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
---
Changes since v2:
- Dropped regulator_enabled value since it is not needed.
Changes since v1:
- Use devm_regulator_get() instead of dev
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 phone.
Interrupts are not working properly on the ak8963 magnet
On Fri, Aug 03, 2018 at 09:03:30AM +0900, Chanwoo Choi wrote:
> Hi Matthias,
>
> On 2018년 08월 03일 08:36, Matthias Kaehlcke wrote:
> > Hi Chanwoo,
> >
> > this patch and "PM / devfreq: Fix handling of min/max_freq == 0"
> > address issues not directly related with the throttler. It seems it
> > co
Atish Patra 於 2018年8月3日 週五 上午2:14寫道：
>
> On 8/2/18 8:23 AM, Zong Li wrote:
> > The boot_sec_cpu is for hutplug CPU on SMP system. It should
> > be conditional compiling. Otherwise, it causes undefined reference
> > to `smp_callin' when compiling uniprocessor kernel.
> >
> > Signed-off-by: Zong Li
Dear Friend,
I know that this mail will come to you as a surprise as we have never met
before,I need your Urgent assistance in transferring the sum of $18 mllion US
Dollars immediately to your Private account.The money has been here in our Bank
lying dormant for years now without anybody coming
Hi Matthias,
On 2018년 08월 03일 09:24, Matthias Kaehlcke wrote:
> On Fri, Aug 03, 2018 at 09:03:30AM +0900, Chanwoo Choi wrote:
>> Hi Matthias,
>>
>> On 2018년 08월 03일 08:36, Matthias Kaehlcke wrote:
>>> Hi Chanwoo,
>>>
>>> this patch and "PM / devfreq: Fix handling of min/max_freq == 0"
>>> address
Big performance benefit (for this first narrow case) with Ronnie's
compounding patches (now merged into cifs-2.6.git for-next). This is
the first code path enabled for smb3 compounding but looks very
promising, if we continue to get such dramatic perf improvements (as
we go forward implementing c
On 08/02/2018 12:45 PM, Greg Kroah-Hartman wrote:
[ ... ]
I've pushed out -rc2 releases for all of these with that patch removed.
Boot tests with updated images passed for all three releases.
Guenter
As a boutique team, we work personally with our clients to ensure the good
results.
Having over a decade of hands-on experience in photography and retouching,
we have been inspired
to expand our services to the public.
We are team of artists who have excelled in fields such as art,
photography, r
when firmware is in filesystem, request_firmware will load it,
and copy it to vmalloc memory, that is page align memory.
but when firmware is builtin, it is 8 bytes or 4 bytes alignment.
make sure builtin firmware is page algnment, that can simplify algorithm
to handle firmware.
Signed-off-by: Z
Hi Greg and Dominique,
We'd better reach an agreement about the patch fix. In my opinion,
replacing strlen(chan->tag) with a local variable sounds reasonable, and
changing strncmp to strcmp may be little beneficial, as strcmp is more
dangerours such as buffer-flow. So I'd like to hear your suggest
From: Todd Poynor
At device/driver registration time, convert a not-very-informative
info message to a more informative debug message, drop some not overly
helpful debug messages.
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_core.c | 7 ++-
1 file changed, 2 insertions(+),
From: Todd Poynor
There's no need to take an additional reference on the pci_dev structure
for the pointer copy saved in gasket data structures.
This reverts commit:
8dd8a48b9a7d ("staging: gasket: core: hold reference to pci_dev while used")
Reported-by: Dmitry Torokhov
Signed-off-by: Todd Po
From: Todd Poynor
Identify gasket as the subsystem printing various messages.
Add the driver name to appropriate messages to indicate which driver
has a problem.
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_core.c | 13 +
1 file changed, 9 insertions(+), 4 deletions
From: Todd Poynor
More cleanups for the gasket+apex drivers.
Patched changed in v2 from v1:
staging: gasket: core: print driver version code at registration time
staging: gasket: core: move driver loaded log after error cases
Above 2 patches replaced by new patch:
staging: gaske
From: Todd Poynor
Remove logs for loading gasket drivers.
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_core.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/staging/gasket/gasket_core.c
b/drivers/staging/gasket/gasket_core.c
index 2b75f100da4d3..fa477d0c3c74c 1
On 07/29/2018 03:29 PM, Linus Walleij wrote:
On Thu, Jul 19, 2018 at 1:56 AM Janusz Krzysztofik wrote:
This should make applications utilizing whole banks work faster.
Signed-off-by: Janusz Krzysztofik
This patch looks good to me and I have an urge to just apply it.
Can we get some fee
As a boutique team, we work personally with our clients to ensure the good
results.
Having over a decade of hands-on experience in photography and retouching,
we have been inspired
to expand our services to the public.
We are team of artists who have excelled in fields such as art,
photography, r
On Mon, 09 Jul 2018 08:50:05 PDT (-0700), r...@kernel.org wrote:
On Tue, Jun 19, 2018 at 3:41 PM Rob Herring wrote:
The DT core will call of_platform_default_populate, so it is not
necessary for arch specific code to call it unless there are custom
match entries, auxdata or parent device. Neit
At 07/23/2018 05:29 PM, Chao Fan wrote:
Imitate the ACPI code to parse ACPI tables. Functions are simplified
cause some operations are not needed here.
And also, this method won't influence the initialization of ACPI.
Signed-off-by: Chao Fan
Hi Fan,
I know you got the code from acpica sub
201 - 300 of 689 matches
Mail list logo
