From: Stanislav Fomichev
This option highlights tasks (using different color) that run more than
given duration or tasks with given name.
Signed-off-by: Stanislav Fomichev
Acked-by: Ingo Molnar
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Cc:
Hi,
> +#define _P_DATA(bank, pin, name, sfx)
> \
> + PINMUX_DATA(name##_DATA, name##_PMC_0, name##_PIPC_0, \
> + name##_PIBC_1, name##_PBDC_1)
> +
> +#define _P_FN(n, fn, pfcae, pfce, pfc)
On Tue, Dec 17 2013, Rafael Aquini wrote:
> After the locking semantics for the SysV IPC API got improved, a couple of
> IPC_RMID race windows were opened because we ended up dropping the
> 'kern_ipc_perm.deleted' check performed way down in ipc_lock().
> The spotted races got sorted out by
From: Arnaldo Carvalho de Melo
There are no references to that array anywhere, it is only used to try
a series of "binary" types in turn, always setting dso->data_type till
one can be used.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Mike Galbraith
Cc:
From: Stanislav Fomichev
Add PID to the figures of CPU usage timechart.
Signed-off-by: Stanislav Fomichev
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Cc: Ramkumar Ramachandra
Link:
From: Arnaldo Carvalho de Melo
Using dso__binary_type_file() make it look like this function will
return a file, not just its filename, so rename it to:
dso__read_binary_type_filename()
to make its purpose clear, just like we have:
dso__read_running_kernel_build_id()
Cc:
P2M is not available for PVH. Fortunatly for us the
P2M code already has mostly the support for auto-xlat guest thanks to
commit 3d24bbd7dddbea54358a9795abaf051b0f18973c
"grant-table: call set_phys_to_machine after mapping grant refs"
which: "
introduces set_phys_to_machine calls for
On Tue, Dec 17, 2013 at 2:29 PM, Linus Torvalds
wrote:
> On Tue, Dec 17, 2013 at 7:05 AM, Josh Boyer wrote:
>>
>> Ping? I sent this 2 months ago and never got a reply. We're still
>> carrying it in Fedora.
>
> Ok, I took it directly. Thanks,
Thanks!
josh
--
To unsubscribe from this list:
I hope it is OK to ask a newbie question here. I'm trying to better
understand the boot process. I can't seem to find where in the kernel
sources the cpu_active_mask (defined in include/linux/cpumask.h) gets
populated. I can see that it does get populated as it brings cpus online
but it is not
From: Mukesh Rathor
Which is a PV guest with auto page translation enabled
and with vector callback. It is a cross between PVHVM and PV.
The Xen side defines PVH as (from docs/misc/pvh-readme.txt,
with modifications):
"* the guest uses auto translate:
- p2m is managed by Xen
- pagetables are
The patches, also available at
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/pvh.v11
implements the neccessary functionality to boot a PV guest in PVH mode.
This blog has a great description of what PVH is:
From: Stanislav Fomichev
Add -t switch to sort CPUs topologically.
Signed-off-by: Stanislav Fomichev
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Cc: Ramkumar Ramachandra
Link:
From: Namhyung Kim
Those functions stringify filter arguments.
As caller of those functions handles NULL string properly, it seems that
it's enough to return NULL rather than calling die().
Signed-off-by: Namhyung Kim
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
On Tue, 17 Dec 2013, Michal Hocko wrote:
> > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > index c72b03bf9679..fee25c5934d2 100644
> > > --- a/mm/memcontrol.c
> > > +++ b/mm/memcontrol.c
> > > @@ -2692,7 +2693,8 @@ static int __mem_cgroup_try_charge(struct mm_struct
> > > *mm,
> > >
From: Mukesh Rathor
Most of the functions in page.h are prefaced with
if (xen_feature(XENFEAT_auto_translated_physmap))
return mfn;
Except the mfn_to_local_pfn. At a first sight, the function
should work without this patch - as the 'mfn_to_mfn' has
a similar check. But
On Tue, Dec 17, 2013 at 03:11:47PM -0500, Johannes Weiner wrote:
> On Tue, Dec 17, 2013 at 04:08:08PM +, Mel Gorman wrote:
> > On Tue, Dec 17, 2013 at 10:38:29AM -0500, Johannes Weiner wrote:
> > > On Tue, Dec 17, 2013 at 11:13:52AM +, Mel Gorman wrote:
> > > > On Mon, Dec 16, 2013 at
On Tue, 2013-12-17 at 14:05 -0500, Steven Rostedt wrote:
> On Tue, 17 Dec 2013 12:29:30 -0600
> Tom Zanussi wrote:
>
> > > Tom,
> > > is git://git.yoctoproject.org/linux-yocto-contrib
> > > tzanussi/event-triggers-v11 the right starting point ?
> > >
> >
> > Yep, that's the last iteration - I
From: Mukesh Rathor
In xen_add_extra_mem() we can skip updating P2M as it's managed
by Xen. PVH maps the entire IO space, but only RAM pages need
to be repopulated.
Signed-off-by: Mukesh Rathor
Signed-off-by: Konrad Rzeszutek Wilk
---
arch/x86/xen/setup.c | 19 +--
1 file
From: Arnaldo Carvalho de Melo
Hi Ingo,
Please consider pulling,
Regards,
- Arnaldo
The following changes since commit b283d2f3b74bc98174e8453c0be41dfcda3cae1b:
Merge tag 'perf-core-for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
(2013-12-16
From: Mukesh Rathor
.. which are surprinsingly small compared to the amount for PV code.
PVH uses mostly native mmu ops, we leave the generic (native_*) for
the majority and just overwrite the baremetal with the ones we need.
We also optimize one - the TLB flush. The native operation would
On 12/17/2013 01:10 PM, David Timothy Strauss wrote:
> System specs:
> * Fedora 19 with the 3.11.10-200.fc19.x86_64 kernel (just the stock RPM)
> * Bare-metal servers with 128GB RAM split between two NUMA regions,
> each region with one hex-core processor
> * More than 700 processes, a couple
From: Mukesh Rathor
As we do not have yet a mechanism for that.
Signed-off-by: Mukesh Rathor
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/cpu_hotplug.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/xen/cpu_hotplug.c b/drivers/xen/cpu_hotplug.c
index
On Tue, Dec 17, 2013 at 11:05:10AM -0600, Rich Johnston wrote:
> This patch stands alone and has been committed.
>
> Thanks
> --Rich
>
> commit ca692f162d36c871c9c1b6169136b2c70503f2d8
> Author: Namjae Jeon
> Date: Sun Dec 8 14:11:30 2013 +
>
> xfsprog: xfsio: Add support
From: Stanislav Fomichev
Print all CPUs, even if there were no events (use perf header to get
number of CPUs).
This is required to support topology in the next patch.
Signed-off-by: Stanislav Fomichev
Cc: Ingo Molnar
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
From: Borislav Petkov
Move debugfs.* to api/fs/. We have a common tools/lib/api/ place where
the Makefile lives and then we place the headers in subdirs.
For example, all the fs-related stuff goes to tools/lib/api/fs/ from
which we get libapikfs.a (acme got almost the naming he wanted :-)) and
From: Mukesh Rathor
PVH allows PV linux guest to utilize hardware extended capabilities,
such as running MMU updates in a HVM container.
The Xen side defines PVH as (from docs/misc/pvh-readme.txt,
with modifications):
"* the guest uses auto translate:
- p2m is managed by Xen
- pagetables are
From: Mukesh Rathor
The VCPU bringup protocol follows the PV with certain twists.
>From xen/include/public/arch-x86/xen.h:
Also note that when calling DOMCTL_setvcpucontext and VCPU_initialise
for HVM and PVH guests, not all information in this structure is updated:
- For HVM guests, the
Today it is there is no protection around pciehp_enable_slot() and
pciehp_disable_slot() to ensure that they complete before another
hot-plug operation can be done on that particular slot.
This patch introduces the slot->hotplug_lock to ensure that any
hotplug operations (add / remove) complete
On Tue, 17 Dec 2013, Sasha Levin wrote:
> I'm still seeing warnings with this patch applied:
Looks like this is related to some device release mechanism that frees
twice?
I do not see any kmem_cache management functions in the backtrace and
therefore would guess that this is not the same issue.
Today, this is how all the hotplug and unplug events work:
Hotplug / Removal needs to be done
=> Set slot->state (protected by slot->lock) to either
POWERON_STATE (for enabling) or POWEROFF_STATE (for disabling).
=> Submit the work item for pciehp_power_thread() to slot->wq.
Problem:
On Tue, Dec 17, 2013 at 05:35:46PM +, Moore, Robert wrote:
> I'm not sure what version of ACPICA you are looking at, but in the master git
> tree for ACPICA, the file accommon.h includes "acutils.h".
This is the version in the latest git tree for the Linux kernel.
- Josh Triplett
> >
Enabled the Link state notifications unconditionaly. Enable the
presence detection notification only if attention button is absent.
This was discussed at this thread:
http://marc.info/?t=13861101431=1=2
Signed-off-by: Rajat Jain
Signed-off-by: Guenter Roeck
---
v3: * created by splitting
From: Alexey Khoroshilov
Date: Sat, 14 Dec 2013 02:56:09 +0400
> + _net("CONNECT EXCL old %d on TRANS %d",
> + conn->debug_id, conn->trans->debug_id);
Please do not add more of these ad-hoc kernel log tracing entries.
Thanks.
--
To unsubscribe from this list: send
Hello Sander,
Tuesday, December 17, 2013, 10:45:48 AM, you wrote:
> Tuesday, December 17, 2013, 3:17:50 AM, you wrote:
>> Hi Sander,
>> On Mon, Dec 16, 2013 at 11:56 PM, Sander Eikelenboom
>> wrote:
>>>
>>> Monday, December 16, 2013, 12:37:47 PM, you wrote:
>>>
On 12/16/2013 12:22 PM,
On Tue, Dec 17, 2013 at 04:08:08PM +, Mel Gorman wrote:
> On Tue, Dec 17, 2013 at 10:38:29AM -0500, Johannes Weiner wrote:
> > On Tue, Dec 17, 2013 at 11:13:52AM +, Mel Gorman wrote:
> > > On Mon, Dec 16, 2013 at 03:25:07PM -0500, Johannes Weiner wrote:
> > > > On Fri, Dec 13, 2013 at
On Tue, 2013-12-17 at 11:03 -0700, Bjorn Helgaas wrote:
> On Tue, Dec 10, 2013 at 11:48:45AM -0700, Alex Williamson wrote:
> >...
> > + pci_read_config_dword(dev->bus->self, pos2 + PCI_VC_PORT_REG1, );
> > + evcc = reg1 & PCI_VC_REG1_EVCC;
>
> I think PCI_VC_PORT_REG1 and PCI_VC_PORT_REG2 are
We need future link up events for hot-add, thus don't disable
the link permanently during device removal. Also, remove the static
functions that are now left unused.
Signed-off-by: Rajat Jain
Signed-off-by: Guenter Roeck
---
v3: no change, created by splitting the patch v2 [2/4]
v2: (non
Spinlocks even in structures require to be properly initialized.
Signed-off-by: Steven Rostedt
Index: linux-rt.git/kernel/sched/deadline.c
===
--- linux-rt.git.orig/kernel/sched/deadline.c
+++ linux-rt.git/kernel/sched/deadline.c
Disable the link notification (in addition to presence detect
notifications) across the slot reset since it could potentialy flap
the link and we don't want to treat it as hot unplug followed by a
hotplug.
Signed-off-by: Rajat Jain
Signed-off-by: Guenter Roeck
---
v3: * created by splitting the
On Mon, Dec 16 2013, Kent Overstreet wrote:
> Jens - small pile of bcache fixes. I've been slacking on the writeback fixes
> but
> those definitely need to get into 3.13:
>
> The following changes since commit c86949486d41d9e7d7681fc72923555114fd702f:
>
> bcache: defensively handle format
A lot of systems do not have the fancy buttons and LEDs, and instead
want to rely only on the Link state change events to drive the hotplug
and removal state machinery.
(http://www.spinics.net/lists/hotplug/msg05802.html)
This patch adds support for that functionality. Here are the details
about
Remove unused Samsung-specific machine include and Kconfig
dependency on S3C.
Signed-off-by: Matt Porter
Reviewed-by: Markus Mayer
Reviewed-by: Tim Kryger
---
drivers/usb/gadget/Kconfig | 7 +++
drivers/usb/gadget/s3c-hsotg.c | 2 --
2 files changed, 3 insertions(+), 6 deletions(-)
On Tue, Dec 17, 2013 at 02:40:02PM -0500, David Miller wrote:
> From: Nicolas Dichtel
> Date: Fri, 13 Dec 2013 10:06:35 +0100
>
> > The upstream commit bb8140947a24 ("ip6tnl: allow to use rtnl ops on fb
> > tunnel")
> > (backported into linux-3.10.y) left a bug which was fixed upstream by
Enable support for the dwc2 binding.
Signed-off-by: Matt Porter
---
drivers/usb/gadget/s3c-hsotg.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/s3c-hsotg.c b/drivers/usb/gadget/s3c-hsotg.c
index db797f2..cbfbf41 100644
--- a/drivers/usb/gadget/s3c-hsotg.c
+++
Hello,
This patch set enables the use of PCI Express link up and link down events
for Hotplug or Unplug. Resending the patch after taking care of review
comments, splitting patch into multiple smaller patches, and incorporating
the conclusions drawn from the discussion here:
It does not make much sense to refuse to disable a slot if an
adapter is not present or the latch is open. If an adapter is not
present, it provides an even better reason to disable the device
slot.
This is specially a problem for link state hot-plug, because some
ports use in band mechanism for
3.5.7.28 -stable review patch. If anyone has any objections, please let me
know.
--
From: Trond Myklebust
commit c97cf606e43b85a6cf158b810375dd77312024db upstream.
If the DELEGRETURN errors out with something like NFS4ERR_BAD_STATEID
then there is no recovery possible. Just
On Tue, 2013-12-17 at 16:48 +0800, Li Yang wrote:
> On Wed, Dec 11, 2013 at 2:33 AM, Scott Wood wrote:
> > On Tue, 2013-12-10 at 18:33 +0800, Hongbo Zhang wrote:
> >> Scott,
> >> This issue is due to the non-continuous MPIC register, I think there is
> >> two ways to fix it.
> >>
> >> The first
This adds a pair of APIs that allows the generic PHY subsystem to
provide information on the PHY bus width. The PHY provider driver may
use phy_set_bus_width() to set the bus width that the PHY supports.
The controller driver may then use phy_get_bus_width() to fetch the
PHY bus width in order to
On Tue, Dec 17, 2013 at 11:27:29AM -0800, Linus Torvalds wrote:
> On Tue, Dec 17, 2013 at 11:21 AM, Paul E. McKenney
> wrote:
> >
> > Looks like xadd() is x86-specific, but this is common code. One
> > approach would be to do xadd() for other arches, another approach
> > would be to make .rw be
dwc2/s3c-hsotg require a single clock to be specified and optionally
a generic phy. On the s3c-hsotg driver old style USB phy support is
present as a fallback so the generic phy properties are optional.
Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
---
On Tue, Dec 17, 2013 at 10:53:34AM -0800, Dirk Brandewie wrote:
> Hi All,
>
> I would like to see what is required to update intel_pstate in the stable
> trees. Some of the patches do NOT meet the all the rules in
> stable_kernel_rules.txt.
Then there's not much we can do, right? Why do you
Em Tue, Dec 17, 2013 at 09:02:36AM +0900, Namhyung Kim escreveu:
> On Mon, 16 Dec 2013 09:40:51 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Dec 16, 2013 at 01:49:11PM +0900, Namhyung Kim escreveu:
> >> On Fri, 13 Dec 2013 11:52:04 -0300, Arnaldo Carvalho de Melo wrote:
> >> > All the rest
Hello,
This patch set enables the use of PCI Express link up and link down events
for Hotplug or Unplug. Resending the patch after taking care of review
comments, splitting patch into multiple smaller patches, and incorporating
the conclusions drawn from the discussion here:
Adds support for the generic PHY subsystem. Generic PHY
support is probed and then the driver falls back to checking
for an old style USB PHY and pdata if not found.
Signed-off-by: Matt Porter
---
drivers/usb/gadget/s3c-hsotg.c | 55 ++
1 file changed, 39
debug_print_object+
0x8d/0xb0()
[ 24.900482] ODEBUG: free active (active state 0) object type: timer_list
hint: delay
ed_work_timer_fn+0x0/0x20
[ 24.900482] Modules linked in:
[ 24.900482] CPU: 12 PID: 3654 Comm: kworker/12:1 Tainted: GW
3.13.0-rc4-n
ext-20131217-sasha-00013-ga878504-dirty
This way it will be more difficult to change the declaration in one
place, but not the other.
In addition, the change allows to use the binding for pxa-gpio on
other PXA CPUs.
Signed-off-by: Sergei Ianovich
CC: Daniel Mack
CC: Arnd Bergmann
---
v2..v3
* no changes
v1..v2
* drop
Hello Greg,
Just a reminder to let you know this patch fixes a bug in the at91 ohci
driver
which appenrently showed up in 3.13-rc1 release, but is caused by bad
assumptions on platform device resources order.
Without this patch the ohci usb host controller is completely unusable
on at91
Hi Mel,
On Tue, Dec 17, 2013 at 04:48:18PM +, Mel Gorman wrote:
> This series is currently untested and is being posted to sync up discussions
> on the treatment of page cache pages, particularly the sysv part. I have
> not thought it through in detail but postings patches is the easiest way
On Tue, Dec 17, 2013 at 10:27:33AM -0800, Kees Cook wrote:
> This makes sure format strings cannot leak into the printk call via the
> constructed buffer.
>
> Signed-off-by: Kees Cook
> ---
> drivers/scsi/esas2r/esas2r_log.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Why is
Add a driver for the internal Broadcom Kona USB 2.0 PHY found
on the BCM281xx family of SoCs.
Signed-off-by: Matt Porter
---
drivers/phy/Kconfig | 6 ++
drivers/phy/Makefile| 1 +
drivers/phy/phy-bcm-kona-usb2.c | 158
3 files
Reorder backplane resources by start address.
Reorder backplane attributes alphabetically.
Signed-off-by: Sergei Ianovich
---
v2..v3
* new patch
.../devicetree/bindings/misc/lp8x4x-bus.txt| 8 ++--
Documentation/misc-devices/lp8x4x_bus.txt | 3 ++
Changes since v6:
- Drop dependency on the Exynos generic phy conversion series
- Bring back original patch that converts s3c-hsotg to use the
generic phy layer with a fall back to the old usb style phy
support.
Changes since v5:
- tweak s3c-hsotg
Adds support for querying the phy bus width from the generic phy
subsystem. Configure UTMI bus width in GUSBCFG based on this value.
Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
---
drivers/usb/gadget/s3c-hsotg.c | 14 +-
drivers/usb/gadget/s3c-hsotg.h | 1 +
2
From: Sebastian Hesselbarth
Date: Fri, 13 Dec 2013 10:20:24 +0100
> This is v2 of the ethernet PHY power optimization patches to reduce
> power consumption of network PHYs with link that are either unused or
> the corresponding netdev is down.
>
> Compared to the last version, this patch set
This patch enumerates parallel modules in expansion slots and exposes
model numbers via sysfs.
Signed-off-by: Sergei Ianovich
---
v2..v3
* no changes (except number 13/16 -> 18/21)
v0..v2
* use device tree
* use devm helpers where possible
The patch adds support for 3 additional LP-8x4x built-in serial
ports.
The device can also host up to 8 extension cards with 4 serial ports
on each card for a total of 35 ports. However, I don't have
the hardware to test extension cards, so they are not supported, yet.
Signed-off-by: Sergei
Status of I-8041 32 digital output channels can be managed via
sysfs now.
http://www.icpdas.com/products/Remote_IO/i-8ke/i-8041w.htm
Signed-off-by: Sergei Ianovich
---
v2..v3
v0..v2
* no changes (except number 14/16 -> 19/21)
Documentation/misc-devices/lp8x4x_bus.txt | 4 ++
Status of I-8042 16 digital output channels can be managed via
sysfs.
Status of I-8042 16 digital input channels can be read via sysfs.
http://www.icpdas.com/products/Remote_IO/i-8ke/i-8042w.htm
Signed-off-by: Sergei Ianovich
---
v2..v3
v0..v2
* no changes (except number 15/16 ->
ICP DAS LP-8x4x contains FPGA chip. The chip functions as a interrupt
source providing 16 additional interrupts among other things. The
interrupt lines are muxed to a GPIO pin. GPIO pins are in turn muxed
to a CPU interrupt line.
Until pxa is completely converted to device tree, it is impossible
Status of I-8042 4 analog output channels can be managed via
sysfs.
http://www.icpdas.com/root/product/solutions/remote_io/rs-485/i-8k_i-87k/i-8024w.html
Signed-off-by: Sergei Ianovich
---
v2..v3
* use usleep_range instead of custom nsleep
* number change (16/16 -> 21/21)
v0..v2
pxa2xx-uart was a separate uart platform driver. It was declaring
the same device names and numbers as 8250 driver. As a result,
it was impossible to use 8250 driver on PXA SoCs.
Upon closer examination pxa2xx-uart turned out to be a clone of
8250_core driver.
Workaround for Erratum #19
Non-dts implementation supply required DMA channel numbers as
IORESOURCE_DMA. We can also get them from the device tree, if it
is present.
This patch updates device tree with the proper dmaengine-based
"marvell,pdma-1.0" DMA.
There is no actual data handling in this patch, because the existing
Signed-off-by: Sergei Ianovich
---
v2..v3
* new patch
.../devicetree/bindings/misc/lp8x4x-bus.txt| 2 ++
Documentation/misc-devices/lp8x4x_bus.txt | 3 +++
arch/arm/boot/dts/pxa27x-lp8x4x.dts| 1 +
drivers/misc/lp8x4x_bus.c | 26
Signed-off-by: Sergei Ianovich
---
v2..v3
* use usleep_range instead of custom nsleep
* number change (07/16 -> 09/21)
v0..v2
* use device tree
* use devm helpers where possible
.../devicetree/bindings/rtc/rtc-ds1302.txt | 14 +++
arch/arm/boot/dts/pxa27x-lp8x4x.dts
The existing PXA MMC driver cannot get DMA channels in a proper
way from the respective device tree binding.
This patch provides temporary workaround which allows using the
existing driver in DT machines by pointing to the proper
dmaengine-based "marvell,pdma-1.0" DMA.
Even though the new DMA
at24c128 write protection is implemented by a separate GPIO line.
EEPROM driver doesn't provide this option, so we implement it
in the board-specific device.
Signed-off-by: Sergei Ianovich
---
v2..v3
* new patch
.../devicetree/bindings/misc/lp8x4x-bus.txt| 3 ++
From: Nicolas Dichtel
Date: Fri, 13 Dec 2013 10:06:35 +0100
> The upstream commit bb8140947a24 ("ip6tnl: allow to use rtnl ops on fb
> tunnel")
> (backported into linux-3.10.y) left a bug which was fixed upstream by commit
> 1e9f3d6f1c40 ("ip6tnl: fix use after free of fb_tnl_dev").
>
> The
On 12/17/2013 02:03 PM, Rafael Aquini wrote:
> After the locking semantics for the SysV IPC API got improved, a couple of
> IPC_RMID race windows were opened because we ended up dropping the
> 'kern_ipc_perm.deleted' check performed way down in ipc_lock().
> The spotted races got sorted out by
This patch implements probing for the bus and reporting the number
of available expansion slots.
Signed-off-by: Sergei Ianovich
---
v2..v3
* fixed goto after bus_register
* number change (11/16 -> 13/21)
v0..v2
* use device tree
* use devm helpers where possible
Signed-off-by: Sergei Ianovich
CC: Daniel Mack
CC: Arnd Bergmann
---
v2..v3
v1..v2
* no changes
arch/arm/boot/dts/pxa27x.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index d7c5d72..44df554 100644
---
Two review comments are not finally settled:
1. Use of new DMA
My best guess is to split the patch in two, so that Daniel could easily
revert the workaround, once a solution is ready.
2. Device tree representation
I've put extbus into platform include file, since the bus is platform-
specific,
On Tue, Dec 17, 2013 at 11:33 AM, Betty Dall wrote:
> On Mon, 2013-12-16 at 12:51 -0700, Bjorn Helgaas wrote:
>> On Fri, Dec 13, 2013 at 4:16 PM, Betty Dall wrote:
>> > On Fri, 2013-12-13 at 15:35 -0700, Bjorn Helgaas wrote:
>> >> On Fri, Dec 13, 2013 at 8:41 AM, Betty Dall wrote:
>> >> > There
Signed-off-by: Sergei Ianovich
CC: Daniel Mack
CC: Arnd Bergmann
---
v2..v3
v1..v2
* no changes
arch/arm/boot/dts/pxa2xx.dtsi | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/pxa2xx.dtsi b/arch/arm/boot/dts/pxa2xx.dtsi
index a5e90f0..3419f87
On Tue, 17 Dec 2013 12:29:30 -0600
Tom Zanussi wrote:
> > Tom,
> > is git://git.yoctoproject.org/linux-yocto-contrib
> > tzanussi/event-triggers-v11 the right starting point ?
> >
>
> Yep, that's the last iteration - I haven't changed anything since then.
>
Is this the same as the last patch
ICP DAS calls LP-8x4x 'programmable automation controller'. It is
an industrial computer based on PXA270 SoC. They ship it with a 2.6.19
kernel and proprietary kernel module and userspace library to access
its industrial IO.
This patch allows to boot the device with a modern kernel with device
Hey Ingo, Thomas,
Here are the timekeeping fixes I'd like to submit for 3.13.
The first is a regression caused by the shadow time code that
causes the tai offset to be overwritten. This keeps ntpd from being
able to initialize the tai_offset.
The second fixes an issue where the action
On Fri, Nov 22, 2013 at 02:04:46PM -0500, Waiman Long wrote:
> There is a pending MCS lock patch series that adds generic MCS lock
> helper functions to do MCS-style locking. This patch will enable
> the queue rwlock to use that generic MCS lock/unlock primitives for
> internal queuing. This patch
On Tue, Dec 17, 2013 at 10:42:54PM +0300, Sergei Shtylyov wrote:
> You're right in your doubting: there are quite a lot of drivers used
> by embedded platforms that nobody has bothered to convert to libata
> thus far.
Hold on, what does that mean? IDE is back from the dead and used only
for
On Fri, Nov 22, 2013 at 02:04:47PM -0500, Waiman Long wrote:
> This patch modifies the queue_write_unlock() function to use the
> new smp_store_release() function in another pending patch. This patch
> should only be merged if the other patch was merged.
>
> Signed-off-by: Waiman Long
Hi Daniel,
On Tue, Nov 26, 2013 at 05:04:50PM -0800, Soren Brinkmann wrote:
> It is not allowed to call clk_get_rate() from interrupt context. To
> avoid such calls the timer input frequency is stored in the driver's
> data struct which makes it accessible to the driver in any context.
>
>
This provides an MTD device driver for 512kB of battery backed up SRAM
on ICPDAS LP-8X4X programmable automation controllers.
SRAM chip is connected via FPGA and is not accessible without a driver,
unlike flash memory which is wired to CPU MMU.
This SRAM becomes an excellent persisent storage of
In 780427f0e11 (Indicate that clock was set in the pvclock
gtod notifier), logic was added to pass a CLOCK_WAS_SET
notification to the pvclock notifier chain.
While that patch added a action flag returned from
accumulate_nsecs_to_secs(), it only uses the returned value
in one location, and not in
On Fri, Nov 22, 2013 at 02:04:44PM -0500, Waiman Long wrote:
> This patch introduces a new read/write lock implementation that put
> waiting readers and writers into a queue instead of actively contending
> the lock like the current read/write lock implementation. This will
> improve performance
On Tue, Dec 17, 2013 at 11:21 AM, Paul E. McKenney
wrote:
>
> Looks like xadd() is x86-specific, but this is common code. One
> approach would be to do xadd() for other arches, another approach
> would be to make .rw be an atomic_t rather than a u32. Making it
> be atomic_t is probably easiest.
On Thu, 2013-12-05 at 16:28 +, Catalin Marinas wrote:
> > +#define FIXMAP_PAGE_NORMAL __pgprot(PROT_NORMAL | PTE_PXN | PTE_UXN)
>
> I'll push a fix to change PROT_DEFAULT to (pgprot_default | PTE_DIRTY).
>
This doesn't help early_ioremap because pgprot_default gets set up in
3.5.7.28 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit e7ca237bfcf6a288702cb95e94ab94f642ccad88 upstream.
ASUS Z35HL laptop also needs the very same fix as the previous one
that was applied to ASUS W7J.
Bugzilla:
3.5.7.28 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hong Zhiguo
commit 2c575026fae6e63771bd2a4c1d407214a8096a89 upstream.
Signed-off-by: Hong Zhiguo
Acked-by: Tejun Heo
Signed-off-by: Jens Axboe
Signed-off-by: Luis Henriques
---
Andrew Morton wrote:
> David ack?
I've signed it off and added here:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/commit/?h=afs=8de69dbba9012693d4f9e7a7e3c12a0b467f85f3
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
3.5.7.28 -stable review patch. If anyone has any objections, please let me
know.
--
From: Seth Heasley
commit c2db409cbc8751ccc7e6d2cc2e41af0d12ea637f upstream.
This patch adds the PCU SMBus DeviceID for the Intel Avoton SOC.
Signed-off-by: Seth Heasley
Reviewed-by: Jean
301 - 400 of 1784 matches
Mail list logo
