Peter Zijlstra writes:
> On Wed, Apr 10, 2019 at 03:51:24PM +0200, Thomas-Mich Richter wrote:
>> Thanks for the fix with commit id 86071b11317550d994b55ce5e31aa06bcad783b5.
>>
>> However doing an fgrep on the pending_disable member of struct perf_event
>> reveals two more hits in file
Web Admin Notificación de correo electrónico
Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos
los propietarios de nuestras cuentas de correo electrónico. Estamos eliminando
el acceso a todos nuestros clientes de correo web, su cuenta de correo
electrónico se
Web Admin Notificación de correo electrónico
Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos
los propietarios de nuestras cuentas de correo electrónico. Estamos eliminando
el acceso a todos nuestros clientes de correo web, su cuenta de correo
electrónico se
On 4/10/19 3:51 PM, Flavio Suligoi wrote:
Calculate the divisor for the SCR (Serial Clock Rate), avoiding
that the SSP transmission rate can be greater than the device rate.
When the division between the SSP clock and the device rate generates
a reminder, we have to increment by one the
Pass Unicode character to k_unicode handler function to honor possible
accent_table definition.
With introduction of KDSKBDIACRUC ioctl, it has been possible to set
compose characters (diacr, base and result) to any Unicode character
(below 0xf000 code point) as defined in struct kbdiacruc.
But
On Wed, 2019-04-10 at 18:43 -0700, Suren Baghdasaryan via Lsf-pc wrote:
> The time to kill a process and free its memory can be critical when
> the
> killing was done to prevent memory shortages affecting system
> responsiveness.
The OOM killer is fickle, and often takes a fairly
long time to
On Thu, 2019-04-11 at 04:56 +0200, Nicholas Mc Guire wrote:
> On Wed, Apr 10, 2019 at 03:53:51PM -0700, Stephen Boyd wrote:
> > Quoting Nicholas Mc Guire (2019-04-06 20:13:24)
> > > Providing a range for usleep_range() allows the hrtimer subsystem to
> > > coalesce timers - the delay is runtime
On Thu, Apr 11, 2019 at 01:42:59AM -0700, Paul Walmsley wrote:
> Similar to ARM64, add support for building DTB files from DT source
> data for RISC-V boards.
>
> This patch starts with the infrastructure needed for SiFive boards.
> Boards from other vendors would add support here in a similar
Am Dienstag, 9. April 2019, 22:49:05 CEST schrieb Douglas Anderson:
> The rk3288 SoC has two PWM implementations available, the "old"
> implementation and the "new" one. You can switch between the two of
> them by flipping a bit in the grf.
>
> The "old" implementation is the default at chip
Hi,
From: Sudeep Holla [sudeep.ho...@arm.com]:
> static void psci_sys_reset(enum reboot_mode reboot_mode, const char *cmd)
> {
> + if ((reboot_mode == REBOOT_WARM || reboot_mode == REBOOT_SOFT) &&
I would omit the REBOOT_SOFT here.
> + psci_system_reset2_supported)
> +
Am Mittwoch, 10. April 2019, 01:14:05 CEST schrieb Matthias Kaehlcke:
> Add GPIO D5 (BT_ENABLE_L) as reset-GPIO to the power sequence for the
> Bluetooth/WiFi module. On devices with a Broadcom module the signal
> needs to be asserted to use Bluetooth.
>
> Note that BT_ENABLE_L is a misnomer in
Am Mittwoch, 10. April 2019, 20:30:10 CEST schrieb Matthias Kaehlcke:
> Some veyron devices have a Bluetooth controller connected on UART0.
> The UART needs to operate at a high speed, however setting the clock
> rate at initialization has no practical effect. During initialization
> user space
On Thu 11-04-19 13:18:07, David Hildenbrand wrote:
> On 11.04.19 12:56, Michal Hocko wrote:
> > On Thu 11-04-19 11:11:05, David Hildenbrand wrote:
> >> On 11.04.19 10:41, Michal Hocko wrote:
> >>> On Wed 10-04-19 12:14:55, David Hildenbrand wrote:
> While current node handling is probably
> > > Right, yes - that analysis seems correct. The interfaces seem a bit
> > > weird here but fixing them looks like the most complete and robust
> fix.
>
> > Ok Mark, I'll fix this problem as soon as I can, using EPROBE_DEFER.
> > For now, in my application, I use the patch that I already
Commit 23d0127096cb ("fs/sync.c: make sync_file_range(2) use WB_SYNC_NONE
writeback") claims that sync_file_range(2) syscall was "created for
userspace to be able to issue background writeout and so waiting for
in-flight IO is undesirable there" and changes the writeback (back) to
WB_SYNC_NONE.
The patch
ASoC: wcd9335: Fix missing regmap requirement
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.1
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
regulator: vexpress: Constify regulator_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
> Right now we are using find_memory_block() to get the node id for the
> pfn range to online. We are missing to drop a reference to the memory
> block device. While the device still gets unregistered via
> device_unregister(), resulting in no user visible problem, the device is
> never released
The patch
regulator: mcp16502: Remove setup_regulators function
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: mcp16502: Remove unneeded fields from struct mcp16502
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually
The patch
regulator: hi6421: Convert to use simplified DT parsing
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
On 11.04.19 12:56, Michal Hocko wrote:
> On Thu 11-04-19 11:11:05, David Hildenbrand wrote:
>> On 11.04.19 10:41, Michal Hocko wrote:
>>> On Wed 10-04-19 12:14:55, David Hildenbrand wrote:
While current node handling is probably terribly broken for memory block
devices that span several
Hi Enric, Srinivas
On Thu, Apr 11, 2019 at 12:55:13PM +0200, Enric Balletbo i Serra wrote:
> Hi,
>
> On 10/4/19 17:31, Jett Rink wrote:
> > Reviewed-by: Jett Rink
> > Tested-by: Jett Rink
> >
> >
> > On Sun, Apr 7, 2019 at 6:10 AM Rushikesh S Kadam
> > wrote:
> >>
> >> This driver
Right now we are using find_memory_block() to get the node id for the
pfn range to online. We are missing to drop a reference to the memory
block device. While the device still gets unregistered via
device_unregister(), resulting in no user visible problem, the device is
never released via
On 4/11/19 4:20 AM, Vlastimil Babka wrote:
> On 4/11/19 5:26 AM, Qian Cai wrote:
>> "cat /proc/slab_allocators" could hang forever on SMP machines with
>> kmemleak or object debugging enabled due to other CPUs running do_drain()
>> will keep making kmemleak_object or debug_objects_cache dirty
On Thu, Apr 11, 2019 at 1:16 PM Jan Kara wrote:
>
> On Wed 10-04-19 13:42:23, Amir Goldstein wrote:
> > On Wed, Apr 10, 2019 at 12:10 PM Jan Kara wrote:
> > >
> > > On Tue 09-04-19 21:01:54, Amir Goldstein wrote:
> > > > On Tue, Apr 9, 2019 at 6:43 PM Jan Kara wrote:
> > > > > On Tue 09-04-19
On Thu, 11 Apr 2019 at 13:04, Nicholas Mc Guire wrote:
>
> Providing a range for usleep_range() allows the hrtimer subsystem to
> coalesce timers - the delay is runtime configurable so a factor 2
> is taken to provide the range. With the expected range for
> enable_delay_us being milliseconds,
Providing a range for usleep_range() allows the hrtimer subsystem to
coalesce timers - the delay is runtime configurable so a factor 2
is taken to provide the range. With the expected range for
enable_delay_us being milliseconds, the range should lie in the 250us
range which is sufficient for
On Thu, Apr 11, 2019 at 11:33:46AM +0100, Sudeep Holla wrote:
> PSCI v1.1 introduced SYSTEM_RESET2 to allow both architectural resets
> where the semantics are described by the PSCI specification itself as
> well as vendor-specific resets. Currently only system warm reset
> semantics is defined as
On Thu, 11 Apr 2019 at 04:48, YueHaibing wrote:
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/memstick/host/jmb38x_ms.c: In function 'jmb38x_ms_issue_cmd':
> drivers/memstick/host/jmb38x_ms.c:371:17: warning:
> variable 'data' set but not used [-Wunused-but-set-variable]
>
>
* Will Deacon wrote:
> Anyway, please take a look at the diff below and let me know if you're
> happy with it. The original commit is currently at the bottom of my mmiowb
> tree, so I'll probably put this on top as an extra commit with your
> Reported-by.
Sure - and the changes look good to
On Thu 11-04-19 11:11:05, David Hildenbrand wrote:
> On 11.04.19 10:41, Michal Hocko wrote:
> > On Wed 10-04-19 12:14:55, David Hildenbrand wrote:
> >> While current node handling is probably terribly broken for memory block
> >> devices that span several nodes (only possible when added during
On Thu, Apr 11, 2019 at 4:28 AM Yurii Pavlovskyi
wrote:
> The DSTS method detection fails, as nothing is returned if method is not
> defined in WMNB. As a result the control of keyboard backlight is not
> functional for TUF Gaming series laptops (at the time the only
> functionality of the driver
Hi,
On 10/4/19 17:31, Jett Rink wrote:
> Reviewed-by: Jett Rink
> Tested-by: Jett Rink
>
>
> On Sun, Apr 7, 2019 at 6:10 AM Rushikesh S Kadam
> wrote:
>>
>> This driver implements a slim layer to enable the ChromeOS
>> EC kernel stack (cros_ec) to communicate with ChromeOS EC
>> firmware
Was this supposed to be patch 6/5 of your previous series?
On Thu, Apr 11, 2019 at 04:05:36PM +1000, Nicholas Piggin wrote:
> Date: Tue, 9 Apr 2019 20:23:16 +1000
> Subject: [PATCH] kernel/sched: run nohz idle load balancer on HK_FLAG_MISC
> CPUs
>
> The nohz idle balancer runs on the lowest
On Wed 10-04-19 18:43:51, Suren Baghdasaryan wrote:
[...]
> Proposed solution uses existing oom-reaper thread to increase memory
> reclaim rate of a killed process and to make this rate more deterministic.
> By no means the proposed solution is considered the best and was chosen
> because it was
On Thu, 11 Apr 2019 at 12:42, Chaotian Jing wrote:
>
> On Thu, 2019-04-11 at 11:49 +0200, Ulf Hansson wrote:
> > Chaotian,
> >
> > On Mon, 25 Mar 2019 at 13:24, Ulf Hansson wrote:
> > >
> > > Cc: Chaotian Jing
> > > Signed-off-by: Ulf Hansson
> > > ---
> > > MAINTAINERS | 6 ++
> > > 1
On Wed, Apr 10, 2019 at 04:28:48AM +0200, Frederic Weisbecker wrote:
> Should I re-issue the set or you do the changes?
I've made it like so; does that work? In particular, do the comments
make sense? It is always hard to write these things down.
---
Subject: locking/lockdep: Test all
On Thu, 11 Apr 2019 at 11:00, Faiz Abbas wrote:
>
> commit 5b0d62108b46 ("mmc: sdhci-omap: Add platform specific reset
> callback") skips data resets during tuning operation. Because of this,
> a data error or data finish interrupt might still arrive after a command
> error has been handled and
On Wed, 3 Apr 2019 at 21:31, Fabien Parent wrote:
>
> 'top_base' memory region is optional. Check that the resource is valid
> before using it. This avoid getting a "invalid resource" error message
> printed by the kernel.
>
> Signed-off-by: Fabien Parent
Applied for next, thanks!
Kind regards
On Mon, 1 Apr 2019 at 14:58, Faiz Abbas wrote:
>
> According to the AM654x Data Manual[1], the setup timing in lower speed
> modes can only be met if the controller uses a falling edge data launch.
>
> To ensure this, the HIGH_SPEED_ENA (HOST_CONTROL[2]) bit should be
> cleared in default speed,
On Thu, 2019-04-11 at 11:49 +0200, Ulf Hansson wrote:
> Chaotian,
>
> On Mon, 25 Mar 2019 at 13:24, Ulf Hansson wrote:
> >
> > Cc: Chaotian Jing
> > Signed-off-by: Ulf Hansson
> > ---
> > MAINTAINERS | 6 ++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/MAINTAINERS
On Thu, Apr 11, 2019 at 07:14:06AM +, Flavio Suligoi wrote:
> > Right, yes - that analysis seems correct. The interfaces seem a bit
> > weird here but fixing them looks like the most complete and robust fix.
> Ok Mark, I'll fix this problem as soon as I can, using EPROBE_DEFER.
> For now,
On Thu, Apr 11, 2019 at 11:36:45AM +0200, Ulf Hansson wrote:
> On Sun, 7 Apr 2019 at 05:13, Nicholas Mc Guire wrote:
> >
> > Providing a range for usleep_range() allows the hrtimer subsystem to
> > coalesce timers - the delay is runtime configurable so a factor 2
> > is taken to provide the
Cc: Oleg too
On Thu, Apr 11, 2019 at 12:30:18PM +0200, Christian Brauner wrote:
> On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> > Add new SS_EXPEDITE flag to be used when sending SIGKILL via
> > pidfd_send_signal() syscall to allow expedited memory reclaim of the
> >
PSCI v1.1 introduced SYSTEM_RESET2 to allow both architectural resets
where the semantics are described by the PSCI specification itself as
well as vendor-specific resets. Currently only system warm reset
semantics is defined as part of architectural resets by the specification.
This patch
This is particularly useful for Wine which needs to implement Win32
API clock functions whose values do not get adjusted by adjtimex().
Cc: Thomas Gleixner
Cc: Andy Lutomirski
Signed-off-by: Huw Davies
---
arch/x86/entry/vsyscall/vsyscall_gtod.c | 6 ++
arch/x86/include/asm/vgtod.h
On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> Add new SS_EXPEDITE flag to be used when sending SIGKILL via
> pidfd_send_signal() syscall to allow expedited memory reclaim of the
> victim process. The usage of this flag is currently limited to SIGKILL
> signal and only to
The 'mask' member of struct vsyscall_gtod_data is unused, so remove
it. Its use was removed in commit a51e996d48ac (x86/vdso: Enforce
64bit clocksource).
Cc: Thomas Gleixner
Cc: Andy Lutomirski
Signed-off-by: Huw Davies
---
arch/x86/entry/vsyscall/vsyscall_gtod.c | 1 -
This will allow clocks with different mult and shift values,
e.g. CLOCK_MONOTONIC_RAW, to be supported in the vDSO.
The coarse clocks do not require these data so the values are not
copied for these clocks.
One could add potential new values of mult and shift alongside the
existing values in
This series adds support for the CLOCK_MONOTONIC_RAW clock in the x86
vDSO, thus decreasing its readout cost. This is particularly useful
for Wine which needs to implement Win32 API clock functions whose
value does not get adjusted with adjtimex().
Cc: Thomas Gleixner
Cc: Andy Lutomirski
Huw
Hi,
Missatge de Pi-Hsun Shih del dia dc., 10 d’abr.
2019 a les 9:13:
>
> Hi,
>
> On Thu, Mar 28, 2019 at 7:16 PM Enric Balletbo Serra
> wrote:
> >
> > Hi
> >
> > Thanks for sending this upstream, Some few comments and questions
> > below. Apart from these LGTM.
> >
> > Missatge de Peter Shih
Add thermal binding documentation for Amazon's Annapurna Labs Thermal
Sensor.
Signed-off-by: Talel Shenhar
Reviewed-by: David Woodhouse
Reviewed-by: Rob Herring
---
.../bindings/thermal/amazon,al-thermal.txt | 33 ++
1 file changed, 33 insertions(+)
create mode
This is a generic thermal driver for simple MMIO sensors, of which
amazon,al-thermal is one.
This device uses a single MMIO transaction to read the temperature and
report it to the thermal subsystem.
Signed-off-by: Talel Shenhar
Reviewed-by: David Woodhouse
---
MAINTAINERS
On Tue, 26 Mar 2019 at 05:56, Takao Orito wrote:
>
> SD Host controller on Milbeaut is consist of two controller parts.
> One is core controller F_SDH30, this is similar to sdhci-fujitsu
> controller.
> Another is bridge controller.
> This bridge controller is not compatible with sdhci-fujitsu
This series introduces support for Amazon's Annapurna Labs Thermal Sensor
based on a new simple MMIO thermal driver. This driver is intended to be
used by other devices as well, which require just a simple MMIO access to
read temperature.
Changes since v2:
=
- dt-binding: changed
On Thu, Apr 11, 2019 at 8:24 AM Heiko Carstens
wrote:
>
> On Wed, Apr 10, 2019 at 10:12:40PM +0200, Arnd Bergmann wrote:
> > llvm does does not understand -march=z9-109 and older target
> > specifiers, so disable the respective Kconfig settings and
> > the logic to make the boot code work on old
On Thu, Apr 11, 2019 at 12:20 AM 'Nick Desaulniers' via Clang Built
Linux wrote:
>
> On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote:
> >
> > llvm does does not understand -march=z9-109 and older target
>
> Please file bugs for these in LLVM's issue tracker. It might be
> possible to enable
On Wed 10-04-19 13:42:23, Amir Goldstein wrote:
> On Wed, Apr 10, 2019 at 12:10 PM Jan Kara wrote:
> >
> > On Tue 09-04-19 21:01:54, Amir Goldstein wrote:
> > > On Tue, Apr 9, 2019 at 6:43 PM Jan Kara wrote:
> > > > On Tue 09-04-19 14:49:22, Amir Goldstein wrote:
> > > > > Commit 23d0127096cb
On Fri, Apr 05, 2019 at 01:24:29AM +0530, Vidya Sagar wrote:
> Export pcie_pme_disable_msi() API to enable drivers using this API be able to
> build as loadable modules
>
> Signed-off-by: Vidya Sagar
> ---
> Changes from [v1]:
> * This is a new patch in v2 series
>
> drivers/pci/pcie/pme.c
On Fri, Apr 05, 2019 at 01:24:28AM +0530, Vidya Sagar wrote:
> Add #defines for the Data Link Feature and Physical Layer 16.0 GT/s
> features.
>
> Signed-off-by: Vidya Sagar
> ---
> Changes from [v1]:
> * None
>
> include/uapi/linux/pci_regs.h | 22 +-
> 1 file changed, 21
Dear Sir/Ma,
Do not let this come as a surprise to you as my organization and I do a lot of
philanthropic work and support a lot of good will project in Africa, Asia and
South America.
I have one of such project that I am currently involved in, it has to do with
providing solar powered
On Mon, 1 Apr 2019 at 19:43, Sowjanya Komatineni wrote:
>
> > > >
> > > > Default tap and trim values are incorrect for Tegra186 SDMMC4.
> > > > This patch fixes it.
> > > >
> > > > Tested-by: Jon Hunter
> > > > Signed-off-by: Sowjanya Komatineni
> > >
> > > Is this a fix and/or for stable?
> >
On Wed, 3 Apr 2019 at 17:39, Sowjanya Komatineni wrote:
>
> This patch adds suspend and resume PM ops for tegra SDHCI.
>
> Acked-by: Thierry Reding
> Signed-off-by: Sowjanya Komatineni
> ---
> drivers/mmc/host/sdhci-tegra.c | 56
> +-
> 1 file changed,
Dear Sir/Ma,
Do not let this come as a surprise to you as my organization and I do a lot of
philanthropic work and support a lot of good will project in Africa, Asia and
South America.
I have one of such project that I am currently involved in, it has to do with
providing solar powered
Currently IRQ is remain enabled after .remove, later if device is probed,
IRQ is requested before .thermal_init, this may cause IRQ function be
triggered but not able to clear IRQ status, thus cause system to hang.
this patch by moving request of IRQ after device initialization to
avoid this
On Fri, 22 Mar 2019 at 18:03, Maxim Levitsky wrote:
>
> Thanks!
> I also expect to start contributing again to maintain the code I have
> in the kernel, after I done with upsteaming the nvme-mdev driver I
> have just sent for initial review.
> I work for Red Hat now, so I hope I'll find some time
Chaotian,
On Mon, 25 Mar 2019 at 13:24, Ulf Hansson wrote:
>
> Cc: Chaotian Jing
> Signed-off-by: Ulf Hansson
> ---
> MAINTAINERS | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3e5a5d263f29..b43e563b4c95 100644
> --- a/MAINTAINERS
> +++
From: Bartosz Golaszewski
Resending again - this time with tags collected.
===
I've previously sent these patches separately. I still don't see them
in next and I don't know what the policy is for picking up uml patches
but I thought I'd resend them rebased together on top of v5.1-rc4.
From: Bartosz Golaszewski
The buf variable is unused. Remove it.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Anton Ivanov
Acked-by: Anton Ivanov
---
arch/um/kernel/skas/uaccess.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/um/kernel/skas/uaccess.c
From: Bartosz Golaszewski
Setting a chip for an interrupt marks it as allocated. Since UM doesn't
support dynamic interrupt numbers (yet), it means we cannot simply
increase NR_IRQS and then use the free irqs between LAST_IRQ and NR_IRQS
with gpio-mockup or iio testing drivers as
From: Bartosz Golaszewski
When defined as macro, the mm argument is unused and subsequently the
variable passed as mm is considered unused by the compiler. This fixes
a build warning.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Geert Uytterhoeven
Reviewed-by: Anton Ivanov
Acked-by: Anton
From: Bartosz Golaszewski
While the affected code is run in user-mode, the build still warns
about it. Convert all uses of VLA to dynamic allocations.
Signed-off-by: Bartosz Golaszewski
---
arch/um/os-Linux/umid.c | 36 +++-
1 file changed, 27 insertions(+), 9
Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes ThumshirnSUSE Labs Filesystems
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG
On Sun, 7 Apr 2019 at 05:13, Nicholas Mc Guire wrote:
>
> Providing a range for usleep_range() allows the hrtimer subsystem to
> coalesce timers - the delay is runtime configurable so a factor 2
> is taken to provide the range.
>
> Signed-off-by: Nicholas Mc Guire
> ---
>
> Problem located with
On Wed, Apr 10, 2019 at 10:04:50PM +0800, Yue Haibing wrote:
> From: YueHaibing
>
> Fix sparse warning:
>
> drivers/memory/tegra/tegra20.c:277:33: warning:
> symbol 'terga20_mc_reset_ops' was not declared. Should it be static?
>
> Reported-by: Hulk Robot
> Signed-off-by: YueHaibing
> ---
>
Since no single Mediatek chip use code for PINCTRL_MTK and code for
PINCTRL_MTK_MOORE/PINCTRL_MTK_PARIS simultaneously, it is better to use
different config to determine if related code will be built or not on
building non-generic kernel.
Add kernel config PINCTRL_MTK_V2 selected by either
We use $(LD) to link vmlinux, modules, decompressors, etc.
VDSO is the only exceptional case where $(CC) is used as the linker
driver, but I do not know why we need to do so. VDSO uses a special
linker script, and does not link standard libraries at all.
I changed the Makefile to use $(LD)
We use $(LD) to link vmlinux, modules, decompressors, etc.
VDSO is the only exceptional case where $(CC) is used as the linker
driver, but I do not know why we need to do so. VDSO uses a special
linker script, and does not link standard libraries at all.
I changed the Makefile to use $(LD)
From: Bartosz Golaszewski
Instead of directly using the vbus GPIO we should model it as a fixed
regulator. Add all necessary fix-ups for the regulator to be registered
and configure the vbus GPIO as its enable pin.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
There's no reason to have a separate variable to keep track of the
regulator state. The regulator core already does that. Remove
reg_enabled from struct da8xx_ohci_hcd.
Signed-off-by: Bartosz Golaszewski
Acked-by: Alan Stern
---
drivers/usb/host/ohci-da8xx.c | 8
On Thu, 11 Apr 2019 17:24:09 +0800
masonccy...@mxic.com.tw wrote:
> Hi Boris,
>
>
> > > > > > Subject
> > > > > >
> > > > > > Re: [PATCH] mtd: rawnand: Add Macronix NAND read retry and
> > > randomizer
> > > > > support
> > > > > >
> > > > > > On Tue, 9 Apr 2019 17:35:39 +0800
> >
On Thu, Apr 04, 2019 at 04:36:07PM +0530, Kishon Vijay Abraham I wrote:
> Hi Lorenzo,
>
> This series includes a couple of patches, one which fixes
> inadvertent removal of pcitest.sh from kernel repo when
> doing a "clean" and other lets the user use 'h' option to
> display the list of options
seems subject is incomplete in v2, v3 posted:
https://lore.kernel.org/patchwork/patch/1060505/
Thanks!
- Wladislav
On 10.04.2019 11:23, Wiebe, Wladislav (Nokia - DE/Ulm) wrote:
> Commit ea837f1c0503 ("kbuild: make modpost processing configurable")
> was intended to give KBUILD_MODPOST_WARN
Le 11/04/2019 à 10:52, Rolf Eike Beer a écrit :
> Am Donnerstag, 11. April 2019, 10:39:40 CEST schrieb Nicolas Dichtel:
>> In case of cross-compilation, there may be two pkg-config tools, one for
>> the host and one for the target. Enable to override the default name.
>>
>> Fixes: 056d28d135bc
Commit ea837f1c0503 ("kbuild: make modpost processing configurable")
was intended to give KBUILD_MODPOST_WARN flexibility to be configurable.
Right now KBUILD_MODPOST_WARN gets just ignored when KBUILD_EXTMOD is
set which happens per default when building modules out of the tree.
This change
These were found with smatch, and then generalized when applicable.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/lapic.c | 4 +++-
include/linux/kvm_host.h | 10 ++
virt/kvm/irqchip.c | 5 +++--
virt/kvm/kvm_main.c | 6 --
4 files changed, 16 insertions(+), 9
_I hope I did this right... Apologies if I made a procedure mistake._
The following changes since commit
582549e3fbe137eb6ce9be591aca25ca36b4:
Merge tag 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2019-04-10
09:39:04 -1000)
are available in the Git repository
On Thu, Apr 11, 2019 at 11:05:41AM +0800, Aaron Lu wrote:
> On Wed, Apr 10, 2019 at 04:44:18PM +0200, Peter Zijlstra wrote:
> > When core_cookie==0 we shouldn't schedule the other siblings at all.
>
> Not even with another untagged task?
>
> I was thinking to leave host side tasks untagged, like
On Wed, Apr 10, 2019 at 11:50:51AM -0400, Joe Lawrence wrote:
> -clean: archclean vmlinuxclean
> +klpclean:
> + $(Q) rm -f $(objtree)/Symbols.list
nit: $(SLIST) can be used here.
> +clean: archclean vmlinuxclean klpclean
>
> # mrproper - Delete all generated files, including .config
> #
On Wed, Apr 10, 2019 at 10:33:20PM -0500, Josh Poimboeuf wrote:
> On Wed, Apr 10, 2019 at 12:28:34PM +0200, Thomas Gleixner wrote:
> > +struct stack_trace {
> > + unsigned int nr_entries, max_entries;
> > + unsigned long *entries;
> > + int skip; /* input argument: How many entries to
On 11.04.19 10:41, Michal Hocko wrote:
> On Wed 10-04-19 12:14:55, David Hildenbrand wrote:
>> While current node handling is probably terribly broken for memory block
>> devices that span several nodes (only possible when added during boot,
>> and something like that should be blocked
On Wed, Apr 10, 2019 at 02:54:16PM +0800, Chunfeng Yun wrote:
> Use devm_clk_get_optional() to get optional clock
>
> Cc: Ryder Lee
> Cc: Honghui Zhang
> Signed-off-by: Chunfeng Yun
> Acked-by: Ryder Lee
> Acked-by: Honghui Zhang
> ---
> v3: add Acked-by Ryder and Honghui
> ---
>
On Wed, Apr 10, 2019 at 11:57:09AM -0700, kan.li...@linux.intel.com wrote:
> +static struct event_constraint *
> +tnt_get_event_constraints(struct cpu_hw_events *cpuc, int idx,
> + struct perf_event *event)
That 'tnt' still cracks me up, I keep seeing explosions.
> +{
> +
On 10 April 2019 17:39, Hans de Goede wrote:
> On 10-04-19 18:14, Adam Thomson wrote:
> > On 10 April 2019 16:45, Hans de Goede wrote:
> >
> >> Hi Kyle,
> >>
> >> On 10-04-19 14:49, Kyle Tso wrote:
> >>> On Wed, Apr 10, 2019 at 6:32 PM Adam Thomson
> >>> wrote:
>
> On 09 April 2019
From: Paolo Bonzini
> Sent: 10 April 2019 18:09
> On 10/04/19 16:57, Sean Christopherson wrote:
> > On Wed, Apr 10, 2019 at 12:55:53PM +, David Laight wrote:
> >> From: Paolo Bonzini
> >>> Sent: 10 April 2019 10:55
> >>>
> >>> This check will soon be done on every nested vmentry and vmexit,
>
Hi Christoph,
On Thu, 11 Apr 2019 at 09:10, Christoph Hellwig wrote:
>
> Just like we do for all other block drivers. Especially as the limit
> imposed at the moment might be way to pessimistic for iommus.
I would appreciate some information in the changelog, as it's quite
unclear of what this
On Wed, Apr 10, 2019 at 09:47:20PM +0200, Peter Zijlstra wrote:
> Sure, those are actually forced 0 with the existing thing.
>
> I'll go fold smething like back in. Thanks!
> > @@ -3472,7 +3475,7 @@ icl_get_event_constraints(struct cpu_hw_events *cpuc,
> > int idx,
> > * Force
Add a serial driver for the SiFive UART, found on SiFive FU540 devices
(among others).
The underlying serial IP block is relatively basic, and currently does
not support serial break detection. Further information on the IP
block can be found in the documentation and Chisel sources:
Add DT binding documentation for the Linux driver for the SiFive
asynchronous serial IP block.
This revision incorporates changes based on feedback from Rob
Herring .
Signed-off-by: Paul Walmsley
Signed-off-by: Paul Walmsley
Cc: linux-ser...@vger.kernel.org
Cc: devicet...@vger.kernel.org
Cc:
501 - 600 of 699 matches
Mail list logo
