Hi Linus,
I'm looking at
c1f64a58003f ("x86: MMIO and gcc re-ordering issue")
and trying to figure out was there any particular reason the address to
the MMIO write routines had to be an input operand?
Because if not, please have a look at the patch below. It boots here and
from the couple
Hi, Dinh,
On 04/09/2019 06:38 PM, Dinh Nguyen wrote:
> Get the reset control for the QSPI controller and bring it out of reset.
Is there a public datasheet where I can check this?
>
> Suggested-by: Tien-Fong Chee
> Signed-off-by: Dinh Nguyen
> ---
> v2: use
The ADJ_TAI adjtimex mode sets the TAI-UTC offset of the system clock.
It is typically set by NTP/PTP implementations and it is automatically
updated by the kernel on leap seconds. The initial value is zero (which
applications may interpret as unknown), but this value cannot be set by
adjtimex.
Add binding documentation of spi-mt65xx for MT8516 SOC.
Signed-off-by: Leilk Liu
---
.../devicetree/bindings/spi/spi-mt65xx.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
From: Timo Wischer
Since ARMv7 hardware cache coherence is supported.
"The SCU maintains coherency between the individual data caches in the
Cortex-A5 MPCore processor using a variation of the MOESI protocol" [1].
Therefore this patch enables the MMAP access to the status and control
Everyone:
This small series adds a driver for UCS1002 Programmable USB Port
Power Controller with Charger Emulation. See [page] for product page
and [datasheet] for device dataseet. Hopefully each individual patch
is self explanatory.
Feedback is welcome!
Thanks,
Andrey Smirnov
[page]
Add driver for Microchip UCS1002 Programmable USB Port Power
Controller with Charger Emulation. The driver exposed a power supply
device to control/monitor various parameter of the device as well as a
regulator to allow controlling VBUS line.
Signed-off-by: Andrey Smirnov
Cc: Chris Health
Cc:
Hi,
I do not see
http://lkml.kernel.org/r/1554348617-12897-1-git-send-email-huangzhaoy...@gmail.com
discussion reaching a conlusion to change the current workingset
implementation. Therefore is there any reason to post a new version of
the patch? If yes it would be really great to see a short
Add POWER_SUPPLY_HEALTH_OVERCURRENT constant in order to allow
singalling overcurrent condition via power supply health information.
Signed-off-by: Andrey Smirnov
Cc: Chris Health
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: Guenter Roeck
Cc: Sebastian Reichel
Cc: linux-kernel@vger.kernel.org
Cc:
Add bindings for Microchip UCS1002 Programmable USB Port Power
Controller with Charger Emulation.
Signed-off-by: Andrey Smirnov
Cc: Chris Health
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: Guenter Roeck
Cc: Rob Herring
Cc: devicet...@vger.kernel.org
Cc: Sebastian Reichel
Cc:
On 2019-04-17 10:21, Pankaj Bansal wrote:
> HI Peter,
>
> Have these changes been applied in any linux branch? I did not see these
> changes in
> https://elixir.bootlin.com/linux/v5.1-rc5/source/drivers/mux/mmio.c#L46
>
Hi,
No they have not, I've been busy with other stuff... However, I
of_iomap returns NULL on error.
Signed-off-by: Axel Lin
---
drivers/regulator/stm32-pwr.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/stm32-pwr.c b/drivers/regulator/stm32-pwr.c
index 222d593d76a2..dd5c2b383e5b 100644
---
Diana Madalina Craciun writes:
> Hi,
>
> I have tested the patches on NXP platforms and they worked as expected.
Thanks Diana.
cheers
> On 4/15/2019 9:45 PM, Greg Kroah-Hartman wrote:
>> commit cf175dc315f90185128fb061dc05b6fbb211aa2f upstream.
>>
>> The speculation barrier can be disabled
On 04/15/19 at 09:47pm, Borislav Petkov wrote:
> On Sun, Apr 14, 2019 at 03:28:04PM +0800, Baoquan He wrote:
> > kernel_randomize_memory() hardcodes the size of vmemmap section as 1 TB,
> > to support the maximum amount of system RAM in 4-level paging mode, 64 TB.
> >
> > However, 1 TB is not
Now that we are not using page address in handles directly, we
can make z3fold pages movable to decrease the memory fragmentation
z3fold may create over time.
This patch starts advertising non-headless z3fold pages as movable
and uses the existing kernel infrastructure to implement moving of
such
On Tue, 16 Apr 2019 at 18:23, Yangtao Li wrote:
>
> WARN_ON() already contains an unlikely(), so it's not necessary to use
> unlikely.
>
> Signed-off-by: Yangtao Li
Reviewed-by: Ulf Hansson
Kind regards
Uffe
> ---
> drivers/base/power/domain.c | 6 ++
> 1 file changed, 2 insertions(+),
The current z3fold implementation only searches this CPU's page
lists for a fitting page to put a new object into. This patch adds
quick search for very well fitting pages (i. e. those having
exactly the required number of free space) on other CPUs too,
before allocating a new page for that
For z3fold to be able to move its pages per request of the memory
subsystem, it should not use direct object addresses in handles.
Instead, it will create abstract handles (3 per page) which will
contain pointers to z3fold objects. Thus, it will be possible to
change these pointers when z3fold
This patch introduces a separate helper function for object
allocation, as well as 2 smaller helpers to add a buddy to the list
and to get a pointer to the pool from the z3fold header. No
functional changes here.
Signed-off-by: Vitaly Wool
---
mm/z3fold.c | 184
Assalamu Alaikum Wa Rahmatullahi Wa Barakatuh,
hello dear
I came across your contact during my private search. Mrs Aisha Al-
Qaddafi is my name, the only daughter of late Libyan president, am a
single Mother and a Widow with three Children.I have funds the sum of
$27.5 million USD for,
On 04/15/19 at 08:53pm, Borislav Petkov wrote:
> Now, lemme make sure I understand exactly what you're fixing here:
> you're fixing the case where CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING is
> not 0. Which is the case when CONFIG_MEMORY_HOTPLUG is enabled.
>
> Yes, no?
Yes, the padding is
On 12/04/2019 04:20, Amit Daniel Kachhap wrote:
> A per vcpu flag is added to check if pointer authentication is
> enabled for the vcpu or not. This flag may be enabled according to
> the necessary user policies and host capabilities.
>
> This patch also adds a helper to check the flag.
>
>
This patchset implements page migration support and slightly better
buddy search. To implement page migration support, z3fold has to move
away from the current scheme of handle encoding. i. e. stop encoding
page address in handles. Instead, a small per-page structure is created
which will contain
On Tue, Apr 16, 2019 at 11:52:08AM -0400, Yangtao Li wrote:
> For some SoCs, the CPU frequency subset and voltage value of each OPP
> varies based on the silicon variant in use. The sun50i-cpufreq-nvmem
> driver reads the efuse value from the SoC to provide the OPP framework
> with required
Dear Greg,
On 19. 4. 16. 오후 7:46, Greg KH wrote:
> On Fri, Apr 05, 2019 at 10:21:25AM +0900, Chanwoo Choi wrote:
>> Dear Greg,
>>
>> This is extcon-fixes pull request for v5.1-rc4. I add detailed description of
>> this pull request on below. Please pull extcon with following updates.
>>
>> Best
On Wed, Apr 17, 2019 at 07:38:30AM +0530, Viresh Kumar wrote:
> On 16-04-19, 11:52, Yangtao Li wrote:
> > Add sunxi nvmem based CPU scaling driver, refers to qcom-cpufreq-kryo.
> >
> > Yangtao Li (2):
> > cpufreq: Add sunxi nvmem based CPU scaling driver
> > dt-bindings: cpufreq: Document
On Tue, Apr 16, 2019 at 11:52:09AM -0400, Yangtao Li wrote:
> Allwinner Process Voltage Scaling Tables defines the voltage and
> frequency value based on the speedbin blown in the efuse combination.
> The sunxi-cpufreq-nvmem driver reads the efuse value from the SoC to
> provide the OPP framework
In the function mmc_alloc_host, the function put_device is called to
release allocated resources when mmc_gpio_alloc fails. Finally, the
function pointed by host->class_dev.class->dev_release (i.e.,
mmc_host_classdev_release) is used to release resources including the
host structure. However,
Hi Lukasz,
On 19. 4. 17. 오후 4:48, Lukasz Luba wrote:
> Extend the documenation by events description with new 'event-data-type'
> field. Add example how the event might be defined in DT.
>
> Signed-off-by: Lukasz Luba
> ---
> .../devicetree/bindings/devfreq/event/exynos-ppmu.txt | 18
>
On 16/04/19 2:07 PM, Bartosz Golaszewski wrote:
> If we agree on the direction of these patches, then I can go with a
> single enabled OPP for lcdk (456 MHz) and all OPPs up to 375 MHz
> enabled for da850-evm.
Sounds good to me.
Thanks,
Sekhar
pci_request_region_exclusive() was introduced with commit e8de1481fd71
("resource: allow MMIO exclusivity for device drivers") in 2.6.29 which
was released 2008.
It never had an in tree user since then, so after 11 years later let's
remove it.
Signed-off-by: Johannes Thumshirn
---
HI Peter,
Have these changes been applied in any linux branch? I did not see these
changes in
https://elixir.bootlin.com/linux/v5.1-rc5/source/drivers/mux/mmio.c#L46
Regards,
Pankaj Bansal
> -Original Message-
> From: Pankaj Bansal [mailto:pankaj.ban...@nxp.com]
> Sent: Thursday, 28
Hi Lukasz,
On 19. 4. 17. 오후 4:48, Lukasz Luba wrote:
> This patch adds posibility to choose what type of data should be counted
> by the PPMU counter. Now the type comes from DT where the event has been
> defined. When there is no 'event-data-type' the default value is used,
> which is 'read data
On 16/04/2019 16:28, Mark Brown wrote:
> On Tue, Apr 16, 2019 at 09:55:41AM +0200, Matthias Brugger wrote:
>> On 23/03/2019 22:16, Fabien Parent wrote:
>>> Add binding documentation of spi-mt65xx for MT8516 SoC.
>
>>> Signed-off-by: Fabien Parent ---
>>>
On Sat, Apr 13, 2019 at 01:22:50PM -0400, Waiman Long wrote:
> +/*
> + * This is safe to be called without holding the wait_lock.
Because @waiter is *our* waiter and it's not going anywhere. So when
it's first, it stays first until we do something about it.
> + */
> +static inline bool
>
On 16/04/19 5:18 PM, Adam Ford wrote:
> On Tue, Apr 16, 2019 at 3:38 AM Bartosz Golaszewski wrote:
>>
>> pon., 15 kwi 2019 o 12:21 Sekhar Nori napisał(a):
>>>
>>> On 12/04/19 9:01 PM, Bartosz Golaszewski wrote:
pt., 12 kwi 2019 o 15:53 Sekhar Nori napisał(a):
>
> On 12/04/19 5:41
On Wed, Apr 17, 2019 at 09:54:19AM +0200, Rafael J. Wysocki wrote:
> On Fri, Apr 12, 2019 at 3:42 PM Heikki Krogerus
> wrote:
> >
> > Hi,
> >
> > This is the third version of my proposal to add reference handling to
> > the software node code. In this version I renamed ACPI_NAME_SIZE to
> >
Hi Lukasz,
On 19. 4. 17. 오후 4:48, Lukasz Luba wrote:
> This patch add support of a new feature which can be used in DT:
> Performance Monitoring Unit with defined event data type.
> In this patch the event data types are defined for Exynos PPMU.
> The patch also updates the MAINTAINERS file
On 17/04/2019 05:01, Jiada Wang wrote:
> Hi Daniel
>
> On 2019/04/17 4:22, Daniel Lezcano wrote:
>> On 11/04/2019 12:03, Jiada Wang wrote:
>>> Currently IRQ is remain enabled after .remove, later if device is
>>> probed,
>>> IRQ is requested before .thermal_init, this may cause IRQ function be
On Tue, Apr 16, 2019 at 02:16:11PM -0400, Waiman Long wrote:
> >> @@ -608,56 +687,63 @@ __rwsem_down_write_failed_common(struct rw_semaphore
> >> *sem, int state)
> >> */
> >>waiter.task = current;
> >>waiter.type = RWSEM_WAITING_FOR_WRITE;
> >> + waiter.timeout = jiffies +
These symbols are only used by this driver, make them static.
Signed-off-by: Axel Lin
---
drivers/regulator/stm32-pwr.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/regulator/stm32-pwr.c b/drivers/regulator/stm32-pwr.c
index e434b26d4c8b..222d593d76a2 100644
add Johannes and answer his previous question.
@Johannes Weiner
Yes. I do agree with you about the original thought of sacrificing
long distance access pages when huge memory demands arise. The problem
is what is the criteria of the distance, which you can find from what
I comment in the patch,
Hi,
DRM comes with an extensive format support to retrieve the various
parameters associated with a given format (such as the subsampling, or the
bits per pixel), as well as some helpers and utilities to ease the driver
development.
v4l2, on the other side, doesn't provide such facilities,
drm_format_horz_chroma_subsampling and drm_format_vert_chroma_subsampling
are basically a lookup in the drm_format_info table plus an access to the
hsub and vsub fields of the appropriate entry.
Most drivers are using this function while having access to the entry
already, which means that we
On Fri, Apr 12, 2019 at 3:42 PM Heikki Krogerus
wrote:
>
> Hi,
>
> This is the third version of my proposal to add reference handling to
> the software node code. In this version I renamed ACPI_NAME_SIZE to
> ACPI_NAMESEG_SIZE in 6/13, and slit patch 9/13 in two separate patches
> (9/13 and
On Mon, Apr 15, 2019 at 04:17:48PM -0500, Alan Tull wrote:
> On Thu, Apr 11, 2019 at 10:06 PM Wu Hao wrote:
> >
> > On Thu, Apr 11, 2019 at 03:07:35PM -0500, Alan Tull wrote:
> > > On Sun, Mar 24, 2019 at 10:24 PM Wu Hao wrote:
> > >
> > > Hi Hao,
> > >
> > > >
> > > > This patch adds support
This patch add support of a new feature which can be used in DT:
Performance Monitoring Unit with defined event data type.
In this patch the event data types are defined for Exynos PPMU.
The patch also updates the MAINTAINERS file accordingly.
Signed-off-by: Lukasz Luba
---
MAINTAINERS
Extend the documenation by events description with new 'event-data-type'
field. Add example how the event might be defined in DT.
Signed-off-by: Lukasz Luba
---
.../devicetree/bindings/devfreq/event/exynos-ppmu.txt | 18 ++
1 file changed, 18 insertions(+)
diff --git
Hi all,
This patch set extends PPMU on Samsung Exynos by choosing type of data
which shell be counter in the PPMU registers.
It is possible to count e.g. read or write requests, read or write data.
A new field has been added in the DT 'event' node called 'event-data-type'.
It is them used during
This patch adds posibility to choose what type of data should be counted
by the PPMU counter. Now the type comes from DT where the event has been
defined. When there is no 'event-data-type' the default value is used,
which is 'read data in bytes'.
It is needed when you want to know not only
From: Zhaoyang Huang
This patch introduce timestamp into workingset's entry and judge if the page
is active or inactive via active_file/refault_ratio instead of refault distance.
The original thought is coming from the logs we got from trace_printk in this
patch, we can find about 1/5 of the
On Fri, Apr 12, 2019 at 02:05:21PM -0700, Moritz Fischer wrote:
> Hi Hao,
>
> this looks suspiciously like a hwmon driver ;-)
>
> https://www.kernel.org/doc/Documentation/hwmon/hwmon-kernel-api.txt
Hi Moritz,
Thanks a lot for the suggestion, yes, agree, and patch for thermal
management should
> From: Anson Huang
> Sent: Tuesday, April 16, 2019 11:22 AM
>
> i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller inside,
> the system controller is in charge of controlling power, clock and thermal
> sensors etc..
>
> This patch adds i.MX system controller thermal driver
On Wed, 17 Apr 2019 at 06:26, Anand Moon wrote:
>
> Hi Krzysztof,
>
> On Tue, 16 Apr 2019 at 15:49, Krzysztof Kozlowski wrote:
> >
> > On Mon, 15 Apr 2019 at 14:24, Anand Moon wrote:
> > > Cache Coherent Interface (CCI) among Cortex-A15 and Cortex-A7, G2D, G3D
> > > and SSS
> > >
> > > Level 0
On 17.04.19 05:37, Andrew Morton wrote:
> On Wed, 10 Apr 2019 10:07:24 +0200 David Hildenbrand wrote:
>
>> Care to fixup both u64 to resource_size_t? Or should I send a patch?
>> Whatever you prefer.
>
> Please send along a fixup.
Will do!
>
> This patch series has no evidence of having been
Den ons 17 apr. 2019 kl 01:18 skrev Andrew Morton :
>
> On Thu, 11 Apr 2019 17:32:12 +0200 Vitaly Wool wrote:
>
> > This patchset implements page migration support and slightly better
> > buddy search. To implement page migration support, z3fold has to move
> > away from the current scheme of
On Mon, Apr 15, 2019 at 06:36:13PM +0300, Alexey Budankov wrote:
>
> When dwarf stacks are collected jointly with user specified register
> set using --user-regs option like below the full register context is
> still captured on a sample:
>
> $ perf record -g --call-graph dwarf,1024
On Tue, Apr 16, 2019 at 08:25:17PM +, Song Liu wrote:
>
>
> > On Apr 16, 2019, at 7:37 AM, Arnaldo Carvalho de Melo
> > wrote:
> >
> > Em Tue, Apr 16, 2019 at 11:35:54AM -0300, Arnaldo Carvalho de Melo escreveu:
> >> Em Tue, Apr 16, 2019 at 04:34:52PM +0200, Jiri Olsa escreveu:
> >>> On
On Tue, Apr 16, 2019 at 02:16:11PM -0400, Waiman Long wrote:
> >> @@ -324,6 +364,12 @@ static void __rwsem_mark_wake(struct rw_semaphore
> >> *sem,
> >>adjustment -= RWSEM_FLAG_WAITERS;
> >>}
> >>
> >> + /*
> >> + * Clear the handoff flag
> >> + */
> > Right, but that is a
From: Tingwei Zhang
Number of free masters is not set correctly in stm
free path. Fix this by properly adding the number
of output channels before setting them to 0 in
stm_output_disclaim().
Currently it is equivalent to doing nothing since
master->nr_free is incremented by 0.
Fixes:
9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git
tags/intel_th-stm-fixes-for-greg-20190417
for you to fetch changes up to a32bb4a8524253943548f6c3794bfe9af5c99f4b
This adds support for Intel TH on Comet Lake.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/pci.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/hwtracing/intel_th/pci.c b/drivers/hwtracing/intel_th/pci.c
index 1cf6290d6435..70f2cb90adc5 100644
---
From: Shahar S Matityahu
The driver uses msix causes-register to handle both msix and non msix
interrupts when performing sync nmi. On devices that do not support
msix this register is unmapped and accessing it causes a kernel panic.
Solve this by differentiating the two cases and accessing
From: RickyWu
this patch fixes rts5260 power saving parameter
make power saving function work on L1.1, L1.2
Signed-off-by: RickyWu
---
drivers/misc/cardreader/rts5260.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/misc/cardreader/rts5260.c
Commit 7bd1d4093c2f ("stm class: Introduce an abstraction for System Trace
Module devices") naively calculates the channel bitmap size in 64-bit
chunks regardless of the size of underlying unsigned long, making the
bitmap half as big on a 32-bit system. This leads to an out of bounds
access with
On Wed, Apr 17, 2019 at 09:55:25AM +0300, Adrian Hunter wrote:
> On 17/04/19 9:51 AM, Jiri Olsa wrote:
> > On Wed, Apr 17, 2019 at 09:35:32AM +0300, Adrian Hunter wrote:
> >> On 16/04/19 7:01 PM, Jiri Olsa wrote:
> >>> The eBPF program can be loaded multiple times
> >>> with the same name (tag).
Hi all,
News: there will be no linux-next release on Friday, Monday or Thursday
April 25.
Changes since 20190416:
The bpf-next tree gained a conflict against the bpf tree.
The drm tree still had its build failure for which I disabled a driver.
The fix is in the drm-misc tree where I reenabled
Commit 045afc24124d ("arm64: futex: Fix FUTEX_WAKE_OP atomic ops with
non-zero result value") removed oldval's zero initialization in
arch_futex_atomic_op_inuser because it is not necessary. Unfortunately,
Android's arm64 GCC 4.9.4 [1] does not agree:
../kernel/futex.c: In function 'do_futex':
On Tue, Apr 16, 2019 at 05:07:26PM -0400, Waiman Long wrote:
> Thinking about it again. I think I will just change its definition to
> "((HZ + 249)/250)" for now to make sure that it is at least 1. The
DIV_ROUND_UP()
On Wed, 17 Apr 2019 10:46:57 +0800
masonccy...@mxic.com.tw wrote:
> Hi Boris,
>
>
> > > > > > > > Subject
> > > > > > > >
> > > > > > > > Re: [PATCH] mtd: rawnand: Add Macronix NAND read retry and
> > > > > randomizer
> > > > > > > support
> > > > > > > >
> > > > > > > > On Tue, 9
Hi Mason,
masonccy...@mxic.com.tw wrote on Wed, 17 Apr 2019 10:46:57 +0800:
> Hi Boris,
>
>
> > > > > > > > Subject
> > > > > > > >
> > > > > > > > Re: [PATCH] mtd: rawnand: Add Macronix NAND read retry and
> > > > > randomizer
> > > > > > > support
> > > > > > > >
> > > > > > > >
On 04/17/19 at 02:00pm, Kairui Song wrote:
> On Wed, Apr 17, 2019 at 12:57 PM Dave Young wrote:
> >
> > On 04/17/19 at 09:38am, Dave Young wrote:
> > > On 04/16/19 at 03:22pm, Borislav Petkov wrote:
> > > > On Tue, Apr 16, 2019 at 07:41:33PM +0800, Dave Young wrote:
> > > > > On 04/16/19 at
On Tue, Apr 16, 2019 at 03:15:59PM -0500, Josh Poimboeuf wrote:
> If you do the regs->eflags thing to mark the regs as fake in
> (perf_arch_fetch_caller_regs()), then I don't think skip_sp would be
> needed, because regs->sp could probably mark the skip point.
>
> Instead I was actually hoping we
On Tue, 2019-04-16 at 12:22 -0700, Kevin Hilman wrote:
> On Tue, Apr 16, 2019 at 11:52 AM Kevin Hilman wrote:
> > Jerome Brunet writes:
> >
> > > This patchset adds most the audio devices of the g12a SoCs.
> > >
> > > Kevin, couple of things worth noting:
> > > * This patch depends of the new
On 17/04/19 9:51 AM, Jiri Olsa wrote:
> On Wed, Apr 17, 2019 at 09:35:32AM +0300, Adrian Hunter wrote:
>> On 16/04/19 7:01 PM, Jiri Olsa wrote:
>>> The eBPF program can be loaded multiple times
>>> with the same name (tag). We can share dso
>>> objects for those programs.
>>
>> Doesn't a eBPF
On 17. 04. 19, 8:52, Jiri Slaby wrote:
> So could you rework the patch to remove only the one? And in a separate
> patch, introduce a printk_ratelimited warning to every "case *:" (i.e.
Not printk_ratelimited, but "dev_warn_ratelimited(tty->dev" as we have a
device.
> no warning in the "default"
Hi Angus,
On 19-04-16 16:36, Angus Ainslie wrote:
> Hi Marco,
>
> On 2019-04-16 15:20, Marco Felsch wrote:
> > Hi Angus,
> >
> > On 19-04-16 11:02, Angus Ainslie wrote:
> > > Hi Marco,
> > >
> > > On 2019-04-16 00:54, Marco Felsch wrote:
> > > > Hi Agnus,
> > > >
> > >
> > > Just a nitpick
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/binfmt_elf.c: In function 'load_elf_binary':
fs/binfmt_elf.c:1140:7: error: 'elf_interpreter' undeclared (first use in this
function); did you mean 'interpreter'?
if
On 17. 04. 19, 8:46, Greg Kroah-Hartman wrote:
> On Wed, Apr 17, 2019 at 08:27:41AM +0200, Jiri Slaby wrote:
>> On 16. 04. 19, 16:53, Fuqian Huang wrote:
>>> --- a/drivers/tty/rocket.c
>>> +++ b/drivers/tty/rocket.c
>> ...
>>> -/* IOCTL call handler into the driver */
>>> -static int
On Wed, Apr 17, 2019 at 09:35:32AM +0300, Adrian Hunter wrote:
> On 16/04/19 7:01 PM, Jiri Olsa wrote:
> > The eBPF program can be loaded multiple times
> > with the same name (tag). We can share dso
> > objects for those programs.
>
> Doesn't a eBPF program get recompiled differently every time
On Tue, Apr 16, 2019 at 11:41:53PM -0700, Nathan Chancellor wrote:
> On Wed, Apr 17, 2019 at 08:15:08AM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Apr 16, 2019 at 09:47:51AM -0700, Nathan Chancellor wrote:
> > > On Tue, Apr 16, 2019 at 11:00:52AM +0200, Greg Kroah-Hartman wrote:
> > > > On Mon,
On Wed, Apr 17, 2019 at 08:27:41AM +0200, Jiri Slaby wrote:
> On 16. 04. 19, 16:53, Fuqian Huang wrote:
> > --- a/drivers/tty/rocket.c
> > +++ b/drivers/tty/rocket.c
> ...
> > -/* IOCTL call handler into the driver */
> > -static int rp_ioctl(struct tty_struct *tty,
> > - unsigned
Hi Andrew,
On Tue, Apr 16, 2019 at 09:19:22PM -0700, Andrew Morton wrote:
> On Wed, 10 Apr 2019 23:37:18 +0800 Feng Tang wrote:
>
> > Currently on panic, kernel will lower the loglevel and print out
> > new printk msg only with console_flush_on_panic().
> >
> > Add an option for users to
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
mm/vmscan.c: In function 'snapshot_refaults':
mm/vmscan.c:2969:14: error: implicit declaration of function
'lruvec_page_state_local'; did you mean 'lruvec_page_state'?
Hi,
On 14/04/19 11:21 PM, Sergei Shtylyov wrote:
> Hello!
>
> On 04/12/2019 12:29 PM, Vignesh Raghavendra wrote:
>
>> Cypress' HyperBus is Low Signal Count, High Performance Double Data Rate
>> Bus interface between a host system master and one or more slave
>> interfaces. HyperBus is used to
On Wed, Apr 17, 2019 at 08:15:08AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 16, 2019 at 09:47:51AM -0700, Nathan Chancellor wrote:
> > On Tue, Apr 16, 2019 at 11:00:52AM +0200, Greg Kroah-Hartman wrote:
> > > On Mon, Apr 15, 2019 at 03:01:51PM -0700, Nathan Chancellor wrote:
> > > > On Mon,
On 14/04/19 11:25 PM, Sergei Shtylyov wrote:
> On 04/12/2019 12:29 PM, Vignesh Raghavendra wrote:
>
>> Add binding documentation for TI's HyperBus memory controller present on
>> AM654 SoC.
>>
>> Signed-off-by: Vignesh Raghavendra
>> ---
>> .../devicetree/bindings/mtd/ti,am654-hbmc.txt | 31
On Tue, Apr 16, 2019 at 11:35:36PM +0200, Hans de Goede wrote:
> Hi,
>
> On 12-04-19 15:41, Heikki Krogerus wrote:
> > Now that the software nodes support references, and the
> > device connection API support parsing fwnode references,
> > replacing the old connection descriptions with software
On 16/04/19 7:01 PM, Jiri Olsa wrote:
> The eBPF program can be loaded multiple times
> with the same name (tag). We can share dso
> objects for those programs.
Doesn't a eBPF program get recompiled differently every time it is loaded?
>
> Link:
On 4/16/2019 7:03 PM, Colin King wrote:
From: Colin Ian King
There is a spelling mistake in a pr_debug message. Fix it.
Signed-off-by: Colin Ian King
Reviewed-by: Mukesh Ojha
Cheers,
-Mukesh
---
drivers/watchdog/intel_scu_watchdog.c | 2 +-
1 file changed, 1 insertion(+), 1
On Tue, Apr 16, 2019 at 09:34:51PM -0400, Sasha Levin wrote:
> 2. Fix to show monitor data only when monitor pages are actually
> allocated, also by Kimberly Brown.
That's not really a "fix", more like a "new feature", right?
> drivers/hv/vmbus_drv.c | 166
>
On 16. 04. 19, 16:53, Fuqian Huang wrote:
> --- a/drivers/tty/rocket.c
> +++ b/drivers/tty/rocket.c
...
> -/* IOCTL call handler into the driver */
> -static int rp_ioctl(struct tty_struct *tty,
> - unsigned int cmd, unsigned long arg)
> -{
> - struct r_port *info =
On Tue, Apr 16, 2019 at 05:13:18PM -0500, Madhumitha Prabakaran wrote:
> Fix a blank line after structure declarations. Also, convert
> macros into inline functions in order to maintain Linux kernel
> coding style based on which the inline function is
> preferable over the macro.
>
> Blank line
* Theodore Ts'o wrote:
> It seems though the assumption that we're assuming the attacker has
> arbitrary ability to get the low bits of the stack, so *if* that's
> true, then eventually, you'd be able to get enough samples that you
> could reverse engineer the prandom state. This could
Attention Please
Please confirm email if active. There is are some funds that need to me
transfer to this bearer,
So get back ASAP
Regards
Hans Schwarz
On Wed, Apr 17, 2019 at 08:15:56AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 17, 2019 at 03:46:09AM +0530, Bharath Vedartham wrote:
> > Compiled and Booted(defconfig) on my x86 machine. No dmesg regressions.
>
> Thanks for testing 2 of these and letting me know.
Oops, you tested 3, thanks
On Wed, Apr 17, 2019 at 03:46:09AM +0530, Bharath Vedartham wrote:
> Compiled and Booted(defconfig) on my x86 machine. No dmesg regressions.
Thanks for testing 2 of these and letting me know.
greg k-h
On Tue, Apr 16, 2019 at 03:41:02PM -0600, shuah wrote:
> On 4/15/19 12:59 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.0.8 release.
> > There are 117 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with
On Tue, Apr 16, 2019 at 09:47:51AM -0700, Nathan Chancellor wrote:
> On Tue, Apr 16, 2019 at 11:00:52AM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Apr 15, 2019 at 03:01:51PM -0700, Nathan Chancellor wrote:
> > > On Mon, Apr 15, 2019 at 08:44:36PM +0200, Greg Kroah-Hartman wrote:
> > > > From:
* Vince Weaver wrote:
> On Tue, 16 Apr 2019, tip-bot for Stephane Eranian wrote:
>
> > Commit-ID: f447e4eb3ad1e60d173ca997fcb2ef2a66f12574
> > Gitweb:
> > https://git.kernel.org/tip/f447e4eb3ad1e60d173ca997fcb2ef2a66f12574
> > Author: Stephane Eranian
> > AuthorDate: Mon, 8 Apr
701 - 800 of 800 matches
Mail list logo
