On Tue, 28 Apr 2015 18:35:00 +0200
Sebastian Hesselbarth wrote:
> On 28.04.2015 17:59, Russell King - ARM Linux wrote:
> > On Mon, Apr 27, 2015 at 11:09:04AM +0200, Sebastian Hesselbarth wrote:
> >> The current implicit GPL only licensing on the device tree makes it
> >> very impractical for
On Tue, Apr 28, 2015 at 12:58:55PM -0400, Chris Metcalf wrote:
> On 04/28/2015 12:40 PM, Peter Zijlstra wrote:
> >On Tue, Apr 28, 2015 at 11:53:21AM -0400, Chris Metcalf wrote:
> >
> >>The reason we use two 32-bit fields on tilepro is that the only available
> >>atomic instruction is tns (test and
From: Bharat Bhushan
This patch is required for vfio-fsl-mc meta driver to successfully bind
layerscape container devices for device passthrough. This patch adds
a mechanism to allow a layerscape device to specify a driver rather than
a layerscape driver provide a device match.
This patch is
- Migrated MC bus driver to use DPRC flib 0.6.
- Changed IRQ setup infrastructure to be able to program MSIs
for MC objects in an object-independent way.
Signed-off-by: J. German Rivera
---
drivers/staging/fsl-mc/bus/dpmcp-cmd.h | 79
drivers/staging/fsl-mc/bus/dprc-cmd.h
When a child DPRC is bound to the vfio_fsl_mc driver via driver_override,
its own children should not be bound to corresponding host kernel
drivers, but instead should be bound to the vfio_fsl_mc driver as
well.
Currently, when a child container is scanned by the vfio_fsl_mc driver,
child devices
Add a locking mechanism to serialize mc_send_command() calls that use
the same fsl_mc_io object (same MC portal). All mc_send_command() calls
with the same fsl_m_io object have to be either from non-atomic context
or from atomic context, but not both. When the fsl_mc_io object is
created the owner
This patch series includes new functionality for the Freescale fsl-mc
bus driver.
Patch 1: MC bus IRQ support
Patch 2: add device binding path 'driver_override'
Patch 3: Propagate driver_override for a child DPRC's children
Patch 4: Upgraded MC bus driver to match MC fw 7.0.0
Patch 5: Allow the
On Tue, Apr 28, 2015 at 07:19:02PM +0300, Kalle Valo wrote:
> Rasmus Villemoes writes:
>
> > Since these fmt_* variables are just const char*, and not const
> > char[], gcc (and smatch) doesn't to type checking of the arguments to
> > the printf functions. Since the linker knows perfectly well
On Tue, 2015-04-28 at 19:17 +0200, Peter Zijlstra wrote:
> To me it makes more sense to reverse these two branches (identical code
> wise of course) and put the special case first.
>
> Alternatively we could also do something like the below, which to my
> eyes looks a little better still, but I
On 04/22/2015 04:20 AM, Ulrich Obergfell wrote:
Chris,
in principle the change looks o.k. to me, even though I'm not really familiar
with the watchdog_nmi_disable_all() and watchdog_nmi_enable_all() functions.
It is my understanding that those functions are only called once via 'initcall'
early
This was left over from an earlier iteration of the BMIPS irqchip changes.
It doesn't actually have an effect, so let's nuke it.
Reported-by: Valentin Rothberg
Signed-off-by: Kevin Cernekee
---
Ralf - could you please pull this for 4.1?
arch/mips/Kconfig | 1 -
1 file changed, 1
On Tue, Apr 28, 2015 at 06:44:15PM +0200, Petr Mladek wrote:
> On Mon 2015-04-27 08:56:27, Josh Poimboeuf wrote:
> > + case 0x89:
> > + insn_get_modrm();
> > + if (insn.modrm.bytes[0] == 0xe5)
> > + /* mov sp, bp */
> > +
On Tue, 28 Apr 2015, Mika Westerberg wrote:
> On Tue, Apr 28, 2015 at 02:32:59PM +0100, Lee Jones wrote:
> > On Tue, 31 Mar 2015, Andy Shevchenko wrote:
> >
> > > The new coming Intel platforms such as Skylake will contain Sunrisepoint
> > > PCH.
> > > The main difference to the previous
On Tue, 2015-04-28 at 10:50 -0700, Jason Low wrote:
> On Tue, 2015-04-28 at 19:17 +0200, Peter Zijlstra wrote:
>
> > To me it makes more sense to reverse these two branches (identical code
> > wise of course) and put the special case first.
> >
> > Alternatively we could also do something like
On Tue, 28 Apr 2015, Alexandre Belloni wrote:
> Hi,
>
> On 28/04/2015 at 13:30:58 +0100, Lee Jones wrote :
> > On Mon, 23 Mar 2015, Alexandre Belloni wrote:
> >
> > > From: Boris Brezillon
> > >
> > > The at91rm9200 SoC embeds a Memory Controller block which is used to
> > > configure several
On 04/28/2015 01:43 PM, Peter Zijlstra wrote:
On Tue, Apr 28, 2015 at 12:58:55PM -0400, Chris Metcalf wrote:
On 04/28/2015 12:40 PM, Peter Zijlstra wrote:
On Tue, Apr 28, 2015 at 11:53:21AM -0400, Chris Metcalf wrote:
The reason we use two 32-bit fields on tilepro is that the only available
On Tue, 2015-04-28 at 17:54 +0100, Russell King - ARM Linux wrote:
> It's probably something I need to look at when I'm in a more relaxed
> state, and when I have more time to deal with the dreaded email
> backlog...
Please take your time. This is just a trivial cleanup. A few lines in
some
All the IRQs for DPAA2 objects in the same DPRC must use
the ICID of that DPRC, as their device Id in the GIC-ITS.
Thus, all these IRQs must share the same ITT table in GIC. As
a result, a pool of IRQs with the same device Id must be
preallocated per DPRC (fsl-mc bus instance). So, the fsl-mc
bus
On Wed, 29 Apr 2015, Ramakrishna Pallala wrote:
> This patch adds the extcon support for AXP288 PMIC which
> has the BC1.2 charger detection capability. Additionally
> it also adds the USB mux switching support b/w SOC and PMIC
> based on GPIO control.
>
> Signed-off-by: Ramakrishna Pallala
>
If the lpi-parent property is not present in the fsl,qoriq-mc node
of the device tree, the MC bus driver will assume that the GIC is not
supported.
This change is made in order to be able to use the MC bus driver in a
KVM VM, without having GIC-ITS support in guests. Added function
- Refactored fsl_mc_io object to have a DPMCP object attached to it
- Created DPMCP object for DPRC's built-in portal, so that waiting
on MC command completions for MC commands sent on the DPRC's built-in
portal can be done using a DPMCP interrupt and a Linux completion
variable. For most
On Tue, 2015-04-28 at 10:50 -0700, Jason Low wrote:
> On Tue, 2015-04-28 at 19:17 +0200, Peter Zijlstra wrote:
>
> > To me it makes more sense to reverse these two branches (identical code
> > wise of course) and put the special case first.
> >
> > Alternatively we could also do something like
Hi Lee Jones,
I have agreed to move the AXP288_EXTCON_* macros to driver source file as
Choi is going to submit another extcon class driver patch to fix the consumer
driver
access issue.
I will submit the v7 patch now with this change. Thank you for your time.
> > This patch adds the extcon
On 04/21/2015 08:32 AM, Ulrich Obergfell wrote:
Chris,
in v9, smpboot_update_cpumask_percpu_thread() allocates 'tmp' mask dynamically.
This allocation can fail and thus the function can now return an error. However,
this error is being ignored by proc_watchdog_cpumask().
Yes, I did that
This patch adds the extcon support for AXP288 PMIC which
has the BC1.2 charger detection capability. Additionally
it also adds the USB mux switching support b/w SOC and PMIC
based on GPIO control.
Signed-off-by: Ramakrishna Pallala
---
drivers/extcon/Kconfig |7 +
Commit c9f038a1a592 ("drm/i915: Don't assume primary & cursor are
always on for wm calculation (v4)") fixes a null pointer dereference.
Setting the primary and cursor panes to false in
ilk_compute_wm_parameters to false does however give the following
errors in the kernel log and causes the screen
On Mon, 2015-04-27 at 16:25 -0400, Waiman Long wrote:
> >> + /*
> >> + * up_write() cleared the owner field before calling this function.
> >> + * If that field is now set, a writer must have stolen the lock and
> >> + * the wakeup operation should be aborted.
> >> + */
> >> + if
Am 28.04.2015 um 14:49 schrieb Tomeu Vizoso:
On 25 April 2015 at 01:15, Alexander Holler wrote:
Am 24.04.2015 um 16:47 schrieb Tomeu Vizoso:
Hi,
while reading the thread [0] that Alexander Holler started with his series to
make probing order deterministic, it occurred to me that it should
On Tue, Apr 28, 2015 at 05:17:11PM +0530, Nizam Haider wrote:
> Fixed two warnings sizeof name and Blank line after declaration
>
> Signed-off-by: Nizam Haider
> ---
> drivers/usb/core/buffer.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Where are patches 1/3 and 2/3?
Please
On Fri, Apr 10, 2015 at 7:27 PM, Benjamin Poirier wrote:
> By default, the number of tx queues is limited by the number of online cpus in
> mlx4_en_get_profile(). However, this limit no longer holds after the ethtool
> .set_channels method has been called. In that situation, the driver may access
On Tue, Apr 28, 2015 at 02:00:48PM -0400, Chris Metcalf wrote:
> Yes, tilepro can do 16-bit atomic load/stores. The reason we didn't use
> your approach (basically having tns provide locking for the head/tail)
> is just a perceived efficiency gain from rolling the tns lock into the head.
>
> The
ACPI 6.0 formalizes e820-type-7 and efi-type-14 as persistent memory.
Mark it "reserved" and allow it to be claimed by a persistent memory
device driver.
This definition is in addition to the Linux kernel's existing type-12
definition that was recently added in support of shipping platforms with
In preparation for the pmem driver attaching to pmem-namespaces emitted
by libnd, convert it to use an ida instead of an always increasing
atomic index. This provides a bit of stability to pmem device names in
the presence of driver re-bind events.
Cc: Christoph Hellwig
Signed-off-by: Dan
Changes since v1 [1]: Incorporates feedback received prior to April 24.
1/ Ingo said [2]:
"So why on earth is this whole concept and the naming itself
('drivers/block/nd/' stands for 'NFIT Defined', apparently)
revolving around a specific 'firmware' mindset and revolving
Manually create and register NFITs to describe 2 topologies. Topology1
is an advanced plausible configuration for BLK/PMEM aliased NVDIMMs.
Topology2 is an example configuration for current platforms that only
ship with a persistent address range.
Kernel provider "nfit_test.0" produces an NFIT
Most configuration of the nd-subsystem is done via nd-sysfs attributes.
However, some nd buses, particularly the ACPI.NFIT bus, define a small
set of messages that can be passed to the platform. For convenience we
derivce the initial nd-ioctl-command formats directly from the NFIT DSM
formats.
The libnd region driver is an intermediary driver that translates
non-volatile "region"s into "namespace" sub-devices that are surfaced by
persistent memory block-device drivers (PMEM and BLK).
ACPI 6 introduces the concept that a given nvdimm may offer multiple
access modes to its media through
This is the position (device topology) independent method to find all
the libnd buses in the system. The expectation is that there will only
ever be one "nd" bus discovered via /sys/class/nd/ndctl0. However, we
allow for the possibility of multiple buses and they will listed in
discovery order
On platforms that have firmware support for reading/writing per-dimm
label space, a portion of the dimm may be accessible via an interleave
set PMEM mapping in addition to the dimm's BLK (block-data-window
aperture(s)) interface. A label, stored in a "configuration data
region" on the dimm,
From: Vishal Verma
BTT stands for Block Translation Table, and is a way to provide power
fail sector atomicity semantics for block devices that have the ability
to perform byte granularity IO. It relies on the ->rw_bytes() capability
of provided nd namespace devices.
The BTT works as a stacked
nd_pmem attaches to persistent memory regions and namespaces emitted by
the nd subsystem, and, same as the original pmem driver, presents the
system-physical-address range as a block device.
The existing e820-type-12 to pmem setup is converted to a full libnd bus
that emits an nd_namespace_io
From: Ross Zwisler
The libnd implementation handles allocating dimm address space (DPA)
between PMEM and BLK mode interfaces. After DPA has been allocated from
a BLK-region to a BLK-namespace the nd_blk driver attaches to handle I/O
as a struct bio based block device. Unlike PMEM, BLK is
On media label format consists of two index blocks followed by an array
of labels. None of these structures are ever updated in place. A
sequence number tracks the current active index and the next one to
write, while labels are written to free slots.
++
||
|
Block devices from an nd bus, in addition to accepting "struct bio"
based requests, also have the capability to perform byte-aligned
accesses. By default only the bio/block interface is used. However, if
another driver can make effective use of the byte-aligned capability it
can claim/disable
After 'uuid', 'size', 'sector_size', and optionally 'alt_name' have been
set to valid values the labels on the dimm can be updated. The
difference with the pmem case is that blk namespaces are limited to one
dimm and can cover discontiguous ranges in dpa space.
Also, after allocating label
A blk label set describes a namespace comprised of one or more
discontiguous dpa ranges on a single dimm. They may alias with one or
more pmem interleave sets that include the given dimm.
This is the runtime/volatile configuration infrastructure for sysfs
manipulation of 'alt_name', 'uuid',
A complete label set is a PMEM-label per dimm where all the UUIDs
match and the interleave set cookie matches an active interleave set.
Present a sysfs ABI for manipulation of a PMEM-namespace's 'alt_name',
'uuid', and 'size' attributes. A later patch will make these settings
persistent by
After 'uuid', 'size', and optionally 'alt_name' have been set to valid
values the labels on the dimms can be updated.
Write procedure is:
1/ Allocate and write new labels in the "next" index
2/ Free the old labels in the working copy
3/ Write the bitmap and the label space on the dimm
4/ Write
A "region" device represents the maximum capacity of a BLK range (mmio
block-data-window(s)), or a PMEM range (DAX-capable persistent memory or
volatile memory), without regard for aliasing. Aliasing, in the
dimm-local address space (DPA), is resolved by metadata on a dimm to
designate which
On Thu, Apr 23, 2015 at 04:35:21PM -0700, Joe Perches wrote:
> On Thu, 2015-04-23 at 16:04 -0700, Mark Fasheh wrote:
> > On Wed, Apr 22, 2015 at 03:46:04PM -0700, Andrew Morton wrote:
> > > If you feel like undertaking such a rotorooting then go wild - that should
> > > wake 'em up ;)
> >
> > Ok,
On 04/28/2015 12:28 PM, David Vrabel wrote:
On 28/04/15 16:52, Boris Ostrovsky wrote:
When a guest is resumed, the hypervisor may change event channel
assignments. If this happens and the guest uses 2-level events it
is possible for the interrupt to be claimed by wrong VCPU since
Register the memory devices described in the nfit as libnd 'dimm'
devices on an nd bus. The kernel assigned device id for dimms is
dynamic. If userspace needs a more static identifier it should consult
a provider-specific attribute. In the case where NFIT is the provider,
the
* Implement the device-model infrastructure for loading modules and
attaching drivers to nd devices. This is a simple association of a
nd-device-type number with a driver that has a bitmask of supported
device types. To facilitate userspace bind/unbind operations 'modalias'
and
Hello.
On 04/28/2015 04:14 AM, K. Y. Srinivasan wrote:
Commit commit b08cc79155fc26d0d112b1470d1ece5034651a4b eliminated memory
One "commit" is enough. :-)
And please also specify that commit's summary in parens.
allocation in the packet send path. This commit introduced a bug since
1/ Autodetect an NFIT table for the ACPI namespace device with _HID of
"ACPI0012"
2/ libnd bus registration
The NFIT provided by ACPI is one possible method by which platforms will
discover NVDIMM resources. However, the intent of the nd_bus_descriptor
abstraction is to abstract "provider"
On Tue 28-04-15 09:57:11, Linus Torvalds wrote:
> On Tue, Apr 28, 2015 at 9:43 AM, Michal Hocko wrote:
> >
> > Hmm, no other thread has the address from the current mmap call except
> > for MAP_FIXED (more on that below).
>
> With things like opportunistic SIGSEGV handlers that map/unmap things
On an older 8 TB box with lots and lots of cpus the boot time, as
measure from grub to login prompt, the boot time improved from 1484
seconds to exactly 1000 seconds.
I have time on 16 TB box tonight and a 12 TB box thursday and will
hopefully have more numbers then.
On 04/28/2015 11:06
On Tue, Apr 28, 2015 at 10:16:33AM -0700, Linus Torvalds wrote:
> I suspect it might be related to things like getting performance
> counters and instruction debug traps etc right. There are quite
> possibly also simply constraints where the front end has to generate
> *something* just to keep the
On 04/28/2015 02:24 PM, Peter Zijlstra wrote:
A few questions:
On Tue, Apr 28, 2015 at 02:00:48PM -0400, Chris Metcalf wrote:
static inline void arch_spin_lock(arch_spinlock_t *lock)
{
unsigned short head, tail;
___tns_lock(>lock); /* XXX does the TNS imply a ___sync? */
On Tue, Apr 28, 2015 at 11:35 AM, Michal Hocko wrote:
>
> I am still not sure I see the problem here.
Basically, I absolutely hate the notion of us doing something
unsynchronized, when I can see us undoing a mmap that another thread
is doing. It's wrong.
You also didn't react to all the *other*
From: Jean Delvare
Subject: firmware: dmi_scan: Only honor end-of-table for 64-bit tables
A 32-bit entry point to a DMI table says how many structures the table
contains. The SMBIOS specification explicitly says that end-of-table
markers should be ignored if they are not actually at the end of
On Tue, Apr 28, 2015 at 06:22:29PM +0200, Borislav Petkov wrote:
> On Tue, Apr 28, 2015 at 11:35:21AM -0400, Don Zickus wrote:
> > Your solution seems much simpler. :-)
>
> ... and I love simpler :-)
>
> > I followed up in another email stating I mis-spoke. I forgot this still
> > uses the
On Wed, 29 Apr 2015, Ramakrishna Pallala wrote:
> This patch adds the extcon support for AXP288 PMIC which
> has the BC1.2 charger detection capability. Additionally
> it also adds the USB mux switching support b/w SOC and PMIC
> based on GPIO control.
>
> Signed-off-by: Ramakrishna Pallala
>
On Mon, Apr 27, 2015 at 09:24:35PM -0400, Doug Ledford wrote:
> On Mon, 2015-04-27 at 17:53 -0700, Tom Talpey wrote:
> Having some of it refer to things as IBOE and some as ROCE would be
> similarly confusing, and switching existing IBOE usage to ROCE would
> cause pain to people with out of tree
> -Original Message-
> From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
> Sent: Tuesday, April 28, 2015 11:27 AM
> To: KY Srinivasan; da...@davemloft.net; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
>
On Tue, Apr 28, 2015 at 6:10 PM, Michael Wang wrote:
> Use raw management helpers to reform IB-core cm.
>
> Cc: Hal Rosenstock
> Cc: Steve Wise
> Cc: Tom Talpey
> Cc: Jason Gunthorpe
> Cc: Doug Ledford
> Cc: Ira Weiny
> Cc: Sean Hefty
> Signed-off-by: Michael Wang
> ---
>
Here are two new releases of userspace RCU for the 0.7 and 0.8
stable branches currently maintained. Those are bugfix releases.
liburcu is a LGPLv2.1 userspace RCU (read-copy-update) library. This
data synchronization library provides read-side access which scales
linearly with the number of
Le 25/03/2015 02:22, Scott Wood a écrit :
On Tue, Feb 03, 2015 at 12:39:27PM +0100, LEROY Christophe wrote:
Signed-off-by: Christophe Leroy
---
arch/powerpc/lib/checksum_32.S | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/lib/checksum_32.S
Le 25/03/2015 03:10, Scott Wood a écrit :
On Tue, 2015-02-03 at 12:39 +0100, Christophe Leroy wrote:
csum_tcpudp_magic() is only a few instructions, and does not modifies any other
register than the returned result. So it is not worth having it as a separate
function and suffer function
On Tue, 2015-04-28 at 16:15 +0200, Valentin Rothberg wrote:
> CONFIG_ACORNSCSI_CONSTANTS is a file local CPP identifier and thereby
> violates the naming convention of Kconfig options in Make and CPP
> syntax; only Kconfig options should carry the 'CONFIG_' prefix.
>
> This patch removes the
On Tue, Apr 28, 2015 at 9:56 PM, Jason Gunthorpe
wrote:
> On Mon, Apr 27, 2015 at 09:24:35PM -0400, Doug Ledford wrote:
>> On Mon, 2015-04-27 at 17:53 -0700, Tom Talpey wrote:
>
>> Having some of it refer to things as IBOE and some as ROCE would be
>> similarly confusing, and switching existing
On 04/24/2015 03:24 PM, r...@redhat.com wrote:
From: Rik van Riel
Currently there is no way to query which CPUs are in nohz_full
mode from userspace.
Export the CPU list running in nohz_full mode in sysfs,
specifically in the file /sys/devices/system/cpu/nohz_full
This can be used by system
On Tue, Apr 28, 2015 at 1:19 PM, David Lang wrote:
> If the examples that are being used to show the performance advantage of
> kdbus vs normal dbus are doing the wrong thing, then we need to get some
> other examples available to people who don't live and breath dbus that 'so
> things right' so
On Tue, Apr 28, 2015 at 5:46 AM, Christoph Hellwig wrote:
> On Fri, Apr 17, 2015 at 09:35:19PM -0400, Dan Williams wrote:
>> diff --git a/arch/ia64/kernel/efi.c b/arch/ia64/kernel/efi.c
>> index c52d7540dc05..cd8b7485e396 100644
>> --- a/arch/ia64/kernel/efi.c
>> +++ b/arch/ia64/kernel/efi.c
>>
On Tue, Apr 28, 2015 at 5:53 AM, Christoph Hellwig wrote:
> On Fri, Apr 17, 2015 at 09:35:30PM -0400, Dan Williams wrote:
>> new file mode 100644
>> index ..5fa74f124b3e
>> --- /dev/null
>> +++ b/drivers/block/nd/Kconfig
>> @@ -0,0 +1,44 @@
>> +config ND_ARCH_HAS_IOREMAP_CACHE
>> +
Add an implementation of the SCM interface that works on ARM64/64-bit SoCs
Signed-off-by: Kumar Gala
Signed-off-by: Lina Iyer
---
* v5:
- use common error defines from qcom_scm.h
- removed R*_STR defines
* v4:
- Folded in change to qcom_scm_cpu_power_down to remove HOTPLUG flag
from Lina.
Split out the 32-bit SCM implementation into its own file to prep for
supporting a 64-bit/ARM64 implementation as well. We create a simple shim
to ensure both versions conform to the same interface.
Signed-off-by: Kumar Gala
---
v5:
Split out error defines in common qcom_scm.h
On Tue, 2015-04-28 at 18:45 +0200, Valentin Rothberg wrote:
> The block could never be compiled; CPU_ICACHE_STREAMING_DISABLE has not
> been defined in Kconfig since the very first Git commit.
Actually, this goes back to a patch titled "1759/1: Add ARM925 support,
updated" that landed in v2.6.4.
So, who is going to pick up this patch?
Regards,
Lucas
Am Dienstag, den 14.04.2015, 18:28 +0200 schrieb Thomas Renninger:
> Hi,
>
> On Monday, April 13, 2015 10:24:01 PM Lucas Stach wrote:
> > libpci 3.3.0 introduced an additional member in the pci_filter struct
> > which needs to be
Hi Paul,
On Tue, Apr 28, 2015 at 9:10 PM, Paul Bolle wrote:
> On Tue, 2015-04-28 at 16:15 +0200, Valentin Rothberg wrote:
>> CONFIG_ACORNSCSI_CONSTANTS is a file local CPP identifier and thereby
>> violates the naming convention of Kconfig options in Make and CPP
>> syntax; only Kconfig options
Hi Valentin,
On Tue, 2015-04-28 at 21:26 +0200, Valentin Rothberg wrote:
> On Tue, Apr 28, 2015 at 9:10 PM, Paul Bolle wrote:
> > Will the Erlangen bot still spot ACORNSCSI_CONSTANTS as a potential
> > issue?
>
> No, undertaker-checkpatch won't complain about this. There are
> thousands of
On Tue, 21 Apr 2015 14:05:11 +0200
Gaël PORTAY wrote:
> *** BLURB HERE ***
We usually replace this line by a description ;-).
Anyway, to the whole series:
Acked-by: Boris Brezillon
>
> Gaël PORTAY (7):
> ARM: at91/dt: kizbox: rename to at91-kizbox
> ARM: at91/dt: at91-kizbox: sanitize
I saw your email address during the course of my research today. My
name is Bill William Groner my wife and I won a Jackpot Lottery of $50
Million Dollars in December 2013, we are donating the sum of $1
million Dollars to 6 lucky individual all over the world as part of
our charity project.
On Tue, Apr 28, 2015 at 5:54 AM, Christoph Hellwig wrote:
> Eww, the --wrap stuff is too ugly too live.
Since when are unit tests pretty?
> Just implement the
> implemenetation of persistent nvdimms into qemu where it belongs.
Ugh, no, I'm not keen to introduce yet another roadblock to running
On Tue, Apr 28, 2015 at 5:56 AM, Christoph Hellwig wrote:
> On Sat, Apr 18, 2015 at 12:37:09PM -0700, Dan Williams wrote:
>> At this point in the patch series I agree, but in later patches we
>> take advantage of nd bus services. "[PATCH 15/21] nd: pmem label sets
>> and namespace instantiation"
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Hiroshi Shimamoto
> Sent: Thursday, April 09, 2015 6:04 PM
> To: Kirsher, Jeffrey T; Alexander Duyck; intel-wired-lan
> Cc: vyase...@redhat.com;
On Tue, Apr 28, 2015 at 9:24 PM, Paul Bolle wrote:
> On Tue, 2015-04-28 at 18:45 +0200, Valentin Rothberg wrote:
>> The block could never be compiled; CPU_ICACHE_STREAMING_DISABLE has not
>> been defined in Kconfig since the very first Git commit.
>
> Actually, this goes back to a patch titled
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Hiroshi Shimamoto
> Sent: Thursday, April 09, 2015 6:08 PM
> To: Kirsher, Jeffrey T; Alexander Duyck; intel-wired-lan
> Cc: vyase...@redhat.com;
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Hiroshi Shimamoto
> Sent: Thursday, April 09, 2015 6:05 PM
> To: Kirsher, Jeffrey T; Alexander Duyck; intel-wired-lan
> Cc: vyase...@redhat.com;
On Tue, 28 Apr 2015 11:17:59 -0400 Don Zickus wrote:
> cc'ing Andrew
>
> On Mon, Apr 27, 2015 at 04:27:16PM -0400, Chris Metcalf wrote:
> > I've been out on vacation the last ten days, but picking this up
> > again now.
> >
> > I'll wait a bit before putting out a v10, and also address Uli's
On 27 April 2015 at 23:40, Pankaj Dubey wrote:
> fixes obvious typo in of_coresight.c
> %s/non-configuable/non-configurable
>
> Signed-off-by: Pankaj Dubey
> ---
> drivers/hwtracing/coresight/of_coresight.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On 04/28/2015 12:42 PM, Linus Torvalds wrote:
On Tue, Apr 28, 2015 at 9:05 AM, Al Viro wrote:
Unfortunately, we _can't_ make strlcpy() never look past src + size - 1 -
not without changing its semantics.
Yeah, strlcpy is actually nasty. I don't understand why people like it
so much. It's a
On Apr 28, 2015, at 1:14 AM, Hefty, Sean wrote:
>>> Keep in mind that this enum was Liran's response to Michael's original
>>> patch. In the enum in Michael's patch, there was both USNIC and
>>> USNIC_UDP.
>>
>> Right! That's why I'm confused. Seems wrong to drop it, right?
>
> I think the
Herbert, David,
Any comment on the crypto driver implementation ?
I've had several reviews focused on:
1/ splitting the patch series into smaller subsets
2/ allowing for smoother transition from the old driver to the new one
I'll address (or have addressed) all of these comments, but I'd like
Linus,
Please pull the following changes for 4.1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git stable
This just fixes a compiler warning from an old bug that only recently started
generating a warning.
Chris Metcalf (1):
tile: properly use node_isset() on
Error recovery pointers for fixups was improperly set as ".word"
which is unsuitable for MIPS64.
Replaced by __stringify(PTR)
Signed-off-by: Leonid Yegoshin
---
arch/mips/kernel/mips-r2-to-r6-emul.c | 104 +
1 file changed, 52 insertions(+), 52 deletions(-)
> Is the concern here about CM issues or the UDP ports used by the actual
> usNIC RQs?
UDP port space sharing
--
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
If get_free_page() fails for nested bitmap area, it's evident that
we are gonna get screwed anyway but returning failure because we failed
allocating memory for a nested structure seems like an unnecessary big
hammer. Also, save the call for later; after we are done with other
non-nested
On Tue, 2015-04-28 at 21:36 +0200, Valentin Rothberg wrote:
> Thanks! I just wanted to point out that this code hasn't been touched
> since I was at high school : )
(Yes, fine, do rub it in.)
Sure, for all practical purposes, v2.6.12-rc2 means: very, very long
ago. But I would be applaud if
On Tue, Apr 28, 2015 at 9:34 PM, Paul Bolle wrote:
> Hi Valentin,
>
> On Tue, 2015-04-28 at 21:26 +0200, Valentin Rothberg wrote:
>> On Tue, Apr 28, 2015 at 9:10 PM, Paul Bolle wrote:
>> > Will the Erlangen bot still spot ACORNSCSI_CONSTANTS as a potential
>> > issue?
>>
>> No,
1501 - 1600 of 1860 matches
Mail list logo
