On 10/18, Andy Lutomirski wrote:
>
> Oleg, the code in kernel/signal.c:
>
> preempt_disable();
> read_unlock(&tasklist_lock);
> preempt_enable_no_resched();
> freezable_schedule();
>
> looks bogus. I don't get what it's trying to achi
> -Original Message-
> From: Radhey Shyam Pandey
> Sent: Saturday, September 29, 2018 10:48 PM
> To: vk...@kernel.org; dan.j.willi...@intel.com; Michal Simek
> ; Appana Durga Kedareswara Rao
> ; Radhey Shyam Pandey
> Cc: dmaeng...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
On 10/17/2018 7:50 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-17 05:04:10)
On 10/17/2018 5:07 PM, Taniya Das wrote:
Hello Stephen,
On 10/12/2018 11:05 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-09 23:12:27)
On 10/10/2018 2:22 AM, Stephen Boyd wrote:
Quoting Taniya D
Hi Paul,
I love your patch! Yet something to improve:
[auto build test ERROR on tty/tty-testing]
[also build test ERROR on v4.19-rc8 next-20181019]
[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
The internal resistance of a battery is not a constant in its life cycle,
this varies over the age of the battery or temperature and so on. But we
just want use one constant battery internal resistance to estimate the
battery capacity. Thus this patch introduces one property to present
the battery
This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
fuel gauge unit device, which is used to calculate the battery capacity.
Signed-off-by: Baolin Wang
Reviewed-by: Linus Walleij
Reviewed-by: Rob Herring
---
Changes from v4:
- None.
Changes from v3:
- Add reviewed ta
We have introduced some battery properties to present the OCV table
temperatures and OCV capacity table values. Thus this patch add OCV
temperature and OCV table for battery information, as well as providing
some helper functions to use the OCV capacity table for users.
Signed-off-by: Baolin Wang
Add one field for 'struct power_supply_battery_info' to present the battery
factory internal resistance.
Signed-off-by: Baolin Wang
Reviewed-by: Linus Walleij
---
Changes from v4:
- None.
Changes from v3:
- New patch in v3, which splits code into one separate patch.
- Add Linusw reviewed tag
This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
which is used to calculate the battery capacity.
Original-by: Yuanjiang Yu
Signed-off-by: Baolin Wang
Acked-by: Linus Walleij
---
Changes from v4:
- None.
Changes from v3:
- None.
Changes from v2:
- Use core helper func
Some battery driver will use the open circuit voltage (OCV) value to look
up the corresponding battery capacity percent in one certain degree Celsius.
Thus this patch provides some battery properties to present the OCV table
temperatures and OCV capacity table values.
Suggested-by: Sebastian Reich
On Mon, Oct 15, 2018 at 04:35:29PM -0700, Andrew Morton wrote:
> On Sat, 13 Oct 2018 15:50:58 +0200 Peter Zijlstra
> wrote:
>
> > The whole raw_spinlock_t is for RT, no other reason.
>
> Oh. I never realised that.
>
> Is this documented anywhere? Do there exist guidelines which tell
> non-rt
Reading the full 4k config space through sysfs leads to an
external abort. Testing on a platform showed that the upper
limit is 512. Limit config space to 512.
Signed-off-by: Stefan Agner
---
I observed this on a Apalis iMX6 which uses the i.MX 6Quad without any
PCIe device connected. It is espec
On Fri, Oct 19, 2018 at 10:50:02AM +0100, Charles Keepax wrote:
Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code. Modifying existing
commits creates problems for other users building on top of those
commits so it's best practice
From: Masahiro Yamada
> Sent: 18 October 2018 17:39
>
> On Thu, Oct 18, 2018 at 6:18 PM Borislav Petkov wrote:
> >
> > On Wed, Oct 17, 2018 at 09:40:53PM -0300, Leonardo Bras wrote:
> > > The idea was to put it as default and fix all the shadowing warnings.
> > > What do you think? I am open to
Hi,
On 19/10/2018 09:02, Ingo Molnar wrote:
>
> * Thara Gopinath wrote:
[...]
> So what unifies RT and DL utilization is that those are all direct task
> loads independent of external factors.
>
> Thermal load is more of a complex physical property of the combination of
> various internal
On 9/11/18 2:42 AM, Daniel Jordan wrote:
> Hi,
>
> This is a work-in-progress of what I presented at LSF/MM this year[0] to
> greatly reduce contention on lru_lock, allowing it to scale on large systems.
>
> This is completely different from the lru_lock series posted last January[1].
>
> I'm ho
On Wed, Sep 26, 2018 at 10:43 AM Vadim Pasternak wrote:
>
>
>
> > -Original Message-
> > From: Nathan Chancellor
> > Sent: Wednesday, September 26, 2018 8:21 AM
> > To: Vadim Pasternak ; Darren Hart
> > ; Andy Shevchenko
> > Cc: platform-driver-...@vger.kernel.org; linux-kernel@vger.kern
On Fri, Oct 05, 2018 at 09:47:49AM +0100, Kristina Martsenko wrote:
> From: Mark Rutland
>
> To use pointer authentication in the kernel, we'll need to switch keys
> in the entry assembly. This patch moves the pointer auth keys into
> thread_info to make this possible.
>
> There should be no fun
On 17/10/2018 04.09, Frederic Weisbecker wrote:
> On Fri, Sep 07, 2018 at 11:39:47PM +0200, Jan H. Schönherr wrote:
>> C) How does it work?
>>
[...]
>> For each task-group, the user can select at which level it should be
>> scheduled. If you set "cpu.scheduled" to "1", coschedu
On Thu, Oct 18, 2018 at 01:08:11PM +0200, luca abeni wrote:
> Ok, I see the issue now: the problem is that the "while (dl_se->runtime
> <= 0)" loop is executed at replenishment time, but the deadline should
> be postponed at enforcement time.
>
> I mean: in update_curr_dl() we do:
> dl_se->r
On 10/18/2018 05:10 PM, Pavel Machek wrote:
> Hi!
>
>> Given this one seems to have not really been finished, it's probably
>> okay to make changes in this case. Still, it would be good to see
>> patches structured so that it's obvious we're breaking things. But how
>> the patches
Rob
Thanks for the review.
On 10/12/2018 11:27 AM, Rob Herring wrote:
> On Thu, Oct 11, 2018 at 11:51:18AM -0500, Dan Murphy wrote:
>> Add the device tree bindings for the lm3697
>> LED driver for backlighting and display.
>
> Bindings are for h/w, not drivers...
>
ACK
Dan
>>
>> Signed-off-by
On Thu, Oct 18, 2018 at 09:02:12AM +, Pascal PAILLET-LME wrote:
> + for (i = 0; i < ARRAY_SIZE(stpmic1_regulator_cfgs); i++) {
> + /* Parse DT & find regulators to register */
> + init_data = stpmic1_regulators_matches[i].init_data;
> + if (init_data)
>
On Thu, Sep 27, 2018 at 11:52 AM Jian-Hong Pan wrote:
>
> The original asus-wmi queues a work which calls the ACPI/WMI methods to
> update the keyboard LED brightness. Similar drivers - acer-wmi,
> dell-wmi-led just call the ACPI/WMI methods directly without workqueues.
>
> This patch simplifies
On Thu, Oct 4, 2018 at 3:35 PM Hans de Goede wrote:
>
> Add touchscreen info for the Trekstor Primebook C11 convertible.
>
Applied, thanks!
> Cc: Alicia Hormann
> Suggested-by: Alicia Hormann
> Signed-off-by: Hans de Goede
> ---
> drivers/platform/x86/touchscreen_dmi.c | 24 +
Okay, I put in a tracepoint (patch attached) and got a trace from the life of
the offending mount object. I've cropped non-useful information out of the
lines, inserted a blank line every time the usage count goes down to 2 and
dropped most of the lines generated by fsnotify.
Most of the lines ar
On Fri, Oct 19, 2018 at 10:33:50AM +0100, Ben Whitten wrote:
> The regmap API had a noinc_read function added for instances where devices
> supported returning data from an internal FIFO in a single read.
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc
On Thu, 18 Oct 2018, Jessica Yu wrote:
> +++ Miroslav Benes [17/10/18 15:39 +0200]:
> >On Mon, 1 Oct 2018, Torsten Duwe wrote:
> >
> >Ad relocations. I checked that everything in struct mod_arch_specific
> >stays after the module is load. Both core and init get SHF_ALLOC set
> >(mod->arch.core.plt
Am 19.10.18 um 13:56 schrieb Mark Brown:
> On Fri, Oct 19, 2018 at 10:33:50AM +0100, Ben Whitten wrote:
>> The regmap API had a noinc_read function added for instances where devices
>> supported returning data from an internal FIFO in a single read.
>
> The following changes since commit 5b394b2dd
On Fri, Oct 19, 2018 at 01:59:07PM +0200, Andreas Färber wrote:
> Am 19.10.18 um 13:56 schrieb Mark Brown:
> > regmap: Add regmap_noinc_write API (2018-10-19 12:51:19 +0100)
> You two forgot my Reviewed-by... oh well.
Ah, sorry - I tend to trust people to carry these things forward :(
signat
The util-linux release v2.33-rc2 is available at
http://www.kernel.org/pub/linux/utils/util-linux/v2.33/
Feedback and bug reports, as always, are welcomed.
Karel
--
Karel Zak
http://karelzak.blogspot.com
On 19/10/18 12:26, Mark Brown wrote:
On Fri, Oct 19, 2018 at 10:50:02AM +0100, Charles Keepax wrote:
Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code. Modifying existing
commits creates problems for other users building on top
On Fri, Oct 19, 2018 at 01:02:45PM +0100, Richard Fitzgerald wrote:
> Most SPDX headers on C files that I've looked at have it this way with a
> C++ style comment above a C-style comment, though some don't.
> license-rules.rst
> doesn't define how or if a SPDX comment line should be merged with t
pt., 11 maj 2018 o 18:21 Bartosz Golaszewski napisał(a):
>
> This series is a follow-up to the RFC[1] posted a couple days ago.
>
> NOTE: this series applies on top of my recent patches[2] that move the
> previous
> implementation of early platform devices to arch/sh.
>
> Problem:
>
> Certain cla
On Thu, Oct 18, 2018 at 2:54 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.14.78 release.
> There are 41 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
On Sat, Oct 6, 2018 at 9:54 AM Rajneesh Bhardwaj
wrote:
>
> This adds support to show the Latency Tolerance Reporting for the IPs on
> the PCH as reported by the PMC. The format shown here is raw LTR data
> payload that can further be decoded as per the PCI specification.
>
> This also fixes some
On Sat, Oct 6, 2018 at 9:54 AM Rajneesh Bhardwaj
wrote:
>
> Cannonlake PCH allows us to ignore LTR from more IPs than Sunrisepoint
> PCH so make the LTR ignore platform specific.
>
Pushed to my reviewing and testing queue, thanks!
> Signed-off-by: Rajneesh Bhardwaj
> ---
> drivers/platform/x86
On Thu, 18 Oct 2018, Josh Poimboeuf wrote:
> On Thu, Oct 18, 2018 at 04:54:56PM +0200, Petr Mladek wrote:
> > On Mon 2018-10-15 18:01:43, Miroslav Benes wrote:
> > > On Fri, 12 Oct 2018, Petr Mladek wrote:
> > >
> > > > On Wed 2018-09-05 11:34:06, Miroslav Benes wrote:
> > > > > On Tue, 28 Aug 20
On 15/10/2018 14:52, Dmitry Osipenko wrote:
> On 10/15/18 3:52 PM, Jon Hunter wrote:
>>
>> On 30/08/18 19:36, Dmitry Osipenko wrote:
>>> This fixes splats like the one below if CONFIG_DEBUG_ATOMIC_SLEEP=y
>>> and machine (Tegra30) booted with SMP=n or all secondary CPU's are put
>>> offline.
>>>
+++ Miroslav Benes [19/10/18 13:59 +0200]:
On Thu, 18 Oct 2018, Jessica Yu wrote:
+++ Miroslav Benes [17/10/18 15:39 +0200]:
>On Mon, 1 Oct 2018, Torsten Duwe wrote:
>
>Ad relocations. I checked that everything in struct mod_arch_specific
>stays after the module is load. Both core and init get
On Fri, Oct 19, 2018 at 12:26:22PM +0100, Mark Brown wrote:
> On Fri, Oct 19, 2018 at 10:50:02AM +0100, Charles Keepax wrote:
>
> Please do not submit new versions of already applied patches, please
> submit incremental updates to the existing code. Modifying existing
> commits creates problems f
FUSE will want to know if stx_attributes is interesting or not, because
there's a non-zero cost of retreiving it.
This just a "want" flag, since stx_attributes_mask already indicates
whether we "got" stx_attributes or not.
Signed-off-by: Miklos Szeredi
Cc: David Howells
Cc: Michael Kerrisk
---
Orangefs only handles STATX_BASIC_STATS in its getattr implementation, so
mask off all other flags. Not doing so results in statx(2) forcing a
refresh of cached attributes on any other requested flag (i.e. STATX_BTIME
currently) due to the following test in orangefs_inode_getattr():
(request_ma
As per statx(2) man page only clear out flags that are unsupported by the
fs or have an unrepresentable value. Atime is supported by NFS as long as
it's supported on the server.
So the STATX_ATIME flag should not be cleared in the result_mask if the
operation was requested on a MNT_NOATIME or MNT
Constants of the *_ALL type can be actively harmful due to the fact that
developers will usually fail to consider the possible effects of future
changes to the definition.
Deprecate STATX_ALL in the uapi, while no damage has been done yet.
We could keep something like this around in the kernel, b
IS_NOATIME(inode) is defined as __IS_FLG(inode, SB_RDONLY|SB_NOATIME), so
generic_fillattr() will clear STATX_ATIME from the result_mask if the super
block is marked read only.
This was probably not the intention, so fix to only clear STATX_ATIME if
the fs doesn't support atime at all.
Signed-off
On Fri, Oct 19, 2018 at 12:35:56PM +0100, Catalin Marinas wrote:
> On Tue, Oct 16, 2018 at 05:14:39PM +0100, Kristina Martsenko wrote:
> > On 05/10/2018 10:04, Ramana Radhakrishnan wrote:
> > > On 05/10/2018 09:47, Kristina Martsenko wrote:
> > The other special case is the XPACLRI instruction, whi
On Fri, Oct 19, 2018 at 01:19:20PM +0100, Charles Keepax wrote:
> On Fri, Oct 19, 2018 at 12:26:22PM +0100, Mark Brown wrote:
> > Please do not submit new versions of already applied patches, please
> > submit incremental updates to the existing code. Modifying existing
> > commits creates proble
The wm_adsp_buffer struct is the control header of a circular
buffer used to transfer data from the firmware over the
control interface to an ALSA compressed stream.
The original names of the fields pointing to the data buffer
were based on ADSP2V2 memory layout where they correspond to
{XM, XM, Y
Increase the address value width in the debug log from 4 digits to
8 digits to allow for DSP cores with larger memory address ranges.
Signed-off-by: Richard Fitzgerald
---
sound/soc/codecs/wm_adsp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/codecs/wm_adsp.c b/
The patch
ASoC: dt-bindings: add mclk support to cs42l51
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent t
The patch
ASoC: dt-bindings: add mclk provider support to stm32 sai
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: cs42l51: add mclk support
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
The patch
ASoC: soc-core: fix trivial checkpatch issues
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: stm32: sai: set sai as mclk clock provider
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
regmap: Add regmap_noinc_write API
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus d
The patch
regulator: bd718x7: Remove struct bd718xx_pmic
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
The patch
regmap: use less #ifdef for LOG_DEVICE
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
The patch
spi: omap2-mcspi: Add slave mode support
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus d
The patch
spi: omap2-mcspi: Set FIFO DMA trigger level to word length
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
spi: omap2-mcspi: Switch to readl_poll_timeout()
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
dt-bindings: spi: add stm32 qspi controller
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linu
The patch
spi: pxa2xx: fix PCI dependency
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the
On Fri, Oct 19, 2018 at 02:49:05AM +0200, KarimAllah Ahmed wrote:
> When expedited grace-period is set, both synchronize_sched
> synchronize_rcu_bh can be optimized to have a significantly lower latency.
>
> Improve wait_rcu_gp handling to also account for expedited grace-period.
> The downside is
On Fri, Oct 19, 2018 at 01:30:02PM +0100, Mark Brown wrote:
> The patch
>
>spi: pxa2xx: fix PCI dependency
>
> has been applied to the spi tree at
>
>https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
Sorry, I'll drop this one - I forgot it had already been applied when
it
The patch
ASoC: cs42l51: add mclk support
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
v3: Comment improvements.
v2: Style improvements.
try_to_merge_two_pages() merges two pages, one of them
is a page of currently scanned mm, the second is a page
with identical hash from unstable tree. Currently, we
merge the page from unstable tree into the first one,
and then free it.
The idea o
On Sat, Oct 6, 2018 at 9:54 AM Rajneesh Bhardwaj
wrote:
>
> The LTR values follow PCIE LTR encoding format and can be decoded as per
> https://pcisig.com/sites/default/files/specification_documents/ECN_LatencyTolnReporting_14Aug08.pdf
>
> This adds support to translate the raw LTR values as read f
The patch
ASoC: stm32: sai: set sai as mclk clock provider
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
ASoC: dt-bindings: add mclk provider support to stm32 sai
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: soc-core: fix trivial checkpatch issues
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: dt-bindings: add mclk support to cs42l51
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent t
On Fri, Oct 19, 2018 at 01:21:18PM +0100, Mark Brown wrote:
> On Fri, Oct 19, 2018 at 01:19:20PM +0100, Charles Keepax wrote:
> > On Fri, Oct 19, 2018 at 12:26:22PM +0100, Mark Brown wrote:
>
> > > Please do not submit new versions of already applied patches, please
> > > submit incremental update
The patch
regulator: bd718x7: Remove struct bd718xx_pmic
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
The patch
regmap: use less #ifdef for LOG_DEVICE
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
On Fri, Oct 19, 2018 at 01:34:42PM +0100, Charles Keepax wrote:
> On Fri, Oct 19, 2018 at 01:21:18PM +0100, Mark Brown wrote:
> > It looks a lot like
> > bef9391cbec547351c6a13e52f3a26bb2d271ec7 regulator: lochnagar: Add support
> > for the Cirrus Logic Lochnagar
> > in -next.
> Well it sure d
On Sat, Oct 6, 2018 at 9:54 AM Rajneesh Bhardwaj
wrote:
>
> On some Goldmont based systems such as ASRock J3455M the BIOS may not
> enable the IPC1 device that provides access to the PMC and PUNIT. In
> such scenarios, the IOSS and PSS resources from the platform device can
> not be obtained and r
On Thu, Oct 18, 2018 at 2:53 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.18.16 release.
> There are 53 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
Update the rest of the comment at the start of the file to also use C++
style comments to match the required style of the SPDX header.
Signed-off-by: Charles Keepax
---
drivers/regulator/lochnagar-regulator.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/dri
On Mon, Oct 8, 2018 at 10:25 AM Marian Cepok wrote:
>
> Add touchscreen info for the Trekstor Primetab T13B tablet.
>
Pushed to my review and testing queue, thanks!
> Reviewed-by: Hans de Goede
> Signed-off-by: Marian Cepok
> ---
> drivers/platform/x86/touchscreen_dmi.c | 24 +
Hi all,
I have posted this series several months ago but interrupted by personal
affairs. Now I get time to complete this task. Thanks for all of the
reviewers.
I know some kernel developers was searching for a method to dissable GCC
optimizations, probably they want to apply GCC '-O0' option. But
The level4_kernel_pgt is only defined when X86_5LEVEL is enabled. So
surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif to
make code correct.
Signed-off-by: Du Changbin
Acked-by: Steven Rostedt (VMware)
---
arch/x86/include/asm/pgtable_64.h | 2 ++
arch/x86/kernel/head64.c
This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting
this option will prevent the compiler from optimizing the kernel by
auto-inlining functions not marked with the inline keyword.
With this option, only functions explicitly marked with "inline" will
be inlined. This will allow the
With '-Og' optimization level, GCC would not optimize a count for a loop
as a constant value. But BUILD_BUG_ON() only accept compile-time constant
values. Let's use __fix_to_virt() to avoid the error.
arch/arm/mm/mmu.o: In function `fix_to_virt':
/home/changbin/work/linux/./include/asm-generic/fix
This will apply GCC '-Og' optimization level which is supported
since GCC 4.8. This optimization level offers a reasonable level
of optimization while maintaining fast compilation and a good
debugging experience. It is similar to '-O1' while perferring
to keep debug ability over runtime speed.
If
On Wed, Oct 10, 2018 at 4:17 PM Hans de Goede wrote:
>
> Add touchscreen platform data for the Onda V80 Plus v3 tablet.
>
Pushed to my review and testing queue, thanks!
> Signed-off-by: Hans de Goede
> ---
> drivers/platform/x86/touchscreen_dmi.c | 26 ++
> 1 file chang
Hi Joakim,
On Fri, Oct 19, 2018 at 6:43 AM Joakim Zhang wrote:
>
> From: Dong Aisheng
>
> CAN transceiver is different on RevA and RevB board.
> It's active high on RevA while active low on Rev B.
>
> Signed-off-by: Dong Aisheng
> Signed-off-by: Joakim Zhang
> ---
> arch/arm/boot/dts/imx6sx-s
Commit-ID: b61b8bba18fe2b63d38fdaf9b83de25e2d787dfe
Gitweb: https://git.kernel.org/tip/b61b8bba18fe2b63d38fdaf9b83de25e2d787dfe
Author: Jithu Joseph
AuthorDate: Fri, 12 Oct 2018 15:51:01 -0700
Committer: Thomas Gleixner
CommitDate: Fri, 19 Oct 2018 14:54:28 +0200
x86/intel_rdt: Prevent
From: Colin Ian King
In the case where eq->fw->size > PAGE_SIZE the error return rc
is being set to EINVAL however this is being overwritten to
rc = req->fw->size because the error exit path via label 'out' is
not being taken. Fix this by adding the jump to the error exit
path 'out'.
Detected b
On Wed, Oct 10, 2018 at 8:23 PM Lubomir Rintel wrote:
>
> According to [1] and [2], the temperature values are in tenths of degree
> Celsius. Exposing the Celsius value makes the battery appear on fire:
>
> $ upower -i /org/freedesktop/UPower/devices/battery_olpc_battery
> ...
> temperat
On Wed, Oct 10, 2018 at 8:23 PM Lubomir Rintel wrote:
>
> It doesn't make sense to always have this built-in, e.g. on ARM
> multiplatform kernels. A better way to address the problem the original
> commit aimed to solve is to fix Kconfig.
>
> This reverts commit f48d1496b8537d75776478c6942dd87f34d
On Wed, Oct 10, 2018 at 8:23 PM Lubomir Rintel wrote:
>
> Also, the header is x86 specific, while there are non-x86 OLPC machines.
Same concern. as per patch 2.
Also, you might want to sort headers in alphabetical order.
>
> Signed-off-by: Lubomir Rintel
> ---
> drivers/platform/olpc/olpc-ec.
On Wed, Oct 10, 2018 at 8:23 PM Lubomir Rintel wrote:
>
> There are ARM OLPC machines that use mostly the same drivers, including
> EC infrastructure, DCON and Battery.
>
> While at that, fix Kconfig to allow building this as a module.
> - depends on MOUSE_PS2 && OLPC
> + depends on
On Wed, Oct 10, 2018 at 8:23 PM Lubomir Rintel wrote:
>
> Just return ENODEV, so that whoever attempted to use the EC call can
> defer their work.
>
> Signed-off-by: Lubomir Rintel
> ---
> drivers/platform/olpc/olpc-ec.c | 7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --g
On Thu, Oct 18, 2018 at 12:33:32PM +0200, luca abeni wrote:
> Hi Peter,
>
> On Thu, 18 Oct 2018 11:48:50 +0200
> Peter Zijlstra wrote:
> [...]
> > > So, I tend to think that we might want to play safe and put some
> > > higher minimum value for dl_runtime (it's currently at 1ULL <<
> > > DL_SCALE
On Thu, Oct 18, 2018 at 2:54 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.9.135 release.
> There are 35 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
From: Jonathan Hunter
The tps6586x driver creates an irqchip that is used by its various child
devices for managing interrupts. The tps6586x-rtc device is one of its
children that uses the tps6586x irqchip. When using the tps6586x-rtc as
a wake-up device from suspend, the following is seen:
PM:
Commit 448a5a552f336bd7b847b1951 ("drivers: base: cacheinfo: use OF
property_read_u32 instead of get_property,read_number") makes cache
size and number_of_sets be 0 if DT doesn't provide there values. I
think this is unreasonable so make them keep the old values, which is
the same as old kernels.
On 10/19/18 3:17 PM, Jon Hunter wrote:
>
> On 15/10/2018 14:52, Dmitry Osipenko wrote:
>> On 10/15/18 3:52 PM, Jon Hunter wrote:
>>>
>>> On 30/08/18 19:36, Dmitry Osipenko wrote:
This fixes splats like the one below if CONFIG_DEBUG_ATOMIC_SLEEP=y
and machine (Tegra30) booted with SMP=n o
On Wed, Oct 10, 2018 at 8:24 PM Lubomir Rintel wrote:
>
> It is actually plaform independent. Move it to the olpc-ec driver from
> the X86 OLPC platform, so that it could be used by the ARM based laptops
> too.
What is platform independent exactly?
> #define OLPC_F_PRESENT 0x01
> #defi
101 - 200 of 495 matches
Mail list logo
