AS3935 chipset can detect lightning strikes and reports those back as
events and the estimated distance to the storm.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-distance-as3935 | 19 +
drivers/iio/Kconfig| 1 +
drivers/iio/Makefile
rtl8192ce is disabling for too long the local interrupts during hw
initiatialisation when performing scans
The observable symptoms in dmesg can be:
- underruns from ALSA playback
- clock freezes (tstamps do not change for several dmesg entries until irqs are
finaly reenabled):
[ 250.817669]
Allow drivers to report distance values, but however it is up to
drivers to set scaling for meters, kilometers, etc.
Signed-off-by: Matt Ranostay
---
drivers/iio/industrialio-core.c | 1 +
include/linux/iio/types.h | 1 +
2 files changed, 2 insertions(+)
diff --git
Document compatible string, required and optional DT properties for
AS3935 chipset driver.
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/distance/as3935.txt| 25 ++
1 file changed, 25 insertions(+)
create mode 100644
rtl_ps_enable_nic() is called from loops that will loop until this function
returns true or a
maximum number of retries is performed.
hw_init() returns non-zero on error. In that situation return false to
restore the original design intent to retry hw init when it fails.
Signed-off-by: Olivier
I pointed some folks at this and they wondered why it wasn't in the
kernel Documentation directory. So now it is.
Signed-off-by: Daniel Vetter
Signed-off-by: Michael Ellerman
---
Documentation/ioctl/00-INDEX | 2 +
Documentation/ioctl/botching-up-ioctls.txt | 219
On Fri, Jan 31, 2014 at 5:49 PM, Sören Brinkmann
wrote:
> ping?
Hi Soren,
I'm a bit slow to review patches during the merge window. Thanks for
the doc update. I'll take it in after -rc1 drops.
Regards,
Mik
>
> On Wed, Jan 22, 2014 at 11:48:37AM -0800, Soren Brinkmann wrote:
>> Contradicting
> Right now (on ARM at least but I imagine this is pretty universal), the
> biggest impact on information accuracy for a CPU depends on what the
> other CPUs are doing. The most obvious example is cluster power down.
> For a cluster to be powered down, all the CPUs sharing this cluster must
>
On Thu, 2014-16-01 at 23:53:50 UTC, Cody P Schafer wrote:
> "H_GetPerformanceCounterInfo" (refered to as hv_gpci or just gpci from
> here on) is an interface to retrieve specific performance counters and
> other data from the hypervisor. All outputs have a fixed format (and
> are represented as
On Thu, 2014-16-01 at 23:53:47 UTC, Cody P Schafer wrote:
> Add PMU_RANGE_ATTR() and PMU_RANGE_RESV() (for reserved areas) which
> generate functions to extract the relevent bits from
> event->attr.config{,1,2} for use by sw-like pmus where the
> 'config{,1,2}' values don't map directly to
Peter, Ingo, can we get your ACK on this please?
cheers
On Thu, 2014-16-01 at 23:53:48 UTC, Cody P Schafer wrote:
> Export the swevent hrtimer helpers currently only used in events/core.c
> to allow the addition of architecture specific sw-like pmus.
> Signed-off-by: Cody P Schafer
> ---
>
On Thu, 2014-16-01 at 23:53:49 UTC, Cody P Schafer wrote:
> Signed-off-by: Cody P Schafer
> ---
> arch/powerpc/include/asm/hvcall.h | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/include/asm/hvcall.h
> b/arch/powerpc/include/asm/hvcall.h
> index
On Thu, 2014-16-01 at 23:53:51 UTC, Cody P Schafer wrote:
> 24x7 (also called hv_24x7 or H_24X7) is an interface to obtain
> performance counters from the hypervisor. These counters do not have a
> fixed format/possition and are instead documented in a "24x7 Catalog",
> which is provided by the
On Thu, 2014-16-01 at 23:53:52 UTC, Cody P Schafer wrote:
> This provides a basic link between perf and hv_gpci. Notably, it does
> not yet support transactions and does not list any events (they can
> still be manually composed).
What are the plans for listing?
The manual compose is nice but
On Saturday, February 01, 2014 at 06:03:22 AM, Matt Ranostay wrote:
> Duly noted. Will be fixed in the next rev... mutexs are pointless as you
> say.. only corner case would be if you were changing gain_boost and a event
> came in at the same time. But that wouldn't harm anything except slightly
>
On Sat, 2014-02-01 at 05:21 +0100, Mike Galbraith wrote:
> On Fri, 2014-01-31 at 23:07 +0100, Sebastian Andrzej Siewior wrote:
> > * Mike Galbraith | 2014-01-17 06:17:12 [+0100]:
> >
> > >On Thu, 2014-01-16 at 23:22 -0500, Steven Rostedt wrote:
> > >> On Thu, 16 Jan 2014 04:08:57 +0100
> > >>
I need your assistance to reprofile funds to the tune of 82M USD. Should you be
interested, kindly respond.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Fri, 2014-01-31 at 23:07 +0100, Sebastian Andrzej Siewior wrote:
> * Mike Galbraith | 2014-01-17 06:17:12 [+0100]:
>
> >On Thu, 2014-01-16 at 23:22 -0500, Steven Rostedt wrote:
> >> On Thu, 16 Jan 2014 04:08:57 +0100
> >> Mike Galbraith wrote:
> >>
> >> > On Wed, 2014-01-15 at 20:58 -0500,
pm_runtime_get*() may return -EACCESS to indicate a device does not have
runtime PM enabled. This is the case when the nouveau.runpm parameter is
set to 0, and is not an error in that context. Handle this case without
failure.
Signed-off-by: Alexandre Courbot
---
GK20A's FIFO is compatible with NVE0, but only features 128 channels and
1 runlist.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/Makefile | 1 +
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h| 1 +
drivers/gpu/drm/nouveau/core/engine/fifo/nvea.c| 27
Use abstracted resource query functions, and obtain the IRQ from the
correct bus.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/include/subdev/mc.h | 1 +
drivers/gpu/drm/nouveau/core/subdev/mc/base.c| 43 +++-
2 files changed, 29 insertions(+), 15
Use abstracted resource query functions to allow FB core to handle
both PCI and platform devices.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/subdev/fb/nvc0.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git
Hello i have a sensitive partnership deal/ business transaction i would like to
discuss with you but I do not know if I am talking to the right person, But I
will like you to confirm if you are the owner of this EMAIL ADDRESS and a
proven identity to show you are. All I want is a confirmation
Some chips that use system memory exclusively (e.g. GK20A) do not
expose 2 BAR regions. For them only BAR1 exists, and it should be used
for USERD mapping. Do not map BAR3 if its resource does not exist.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/subdev/bar/base.c | 7
The T124 generation of Tegra GPUs uses the Kepler architecture and can
thus be driven by Nouveau. However, they are declared as platform
devices using the Device Tree, and Nouveau has a very strong dependency
on PCI. This patch makes Nouveau core able to handle platform devices as
well as PCI
Set the correct subdev/engine classes when GK20A (0xea) is probed.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/engine/device/nve0.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nve0.c
Add a clumsy-but-working FB support for GK20A. This chip only uses system
memory, so we allocate a big chunk using CMA and let the existing memory
managers work on it.
A better future design would be to allocate objects directly from system
memory without having to suffer from the limitations of
GK20A's timer is directly attached to the system timer and cannot be
calibrated. Skip the calibration phase on that chip since the
corresponding registers do not exist.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/subdev/timer/nv04.c | 19 +--
1 file
Add support for initializing the priv ring of GK20A. This is done by the
BIOS on desktop GPUs, but needs to be done by hand on Tegra.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/Makefile | 1 +
drivers/gpu/drm/nouveau/core/include/subdev/ibus.h | 1 +
Memory was always allocated for 4096 channels. Change this to allocate
what we actually need according to the number of channels we use.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Remove PCI-dependent code so the FIFO engine can also handle platform
devices.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/engine/fifo/base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/base.c
Hello everyone,
GK20A is the Kepler-based GPU used in the upcoming Tegra K1 chips. The following
patches perform architectural changes to Nouveau that are necessary to support
non-PCI GPUs and add initial support for GK20A. Although the support is still
very basic and more user-space changes will
GK20A does not embed a dedicated COPY engine and thus cannot allocate
the copy channel that nouveau_accel_init() attempts to create. It also
lacks any display hardware, so the creation of a software channel does
not apply neither.
Signed-off-by: Alexandre Courbot
---
Remove PCI-dependent code so the BAR core can also handle platform
devices.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/subdev/bar/base.c | 4 ++--
drivers/gpu/drm/nouveau/core/subdev/bar/nv50.c | 4 ++--
drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c | 15
Adapt the NVC0 BAR driver to make it able to support chips that do not
expose a BAR3. When this happens, BAR1 is then used for USERD mapping
and the BAR alloc() functions is disabled, making GPU objects unable
to rely on BAR for data access and falling back to PRAMIN.
Signed-off-by: Alexandre
Add a nouveau_drm_platform_probe() function that probes a Nouveau
platform device and registers it using drm_platform_init().
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/engine/device/base.c | 34 ++
.../gpu/drm/nouveau/core/include/engine/device.h |
On Friday, January 31, 2014 at 04:38:23 PM, Matt Ranostay wrote:
[...]
> diff --git a/Documentation/devicetree/bindings/iio/distance/as3935.txt
> b/Documentation/devicetree/bindings/iio/distance/as3935.txt new file mode
> 100644
> index 000..af35827
> --- /dev/null
> +++
On Friday, January 31, 2014 at 04:38:22 PM, Matt Ranostay wrote:
The commit message is completely missing, it's entirely unclear what the
intention of this patch is. Please write a commit message !
> Signed-off-by: Matt Ranostay
> ---
> drivers/iio/industrialio-core.c | 1 +
>
On Mon, 13 Jan 2014, Weijie Yang wrote:
> On Mon, Jan 13, 2014 at 2:27 PM, Mateusz Guzik wrote:
> >
> > Newly introduced window:
> >
> > p->swap_map == NULL && (p->flags & SWP_USED)
> >
> > breaks swap_info_get:
> > if (!(p->flags & SWP_USED))
> > goto bad_device;
> >
On Fri, 31 Jan 2014, Zoran Markovic wrote:
> From: Shaibal Dutta
>
> Allow the scheduler to select the best CPU to handle hub initalization
> and LED blinking work. This extends idle residency times on idle CPUs
> and conserves power.
>
> This functionality is enabled when
On Sat, 1 Feb 2014 01:07:29 + "Pearson, Greg" wrote:
> As far as I know the only consequence of dropping a PT_NOTE entry is
> that it would not be available in the crash dump for use in debugging.
> I'm not sure how important this data might be for triage. I'm guessing
> that in cases
On Thu, 9 Jan 2014, Weijie Yang wrote:
> swapoff clear swap_info's SWP_USED flag prematurely and free its resources
> after that. A concurrent swapon will reuse this swap_info while its previous
> resources are not cleared completely.
>
> These late freed resources are:
> - p->percpu_cluster
> -
On Fri, Jan 31, 2014 at 3:34 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Revert commit ef83b0781a73 "PCI: Remove from bus_list and release
> resources in pci_release_dev()" that made some nasty race conditions
> become possible. For example, if a Thunderbolt link is unplugged
>
ping?
On Wed, Jan 22, 2014 at 11:48:37AM -0800, Soren Brinkmann wrote:
> Contradicting to documenation, the notifier callbacks do receive
> the original clock rate in struct clk_notifier_data.old_rate and the new
> frequency struct clk_notifier_data.new_rate, independent of the
> notification
2014-01-31 Max Filippov :
> On Sat, Feb 1, 2014 at 4:54 AM, Florian Fainelli wrote:
>> 2014-01-31 Florian Fainelli :
> Maybe they boot up with gigabit advertisement disabled in their PHY
> and thus they don't see the problem?
>
>> Other drivers do the following:
>>
>> -
On Fri, 2014-01-31 at 16:09 -0500, Waiman Long wrote:
> On 01/31/2014 03:14 PM, Peter Zijlstra wrote:
> > On Fri, Jan 31, 2014 at 01:59:02PM -0500, Waiman Long wrote:
> >> On 01/31/2014 04:26 AM, Peter Zijlstra wrote:
> >>> On Thu, Jan 30, 2014 at 04:17:15PM +0100, Peter Zijlstra wrote:
> The
On Sat, Feb 1, 2014 at 4:54 AM, Florian Fainelli wrote:
> 2014-01-31 Florian Fainelli :
Maybe they boot up with gigabit advertisement disabled in their PHY
and thus they don't see the problem?
> Other drivers do the following:
>
> - connect to the PHY
> -
On 01/31/2014 04:16 PM, Andrew Morton wrote:
> On Fri, 31 Jan 2014 16:06:06 -0700 Greg Pearson wrote:
>
>> Currently, update_note_header_size_elf64() and
>> update_note_header_size_elf32() will add the size
>> of a PT_NOTE entry to real_sz even if that causes real_sz
>> to exceeds max_sz. This
On Fri, Jan 31, 2014 at 03:59:30PM -0500, Trond Myklebust wrote:
> On Thu, 2014-01-30 at 15:38 +, Russell King - ARM Linux wrote:
> > On Thu, Jan 30, 2014 at 06:32:08AM -0800, Christoph Hellwig wrote:
> > > On Thu, Jan 30, 2014 at 02:27:52PM +, Russell King - ARM Linux wrote:
> > > > Yes
On Fri, Jan 31, 2014 at 03:28:10PM -0800, Florian Fainelli wrote:
> - you tell of_mdiobus_register() to look for a reset phandle and have
> a reset controller release the PHY from reset before it tries to probe
> for it, because doing that could avoid doing the PHY out of reset
> sequence in a few
2014-01-31 Florian Fainelli :
>>> Maybe they boot up with gigabit advertisement disabled in their PHY
>>> and thus they don't see the problem?
>>>
Other drivers do the following:
- connect to the PHY
- phydev->supported = PHY_BASIC_FEATURES
- phydev->advertising &=
2014-01-30 Max Filippov :
> On Wed, Jan 29, 2014 at 10:32 PM, Max Filippov wrote:
>> On Wed, Jan 29, 2014 at 9:12 PM, Florian Fainelli
>> wrote:
>>> On Jan 28, 2014 11:01 PM, "Max Filippov" wrote:
On Wed, Jan 29, 2014 at 10:47 AM, Florian Fainelli
wrote:
> Hi Max,
>
On Fri, 2014-01-31 at 15:43 -0800, dormando wrote:
> chpxchg_double()? that's not related to the 62713c4b fix right?
>
> I'll see what I can do.. it's going to take a long time to iterate on this
> though.
Dont know about this commit.
I was more thinking about
Hi Eduardo,
The merge window for 3.14 is now open and I'm wondering if you had a
chance to look at these numbers?
Thanks,
Zoran
On 30 December 2013 12:48, Zoran Markovic wrote:
> Eduardo,
>
>>> What is the workload you're running besides the proprietary heater code?
> I re-did experiments from
From: Shaibal Dutta
Allow the scheduler to select the most appropriate CPU for running the
firmware load timeout routine and delayed routine for firmware unload.
This extends idle residency times and conserves power.
This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected.
Cc:
On Fri, 31 Jan 2014, David Rientjes wrote:
> On Fri, 31 Jan 2014, dormando wrote:
>
> > > CONFIG_SLUB_DEBUG_ON will definitely be slower but can help to identify
> > > any possible corruption issues.
> > >
> > > I'm wondering if you have CONFIG_MEMCG enabled and are actually allocating
> > > slab
2014-01-31 Jason Gunthorpe :
> On Fri, Jan 31, 2014 at 02:24:52PM -0800, Florian Fainelli wrote:
>
>> > This is necessary to support phy's that cannot be autoprobed when
>> > of_mdiobus_register is called. Specifically, my case has the phy in reset
>> > at
>> > of_mdiobus_register, the reset is
On Fri, Jan 31, 2014 at 01:06:13PM -0700, Alex Williamson wrote:
> On Fri, 2014-01-31 at 12:26 -0700, Bjorn Helgaas wrote:
> > On Mon, Jan 20, 2014 at 03:01:52PM -0700, Alex Williamson wrote:
> > > +/*
> > > + * Many Intel PCH root ports do provide ACS-like features to disable peer
> > > + *
On Fri, 31 Jan 2014, dormando wrote:
> > CONFIG_SLUB_DEBUG_ON will definitely be slower but can help to identify
> > any possible corruption issues.
> >
> > I'm wondering if you have CONFIG_MEMCG enabled and are actually allocating
> > slab in a non-root memcg? What does /proc/self/cgroup say?
>
Currently, update_note_header_size_elf64() and
update_note_header_size_elf32() will add the size
of a PT_NOTE entry to real_sz even if that causes real_sz
to exceeds max_sz. This patch corrects the while loop logic
in those routines to ensure that does not happen.
One possible negative side
Quoting Paul Gortmaker (2014-01-21 13:22:30)
> The clk-nomadik.o is built for ARCH_NOMADIK -- which is bool, and
> hence this code is either present or absent. It will never be
> modular, so using module_init as an alias for __initcall can be
> somewhat misleading.
>
> Fix this up now, so that
From: Rafael J. Wysocki
Revert commit ef83b0781a73 "PCI: Remove from bus_list and release
resources in pci_release_dev()" that made some nasty race conditions
become possible. For example, if a Thunderbolt link is unplugged
and then replugged immediately, the pci_release_dev() resulting
The HPET is so amazingly slow that this is barely a win. It adds
complexity, and it scares me a tiny bit to map a piece of crappy
hardware where every userspace program can poke at it (even if said
poking is read-only). Let's just remove it.
This is probably a tiny speedup on kvmclock systems.
On Fri, 31 Jan 2014 16:06:06 -0700 Greg Pearson wrote:
> Currently, update_note_header_size_elf64() and
> update_note_header_size_elf32() will add the size
> of a PT_NOTE entry to real_sz even if that causes real_sz
> to exceeds max_sz. This patch corrects the while loop logic
> in those
On Fri, 31 Jan 2014 16:06:06 -0700 Greg Pearson wrote:
> Currently, update_note_header_size_elf64() and
> update_note_header_size_elf32() will add the size
> of a PT_NOTE entry to real_sz even if that causes real_sz
> to exceeds max_sz. This patch corrects the while loop logic
> in those
From: Shaibal Dutta
Instead of binding the clock gating work to the CPU that scheduled it,
allow the scheduler to select the best CPU to handle it. This extends
idle residency times and conserves power.
This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected.
Cc: Chris Ball
*sigh*. Feel free to make the subject less dumb if you apply this.
--Andy
On Fri, Jan 31, 2014 at 3:04 PM, Andy Lutomirski wrote:
>
> This has probably been broken since the VVAR page was introduced.
> The symptom is that BIOS crud can be left behind where userspace can
> see it. (I saw this
On Fri, Jan 24, 2014 at 10:48:40AM -0800, Tim Kryger wrote:
> On Wed, Jan 8, 2014 at 4:54 PM, Christian Daudt wrote:
> > On Wed, Jan 8, 2014 at 4:28 PM, Tim Kryger wrote:
> >> On Wed, Jan 8, 2014 at 3:38 PM, Christian Daudt wrote:
> >>> On Tue, Jan 7, 2014 at 10:53 AM, Tim Kryger wrote:
>
On Fri, 31 Jan 2014 22:30:14 +
Al Viro wrote:
> On Fri, Jan 31, 2014 at 04:32:31PM -0500, Jeff Layton wrote:
>
> > done_path_create(_path, new_dentry);
> > + path_put(_path);
>
> ... and the filesystem in question isn't pinned anymore, so it can be
> unmounted, except that
>
> >
On Thu, Jan 30, 2014 at 11:43 AM, Stefani Seibold wrote:
> Am Donnerstag, den 30.01.2014, 10:21 -0800 schrieb Andy Lutomirski:
>> On Thu, Jan 30, 2014 at 2:49 AM, wrote:
>> > From: Stefani Seibold
>> >
>> > This patch add the support for the IA32 Emulation Layer to run 32 bit
>> > applications
> -Original Message-
> From: Network Nut [mailto:sillyst...@gmail.com]
> Sent: Friday, January 31, 2014 5:00 PM
> To: 'Clemens Ladisch'
> Cc: 'Austin S. Hemmelgarn'; linux-kernel@vger.kernel.org
> Subject: RE: WaitForMultipleObjects/etc. In Kernel
> > -Original Message-
> > From:
On Friday 31 January 2014 05:15 PM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Jan 31, 2014 at 02:20:48PM -0500, Santosh Shilimkar wrote:
>
> [ snip ]
>
>>> note that because of pm_runtime_set_active() that first
>>> pm_runtime_get_sync() in probe() will simply increase the reference
>>> counter
This has probably been broken since the VVAR page was introduced.
The symptom is that BIOS crud can be left behind where userspace can
see it. (I saw this with QEMU.)
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/vmlinux.lds.S | 5 +
1 file changed, 5 insertions(+)
diff --git
A release candidate Git v1.9-rc2 is now available for testing at
the usual places.
I've heard rumours that various third-party tools do not like the
two-digit version numbers (e.g. "Git 2.0") and started barfing left
and right when the users install v1.9-rc1. While it is tempting to
laugh at
On Fri, 31 Jan 2014 12:23:45 -0600 Alex Thorlton wrote:
> This patch adds a VM_INIT_DEF_MASK, to allow us to set the default flags
> for VMs. It also adds a prctl control which alllows us to set the THP
> disable bit in mm->def_flags so that VMs will pick up the setting as
> they are created.
>
> -Original Message-
> From: Clemens Ladisch [mailto:clem...@ladisch.de]
> Sent: Friday, January 31, 2014 4:54 PM
> To: Network Nut
> Cc: 'Austin S. Hemmelgarn'; linux-kernel@vger.kernel.org
> Subject: Re: WaitForMultipleObjects/etc. In Kernel
>
> Network Nut wrote:
> >> Assuming that
On Fri, Jan 31, 2014 at 02:24:52PM -0800, Florian Fainelli wrote:
> > This is necessary to support phy's that cannot be autoprobed when
> > of_mdiobus_register is called. Specifically, my case has the phy in reset at
> > of_mdiobus_register, the reset is only released once the ethernet driver
> >
Network Nut wrote:
>> Assuming that you're porting to mainline distributions (and not embedded
>> devices), named SHM segments are accessible (providing the accessing
>> process has correct permissions) under /dev/shm. You just need to make
>> sure that you create the segment with the right
On Fri, 31 Jan 2014 12:23:43 -0600 Alex Thorlton wrote:
> This reverts commit 8e72033f2a489b6c98c4e3c7cc281b1afd6cb85cm, and adds
'm' is not a hex digit ;)
> in code to fix up any issues caused by the revert.
>
> The revert is necessary because hugepage_madvise would return -EINVAL
> when
On Fri, Jan 31, 2014 at 09:18:21AM -0700, Stephen Warren wrote:
> On 01/31/2014 03:23 AM, Maxime Ripard wrote:
> > Make the existing users of devm_spi_register_master use the
> > devm_spi_alloc_master function to avoid leaking memory.
>
> > diff --git a/drivers/spi/spi-tegra114.c
On Fri, Jan 31, 2014 at 12:48:09PM +, Mark Brown wrote:
> On Fri, Jan 31, 2014 at 11:55:50AM +0100, Maxime Ripard wrote:
>
> > + master = devm_spi_alloc_master(>dev, sizeof(struct sun6i_spi));
> > + if (!master) {
> > + dev_err(>dev, "Unable to allocate SPI Master\n");
> > +
On Fri, Jan 31, 2014 at 12:12:15PM +, Mark Brown wrote:
> On Fri, Jan 31, 2014 at 11:23:09AM +0100, Maxime Ripard wrote:
>
> > This patchset introduces a devm_spi_alloc_master to the spi core. While
> > most of
> > the drivers have a spi_master_put call in the probe, a lot of them using the
From: Shaibal Dutta
Allow the scheduler to select the best CPU to handle hub initalization
and LED blinking work. This extends idle residency times on idle CPUs
and conserves power.
This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected.
Cc: Greg Kroah-Hartman
Cc: Alan Stern
On 01/31/2014 10:45 AM, Linus Torvalds wrote:
> On Fri, Jan 31, 2014 at 10:06 AM, H. Peter Anvin wrote:
>>
>> My feeling is that {get,put}_compat_timespec() should at the very least
>> have leading underscores to flag it as a low-level function, but better
>> suggestions would be appreciated.
>
> -Original Message-
> From: Austin S. Hemmelgarn [mailto:ahferro...@gmail.com]
> Sent: Friday, January 31, 2014 11:05 AM
> To: Network Nut; 'Clemens Ladisch'
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: WaitForMultipleObjects/etc. In Kernel
> >> Network Nut wrote:
> > I was thinking
Recent changes to retry on ESTALE in linkat
(commit 442e31ca5a49e398351b2954b51f578353fdf210)
introduced a mountpoint reference leak and a small memory
leak in case a filesystem link operation returns ESTALE
which is pretty normal for distributed filesystems like
lustre, nfs and so on.
Free
Hi,
I would like to attend the LSF/MM Summit and discuss about the ongoing work
on developing Memory Power Management technology in the Linux kernel. Main
memory can consume a significant amount of power in the system (upto even 40%).
Hence, memory is the next big target for power-management,
2014-01-31 Jason Gunthorpe :
> This describes a compatible entry of the form:
> ethernet-phy-id,
> Which is modelled after the PCI structured compatible entry
> (pci,...RR)
>
> If present the OF core will be able to use this information to
> directly create the correct
On Fri, Jan 31, 2014 at 04:32:31PM -0500, Jeff Layton wrote:
> done_path_create(_path, new_dentry);
> + path_put(_path);
... and the filesystem in question isn't pinned anymore, so it can be
unmounted, except that
> if (delegated_inode) {
> error =
i2o_cfg_compat_ioctl(I2OGETIOPS) locks i2o_cfg_mutex and then calls
i2o_cfg_ioctl(I2OGETIOPS) that locks i2o_cfg_mutex as well.
A deadlock is guaranteed.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/message/i2o/i2o_config.c | 4
Hi,
2014-01-31 Jason Gunthorpe :
> This makes the generic of_mdiobus_register parse the DT compatible string for
> the pattern ethernet-phy-id.. If present it should be a value that
> matches the phy-id register normally readable through MDIO.
>
> When the ID is given the phy autoprobing
On Wed, 29 Jan 2014 22:24:11 -0600 Rob Landley wrote:
> On 01/29/14 18:27, Henrik Austad wrote:
> > Some of the 00-INDEX files are somewhat outdated and some folders does not
> > contain 00-INDEX at all. Only outdated (with the notably exception of
> > spi) indexes are touched here, the 169
* Pavel Vasilyev | 2014-01-27 13:42:29 [+0400]:
>3) 3.10 not works at all, even without -RT patches;
I bootet 3.10.20-rt17 some time ago on an Intel Atom with EG20T chipset
(with those pch driver like pch_udc for usb gadget, pch_uart for serial
and so on). That on _was_ working. I can share the
Hi,
On Fri, Jan 31, 2014 at 02:20:48PM -0500, Santosh Shilimkar wrote:
[ snip ]
> > note that because of pm_runtime_set_active() that first
> > pm_runtime_get_sync() in probe() will simply increase the reference
> > counter without calling my ->runtime_resume() callback, which is exactly
> >
On Fri, Jan 31, 2014 at 04:13:19PM -0500, Alan Stern wrote:
> On Fri, 31 Jan 2014, Felipe Balbi wrote:
>
> > probe()
> > {
> > ...
> >
> > clk_get(dev, "fck");
> > clk_prepare(clk);
> > clk_enable(clk);
> > pm_runtime_set_active(dev);
> > pm_runtime_enable(dev);
> >
On Fri, Jan 31, 2014 at 4:03 PM, Heiko Stübner wrote:
> On Monday, 20. January 2014 16:41:43 Heiko Stübner wrote:
>> This series enables the use of the additional cores on Rockchip
>> Cortex-A9 SoCs.
>
> So, two weeks without any general complaints, but I guess part of the more
> general patches
* Joakim Hernberg | 2014-01-29 15:30:43 [+0100]:
>On Sat, 25 Jan 2014 14:45:19 +0100
>Sebastian Andrzej Siewior wrote:
>
>> Dear RT folks!
>>
>> I'm pleased to announce the v3.12.8-rt11 patch set.
>
>So far the only thing seen in the kernel buffer on this 64b system are a
>smattering of "NOHZ:
* Mike Galbraith | 2014-01-17 06:17:12 [+0100]:
>On Thu, 2014-01-16 at 23:22 -0500, Steven Rostedt wrote:
>> On Thu, 16 Jan 2014 04:08:57 +0100
>> Mike Galbraith wrote:
>>
>> > On Wed, 2014-01-15 at 20:58 -0500, Steven Rostedt wrote:
>> >
>> >
>> > > 3.2.53-rt76-rc1 stable review patch.
>> >
On Monday, 20. January 2014 16:41:43 Heiko Stübner wrote:
> This series enables the use of the additional cores on Rockchip
> Cortex-A9 SoCs.
So, two weeks without any general complaints, but I guess part of the more
general patches could use an ack.
Going forward, what would be best way to
On Fri, Jan 31 2014, Hugh Dickins wrote:
> On Thu, 16 Jan 2014, Kent Overstreet wrote:
> >
> > Ok, I reread the code and figured it out - the analagous change also has to
> > be
> > made in __blk_segment_map_sg(). I'll mail out a patch for this tomorrow
> > after
> > I've stared at the code
1 - 100 of 1054 matches
Mail list logo
