XSAVES is a kernel-mode instruction. It offers a compacted format and
memory-write optimization. These patches fix known issues in the first
implementation. They are intended for discussion and getting feedback
before actually getting applied.
Patch 1, 2, and 4 are for converting between
On Fri, 2016-02-19 at 17:18 +, David Howells wrote:
> Here's a set of patches that cleans up the public key handling in the
> asymmetric key functions:
>
> (1) - (3) These are Tadeusz's RSA akcipher conversion.
Up to here, IMA-appraisal works properly.
Mimi
> (4) This removes all
CPUID function 0x0d, sub function (i, i > 1) returns in ecx[1] the
alignment requirement of component i when the compacted format is used.
If ecx[1] is 0, component i is located immediately following the preceding
component. If ecx[1] is 1, component i is located on the next 64-byte
boundary
Andi,
On Mon, 22 Feb 2016, Andi Kleen wrote:
> Thomas Gleixner writes:
>
> > Add the necessary exit functions so it can be built as a module.
>
> If you make it a module you also need to add MODULE_DEVICE_TABLE
> for the PCI IDs and also add x86_cpu_id tables/annotations
>
* John Ogness [160222 07:30]:
> Hi Tony,
>
> On 2016-02-11, Tony Lindgren wrote:
> >> At these speeds, nearly every DMA interrupt is accompanied by a
> >> spurious UART interrupt. So, sadly, the interrupts are doubled.
> >>
> >> It is on my TODO
On Mon, Feb 22, 2016 at 09:58:27AM +0100, Michael Hennerich wrote:
> On 11/19/2015 09:22 AM, Michael Hennerich wrote:
> >On 11/18/2015 05:16 PM, Dan Bogdan Nechita wrote:
> >>Currently writing the attributes with "echo" will result in comparing:
> >>"enabled\n" with "enabled\0" and attribute is
Hi Guenter,
Please don't do things like this to me:
On Sun, Feb 21, 2016 at 10:22 AM, Guenter Roeck wrote:
>
> Please pull hwmon fixes for Linux v4.5-rc6 from signed tag:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
> hwmon-v4.5-rc6
>
>
On Sun, Feb 21, 2016 at 08:06:17AM -0500, Gabriel L. Somlo wrote:
> > > +static void fw_cfg_io_cleanup(void)
> > > +{
> > > + if (fw_cfg_is_mmio) {
> > > + iounmap(fw_cfg_dev_base);
> > > + release_mem_region(fw_cfg_p_base, fw_cfg_p_size);
> > > + } else {
> > > +
On 2/22/2016 1:03 PM, Peter Seiderer wrote:
> Regulator stuff and pin configuration copied from imx6qdl-nitrogen6_max.dtsi
> and checked against Boundary Devices linux kernel tree ([1]).
>
> [1]
>
On Mon, Feb 22, 2016 at 5:48 PM, Troy Kisky
wrote:
> I'm ok with this patch, but a more correct fix would be to add a
> reset-gpios to usbh1 instead, as this is a reset pin for
> a usb hub. So if nobody else has a problem,
The problem is that such solution does
Moving around the Makefile for DSI caused a link error with
the main driver referring to a builtin module that has no
exported symbols:
drivers/gpu/built-in.o: In function `msm_drm_register':
:(.init.text+0x654): undefined reference to `msm_dsi_register'
This changes the DSI symbol to a
Moving around the Makefile for EDP caused a link error with
the main driver referring to a builtin module that has no
exported symbols:
drivers/gpu/built-in.o: In function `msm_drm_register':
:(.init.text+0x654): undefined reference to `msm_edp_register'
This changes the EDP symbol to a
Guennadi Liakhovetski writes:
> On Sun, 21 Feb 2016, Robert Jarzmik wrote:
> Please, have a look at
> http://git.linuxtv.org/gliakhovetski/v4l-dvb.git/log/?h=for-4.6-2
> If all is good there, no need for a v6
Thanks for fixing the *_dma_irq() mess, and sorry for that.
On Fri, Feb 19, 2016 at 08:01:17PM -0600, John Dahlstrom wrote:
> On Fri, 19 Feb 2016, Darren Hart wrote:
>
> >See stable_kernel_rules.txt for how to specify relevant versions. I'm curious
> >why there is a gap from 3.18 to 4.1.
> >
> >What you probably meant was:
> >
> >Cc:
On Mon, Feb 22, 2016 at 10:33 AM, Christopher Hall
wrote:
> I just sent another patchset (v8). I corrected the comment problems pointed
> out by Richard Cochran. I also changed the arch/x86 code to use "non-stop"
> TSC rather than "invariant" TSC. They are *exactly*
On Sun, Feb 21, 2016 at 2:08 PM, Alasdair G Kergon wrote:
> On Sat, Feb 20, 2016 at 10:13:49AM -0800, Kees Cook wrote:
>> This is a resurrection of a patch series from a few years back, first
>> brought to the dm maintainers in 2010. It creates a way to define dm
>> devices on
Thomas Gleixner writes:
> +
> + if (c->cpuid_level >= 0x0001) {
> + u32 eax, ebx, ecx, edx;
> +
> + cpuid(0x0001, , , , );
Use cpuid_edx()
> + /*
> + * If HTT (EDX[28]) is set EBX[16:23] contain the number of
> +
On Mon, Feb 22, 2016 at 7:09 AM, Pavel Machek wrote:
> Hi!
>
>> Every time I initiate a suspend (systemctl suspend) the machine hangs
>> at resume unless I unload the jme driver.
>
> It seems to have some kind of suspend/resume support. ... and it is
> rather complex.
>
>
Am 2016-02-22 um 15:12 schrieb Takashi Iwai:
> On Mon, 22 Feb 2016 15:02:56 +0100,
> Martin Kepplinger wrote:
>>> And how about my questions in the previous mail? Does
>>> i915_audio_component_get_eld() is called and returns 0?
>>> And is monitor_present set true or false?
>>
>>
Keep init_fpstate.xsave.header.xfeatures as zero for init optimization.
This is important for init optimization that is implemented in processor.
If a bit corresponding to an xstate in xstate_bv is 0, it means the
xstate is in init status and will not be read from memory to the processor
during
User space uses standard format xsave area. fpstate in signal frame should
have standard format size.
To explicitly distinguish between xstate size in kernel space and the one
in user space, we rename xstate_size to kernel_xstate_size. This patch is
not fixing a bug. It just makes kernel code
On 02/22/2016 10:59 AM, Yu-cheng Yu wrote:
> This actually does not apply to XSAVES as XSAVES uses optimization. After
> init, all components are in INIT and not MODIFIED state and will not be
> saved. There is no need of setting xcomp_bv except for bit 63 to indicate
> a compacted format.
I look
On Mon, Feb 22, 2016 at 12:00:02PM -0800, Dave Hansen wrote:
> On 02/22/2016 11:00 AM, Yu-cheng Yu wrote:
> > + if (xsave->header.xfeatures & XFEATURE_MASK_SUPERVISOR)
> > + xsave->header.xfeatures = xfeatures | XFEATURE_MASK_SUPERVISOR;
> > + else
> > +
Sparse complains here because we dropped the __iomem annotation
when casting the aligned address. Add __iomem back so that sparse
stops complaining.
Cc: Yoshinori Sato
Cc:
Signed-off-by: Stephen Boyd
---
On Mon, Feb 22, 2016 at 6:02 AM, Ard Biesheuvel
wrote:
> Currently, the memremap code serves MEMREMAP_WB mappings directly from
> the kernel direct mapping, unless the region is in high memory, in which
> case it falls back to using ioremap_cache(). However, the
On 22 February 2016 at 20:05, Dan Williams wrote:
> On Mon, Feb 22, 2016 at 6:02 AM, Ard Biesheuvel
> wrote:
>> Currently, the memremap code serves MEMREMAP_WB mappings directly from
>> the kernel direct mapping, unless the region is in high
On Mon, Feb 22, 2016 at 2:10 AM, Thomas Petazzoni
wrote:
> Hello,
>
> FWIW, you're replying to the v1 of this patch, while v2 and v3 have
> already been posted, and v3 has already been merged by the irqchip
> maintainers:
>
>
>
We know "len" is not zero because we tested for that at the beginning of
the function so this test can be removed.
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/gdm72xx/gdm_wimax.c
b/drivers/staging/gdm72xx/gdm_wimax.c
index 6d647d6..09bf64e 100644
---
"size" here should be unsigned, otherwise we might end up trying to copy
negative bytes in gdm_wimax_ioctl_get_data() resulting in an information
leak.
Reported-by: Alan Cox
Signed-off-by: Dan Carpenter
diff --git
On Wed, Feb 17, 2016 at 02:19:26PM +0100, Manfred Schlaegl wrote:
> If the pwm can sleep defer actions to it using a worker.
> A similar approach was used in leds-pwm (c971ff185)
>
> Trigger:
> On a Freescale i.MX53 based board we ran into "BUG: scheduling while
> atomic" because
Regulator stuff and pin configuration copied from imx6qdl-nitrogen6_max.dtsi
and checked against Boundary Devices linux kernel tree ([1]).
[1]
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.14.28_1.0.0_ga/arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi
Signed-off-by: Peter Seiderer
On 02/19/2016 09:18 AM, David Howells wrote:
> Move the RSA EMSA-PKCS1-v1_5 encoding from the asymmetric-key public_key
> subtype to the rsa crypto module. This means that the public_key subtype
> no longer has any dependencies on public key type.
>
> To make this work, I've made the following
From: Dinh Nguyen
There are some Arria10 clocks of type "altr,socfpga-a10-perip-clk" that can
have multiple parents. Fix up the __socfpga_periph_init() to call
of_clk_parent_fill() that will return the appropriate number of parents.
Also, update
On Mon, Feb 22, 2016 at 11:06:56AM -, Thomas Gleixner wrote:
> The Knights Landings support added the events and the detection case, but then
> returns 0 without actually initializing the driver.
>
> Fixes: 3a2a7797326a4 "perf/x86/intel/rapl: Add support for Knights Landing
> (KNL)"
>
On 02/22/2016 11:15 AM, Yang Shi wrote:
On 2/22/2016 4:43 AM, Aaro Koskinen wrote:
Hi,
On Fri, Feb 19, 2016 at 05:12:41PM -0800, Yang Shi wrote:
I tried to boot 4.5-rc4 kernel on my CN6880 board, but it is failed at
booting up secondary cores. The error is:
With v4.5-rc5, EBB6800 is booting
Russell King recently pointed out a bug in the clk-gpio code
where it fails to register the clk if of_clk_get_parent_count()
returns an error because the "clocks" property isn't present in
the DT node. If we're trying to count parents from DT we'd like
to know the count, not if there is a "clocks"
Change the types here to unsigned int instead of int and update
the checks for == 0 instead < 1 to be more explicit about what's
going on now that of_clk_get_parent_count() has changed return
types.
Cc: Tero Kristo
Signed-off-by: Stephen Boyd
---
The check for < 0 is impossible now that
of_clk_get_parent_count() returns an unsigned int. Simplify the
code and update the types.
Cc: Felipe Balbi
Cc:
Signed-off-by: Stephen Boyd
---
Please ack so this can go through clk tree
ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure
as follows.
- Valid Fields, Manufacturing Location, and Manufacturing Date
are added from reserved range. No change in the structure size.
- IDs defined as SPD values are arrays of bytes. The spec
clarified that they need to
Update the test code that initializes SPD IDs of NFIT control
region structures. nfit_set_spd_id() is added to handle
initialization of the SPD IDs, which are arrays of bytes.
Signed-off-by: Toshi Kani
Cc: Dan Williams
Cc: Rafael J. Wysocki
ACPI 6.1, section 5.2.25.9, defines an identifier for an NVDIMM.
Change the NFIT driver to create read-only "id" file under NVDIMM's
nfit directory of sysfs, which shows the NVDIMM ID.
Signed-off-by: Toshi Kani
Cc: Rafael J. Wysocki
Cc: Dan Williams
ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure
as follows.
- Valid Fields, Manufacturing Location, and Manufacturing Date
are added from reserved range. No change in the structure size.
- IDs defined as SPD values are arrays of bytes. The spec
clarified that they need to
The GEM code is used by dsi, so it can't be part of
the main module. This exports all functions that are called
by other code, and puts it into the helper module.
Signed-off-by: Arnd Bergmann
---
drivers/gpu/drm/msm/Makefile | 3 +--
drivers/gpu/drm/msm/msm_gem.c | 29
On Mon, Feb 22, 2016 at 12:11:48PM -0700, Jason Gunthorpe wrote:
> On Mon, Feb 22, 2016 at 09:08:28PM +0200, Jarkko Sakkinen wrote:
> > On Mon, Feb 22, 2016 at 10:52:45AM -0700, Jason Gunthorpe wrote:
> > > On Mon, Feb 22, 2016 at 04:50:23PM +0200, Jarkko Sakkinen wrote:
> > >
> > > > I already
The fsl-dcu driver copies a drm_mode_config object to its
stack but then only accesses a single member (dpms_property)
once. The data structure is large enough to trigger a warning
about the amount of kernel stack being used:
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_rgb.c: In function
On Mon, Feb 22, 2016 at 10:52:45AM -0700, Jason Gunthorpe wrote:
> On Mon, Feb 22, 2016 at 04:50:23PM +0200, Jarkko Sakkinen wrote:
>
> > I already pushed a fix to my master for this issue:
> >
> > https://github.com/jsakkine/linux-tpmdd/commit/6386544ad7bceb3d0248b85da29d4d99eebe9161
>
> The
On Friday 02/19 at 07:14 -0600, Corey Minyard wrote:
> On 02/19/2016 12:41 AM, Calvin Owens wrote:
> >Hello,
> >
> >I've got a few boxes that are leaking memory in handle_new_recv_msgs()
> >in ipmi_msghandler. AFAICS this is intentional, there's even an explicit
> >counter that tracks the number
* Nishanth Menon [160222 08:51]:
> Add EEPROM at 0x50 that describes the board configuration.
> This is useful for userspace programs that may need to check board
> revision and other similar information.
>
> Signed-off-by: Nishanth Menon
> ---
>
These warnings still seem to be present with DP MST configurations. They
don't actually indicate any impending doom, so we may as well use
I915_STATE_WARN_ON() here to help quiet things down a little bit for
distro kernel users.
Signed-off-by: Lyude
---
If nlh->nlmsg_len is less than ND_IFINDEX_LEN we end up trying to memcpy
a negative size. I also re-ordered slighty the condition to make it
more uniform.
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/gdm72xx/netlink_k.c
+++ Andy Shevchenko [22/02/16 11:27 +0200]:
On Fri, 2016-02-19 at 20:20 -0500, Jessica Yu wrote:
Hi,
This patch adds support for the '%[' conversion specifier for
sscanf().
Since functions that calculate substring lengths based on accepted or
rejected characters already exist in the kernel
On 2/22/2016 11:41 AM, Scott Branden wrote:
My comments below
On 16-02-22 11:36 AM, Dmitry Torokhov wrote:
On Fri, Feb 19, 2016 at 11:43:50AM +0530, Raveendra Padasalagi wrote:
On Thu, Feb 18, 2016 at 8:06 PM, Rob Herring wrote:
On Wed, Feb 17, 2016 at 03:13:44PM +0530,
On 02/19/2016 09:18 AM, David Howells wrote:
>
> Here's a set of patches that cleans up the public key handling in the
> asymmetric key functions:
>
> (1) - (3) These are Tadeusz's RSA akcipher conversion.
Thanks for taking this David.
>
> (4) This removes all knowledge of RSA from the
Hi Dan,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.5-rc5 next-20160222]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Dan-Carpenter/staging-gdm72xx
On Mon, Feb 22, 2016 at 02:04:35PM +0100, Jan Kara wrote:
> On Mon 22-02-16 13:12:22, Peter Zijlstra wrote:
> > On Mon, Feb 22, 2016 at 12:54:35PM +0100, Jan Kara wrote:
> > > > Also, I think fsnotify_unmount_inodes() (as per mainline) is missing a
> > > > final iput(need_iput) at the very end,
msm.ko is not an appropriate name for a module that drives a specific
device on the msm platform. This changes the name to drm_msm.ko
to have something that won't conflict with any other module name.
Signed-off-by: Arnd Bergmann
---
drivers/gpu/drm/msm/Makefile | 12 ++--
This is a preparation for having edp, dsi and hdmi in separate
modules. Those three drivers depend on the iotrace code and,
and edp depends on gem, which in turn depends on the fence.
With this change, those two pieces of the main driver can be
loaded first, to resolve circular dependencies.
Refrain from defining default fw_cfg register offsets on
unsupported architectures -- throw an error instead. If
QEMU were to add fw_cfg support on additional architectures,
we should add them to the FW_CFG_SYSFS depends statement in
drivers/firmware/Kconfig, and provide default values for
From: "Steven Rostedt (Red Hat)"
The sched_domain_sysctl setup is only enabled when SCHED_DEBUG is
configured. As debug.c is only compiled when SCHED_DEBUG is configured as
well, move the setup of sched_domain_sysctl into that file.
Note, the
From: "Steven Rostedt (Red Hat)"
To have nanosecond output displayed in a more human readable format, its
nicer to convert it to a seconds format (XXX.Y). The problem is that
to do so, the numbers must be divided by NSEC_PER_SEC, and moded too. But as
these numbers
We did not handle XSAVES* instructions correctly. There were issues in
converting between standard and compacted format when interfacing with
user-space. These issues have been corrected.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/init.c | 15 ---
1
Online defrag operations for ext4 are hard coded to use the page cache.
See ext4_ioctl() -> ext4_move_extents() -> move_extent_per_page()
When combined with DAX I/O, which circumvents the page cache, this can
result in data corruption. This was observed with xfstests ext4/307 and
ext4/308.
Fix
When S_DAX is set on an inode we assume that if there are pages attached
to the mapping (mapping->nrpages != 0), those pages are clean zero pages
that were used to service reads from holes. Any dirty data associated with
the inode should be in the form of DAX exceptional entries
XSAVES uses compacted format and is a kernel instruction. The kernel
should use standard-format, non-supervisor state data for PTRACE.
Signed-off-by: Yu-cheng Yu
---
arch/x86/include/asm/fpu/xstate.h | 4 +
arch/x86/kernel/fpu/regset.c | 56 +
On Mon, Feb 22, 2016 at 09:08:28PM +0200, Jarkko Sakkinen wrote:
> On Mon, Feb 22, 2016 at 10:52:45AM -0700, Jason Gunthorpe wrote:
> > On Mon, Feb 22, 2016 at 04:50:23PM +0200, Jarkko Sakkinen wrote:
> >
> > > I already pushed a fix to my master for this issue:
> > >
> > >
On 2/22/2016 4:43 AM, Aaro Koskinen wrote:
Hi,
On Fri, Feb 19, 2016 at 05:12:41PM -0800, Yang Shi wrote:
I tried to boot 4.5-rc4 kernel on my CN6880 board, but it is failed at
booting up secondary cores. The error is:
With v4.5-rc5, EBB6800 is booting fine:
[0.00] CPU0 revision is:
The value of "group" comes from "idx" in __gdm_wimax_event_send():
if (sscanf(e->dev->name, "wm%d", ) == 1)
Smatch marks sscanf values as user controlled. It's supposed to be a
number in 0-30 range. We cap the upper bound but allow negatives. Fix
this by making it type u16 instead.
Provide an interface for the airplane-mode indicator be controlled from
userspace. User has to first acquire the control through
RFKILL_OP_AIRPLANE_MODE_INDICATOR_ACQUIRE and keep the fd open for the
whole time it wants to be in control of the indicator. Closing the fd
restores the default policy.
Add 'nvmem-composite' driver which allows to combine multiple chunks of
various NVMEM cells into a single continuous NVMEM device.
Signed-off-by: Andrey Smirnov
---
.../devicetree/bindings/nvmem/composite.txt| 44
drivers/nvmem/Makefile
On 02/22/2016 05:49 AM, Alan Cox wrote:
>> we have some good alternatives in the form of bus and platform
>> drivers that
>> can manage the appropriate serialization and keep things from
>> stomping
>> on one another.
>
> It's not used much, especially nowdays. The use case is basically multi
>
From: Arnd Bergmann
Date: Mon, 22 Feb 2016 21:50:39 +0100
> A change to the prototype of netcp_setup_tc() missed a '*'
> character, which broke compilation of hte netcp driver:
>
> drivers/net/ethernet/ti/netcp_core.c: In function 'netcp_setup_tc':
>
Previously calls to dax_writeback_mapping_range() for all DAX filesystems
(ext2, ext4 & xfs) were centralized in filemap_write_and_wait_range().
dax_writeback_mapping_range() needs a struct block_device, and it used to
get that from inode->i_sb->s_bdev. This is correct for normal inodes
mounted
If "xsaves" is enabled, kernel always uses compacted format of xsave area.
But user space still uses standard format of xsave area. Thus, xstate size
in kernel's xsave area is smaller than xstate size in user's xsave area.
The xstate in signal frame should be in standard format for user's signal
dax_clear_blocks() needs a valid struct block_device and previously it was
using inode->i_sb->s_bdev in all cases. This is correct for normal inodes
on mounted ext2, ext4 and XFS filesystems, but is incorrect for DAX raw
block devices and for XFS real-time devices.
Instead, rename
Andi,
On Mon, 22 Feb 2016, Andi Kleen wrote:
> Thomas Gleixner writes:
> >
> > +static void __init rapl_advertise(void)
> > +{
> > + int i;
> > +
> > + pr_info("API unit is 2^-32 Joules, %d fixed counters, %llu ms ovfl
> > timer\n",
> > +
Andi,
On Mon, 22 Feb 2016, Andi Kleen wrote:
> Thomas Gleixner writes:
> > + if (c->cpuid_level >= 0x0001) {
> > + u32 eax, ebx, ecx, edx;
> > +
> > + cpuid(0x0001, , , , );
>
> Use cpuid_edx()
That does not give me EBX ...
> > + /*
* Pavel Machek [160221 06:05]:
> On Sun 2016-02-21 12:28:23, Pali Rohár wrote:
> > This change does not break existing userspace or Maemo software because
> > isp1704_charger.c always export power supply device under isp1704 name.
>
> ..exports..
>
> > Signed-off-by: Pali Rohár
Thierry,
On Mon, Feb 22, 2016 at 9:59 AM, Thierry Reding
wrote:
>> This is because only some drivers would be able to read the hardware
>> state? I'm not sure how we can get away from that. In all proposals
>> we've talked about (including what you propose below,
On Fri, Feb 19, 2016 at 11:43:50AM +0530, Raveendra Padasalagi wrote:
> On Thu, Feb 18, 2016 at 8:06 PM, Rob Herring wrote:
> > On Wed, Feb 17, 2016 at 03:13:44PM +0530, Raveendra Padasalagi wrote:
> >> In Cygnus SOC touch screen controller registers are shared
> >> with ADC and
On 22 February 2016 at 12:00, Dan Williams wrote:
> On Mon, 2016-02-22 at 11:36 -0500, João Paulo Rechi Vita wrote:
>> This series implements an airplane-mode indicator LED trigger, which
>> can be
>> used by platform drivers. The default policy have have airplane-mode
>> set
My comments below
On 16-02-22 11:36 AM, Dmitry Torokhov wrote:
On Fri, Feb 19, 2016 at 11:43:50AM +0530, Raveendra Padasalagi wrote:
On Thu, Feb 18, 2016 at 8:06 PM, Rob Herring wrote:
On Wed, Feb 17, 2016 at 03:13:44PM +0530, Raveendra Padasalagi wrote:
In Cygnus SOC touch
On Mon, Feb 22, 2016 at 08:17:11PM +0100, Ard Biesheuvel wrote:
> I am not exactly sure why ioremap_cache() does not use MT_MEMORY_RW
> attributes, but the ARM architecture simply does not allow mismatched
> attributes, so we cannot simply replace each instance of
> ioremap_cache() with memremap()
On 02/22/2016 02:48 PM, Steven Rostedt wrote:
> On Mon, 22 Feb 2016 18:32:59 +0100
> Peter Zijlstra wrote:
>
>
>> > So I'm a bit allergic to tracepoints and this is very flimsy on reasons
>> > why I would want to do this.
> Because there's no way to know if
On Thu, Feb 18, 2016 at 1:27 PM, PaX Team wrote:
> On 18 Feb 2016 at 12:34, Ard Biesheuvel wrote:
>
>> However, that does not fix the issue Kees is trying to solve, where a
>> .rodata section is emitted with the "x" bit set, which causes the
>> linker to complain:
>>
>>
The return type of of_clk_get_parent_count() is an unsigned int
now, so let's update the code here to be more explicit about the
range of values we can test for.
Cc: Maxime Ripard
Cc: Chen-Yu Tsai
Signed-off-by: Stephen Boyd
The checks for < 1 can be simplified now that
of_clk_get_parent_count() returns an unsigned int. Update the
code to reflect the int to unsigned int change.
Cc: Yoshinori Sato
Cc:
Signed-off-by: Stephen Boyd
The check for < 0 is impossible now that
of_clk_get_parent_count() returns an unsigned int. Simplify the
code and update the types.
Cc: Hans de Goede
Cc: Jean-Christophe Plagniol-Villard
Cc: Tomi Valkeinen
Cc:
On Mon, Feb 22, 2016 at 09:56:50AM +0100, Michał Kępień wrote:
> > > /*
> > > * Certain keys are flagged as KE_IGNORE. All of these are either
> > > * notifications (rather than requests for change) or are also sent
> > > @@ -513,6 +533,7 @@ static int __init dell_wmi_init(void)
> > > {
> >
On Mon, Feb 22, 2016 at 11:15:09AM -0800, Doug Anderson wrote:
> Note that historically I remember that Linus Torvalds has stated that
> there is no stable API within the Linux kernel and that forcing the
> in-kernel API to never change was bad for software development. I
> tracked down my
On Mon, Feb 22, 2016 at 12:48:54PM -0500, Steven Rostedt wrote:
> > As it stands, the existing tracepoint have already been an ABI
> > trainwreck, why would I want to add more?
>
> Yes, this may become a type of ABI, but even the sched switch
> tracepoints haven't been that bad. Has it really
From: Dan Williams
The recent *sync enabling discovered that we are inserting into the
block_device pagecache counter to the expectations of the dirty data
tracking for dax mappings. This can lead to data corruption.
We want to support DAX for block devices
Component offset print out was incorrect for XSAVES. Correct it and move
to a separate function.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/xstate.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git
On Mon, Feb 22, 2016 at 07:39:36PM +0100, Thomas Gleixner wrote:
> On Sun, 21 Feb 2016, William Breathitt Gray wrote:
>
> > On 01/27/2016 05:07 AM, Thomas Gleixner wrote:
> > > On Fri, 22 Jan 2016, William Breathitt Gray wrote:
> > >> Many motherboards utilize a LPC to ISA bridge in order to
We pad the start of this buffer with 256 bytes of padding. It's not
clear to me exactly what's going on or how it's used but let's zero it
out.
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/gdm72xx/usb_boot.c
b/drivers/staging/gdm72xx/usb_boot.c
index
We had an underflow bug here and I think I fixed it but we may as
well be proactive and make "len" unsigned to be double sure.
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/gdm72xx/gdm_wimax.h
b/drivers/staging/gdm72xx/gdm_wimax.h
index 3330cd79..ed12813
Add 'nvmem-blob' driver, which allows to access device tree embedded
data via NVMEM subsystem API.
Signed-off-by: Andrey Smirnov
---
Documentation/devicetree/bindings/nvmem/blob.txt | 35 ++
drivers/nvmem/Makefile | 1 +
Hello,
This RFC introduces two new drivers to NVMEM subsytem. First driver,
'nvmem-blob', serves the purpose of exposing data, embedded in DTB,
via NVMEM consumer API. Second, 'nvmem-composite', allows the user to
combin a number of NVMEM cells (or parts of them) into a single
continuos "blob" of
Add 'of_nvmem_cell_from_device_node()' -- a function that allows to
obtain 'struct nvmem_cell' from a device tree node representing it. One
use-case for such a function would be to access nvmem cells with known
phandles.
Signed-off-by: Andrey Smirnov
---
On 02/22/2016 11:00 AM, Yu-cheng Yu wrote:
> + if (xsave->header.xfeatures & XFEATURE_MASK_SUPERVISOR)
> + xsave->header.xfeatures = xfeatures | XFEATURE_MASK_SUPERVISOR;
> + else
> + xsave->header.xfeatures = xfeatures;
This is dangerous. It says, "if any
On 22/02/16 18:42, Tony Lindgren wrote:
> * Roger Quadros [160222 02:16]:
>> On 20/02/16 00:04, Tony Lindgren wrote:
>>> * Roger Quadros [160219 13:27]:
Hi,
@Tony
Patches 15 and 24 are new and will need your review.
I've modified patch 22 to
1 - 100 of 2460 matches
Mail list logo