ached. Looks like older versions of gcc (or at least 4.6.3)
don't like the newly introduced __invpcid().
Guenter
---
# bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files
for 20160212
# good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe9
While creating a linux module that should be usable across a wide
array of linux versions and builds, I've run into struct modules
(THIS_MODULE) being a problem. It's the only internal struct accessed
as a requirement to struct block_device_operations .owner. It's a
bit annoying for this module
Hi Tomi,
On 11.01.2016 20:34, Tomi Valkeinen wrote:
So, I'm not very enthusiastic about adding this feature as an omapfb
specific boot parameter.
What about something like (not properly formatted, just want your
opinion on the idea):
diff --git a/arch/arm/mach-omap2/fb.c
On Fri, Feb 12, 2016 at 5:57 AM, Arnd Bergmann wrote:
> On Friday 12 February 2016 01:45:47 Deepa Dinamani wrote:
>> + ts = vfs_time_to_timespec(inode->i_mtime);
>> + if (!timespec_equal(, ))
>> + inode->i_mtime = timespec_to_vfs_time(now);
>> +
>> + ts =
> Regarding the three versions, I think all of them are doable
> doable, and they all have their upsides and downsides but no
> showstoppers.
I agree that all the approaches are doable.
> Let me summarize what I see in the patches:
>
> 2a is the smallest set of changes in number of lines, as you
Hi Wolfram,
> -Original Message-
> From: Wolfram Sang [mailto:w...@the-dreams.de]
> Sent: Saturday, February 13, 2016 12:08 AM
> To: Sricharan R
> Cc: devicet...@vger.kernel.org; linux-arm-...@vger.kernel.org;
> agr...@codeaurora.org; linux-kernel@vger.kernel.org; linux-
>
On Fri 12 Feb 21:16 PST 2016, John Stultz wrote:
> On Fri, Feb 5, 2016 at 11:21 AM, John Stultz wrote:
> > This patch adds a dts file to support the Nexus7 2013
> > device. Its based off of the qcom-apq8064-ifc6410.dts
> > which is similar hardware.
> >
> > Also includes some comments and
Hi Itaru,
On Friday, February 12, 2016, Itaru Kitayama wrote:
>
> Hi Duc,
>
> I've been testing your patch set for v4.5-rc1 on Mustang, with ACPI, however
> the boot hangs in the middle of it:
>
> EFI stub: Booting Linux Kernel...
> EFI stub: Using DTB from configuration table
> EFI stub:
On Fri, Feb 5, 2016 at 11:21 AM, John Stultz wrote:
> This patch adds a dts file to support the Nexus7 2013
> device. Its based off of the qcom-apq8064-ifc6410.dts
> which is similar hardware.
>
> Also includes some comments and context folded in
> from Vinay Simha BN
>
> Cc: Rob Herring
> Cc:
Hi Duc,
I've been testing your patch set for v4.5-rc1 on Mustang, with ACPI,
however the boot hangs in the middle of it:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
L3c Cache: 8MB
Booting
On Sat, Feb 13, 2016 at 01:38:49PM +1100, Dave Chinner wrote:
> On Fri, Feb 12, 2016 at 12:03:20PM -0700, Ross Zwisler wrote:
> > On Thu, Feb 11, 2016 at 01:43:04PM +0100, Jan Kara wrote:
> > > On Wed 10-02-16 13:48:54, Ross Zwisler wrote:
> > > > 3) In filemap_write_and_wait() and
On 12/02/2016 16:53, Eric Anholt wrote:
> Florian Fainelli writes:
>
>> On 10/02/2016 10:51, Eric Anholt wrote:
>>> Martin Sperl writes:
>>>
> On 09.02.2016, at 01:32, Eric Anholt wrote:
>
> Hi Florian. Here's the first set of patches for bcm2835 for 4.6.
> We've got more DT
Mailbox device tree node for APM X-Gene platform.
Signed-off-by: Feng Kan
Signed-off-by: Duc Dang
---
Changes since v5:
- None
Changes since v4:
- Rebase over v4.5-rc1
- Change node name to mailbox@1054
Changes since v3:
- Rebase over v4.4
X-Gene mailbox controller provides 8 mailbox channels, with
each channel has a dedicated interrupt line.
Signed-off-by: Feng Kan
Signed-off-by: Duc Dang
---
Changes since v5:
- Add description for struct slimpro_mbox_chan
and struct slimpro_mbox
Changes since v4:
-
APM X-Gene SoC has a mailbox controller that provides
communication mechanism for X-Gene Arm64 cores to communicate
with X-Gene SoC's Cortex M3 (SLIMpro) processor.
X-Gene mailbox controller provides 8 mailbox channels, with
each channel has a dedicated interrupt line.
Changes since v5:
This adds the APM X-Gene SLIMpro mailbox device tree
node documentation.
Signed-off-by: Feng Kan
Signed-off-by: Duc Dang
Acked-by: Rob Herring
---
Changes since v5:
- None
Changes since v4:
- Rebase over v4.5-rc1
- Fix number of total interrupts in
introduction
Modern Intel hardware adds an Always Running Timer (ART) that allows the
network and audio device clocks to precisely cross timestamp the device
clock with the system clock. This allows a precise correlation of the
device time and system time.
This patchset adds interfaces to the timekeeping code
In the current timekeeping code there isn't any interface to
atomically capture the current relationship between the system counter
and system time. ktime_get_snapshot() returns this triple (counter,
monotonic raw, realtime) in the system_time_snapshot struct.
Signed-off-by: Christopher S. Hall
ACKNOWLEDGMENT: cross timestamp code was developed by Thomas Gleixner
. It has changed considerably and any mistakes are
mine.
The precision with which events on multiple networked systems can be
synchronized using, as an example, PTP (IEEE 1588, 802.1AS) is limited
by the precision of the cross
On Fri, Feb 12, 2016 at 08:31:21PM -0500, Stefan Berger wrote:
> > I'll send you something else that might work for vtpm...'
>
> The vtpm driver will introduce chip->priv, which will point to vtpm_dev. For
> this reason we need to hold a reference to the vtpm_dev->dev in the
> front end.
This
On modern Intel systems TSC is derived from the new Always Running Timer
(ART). ART can be captured simultaneous to the capture of
audio and network device clocks, allowing a correlation between timebases
to be constructed. Upon capture, the driver converts the captured ART
value to the
Another representative use case of time sync and the correlated
clocksource (in addition to PTP noted above) is PTP synchronized
audio.
In a streaming application, as an example, samples will be sent and/or
received by multiple devices with a presentation time that is in terms
of the PTP master
Currently, network /system cross-timestamping is performed in the
PTP_SYS_OFFSET ioctl. The PTP clock driver reads gettimeofday() and
the gettime64() callback provided by the driver. The cross-timestamp
is best effort where the latency between the capture of system time
(getnstimeofday()) and the
Modern Intel systems supports cross timestamping of the network device
clock and Always Running Timer (ART) in hardware. This allows the
device time and system time to be precisely correlated. The timestamp
pair is returned through e1000e_phc_get_syncdevicetime() used by
The timekeeping code does not currently provide a way to translate
externally provided clocksource cycles to system time. The cycle count
is always provided by the result clocksource read() method internal to
the timekeeping code. The added function timekeeping_cycles_to_ns()
calculated a
The code in ktime_get_snapshot() is a superset of the code in
ktime_get_raw_and_real() code. Further, ktime_get_raw_and_real() is
called only by the PPS code, pps_get_ts(). Consolidate the
pps_get_ts() code into a single function calling ktime_get_snapshot()
and eliminate ktime_get_raw_and_real().
On Wed, Feb 10, 2016 at 6:41 AM, Mathieu Poirier
wrote:
> On 9 February 2016 at 20:46, Duc Dang wrote:
>> On Tue, Feb 9, 2016 at 8:40 AM, Mathieu Poirier
>> wrote:
>>> On 8 February 2016 at 15:04, Duc Dang wrote:
X-Gene mailbox controller provides 8 mailbox channels, with
each
Keith Packard writes:
> The goal would be to create an html document which could be used without
> javascript, and that would work without css as well.
I've managed to hack up asciidoc to generate the TOC within the
document, rather than requiring javascript. The changes are fairly
minor, and
This patch is to fix misused error number.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 57a5f7b..47fbb72 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -505,7 +505,7 @@
This patch fixes to eliminate garbage name lengths in dentries in order
to provide correct answers of readdir.
For example, if a valid dentry consists of:
bitmap : 1 1 1 1
len: 32 0 x 0,
readdir can start with second bit_pos having len = 0.
Or, it can start with third bit_pos having
This patch fixes wrong adoption on fname padding.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/crypto_fname.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/crypto_fname.c b/fs/f2fs/crypto_fname.c
index 905c065..73741fb 100644
--- a/fs/f2fs/crypto_fname.c
+++
On Fri, Feb 12, 2016 at 12:03:20PM -0700, Ross Zwisler wrote:
> On Thu, Feb 11, 2016 at 01:43:04PM +0100, Jan Kara wrote:
> > On Wed 10-02-16 13:48:54, Ross Zwisler wrote:
> > > 3) In filemap_write_and_wait() and filemap_write_and_wait_range(),
> > > continue
> > > the writeback in the case that
Hi,
On Fri, Feb 12, 2016 at 5:31 PM, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This is v2 of the A80 APBS clock fixes series.
>
> When I did the A80 PRCM support, I failed to notice the A80's APBS clock
> was not the same as the A23's APB0 clock. The former is a zero-based
> divider, while the
On Fri, Feb 12, 2016 at 01:45:49AM -0800, Deepa Dinamani wrote:
> This is in preparation for changing VFS inode timestamps to
> use 64 bit time.
> The VFS inode timestamps are not y2038 safe as they use
> struct timespec. These will be changed to use struct timespec64
> instead and that is y2038
On Fri, Feb 12, 2016 at 08:31:21PM -0500, Stefan Berger wrote:
> The vtpm driver will introduce chip->priv, which will point to
> vtpm_dev. For
Why not just use chip->vendor.priv? Aka TPM_VPRIV
> this reason we need to hold a reference to the vtpm_dev->dev in the
> front end.
Yes, but all
On Tue, 2016-02-09 at 16:29 -0800, David Decotigny wrote:
> From: David Decotigny
>
> This patch defines a new ETHTOOL_GSETTINGS/SSETTINGS API, handled by
> the new get_ksettings/set_ksettings callbacks. This API provides
> support for most legacy ethtool_cmd fields, adds support for larger
>
On 02/12/2016 09:36 AM, Mark Rutland wrote:
On Fri, Feb 12, 2016 at 05:55:06PM +0100, Jan Glauber wrote:
[...]
2) Counters are summarized across the different units of the same type,
e.g. L2C TAD 0..7 is presented as a single counter (adding the
values from TAD 0 to 7). Although losing
This test opens user specified Media Device and calls
MEDIA_IOC_DEVICE_INFO ioctl in a loop once every 10
seconds. This test is for detecting errors in device
removal path.
Usage:
sudo ./media_devkref_test -d /dev/mediaX
While test is running, remove the device and
ensure there are no use
On Tue, 2016-02-09 at 16:29 -0800, David Decotigny wrote:
> From: David Decotigny
>
> This is mainly testing bitmap construction and conversion to/from u32[]
> for now.
>
> Tested:
> qemu i386, x86_64, ppc, ppc64 BE and LE, ARM.
>
> Signed-off-by: David Decotigny
[...]
> diff --git
On Fri, 2016-02-12 at 17:45 +0100, Petr Mladek wrote:
> On Sat 2016-02-13 03:13:29, Balbir Singh wrote:
> > On Thu, 2016-01-28 at 16:32 +0100, Torsten Duwe wrote:
> > > From: Petr Mladek
> > >
> > > Livepatch works on x86_64 and s390 only when the ftrace call
> > > is at the very beginning of
On 02/11, Michael Turquette wrote:
> >From the clk_put kerneldoc in include/linux/clk.h:
>
> """
> Note: drivers must ensure that all clk_enable calls made on this clock
> source are balanced by clk_disable calls prior to calling this function.
> """
>
> The common clock framework implementation
On 02/11, Michael Turquette wrote:
> This patch adds prepare and enable reference counts for the per-user
> handles that clock consumers have for a clock node. This patch warns if
> an imbalance occurs while trying to disable or unprepare a clock and
> aborts, leaving the hardware unaffected.
>
>
On 02/11, Michael Turquette wrote:
> From: Lee Jones
>
> Signed-off-by: Lee Jones
> Signed-off-by: Michael Turquette
> ---
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On Sat, Feb 13, 2016 at 09:01:06AM +0800, kbuild test robot wrote:
> url:
> https://github.com/0day-ci/linux/commits/Jason-Gunthorpe/tpm-Hold-the-kref-during-tpm_chip_find_get/20160213-080824
> config: xtensa-allyesconfig (attached as .config)
> reproduce:
> wget
>
On 02/11, Michael Turquette wrote:
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index b4db67a..993f775 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -2484,6 +2484,11 @@ static int __clk_init(struct device *dev, struct clk
> *clk_user)
> if (core->ops->init)
>
On Fri, Feb 12, 2016 at 07:37:10PM -0500, Stefan Berger wrote:
>Jason Gunthorpe wrote on 02/12/2016
>07:04:30 PM:
>>
>> This is a hold over from before the struct device conversion.
>>
>> - All prints should be using >dev, which is the Linux
>> standard. This changes
On 02/11, Michael Turquette wrote:
> +int of_clk_mark_if_critical(struct device_node *np,
> + int index, unsigned long *flags)
> +{
> + struct property *prop;
> + const __be32 *cur;
> + uint32_t idx;
> +
> + if (!np || !flags)
> +
On Tue, 2016-02-09 at 16:29 -0800, David Decotigny wrote:
> From: David Decotigny
>
> Aimed at transferring bitmaps to/from user-space in a 32/64-bit agnostic
> way.
>
> Tested:
> unit tests (next patch) on qemu i386, x86_64, ppc, ppc64 BE and LE,
> ARM.
>
> Signed-off-by: David Decotigny
Hi Jason,
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on v4.5-rc3 next-20160212]
[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/Jason-Gunthorpe/tpm-Hold
Florian Fainelli writes:
> On 10/02/2016 10:51, Eric Anholt wrote:
>> Martin Sperl writes:
>>
On 09.02.2016, at 01:32, Eric Anholt wrote:
Hi Florian. Here's the first set of patches for bcm2835 for 4.6.
We've got more DT patches that are going to happen for new boards,
On 02/12/2016 04:57 AM, Tomeu Vizoso wrote:
>
>
> diff --git a/drivers/power/cros_usbpd-charger.c
> b/drivers/power/cros_usbpd-charger.c
> new file mode 100644
> index ..c1aa58b47f56
> --- /dev/null
> +++ b/drivers/power/cros_usbpd-charger.c
> @@ -0,0 +1,908 @@
> +/*
> + * Power
On Thu, Feb 11, 2016 at 03:19:20PM +0100, Ard Biesheuvel wrote:
diff --git a/arch/arm64/kernel/vdso/vdso.S b/arch/arm64/kernel/vdso/vdso.S
index 60c1db5..db7c0f2 100644
--- a/arch/arm64/kernel/vdso/vdso.S
+++ b/arch/arm64/kernel/vdso/vdso.S
@@ -24,6 +24,7 @@
__PAGE_ALIGNED_DATA
^^ You
On Fri, 2016-02-05 at 22:30 +, Rainer Weikusat wrote:
> The present unix_stream_read_generic contains various code sequences of
> the form
>
> err = -EDISASTER;
> if ()
> goto out;
[...]
I wish people would stop writing code like this. At one time it may
have been a useful
On Fri, Feb 12, 2016 at 10:59:10AM -0800, Andy Lutomirski wrote:
> On Tue, Feb 2, 2016 at 9:00 AM, Darren Hart wrote:
> > On Sat, Jan 30, 2016 at 08:18:50PM +0100, Jean Delvare wrote:
> >> On Sat, 30 Jan 2016 10:13:09 -0800, Andy Lutomirski wrote:
> >> > On Sat, Jan 30, 2016 at 10:05 AM, Darren
We can't always support mmap across an entire device region, for
example we deny mmaps covering the MSI-X table of PCI devices, but
we don't really have a way to report it. We expect the user to
implicitly know this restriction. We also can't split the region
because vfio-pci defines an API with
We have a few cases where we need to extend the data returned from the
INFO ioctls in VFIO. For instance we already have devices exposed
through vfio-pci where VFIO_DEVICE_GET_REGION_INFO reports the region
as mmap-capable, but really only supports sparse mmaps, avoiding the
MSI-X table. If we
This is a hold over from before the struct device conversion.
- All prints should be using >dev, which is the Linux
standard. This changes prints to use tpm0 as the device name,
not the PnP/etc ID.
- The few places involving sysfs/modules that really do need the
parent just use
This was missed during the struct device conversion, we
need to hold a kref on the chip to make sure it isn't freed.
Signed-off-by: Jason Gunthorpe
---
drivers/char/tpm/tpm-chip.c | 2 ++
drivers/char/tpm/tpm.h | 1 +
2 files changed, 3 insertions(+)
diff --git
Now that we have a proper struct device just use dev_name() to
access this value instead of keeping two copies.
Signed-off-by: Jason Gunthorpe
---
drivers/char/tpm/tpm-chip.c| 17 +++--
drivers/char/tpm/tpm.h | 1 -
drivers/char/tpm/tpm_eventlog.c| 2 +-
These little clean ups were missed during the struct device conversion of
tpm_chip. There were noticed when looking at Stefan's vtpm patch sets.
Nothing very significant
- Add some missing krefs
- Replace chip->devname with dev_name
- Replace chip->pdev with chip->dev.parent
Jason Gunthorpe
Add support for additional regions with indexes started after the
already defined fixed regions. Device specific code can register
these regions with the new vfio_pci_register_dev_region() function.
The ops structure per region currently only includes read/write
access and a release function,
We do not provide a way for the user to access the host stolen memory
therefore hide both the base address and the size. This is mostly
useful for VM users where the driver may try to make use of the memory
referenced by these registers, whether the VM considers it reserved
for the GPU or not.
This is the first consumer of vfio device specific resource support,
providing read-only access to the OpRegion for Intel graphics devices.
Signed-off-by: Alex Williamson
---
drivers/vfio/pci/Kconfig|4 +
drivers/vfio/pci/Makefile |1
drivers/vfio/pci/vfio_pci.c
Integrated graphics may have their ROM shadowed at 0xc rather than
implement a PCI option ROM. Make this ROM appear to the user using
the ROM BAR.
Signed-off-by: Alex Williamson
---
drivers/vfio/pci/vfio_pci.c| 10 --
drivers/vfio/pci/vfio_pci_config.c | 11 ---
Typically config space for a device is mapped out into capability
specific handlers and unassigned space. The latter allows direct
read/write access to config space. Sometimes we know about registers
living in this void space and would like an easy way to virtualize
them, similar to how BAR
Provide read-only access to PCI config space of the PCI host bridge
and LPC bridge through device specific regions. This may be used to
configure a VM with matching register contents to satisfy driver
requirements. Providing this through the vfio file descriptor removes
an additional userspace
To this point vfio has only provided an interface to the user that
allows them to determine the number of regions and specifics about
each region. What the region represents is left to the vfio bus
driver. vfio-pci chooses to use fixed indexes for fixed resources,
index 0 is BAR0, 1 is BAR1,...
v2:
v2 includes more IGD support. Read only access to the host bridge
and LPC bridge config space is provided to allow configuration of
emulated devices for VM use cases. We also try to hide the stolen
memory window from the user. This probably needs additional work as
I'd prefer not to need
vfio-pci has never allowed the user to directly mmap the MSI-X vector
table, but we've always relied on implicit knowledge of the user that
they cannot do this. Now that we have capability chains that we can
expose in the region info ioctl and a sparse mmap capability that
represents the
Allow sub-modules to easily reallocate a buffer for managing
capability chains for info ioctls.
Signed-off-by: Alex Williamson
---
drivers/vfio/vfio.c | 54 ++
include/linux/vfio.h | 11 ++
2 files changed, 65 insertions(+)
diff
On 05/02/16 14:43, Jon Mason wrote:
> Northstar Plus device tree changes. The first 2 are bug fixes that
> probably should go in ASAP. The other 3 enable new hardware and can be
> pushed into the next merge window.
Series applied to devicetree/next, with the update to the last patch
based on
On 09/02/16 22:10, Anup Patel wrote:
> This patchset primarily adds more DT nodes for NS2 SVK. It also does
> minor update to arch/arm64/Kconfig.platforms and adds missing DT
> bindings document for sp805 driver.
>
> The patchset is based on v4.5-rc3 tag and is available in ns2_dt2_v1
> branch of
Some devices take longer than the spec indicates to return from FLR
reset, a notable case of this is Intel integrated graphics (IGD),
which can often take an additional 300ms powering down an attached
LCD panel as part of the FLR. Allow devices up to an additional
1000ms, testing every 100ms
MEMORY_HOTPLUG already depends on ARCH_ENABLE_MEMORY_HOTPLUG which is selected
by the supported architectures, so the following arch depend is unnecessary.
Signed-off-by: Yang Shi
---
mm/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/mm/Kconfig b/mm/Kconfig
index 03cbfa0..c077765
Since the switch from mmp_pdma to pxa_dma driver for pxa architectures,
the pxa_dma requires 2 arguments, namely the requestor line and the
requested priority.
Fix the only left device node which was still passing only one argument,
making the pxa3xx-nand driver misbehave in a device-tree
Dear RT folks!
I'm pleased to announce the v4.4.1-rt6 patch set.
Changes since v4.4.1-rt5:
- The rtmutex wait_lock is taken with interrupts disabled again. It
fixes a possible deadlock in the posix timer code. Patch by Thomas
Gleixner.
- Don't disable interrupts around atomic_dec_and_lock()
On Fri, 2013-11-15 at 15:54 +0400, Stanislav Kinsbursky wrote:
> 15.11.2013 15:03, Eric W. Biederman пишет:
> > Stanislav Kinsbursky writes:
> >
> > > 12.11.2013 17:30, Jeff Layton пишет:
> > > > On Tue, 12 Nov 2013 17:02:36 +0400
> > > > Stanislav Kinsbursky wrote:
> > > >
> > > > >
On Fri, Feb 12, 2016 at 2:30 PM, Toshi Kani wrote:
> On Fri, 2016-02-12 at 11:41 -0800, Dan Williams wrote:
>> On Tue, Feb 2, 2016 at 10:55 AM, Toshi Kani wrote:
>> > Change acpi_nfit_register_region() to call iomem_set_desc() with
>> > IORES_DESC_PERSISTENT_MEMORY for NFIT_SPA_PM ranges found
>> diff --git a/drivers/staging/lustre/lustre/libcfs/linux/linux-module.c
>> b/drivers/staging/lustre/lustre/libcfs/linux/linux-module.c
>> index 33f6036..64f0fbf 100644
>> --- a/drivers/staging/lustre/lustre/libcfs/linux/linux-module.c
>> +++
On Fri, Feb 12, 2016 at 09:52:03AM +0200, Oleksandr Natalenko wrote:
> Ville,
>
> I've applied patch you've provided and did couple of replugging with
> intel_reg in between. Here are the results.
>
> I used additional VGA cable to see what actually I type in console :).
>
My life would have
On Fri, Feb 12, 2016 at 6:33 PM, Doug Smythies wrote:
> On 2016.02.12 05:39 Rafael J. Wysocki wrote:
>> On Fri, Feb 12, 2016 at 8:25 AM, Doug Smythies wrote:
>>> On 2016.02.11 14:50 Doug Smythies wrote:
On 2016.02.10 22:03 Srinivas Pandruvada wrote:
> On Wednesday, February 10, 2016
>On Fri, 2016-02-12 at 12:06 -0500, James Simmons wrote:
>> Add missing spaces in the code reported by checkpatch.pl.
>[]
>> diff --git a/drivers/staging/lustre/include/linux/lnet/lib-types.h
>> b/drivers/staging/lustre/include/linux/lnet/lib-types.h
>[]
>> @@ -112,7 +112,7 @@ typedef struct
On Fri, Feb 12, 2016 at 11:09:06AM -0500, Tejun Heo wrote:
> Hello,
>
> On Fri, Feb 12, 2016 at 12:18:28AM +0100, Alban Crequy wrote:
> > I just noticed commit c38c4597e4bf ("netfilter: implement xt_cgroup
> > cgroup2 path match") which, as far as I understand, introduces a new
> > userland
From: Tirumalesh Chalamarla
Due to Errata in ThunderX, HOST_IRQ_STAT should be
cleared before leaving the interrupt handler.
The patch attempts to satisfy the need.
Changes from V1:
- Rebased on top of libata/for-4.6
- Moved ThunderX intr handler to new file
Signed-off-by:
dev->ctrl_input is set in vidioc_s_input() and
doesn't get set in au0828_s_input(). As a result,
dev->ctrl_input is left uninitialized until user
space calls s_input. It works correctly because
the default input value is 0 and which is what
dev->ctrl_input gets initialized via kzalloc().
Change
On Fri, Feb 12, 2016 at 6:02 PM, Doug Smythies wrote:
> On 2016.02.12 08:01 Rafael J. Wysocki wrote:
>> On Fri, Feb 12, 2016 at 3:10 PM, Peter Zijlstra wrote:
>>> On Thu, Feb 11, 2016 at 10:52:20AM -0800, Steve Muckle wrote:
On 02/11/2016 09:30 AM, Peter Zijlstra wrote:
>> My concern
On Fri, Feb 12, 2016 at 06:16:40PM +0100, Gerald Schaefer wrote:
> On Fri, 12 Feb 2016 16:57:27 +0100
> Christian Borntraeger wrote:
>
> > On 02/12/2016 04:41 PM, Kirill A. Shutemov wrote:
> > > On Thu, Feb 11, 2016 at 08:57:02PM +0100, Gerald Schaefer wrote:
> > >> On Thu, 11 Feb 2016 21:09:42
The comparisons should be >= since 0x800 and 0x80 require an additional bit
to store.
For the 3 byte case, the existing shift would drop off 2 more bits than
intended.
For the 2 byte case, there should be 5 bits bits in byte 1, and 6 bits in
byte 2.
Signed-off-by: Jason Andryuk
---
Tested in
On Fri, Feb 12, 2016 at 5:53 PM, Ashwin Chaugule
wrote:
> On 12 February 2016 at 11:15, Rafael J. Wysocki wrote:
>> On Fri, Feb 12, 2016 at 5:01 PM, Rafael J. Wysocki wrote:
>>> On Fri, Feb 12, 2016 at 3:10 PM, Peter Zijlstra
>>> wrote:
On Thu, Feb 11, 2016 at 10:52:20AM -0800, Steve
I'm writing a test case for SCHED_DEADLINE, and notice a strange
anomaly. Every so often, a deadline is missed and when I looked into
it, it happened because the sched_yield() had no effect (it didn't end
the previous period and let the start of the next runtime happen on the
end of the old
On Fri, Feb 12, 2016 at 7:51 PM, Greg Kroah-Hartman
wrote:
> On Fri, Feb 12, 2016 at 08:43:34PM +0300, Aleksey Makarov wrote:
>> The function acpi_table_parse() has some problems:
>> 1 It can be called only from __init code
>> 2 It does not pass any data to the handler
>> 3 It just throws out the
On Fri, Feb 12, 2016 at 6:43 PM, Aleksey Makarov
wrote:
> The function acpi_table_parse() has some problems:
> 1 It can be called only from __init code
> 2 It does not pass any data to the handler
> 3 It just throws out the value returned from the handler
So why are those problems?
> These
The patch
regulator: ltc3589: Make IRQ optional
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
With interrupts off it makes no sense to do the long path since we can't
leave the CPU anyway. Also we might end up in a recursion with lockdep.
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/sched/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
We unlock the lock while the interrupts are off. This isn't a problem
now but will get because the migrate_disable() + enable are not
symmetrical in regard to the status of interrupts.
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/softirq.c | 4 +++-
1 file changed, 3 insertions(+), 1
We don't use ru_bh on -RT but we still fork a thread for it and keep it
as a flavour. No more.
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/rcu/tree.c | 6 ++
kernel/rcu/tree.h | 2 ++
2 files changed, 8 insertions(+)
diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
index
With completion using swait and so rawlocks we don't need this anymore.
Further, bisect thinks this patch is responsible for:
|BUG: unable to handle kernel NULL pointer dereference at (null)
|IP: [] sched_cpu_active+0x53/0x70
|PGD 0
|Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
|Dumping
No point in having the migrate disable/enable invocations in all the
macro/inlines. That's just more code for no win as we do a function
call anyway. Move it to the core code and save quite some text size.
text databssdecfilename
11034127 3676912 14901248
On Thu, Feb 11, 2016 at 04:17:55PM -0800, Stephen Boyd wrote:
> On 02/11, Georgi Djakov wrote:
> > 8064 uses SSBI instead of SPMI and we currently do not have any
> > existing regulator support upstream yet. So this driver is not
> > duplicating any existing regulator. We should decide whether to
From: Thomas Gleixner
We currently disable migration across lock acquisition. That includes the part
where we block on the lock and schedule out. We cannot disable migration after
taking the lock as that would cause a possible lock inversion.
But we can be smart and enable migration when we
1 - 100 of 1470 matches
Mail list logo
