On Wed, 24 May 2017, Tobias Klauser wrote:
> struct irq_domain_ops is not modified, so it can be made const.
>
> Signed-off-by: Tobias Klauser
> ---
> drivers/mfd/fsl-imx25-tsadc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
> diff --git
A NVMe Identify NS command with a CNS value of '3' is expecting a list
of Namespace Identification Descriptor structures to be returned to
the host for the namespace requested in the namespace identify
command.
This Namespace Identification Descriptor structure consists of the
type of the
If a target identifies itself as NVMe 1.3 compliant, try to get the
list of Namespace Identification Descriptors and populate the UUID,
NGUID and EUI64 fileds in the NVMe namespace structure with these
values.
Signed-off-by: Johannes Thumshirn
---
drivers/nvme/host/core.c |
On 05/30/2017 10:08 AM, Johannes Thumshirn wrote:
> Now that we can configure a namespace's EUI-64, report it back to the
> host in an 'Identify Namespace' command reply.
>
> Signed-off-by: Johannes Thumshirn
> ---
> drivers/nvme/target/admin-cmd.c | 1 +
> 1 file changed, 1
On 30/05/17 09:15, Dmitry Vyukov wrote:
> On Tue, May 30, 2017 at 9:58 AM, Vladimir Murzin
> wrote:
>> On 29/05/17 16:29, Dmitry Vyukov wrote:
>>> I have an alternative proposal. It should be conceptually simpler and
>>> also less arch-dependent. But I don't know if I
On 05/30/2017 10:08 AM, Johannes Thumshirn wrote:
> Now that we have a way for getting the UUID from a target, provide it
> to userspace as well.
>
> Unfortunately there is already a sysfs attribute called UUID which is
> a misnomer as it holds the NGUID value. So instead of creating yet
>
Hello,
A few more comments :)
On Mon, 29 May 2017 16:45:37 +0200, Mylène Josserand wrote:
> +struct cyttsp5 {
> + struct device *dev;
> + struct mutex system_lock;
> + struct mutex btn_lock;
> + struct mutex mt_lock;
Three mutexes for such a driver is probably excessive,
Hi Andreas,
On Mon, 2017-05-29 at 15:07 +0200, Andreas Färber wrote:
[...]
> > Thank you, I have the same patch queued already.
>
> Is your tree not integrated into linux-next? If so, please send Stephen
> Rothwell an email to have that fixed.
Fixed, sorry for the duplicated effort.
regards
Dear fellow Maintainers,
Enjoy!
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
tags/ib-mfd-gpio-thermal-x86-v4.13
The watchdog framework takes care of feeding a hardware watchdog until
userspace opens /dev/watchdogN. If that never happens for some reason
(buggy init script, corrupt root filesystem or whatnot) but the kernel
itself is fine, the machine stays up indefinitely. This patch allows
setting an upper
This allows setting a default value for the watchdog.open_timeout
commandline parameter via Kconfig.
Some BSPs allow remote updating of the kernel image and root file
system, but updating the bootloader requires physical access. Hence, if
one has a firmware update that requires relaxing the
Indicate the error number and make the message a bit more elaborate.
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-mockup.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpio-mockup.c b/drivers/gpio/gpio-mockup.c
index
When the requested number of GPIO lines is 0, return -EINVAL, not
-1 which is -EPERM.
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-mockup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-mockup.c b/drivers/gpio/gpio-mockup.c
With "SPI_MASTER=y && I2C=m", we can build mcp23s08 as a built-in driver,
which then results in a link failure:
drivers/pinctrl/built-in.o: In function `mcp23s08_probe_one.isra.0':
:(.text+0x7910): undefined reference to `__devm_regmap_init_i2c'
drivers/pinctrl/built-in.o: In function
On Fri, 2017-05-12 at 03:58:10 UTC, Andrew Jeffery wrote:
> Experiments with the netperf benchmark indicated that the size selecting
> VMX-based copies in __copy_tofrom_user_power7() was suboptimal on POWER8.
> Measurements showed that parity was in the neighbourhood of 3328 bytes,
> rather than
On Mon, 2017-05-15 at 13:07:52 UTC, Ivan Mikhaylov wrote:
> Add a device tree for fsp2 board (476 based).
>
> Signed-off-by: Ivan Mikhaylov
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9eec6cb142bddd35268c7c59b6c81b
cheers
This commit modifies the Marvell EBU Armada 7K and 8K Device Tree files
to describe the ICU and GICP units, and use ICU interrupts for all
devices in the CP110 blocks.
Signed-off-by: Thomas Petazzoni
---
arch/arm64/boot/dts/marvell/armada-ap806.dtsi |
This commit modifies the Marvell EBU Armada 7K and 8K Device Tree files
to describe the ICU and GICP units, and use ICU interrupts for all
devices in the CP110 blocks.
Signed-off-by: Thomas Petazzoni
---
arch/arm64/boot/dts/marvell/armada-ap806.dtsi |
On Wed, 24 May 2017, Mark Brown wrote:
> On Wed, May 24, 2017 at 09:32:43AM +0100, Lee Jones wrote:
>
> > Plan is to push this through the MFD tree.
>
> Great, thanks.
Just taking a look at this now. It looks like the dependency:
656211b1dfb9 mfd: Add support for DA9061
... is now in
This commit enables the newly introduced Marvell GICP and ICUs driver
for the 64-bit Marvell EBU platforms.
Signed-off-by: Thomas Petazzoni
---
arch/arm64/Kconfig.platforms | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms
Hi Eduardo,
Thank you for your comment.
On Mon, 29 May 2017 09:30:09 -0700 Eduardo Valentin wrote:
> On Mon, May 29, 2017 at 06:15:44PM +0900, Kunihiko Hayashi wrote:
> > Add nodes of thermal monitor and thermal zone for UniPhier PXs2 SoC.
> > The thermal monitor is
On 30 May 2017 at 09:16, Lee Jones wrote:
> On Mon, 29 May 2017, Ulf Hansson wrote:
>
>> On 28 May 2017 at 11:30, Wolfram Sang
>> wrote:
>> > It is 'R-Car', not 'RCar'. No code or binding changes, only descriptive
>> > text.
>> >
>> >
On Tue, May 30, 2017 at 10:08:18AM +0200, Johannes Thumshirn wrote:
> Add the EUI-64 field from the NVMe Namespace Identification Descriptor
> to the nvmet_ns structure and allow it's population via configfs.
Is there any good use case for bothering with this identifier that's
too short to
On Sun, May 28, 2017 at 01:31:09PM -0700, Stephane Eranian wrote:
> Ultimately, I would like to see the watchdog move out of the PMU. That
> is the only sensible solution.
> You just need a resource able to interrupt on NMI or you handle
> interrupt masking in software as has
> been proposed on
On Mon, 29 May 2017, Benjamin Gaignard wrote:
> Use devm_of_platform_populate() to be sure that of_platform_depopulate
> is called when removing the driver.
>
> Signed-off-by: Benjamin Gaignard
>
> CC: Lee Jones
> CC: Kukjin Kim
On Mon, 29 May 2017, Benjamin Gaignard wrote:
> Use devm_of_platform_populate() to be sure that of_platform_depopulate
> is called when removing the driver.
>
> Signed-off-by: Benjamin Gaignard
>
> CC: Lee Jones
> CC:
On Mon, 29 May 2017, Benjamin Gaignard wrote:
> Use devm_of_platform_populate() instead of of_platform_populate()
> and suppress stm32_timers_remove() which become useless.
>
> Signed-off-by: Benjamin Gaignard
>
> CC: Lee Jones
> CC:
On Mon, 29 May 2017, Benjamin Gaignard wrote:
> Use devm_of_platform_populate() to be sure that of_platform_depopulate
> is called when removing the driver.
>
> Signed-off-by: Benjamin Gaignard
>
> CC: Lee Jones
> CC:
On Mon, 29 May 2017, Benjamin Gaignard wrote:
> Use devm_of_platform_populate() to be sure that of_platform_depopulate
> is called when removing the driver.
>
> Signed-off-by: Benjamin Gaignard
>
> CC: Tony Lindgren
> CC: Lee Jones
Christoph Hellwig wrote:
> This reverts commit ff548773106ec7f8031bc6172e0234bd2a02c19c.
>
> The V1 uuid intrepreatation in struct form isn't really useful to the
> rest of the kernel, and not really compatible to it either, so move it
> back to AFS instead of polluting the global
From: Colin Ian King
We need to include pcm_local.h to clean up some smatch warnings:
symbol 'snd_pcm_timer_done' was not declared. Should it be static?
symbol 'snd_pcm_timer_init' was not declared. Should it be static?
symbol 'snd_pcm_timer_resolution_change' was not
This adds the bindings documentation for a basic single-register reset
controller.
The bindings describe a single 32-bit register that contains up to 32
reset lines, each deasserted by clearing the appropriate bit in the
register. Optionally a property can be provided that changes this
behaviour
This driver is a basic single-register reset controller driver that
supports clearing a single bit in a register.
Signed-off-by: Joel Stanley
---
v2:
- Support assert-on-clear dt property
- Depend on OF and MFD_SYSCON
Signed-off-by: Joel Stanley
---
Hello,
This is v2 of the basic reset controller, which addresses the points that
Philipp made. See the individual patches for changelogs. The original cover
letter follows:
In the Aspeed SoCs we have some reset registers spread out in various parts of
the soc: in the system controller IP, as
Fixed block comments across whole ccree driver
Version #1 has some trailing white space issue in a few patches
Derek Robson (27):
Drivers: ccree: ssi_sysfs.h - align block comments
Drivers: ccree: ssi_sysfs.c - align block comments
Drivers: ccree: ssi_request_mgr.h - align block comments
MMU contains invalid mapping which wasn't flushed and new mapping
is using the same addresses as previous one. That's why TLB miss is not
happening to get new correct TLB entry and MMU points to incorrect area.
This is replicatable when large files(256MB and more) are copied and
checked.
On Tue, 16 May 2017 14:19:47 +0530
"Gautham R. Shenoy" wrote:
> From: "Gautham R. Shenoy"
>
> On Power9 DD1 due to a hardware bug the Power-Saving Level Status
> field (PLS) of the PSSCR for a thread waking up from a deep state can
>
On Thu, May 25, 2017 at 03:19:13PM +0100, Jose Abreu wrote:
> Add a new helper to call crtc->mode_valid, connector->mode_valid
> and encoder->mode_valid callbacks.
>
> Suggested-by: Ville Syrjälä
> Signed-off-by: Jose Abreu
> Reviewed-by:
Some debug output whose log level is set 1 flooded the log.
Their log level is lowered to find the important log easily.
Signed-off-by: Hirokazu Honda
---
drivers/media/v4l2-core/videobuf2-core.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
On 05/30/2017 10:08 AM, Johannes Thumshirn wrote:
> Add the UUID field from the NVMe Namespace Identification Descriptor
> to the nvmet_ns structure and allow it's population via configfs.
>
> Signed-off-by: Johannes Thumshirn
> ---
> drivers/nvme/target/configfs.c | 48
>
On 05/30/2017 10:08 AM, Johannes Thumshirn wrote:
> Add the EUI-64 field from the NVMe Namespace Identification Descriptor
> to the nvmet_ns structure and allow it's population via configfs.
>
> Signed-off-by: Johannes Thumshirn
> ---
> drivers/nvme/target/configfs.c | 48
>
Alexey Budankov writes:
> On 29.05.2017 15:03, Alexander Shishkin wrote:
>> Alexey Budankov writes:
>>
>> Here (above the function) you could include a comment describing what
>> happens when this is called, locking
On Sat, 27 May 2017 16:46:15 +0200,
Bhumika Goyal wrote:
>
> Declare snd_kcontrol_new structures as const as they are only passed an
> argument to the function snd_ctl_new1. This argument is of type const,
> so snd_kcontrol_new structures having this property can be made const.
> Done using
On 30/05/2017 09:44, Linus Walleij wrote:
> On Sun, May 28, 2017 at 8:27 PM, Daniel Lezcano
> wrote:
>> On 28/05/2017 15:59, Linus Walleij wrote:
>>> On Tue, May 16, 2017 at 9:58 AM, Andrew Jeffery wrote:
>>>
Also clean up space-before-tab issues
For future reference, when submitting a patch-set, you really should
provide a cover letter ([PATCH 00/XX]).
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
On Tue, 23 May 2017, Hans de Goede wrote:
> Add mfd driver for Intel CHT Whiskey Cove PMIC, based on various non
> upstreamed CHT Whiskey Cove PMIC patches.
>
> This is a somewhat minimal version which adds irqchip support and cells
> for: ACPI PMIC opregion support, the i2c-controller driving
Currently we ignore the last odd range value, since each chip is
described by two values. Be more strict and require the user to
pass an even number of ranges.
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-mockup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 30/05/17 09:49, Dmitry Vyukov wrote:
> On Tue, May 30, 2017 at 10:40 AM, Vladimir Murzin
> wrote:
>> On 30/05/17 09:31, Vladimir Murzin wrote:
>>> [This sender failed our fraud detection checks and may not be who they
>>> appear to be. Learn about spoofing at
On Tue, May 30, 2017 at 09:29:44AM +0200, Neil Armstrong wrote:
> On 05/25/2017 04:19 PM, Jose Abreu wrote:
> > Now that we have a callback to check if crtc supports a given mode
> > we can use it in malidp so that we restrict the number of probbed
> > modes to the ones we can actually display.
>
On Fri, May 26, 2017 at 01:56:01PM -0700, Andi Kleen wrote:
> I have a need for read group reads for inherited events.
>
> It looks like the perf group read code already has all the code
> to handle inheritance, __perf_read_group_add walks
> the children list and adds them all up.
>
>4409
On Tue, May 30, 2017 at 11:39 AM, Vladimir Murzin
wrote:
>
> On 30/05/17 10:26, Dmitry Vyukov wrote:
> > On Tue, May 30, 2017 at 11:08 AM, Vladimir Murzin
> > wrote:
> >>> wrote:
> On 30/05/17 09:31, Vladimir Murzin
On Tue, 2017-05-30 at 11:21 +0200, Arnd Bergmann wrote:
> This was left behind by a cleanup patch:
>
> drivers/gpio/gpiolib.c: In function
> 'gpiochip_irqchip_init_valid_mask':
> drivers/gpio/gpiolib.c:1474:6: error: unused variable 'i' [-
> Werror=unused-variable]
Right, thanks for it!
On 30/05/2017 00:48, Nick Desaulniers wrote:
> em_fxstor previously called fxstor_fixup. Both created instances of
> struct fxregs_state on the stack, which triggered the warning:
>
> arch/x86/kvm/emulate.c:4018:12: warning: stack frame size of 1080 bytes
> in function
> 'em_fxrstor'
Hi,
> This patch set adds the dma-buf support for intel GVT-g.
> dma-buf is a uniform mechanism to share DMA buffers across different
> devices and sub-systems.
> dma-buf for intel GVT-g is mainly used to share the vgpu's
> framebuffer
> to other users or sub-systems so they can use the dma-buf
On 5/24/2017 10:25 PM, Jarkko Sakkinen wrote:
On Wed, May 24, 2017 at 10:33:54AM -0700, Jarkko Sakkinen wrote:
On Mon, May 22, 2017 at 09:21:28AM +0200, Roberto Sassu wrote:
On 5/20/2017 3:22 PM, Jarkko Sakkinen wrote:
On Mon, May 15, 2017 at 04:22:22PM +0200, Roberto Sassu wrote:
On
Hi,
On 05/25/2017 07:49 PM, Jose Abreu wrote:
Now that we have a callback to check if bridge supports a given mode
we can use it in Synopsys Designware HDMI bridge so that we restrict
the number of probbed modes to the ones we can actually display.
Also, there is no need to use mode_fixup()
On Sat, 27 May 2017, Kees Cook wrote:
> On Sat, May 27, 2017 at 1:41 AM, Christoph Hellwig wrote:
> > On Fri, May 26, 2017 at 01:17:09PM -0700, Kees Cook wrote:
> >> The LSM initialization routines walk security_hook_heads as an array
> >> of struct list_head instead of via
An unknown change in the kernel headers caused a build regression
in an MTD partition driver:
In file included from drivers/mtd/bcm47xxpart.c:12:0:
include/linux/bcm47xx_nvram.h: In function 'bcm47xx_nvram_init_from_mem':
include/linux/bcm47xx_nvram.h:27:10: error: 'ENOTSUPP' undeclared (first
This driver is predominantly used by device tree systems, all
of which can deal with modern GPIO descriptors. The legacy
GPIO API is only used by one SH board so make the GPIO
descriptor the default way to deal with it.
As an intended side effect we do not need to look around in
the device tree
Hello,
On Tue, 30 May 2017 12:10:29 +0100, Marc Zyngier wrote:
> Thanks for that, looks pretty interesting. A couple of comments below.
Thanks again for the review!
> > +/* GICP registers */
> > +#define GICP_SETSPI_NSR_OFFSET 0x0
> > +#define GICP_CLRSPI_NSR_OFFSET 0x8
>
>
> >> I'll think about possible solutions, but I have no prior experience
> >> with the tty code. In the meantime syzkaller also hit a couple of
> >> other fun tty/pty bugs including a write/ioctl race that results in
> >> buffer overflow :-/
There are several of those, including some of that
From: Linu Cherian
Cavium ThunderX2 SMMU implementation doesn't support page 1 register space
and PAGE0_REGS_ONLY option is enabled as an errata workaround.
This option when turned on, replaces all page 1 offsets used for
EVTQ_PROD/CONS, PRIQ_PROD/CONS register access
Hi,
I've run into a problem using the fixed-factor clock on Raspberry Pi and I'd
like some advice before I submit a patch.
Some context: the aim is to use a standard UART and some external circuitry
as a MIDI interface. This would be straightforward except that Linux doesn't
recognise the
Look there are two problems here
1. TIOCSTI has users
2. You don't actually fix anything
The underlying problem is that if you give your tty handle to another
process which you don't trust you are screwed. It's fundamental to the
design of the Unix tty model and it's made worse in Linux by the
From: Geetha Sowjanya
Cavium ThunderX2 SMMU doesn't support MSI and also doesn't have unique irq
lines for gerror, eventq and cmdq-sync.
This patch addresses the issue by checking if any interrupt sources are
using same irq number, then they are registered as
On Tue, May 30, 2017 at 08:17:00AM -0400, Nicolas Pitre wrote:
> On Tue, 30 May 2017, Peter Zijlstra wrote:
>
> > On Mon, May 29, 2017 at 05:03:01PM -0400, Nicolas Pitre wrote:
> >
> > > @@ -1303,8 +1303,17 @@ config SCHED_AUTOGROUP
> > > desktop applications. Task group autogeneration is
From: Abhijeet Dharmapurikar
The system crashes due to bad access when reading from an non configured
peripheral and when writing to peripheral which is not owned by current
ee. This patch verifies ownership to avoid crashing on
write.
For reads, since the forward
This patch series add the support for pmic arbiter hardware v3 and v5
support along with the multiple bug fixes and code cleanup.
spmi_pmic_arb v3: Added 512 channel support.
spmi_pmic_arb v5: Register offset changes.
Multiple EEs can write to a single
Le 30/05/2017 à 12:50, Michael Ellerman a écrit :
Christophe Leroy writes:
...
Please tell me why.
Because of patch https://patchwork.ozlabs.org/patch/766777/ which
modifies patch_instruction() to use an alternative mapping.
Compilation fails on PPC32 because
On Tue, May 30, 2017 at 7:37 AM, Andrey Smirnov
wrote:
> Trying to load a serdev driver agains a tty port on i.MX6Q results in
> the following lockdep warning:
>
> kworker/u8:1/100 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
> (&(>files_lock)->rlock){+.+...}, at: []
Hi Richard,
On mar., mai 30 2017, Richard Genoud wrote:
> If more than one gpio bank has the "pwm" property, only one will be
> registered successfully, all the others will fail with:
> mvebu-gpio: probe of f1018140.gpio failed with error -17
>
> That's because in
On Tue, 2017-05-23 at 22:08 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Dennis Yang
>
> commit 583da48e388f472e8818d9bb60ef6a1d40ee9f9d upstream.
>
> When growing raid5
While trying to address the longstanding FIXME in the posix timer code
related to ignored signals, I stumbled over the following issue:
I blocked the signal of the timer, then installed the SIG_IGN handler,
created and started the timer. After a short sleep the timer has fired
several times, but
On Tue, May 30, 2017 at 02:24:36PM +0200, Michal Hocko wrote:
> On Mon 29-05-17 14:01:41, Roman Gushchin wrote:
> > Historically, PGSTEAL*/PGSCAN*/ALLOCSTALL counters were used to
> > account only for global reclaim events, memory cgroup targeted reclaim
> > was ignored.
> >
> > It doesn't make
> > Once again: patches not submitted to the mailing list simply don't
> > exist. So if you continue to keep those huge stack of patches out of
> > tree and don't submit your work more regularly, in fine-grained patches
> > series, the situation we have today will continue to happen.
>
> Given
On Tue, 30 May 2017, Keerthy wrote:
>
>
> On Tuesday 30 May 2017 02:53 PM, Lee Jones wrote:
> > On Tue, 23 May 2017, Keerthy wrote:
> >
> >> The LP87565 chip is a power management IC for Portable Navigation Systems
> >> and Tablet Computing devices. It contains the following components:
> >>
>
Hi Andy,
On 28.05.2017 01:28, Andy Shevchenko wrote:
> On Tue, May 9, 2017 at 11:19 AM, Claudiu Beznea
> wrote:
>> Extends PWM framework to support PWM dead-times.
>> The notions introduced are rising edge dead-time
>> and falling edge dead-time. These are useful
On 05/30/2017 11:30 AM, Christoph Hellwig wrote:
> Eww. This looks pretty sketchy and at least needs a good comment in
> the source. Maybe even a printk_ratelimited warning.
Comment sure, but do we really need a warning?
--
Johannes Thumshirn Storage
Hi Nicholas,
On Tue, May 30, 2017 at 03:56:12PM +1000, Nicholas Piggin wrote:
> On Tue, 16 May 2017 14:19:43 +0530
> "Gautham R. Shenoy" wrote:
>
> > From: "Gautham R. Shenoy"
> >
> > The lower 8 bits of core_idle_state_ptr tracks the number
On Sun, 28 May 2017, Tetsuo Handa wrote:
> can afford enabling". And we know that we cannot merge all security modules
> into mainline. Thus, allowing LKM-based LSM modules is inevitable.
Nope, it's not inevitable. The LSM API only caters to in-tree users.
I'm not sure why you persist against
On Tue, 2017-05-30 at 10:58 +0100, Colin King wrote:
> From: Colin Ian King
>
> We need to include pcm_local.h to clean up some smatch warnings:
>
> symbol 'snd_pcm_timer_done' was not declared. Should it be static?
> symbol 'snd_pcm_timer_init' was not declared.
On Tue, May 30, 2017 at 12:02 PM, Lee Jones wrote:
> On Tue, 23 May 2017, Hans de Goede wrote:
>> +static const struct i2c_device_id cht_wc_i2c_id[] = {
>> + { }
>> +};
>
> What's the point in this empty table?
This is artifact of I2C framework, otherwise if will be
Hello,I am confused about the index field in page structure,How kernel
can get all the virtual page frame in different process according to
the unique index??
clk_prepare_enable() can fail here and we must check its return value.
Signed-off-by: Arvind Yadav
---
drivers/input/touchscreen/s3c2410_ts.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/s3c2410_ts.c
On Tue, May 30, 2017 at 10:44:20AM +0100, Colin King wrote:
> From: Colin Ian King
>
> Fixes smatch warning: unused variable 'i' [-Wunused-variable]
>
> Signed-off-by: Colin Ian King
> ---
> drivers/gpio/gpiolib.c | 2 --
>
Hi Günter, Linus, Wim,
On Sun, May 14, 2017 at 5:55 AM, Guenter Roeck wrote:
> As requested by Wim:
>
> Please pull watchdog updates for Linux v4.12 from signed tag:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
> watchdog-for-linus-v4.12
>
>
This control enables the automatic volume control (AVC) of SGTL5000
using its DAP_AVC_CTRL register.
Signed-off-by: Richard Leitner
---
sound/soc/codecs/sgtl5000.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/soc/codecs/sgtl5000.c
WhiteEgret supports communication between kernel space and
user space using device driver.
This RFC provides the driver implementation.
Build the kernel with CONFIG_WHITEEGRET_DRIVER=y.
This option is defined automatically when
CONFIG_SECURITY_WHITEEGRET_DRIVER=y is set.
Then the loadable kernel
Hi Geert,
> Hi Günter, Linus, Wim,
>
> On Sun, May 14, 2017 at 5:55 AM, Guenter Roeck wrote:
> > As requested by Wim:
> >
> > Please pull watchdog updates for Linux v4.12 from signed tag:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
> >
Script that generated by '--gen-script' option contains an outdated
comment. It mentions about 'perf-trace-python' document while it has
renamed to 'perf-script-python'. This commit fixes the outdated
comment.
Signed-off-by: SeongJae Park
Fixes: 133dc4c39c57 ("perf: Rename
Default definition of trace_unhandled() has updated while
perf-script-python.txt has not updated. This commit updates the
document for that.
Signed-off-by: SeongJae Park
Fixes: c02514850d67b ("perf scripts python: Give field dict to unhandled
callback")
---
On Mon, May 29, 2017 at 04:24:03PM +0200, Daniel Bristot de Oliveira wrote:
> +/*
> + * Regarding the deadline, a task with implicit deadline has a relative
> + * deadline == relative period. A task with constrained deadline has a
> + * relative deadline <= relative period.
> + *
> + * Linux
Hyper-V host can suggest us to use hypercall for doing remote TLB flush,
this is supposed to work faster than IPIs.
Implementation details: to do HvFlushVirtualAddress{Space,List} hypercalls
we need to put the input somewhere in memory and we don't really want to
have memory allocation on each
Hyper-V hosts may support more than 64 vCPUs, we need to use
HVCALL_FLUSH_VIRTUAL_ADDRESS_SPACE_EX/LIST_EX hypercalls in this
case.
Signed-off-by: Vitaly Kuznetsov
Acked-by: K. Y. Srinivasan
---
Changes since v4:
- Use __set_bit(), minor code style
To support implementing remote TLB flushing on Hyper-V with a hypercall
we need to make vp_index available outside of vmbus module. Rename and
globalize.
Signed-off-by: Vitaly Kuznetsov
Acked-by: K. Y. Srinivasan
Tested-by: Simon Xiao
Add Hyper-V tracing subsystem and trace hyperv_mmu_flush_tlb_others().
Tracing is done the same way we do xen_mmu_flush_tlb_others().
Signed-off-by: Vitaly Kuznetsov
Acked-by: K. Y. Srinivasan
Tested-by: Simon Xiao
Tested-by:
Changes since v4:
- Get rid of union aliasing in the series [Andy Shevchenko]. We still use
it a lot across Hyper-V code and we should probably get rid of it
entirely.
- Code style changes [Andy Shevchenko].
- Use __set_bit(), lower/upper_32_bits where possible [Andy Shevchenko].
- Use 'A'
Max virtual processor will be needed for 'extended' hypercalls supporting
more than 64 vCPUs. While on it, unify on 'Hyper-V' in mshyperv.c as we
currently have a mix, report acquired misc features as well.
Signed-off-by: Vitaly Kuznetsov
Acked-by: K. Y. Srinivasan
Hyper-V supports 'fast' hypercalls when all parameters are passed through
registers. Implement an inline version of a simpliest of these calls:
hypercall with one 8-byte input and no output.
Signed-off-by: Vitaly Kuznetsov
Acked-by: K. Y. Srinivasan
---
Code is arch/x86/hyperv/ is only needed when CONFIG_HYPERV is set, the
'basic' support and detection lives in arch/x86/kernel/cpu/mshyperv.c
which is included when CONFIG_HYPERVISOR_GUEST is set.
Signed-off-by: Vitaly Kuznetsov
Acked-by: K. Y. Srinivasan
501 - 600 of 2166 matches
Mail list logo