Hi Philipp,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 25cb62b76430a91cc6195f902e61c2cb84ade622
commit: 2091f5181c66b3617a977e79843aba10e087be6c [media] videobuf2: add trace
events
date: 3 months ago
config:
On some boards the energy enable detect mode leads in
trouble with some switches, so make the enabling of
this mode configurable through DT.
Signed-off-by: Heiko Schocher
---
.../devicetree/bindings/net/smsc-lan87xx.txt | 19 +
drivers/net/phy/smsc.c
On 10/12/15 9:34 PM, Wangnan (F) wrote:
On 2015/10/13 12:16, Alexei Starovoitov wrote:
On 10/12/15 8:51 PM, Wangnan (F) wrote:
why 'set disable' is needed ?
the example given in cover letter shows the use case where you want
to receive samples only within sys_write() syscall.
The example make
add a shutdown function for setting the gpio-leds
into off state when shuting down.
Signed-off-by: Heiko Schocher
---
drivers/leds/leds-gpio.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
index af1876a..5db4515 100644
---
Hi!
On 10/13/2015 12:35 AM, Dan Williams wrote:
> Per commit 2e586a7e017a "drm/vmwgfx: Map the fifo as cached" the driver
> expects the fifo registers to be cacheable. In preparation for
> deprecating ioremap_cache() convert its usage in vmwgfx to memremap().
>
> Cc: David Airlie
> Cc: Thomas He
On Tue, Oct 6, 2015 at 3:06 AM, Grant Likely wrote:
> [Resending because I messed up the first one]
>
> The elections for five of the ten members of the Linux Foundation
> Technical Advisory Board (TAB) are held every year[1]. This year the
> election will be at the 2015 Kernel Summit in Seoul, So
On Mon, Oct 12, 2015 at 11:45:19AM -0700, Christopher S. Hall wrote:
> +int get_correlated_timestamp(struct correlated_ts *crt,
> + struct correlated_cs *crs)
> +{
> + struct timekeeper *tk = &tk_core.timekeeper;
> + unsigned long seq;
> + cycles_t cycles, cycle
We just made sure policy->cpu is online and this check will always fail
as the policy is active. Drop it.
Signed-off-by: Viresh Kumar
Acked-by: Saravana Kannan
---
Resending as a separate patch.
drivers/cpufreq/cpufreq.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/cpufreq
In nr_hw_queues >1 cases when certain number of cpus are onlined/or
offlined, that results change in request_queue map in block-mq layer,
we see the kernel dumping like:
BUG: unable to handle kernel NULL pointer dereference at 0080
IP: [] cpumask_set_cpu+0x6/0xd
PGD 6d957067 PUD 760
On embedded devices, often there is a combination of
removable mmc devices (e.g. MMC/SD cards) and hard
wired ones (e.g. eMMC). Depending on the hardware
configuration, the 'mmcblkN' node might change if
the removable device is available or not at boot time.
E.g. if the removable device is attache
On 10/12/2015 10:28 PM, James Morse wrote:
On 29/05/15 06:38, AKASHI Takahiro wrote:
The current kvm implementation on arm64 does cpu-specific initialization
at system boot, and has no way to gracefully shutdown a core in terms of
kvm. This prevents, especially, kexec from rebooting the system o
On Tue, Oct 13, 2015 at 12:19:12AM +0530, punit vara wrote:
> On Tue, Oct 13, 2015 at 12:16 AM, Punit Vara wrote:
> > This patch is to the rtl871x_ioctl_linux.c file that fixes up following
> > warning reported by checkpatch.pl :
> >
> > -Prefer ether_addr_equal() or ether_addr_equal_unaligned() o
On Sat, Oct 10, 2015 at 01:28:34PM +0700, Ivan Safonov wrote:
> This patch replace BITn macro to BIT(n).
Why? Have you deleted the BITn macros?
--
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 Sat, Oct 10, 2015 at 01:23:13PM +0700, Ivan Safonov wrote:
> Unnecessary channel groups for 5 GHz removed from Hal_GetChnlGroup88E
> and it transformed to pretty get_channel_group(const u8 channel).
>
> Also removed code for 5 GHz frequency in Hal_ReadPowerValueFromPROM_8188E.
Why did you do t
On Sat, Oct 10, 2015 at 01:27:00PM +0700, Ivan Safonov wrote:
> Correct channels range is 1..14 (numbering from 1) but not 0..13.
Why? Have you tested this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majord
On Sun, Oct 04, 2015 at 06:55:57PM -0400, Raphaël Beamonte wrote:
> Add some temporary variables to reduce line length under the maximum
> of 80 characters, as per the kernel code style.
>
> Signed-off-by: Raphaël Beamonte
> ---
> drivers/staging/rtl8192u/r8192U_core.c | 130
> +
On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos wrote:
>> >> > sparc64 machines:
>> >>
>> >> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
>> >> for-pci-v4.4-next
>> >>
>> >> It should fix some "no compatible bridge window"
>> >
>> > Blade 100: still has 2 address conflicts
On 12 October 2015 18:59:57 BST, Daniel Baluta wrote:
>
>
>>> +static unsigned instances = 1;
>>> +module_param(instances, uint, 0);
>
>One concern about this. We will still create a default number of
>'instances'
>when using configuration via configfs?
>
>I'm not sure we can remove this paramet
On 10/12/2015 05:10 PM, Arnd Bergmann wrote:
> The advansys drvier uses the request_dma function that is used on ISA
> machines for the internal DMA controller, which causes build errors
> on platforms that have ISA slots but do not provide the ISA DMA API:
>
> drivers/scsi/advansys.c: In function
On Sat, Oct 10, 2015 at 03:41:54PM +0300, Stanislav Kholmanskikh wrote:
> The config option in the subject may be removed, because,
> indeed, it only serves as the 'n' value for
> CONFIG_WILC1000_PREALLOCATE_AT_LOADING_DRIVER
>
> Signed-off-by: Stanislav Kholmanskikh
> ---
> drivers/staging/wilc
On Tue, Oct 13, 2015 at 11:38:38AM +0900, Minchan Kim wrote:
> Use is_zero_pfn on pteval only after pte_present check on pteval
> (It might be better idea to introduce is_zero_pte where checks
> pte_present first). Otherwise, it could work with swap or
> migration entry and if pte_pfn's result is e
On 12-10-15 14:38, Michal Simek wrote:
Hi Mike,
On 10/12/2015 02:22 PM, Mike Looijmans wrote:
On 12-10-15 13:16, Michal Simek wrote:
+static int zynq_fpga_ops_write(struct fpga_manager *mgr,
+const char *buf, size_t count)
+{
+ struct zynq_fpga_priv *priv;
+
Of this, secure content (including PPA) uses initial
portion of the SRAM. This chunk is not (and shouldn't
be) accessible from the public code.
The minimum size of this chunk (0x350) is used in this
patch. Available size is rounded off to 63K.
Both values would require a change if size of secure
On Tue, Oct 13, 2015 at 11:32:31AM +0800, Liao Tonglang wrote:
> Cleanup for checkpatch.pl warn below:
> CHECK: Alignment should match open parenthesis
> #836: FILE: drivers/staging/android/ashmem.c:836:
> by split three lines to four.
>
> Signed-off-by: Liao Tonglang
> ---
> drivers
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Tuesday, October 13, 2015 5:00 AM
> To: Chao Yu
> Cc: linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] f2fs crypto: fix racing of accessing encrypted page
> among differe
On 12-10-15, 12:35, Saravana Kannan wrote:
> Doesn't really seem related to the sysfs reorg/clean up. Should it
> be a separate patch outside of this series?
Sent it separately now ..
> Acked-by: Saravana Kannan
A reviewed-by would have been more appropriate here though.
--
viresh
--
To unsub
On Wed, 2015-10-07 at 09:21 -0400, Jarod Wilson wrote:
> Some pci changes upcoming in 4.3 seem to cause additional
> disconnects,
> which can happen at unfortuitous times for igb, leading to issues
> such as
> this:
>
> [ 414.440115] igb :15:00.0: enabling device ( -> 0002)
> [ 414.47493
On 12-10-15, 12:31, Saravana Kannan wrote:
> Can we use the first CPU in the related CPUs mask? Instead of the
> first CPU that the policy got created on? The policyX numbering
> would be a bit more consistent that way.
Okay, checked this again. The problem is that ->init() isn't called
yet and we
On 10/12/2015 05:16 PM, Vitaly Kuznetsov wrote:
> Hannes Reinecke writes:
>
>> On 10/08/2015 06:54 PM, Vitaly Kuznetsov wrote:
>>> Some host adapters (e.g. Hyper-V storvsc) are known for not respecting the
>>> SPC-2/3/4 requirement for 'INQUIRY data (see table ...) shall contain at
>>> least 36 b
On Tue, Oct 13, 2015 at 12:12:29AM +0300, Laurent Pinchart wrote:
> Hello,
>
> While working on regulators, GPIOs and DT I noticed that many of our DT source
> files incorrectly describe fixed regulators. The common error patterns are
>
> - Usage of the undefined (and never parsed) enable-active-
On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos wrote:
>> >> > sparc64 machines:
>
> Updated on V210 - the others were more recent. Now I get more BAR
> warning there too:
>
> http://kodu.ut.ee/~mroos/dm/dm.v210+patches
other warning:
[ 38.829890] pci 0001:00:07.0: can't claim BAR 2 [mem
0x7ff00
On Mon, Oct 12, 2015 at 10:43 PM, Yinghai Lu wrote:
> On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos wrote:
>>> >> > sparc64 machines:
>>
>> Updated on V210 - the others were more recent. Now I get more BAR
>> warning there too:
>>
>> http://kodu.ut.ee/~mroos/dm/dm.v210+patches
>>
>
> interesting,
On Mon, Oct 12, 2015 at 10:41:24PM -0700, Greg Kroah-Hartman wrote:
> On Tue, Oct 13, 2015 at 11:38:38AM +0900, Minchan Kim wrote:
> > Use is_zero_pfn on pteval only after pte_present check on pteval
> > (It might be better idea to introduce is_zero_pte where checks
> > pte_present first). Otherwis
On Tue, Oct 13, 2015 at 11:40:00AM +0800, Greg KH wrote:
- ashmem_area_cachep = kmem_cache_create("ashmem_area_cache",
- sizeof(struct ashmem_area),
- 0, 0, NULL);
+ ashmem_area_cachep =
+ km
> We're really getting into low-level implementations here, and I think
> it's best to worry about these sorts of things when we have a patch to
> review.
> it's probably safer to simply not exit it.
> I'm personally more inclined to keep it with the task struct, so that
> different threads w
On Fri, 9 Oct 2015 00:01:09 -0400
Theodore Ts'o wrote:
> If there is a error while copying data from userspace into the page
> cache during a write(2) system call, in data=journal mode, in
> ext4_journalled_write_end() were using page_zero_new_buffers() from
> fs/buffer.c. Unfortunately, this s
On 13/10/15 03:43, Tony Lindgren wrote:
> * Roger Quadros [150918 08:00]:
>> Add compatible id, GPMC register resource and interrupt
>> resource to NAND controller nodes.
>>
>> The GPMC driver now implements gpiochip and irqchip so
>> enable gpio-controller and interrupt-controller properties.
>>
There is no need to have the 'struct nfcwilink *drv' variable static in the
probe function.
It only wastes a few bytes of memory.
Signed-off-by: Christophe JAILLET
---
drivers/nfc/nfcwilink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nfc/nfcwilink.c b/drivers/nf
Signed-off-by: Hui Zhu
---
mm/zsmalloc.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
index f135b1b..c7338f0 100644
--- a/mm/zsmalloc.c
+++ b/mm/zsmalloc.c
@@ -1428,8 +1428,6 @@ static void obj_free(struct zs_pool *pool, struct
size_class *class,
st
On 2015/10/13 5:35, Bjorn Helgaas wrote:
> [+cc Arnd, Rob]
>
> Hi Zhou,
>
> I have a few minor comments and two questions: one about the fact
> all the config accesses are 32 bits, and another about the use of the
> "msi-parent" node.
>
> On Sat, Oct 10, 2015 at 10:59:15AM +0800, Zhou Wang wrote
Hi Thomas:
在 2015/10/12 0:45, Thomas Gleixner 写道:
> On Sun, 11 Oct 2015, Marc Zyngier wrote:
>> On Sun, 11 Oct 2015 11:54:49 +0200
>> Thomas Gleixner wrote:
>>
>>> On Sat, 10 Oct 2015, Marc Zyngier wrote:
On Sat, 10 Oct 2015 17:01:32 +0800
"majun (F)" wrote:
> But there is a proble
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 12 October, 2015 19:48
> To: Tirdea, Irina
> Cc: Bastien Nocera; Aleksei Mamlin; Karsten Merker;
> linux-in...@vger.kernel.org; Mark Rutland; Purdila, Octavian; linux-
> ker...@vger.kernel.org; device
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 12 October, 2015 19:31
> To: Bastien Nocera
> Cc: Mark Rutland; Tirdea, Irina; Aleksei Mamlin; Karsten Merker;
> linux-in...@vger.kernel.org; Purdila, Octavian; lkml;
> devicet...@vger.kernel.org
> Su
Hi,
On Tue, Oct 13, 2015 at 1:53 AM, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Oct 12, 2015 at 03:20:10PM -0700, Tony Lindgren wrote:
>> * Tony Lindgren [151012 14:43]:
>> > * Belisko Marek [150926 13:02]:
>> > > Tony sorry I forgot to add you to the recipients for this patchset.
>> > > Can yo
+Nishanth,
On Tuesday 13 October 2015 10:59 AM, Heiko Schocher wrote:
> On embedded devices, often there is a combination of
> removable mmc devices (e.g. MMC/SD cards) and hard
> wired ones (e.g. eMMC). Depending on the hardware
> configuration, the 'mmcblkN' node might change if
> the removable
> On 12.10.2015, at 23:35, Richard Weinberger wrote:
>
> If ubifs_tnc_next_ent() returns something else than -ENOENT
> we leak file->private_data.
>
> Signed-off-by: Richard Weinberger
> ---
> fs/ubifs/dir.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ubifs
Majun,
On Tue, 13 Oct 2015, majun (F) wrote:
> 在 2015/10/12 0:45, Thomas Gleixner 写道:
> > So now in the mbigen case this looks like this:
> >
> > [MSI-BUS] - [MBIGEN]<---[Device interrupt]
> >
> > Again, you have a 'wire' from the device to the MSI unit (MBIGEN) and
> > w
> -Original Message-
> From: linux-input-ow...@vger.kernel.org
> [mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Karsten Merker
> Sent: 09 October, 2015 20:56
> To: Bastien Nocera; Dmitry Torokhov; Tirdea, Irina; Aleksei Mamlin;
> linux-in...@vger.kernel.org; Ian Campbell
> Cc:
Hi Jason,
Your analysis is correct.
The issue was initially reported by Valdis Kletnieks (valdis.kletni...@vt.edu)
http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20150615/000992.html
Commit 37b12910dd11d9ab969f2c310dc9160b7f3e3405 fixes the lockup issue, and
according to my last c
On Sat, 10 Oct 2015, Darren Hart wrote:
> The Debian 3.16.0 kernel does not emit the error, but I have not attempted a
> bisection.
>
> The warning was added by:
> 38cc46d drm/i915/bdw: Ack interrupts before handling them (GEN8)
> 2014-06-18 (1 year, 4 months ago), Oscar Mateo
But we don't star
Another regression for Jairo to track.
-Daniel
On Sat, Oct 10, 2015 at 12:08:43PM -0700, Darren Hart wrote:
> The Debian 3.16.0 kernel does not emit the error, but I have not attempted a
> bisection.
>
> The warning was added by:
> 38cc46d drm/i915/bdw: Ack interrupts before handling them (GEN8)
On Mon, Oct 12, 2015 at 08:46:21AM +0200, Peter Zijlstra wrote:
> On Sun, Oct 11, 2015 at 06:25:20PM +0800, Boqun Feng wrote:
> > On Sat, Oct 10, 2015 at 09:58:05AM +0800, Boqun Feng wrote:
> > > Hi Peter,
> > >
> > > Sorry for replying late.
> > >
> > > On Thu, Oct 01, 2015 at 02:27:16PM +0200,
Hi Paul,
On Mon, Oct 12, 2015 at 1:05 AM, Paul Gortmaker
wrote:
> In a previous merge window, we made changes to allow better
> delineation between modular and non-modular code in commit
> 0fd972a7d91d6e15393c449492a04d94c0b89351 ("module: relocate module_init
> from init.h to module.h"). This a
On 10/12/2015 11:58 AM, Pat Erley wrote:
On 10/11/2015 08:49 PM, Hanjun Guo wrote:
On 10/12/2015 11:08 AM, Pat Erley wrote:
On 10/05/2015 10:12 AM, Al Stone wrote:
On 10/05/2015 07:39 AM, Rafael J. Wysocki wrote:
On Wednesday, September 30, 2015 10:10:16 AM Al Stone wrote:
On 09/30/2015 03:0
On 12 October 2015 at 05:58, Pranith Kumar wrote:
> Hi Michal,
Hi Pranith,
I've trimmed the CC-list - I doubt all those people care about
building kernel debian packages, and presume they get to read this via
lkml/linux-kbuild anyways.
> Other than that, I keep seeing these errors now:
> dpkg-g
Hi Thomas,
[CC arnd]
On Mon, Oct 12, 2015 at 8:52 AM, Thomas Gleixner wrote:
> On Mon, 12 Oct 2015, Simon Horman wrote:
>> On Fri, Oct 09, 2015 at 02:19:51PM +0200, Thomas Gleixner wrote:
>> > On Wed, 7 Oct 2015, Geert Uytterhoeven wrote:
>> > > On Wed, Oct 7, 2015 at 8:51 PM, kbuild test robot
On 10/12/2015 10:40 AM, Hanjun Guo wrote:
On 10/12/2015 05:01 AM, Thomas Gleixner wrote:
On Tue, 6 Oct 2015, Marc Zyngier wrote:
[This patch series used to be called "Making the generic ACPI GSI
layer irqdomain aware", but as I've radically changed my approach to
this problem, I've decided to r
This patch adds the mfd cell info for axp288 power key device.
Signed-off-by: Borun Fu
Signed-off-by: Fei Yang
---
drivers/mfd/axp20x.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index 3f576b7..3f4e11f 100644
--- a/dri
Hi Julia,
On Sat, Oct 10, 2015 at 2:30 PM, Julia Lawall wrote:
> --- a/arch/arm/mach-shmobile/pm-rmobile.c
> +++ b/arch/arm/mach-shmobile/pm-rmobile.c
> @@ -313,8 +313,10 @@ static int __init rmobile_add_pm_domains(void __iomem
> *base,
> }
>
> pd = kzalloc(sizeof
On 10/12/2015 02:54 PM, Krzysztof Kozlowski wrote:
On 12.10.2015 13:29, Yakir Yang wrote:
Both hsync/vsync polarity and interlace mode can be parsed from
drm display mode, and dynamic_range and ycbcr_coeff can be judge
by the video code.
But presumably Exynos still relies on the DT properties
Hi Kiera,
On Sun, Oct 11, 2015 at 12:39:31PM +0100, Kieran Bingham wrote:
> A change of return status was introduced in commit 3fffd1283927
> ("i2c: allow specifying separate wakeup interrupt in device tree")
Thanks for catching this!
> The commit prevents the defer status being passed up the ca
On Sun, Oct 11, 2015 at 07:42:01PM +0200, Mike Galbraith wrote:
> (change subject, CCs)
>
> On Sun, 2015-10-11 at 04:25 +0200, Mike Galbraith wrote:
>
> > > Is the interactivity the same (horrible) at fe32d3cd5e8e (ie, before the
> > > load tracking rewrite from Yuyang)?
>
> It is the rewrite, 9
On Mon, 12 Oct 2015, Geert Uytterhoeven wrote:
> Hi Julia,
>
> On Sat, Oct 10, 2015 at 2:30 PM, Julia Lawall wrote:
> > --- a/arch/arm/mach-shmobile/pm-rmobile.c
> > +++ b/arch/arm/mach-shmobile/pm-rmobile.c
> > @@ -313,8 +313,10 @@ static int __init rmobile_add_pm_domains(void __iomem
> > *ba
And add the original patch author to CC when resending.
signature.asc
Description: Digital signature
Below is the list of build error/warning regressions/improvements in
v4.3-rc5[1] compared to v4.2[2].
Summarized:
- build errors: +13/-8
- build warnings: +189/-111
JFYI, when comparing v4.3-rc5[1] to v4.3-rc4[3], the summaries are:
- build errors: +13/-6
- build warnings: +54/-51
Note t
When configuring the MDIO subsystem it is also necessary to configure
the TBI register. Make sure the TBI is contained within the mapped
register range in order to:
a) make sure the address is computed correctly
b) make users aware that we're actually accessing that register
In case of error, prin
commit afae5ad78b342f401c28b0bb1adb3cd494cb125a
"net/fsl_pq_mdio: streamline probing of MDIO nodes"
added support for different types of MDIO devices:
1) Gianfar MDIO nodes that only map the MII registers
2) Gianfar MDIO nodes that map the full MDIO register set
3) eTSEC2 MDIO nodes (which map t
Hi Julia,
On Mon, Oct 12, 2015 at 9:24 AM, Julia Lawall wrote:
> On Mon, 12 Oct 2015, Geert Uytterhoeven wrote:
>> On Sat, Oct 10, 2015 at 2:30 PM, Julia Lawall wrote:
>> > --- a/arch/arm/mach-shmobile/pm-rmobile.c
>> > +++ b/arch/arm/mach-shmobile/pm-rmobile.c
>> > @@ -313,8 +313,10 @@ static i
On Mon, Oct 12, 2015 at 9:24 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.3-rc5[1] to v4.3-rc4[3], the summaries are:
> - build errors: +13/-6
+ error: initramfs.c: undefined reference to `__stack_chk_guard':
=> .init.text+0x1615)
i386-randconfig
+ error: regmap-spmi.c: undefin
Dear Geert Uytterhoeven,
On Mon, 12 Oct 2015 09:18:52 +0200, Geert Uytterhoeven wrote:
> > pd = kzalloc(sizeof(*pd), GFP_KERNEL);
> > - if (!pd)
> > + if (!pd) {
> > + of_node_put(np);
> > return -ENOMEM;
>
On Mon, Oct 12, 2015 at 9:29 AM, Thomas Petazzoni
wrote:
> On Mon, 12 Oct 2015 09:18:52 +0200, Geert Uytterhoeven wrote:
>
>> > pd = kzalloc(sizeof(*pd), GFP_KERNEL);
>> > - if (!pd)
>> > + if (!pd) {
>> > + of_node_put(np);
>> >
In order to have the ability to declare a non exclusive shared-dma-pool,
i.e. without the DMA_MEMORY_EXCLUSIVE flag, add the 'no-exclusive' DT
optional parameter to initialize the coherent memory without the flag.
Leave exclusive memory as default.
Signed-off-by: Neil Armstrong
---
drivers/base
The shared-dma-pool dt node only exposes exclusive memory, but in order to
export
non-exclusive coherent memory, add the no-exclusive property and document it.
Neil Armstrong (2):
base: dma-coherent: Add DT property for non exclusive shared-dma-pool
devicetree: reserved-memory: document the o
Document the 'no-exclusive' parameter used for the 'shared-dma-pool'
compatible reserved-memory type.
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree/bindings/
Hi David,
After merging the dwmw2-iommu tree, today's linux-next build (i386
defconfig) failed like this:
In file included from drivers/gpu/drm/i915/i915_drv.h:50:0,
from drivers/gpu/drm/i915/i915_drv.c:34:
include/linux/intel-iommu.h:477:22: error: field 'notifier' has incomplet
* kernel test robot wrote:
> FYI, we noticed the below changes on
>
> git://internal_mailing_list_patch_tree
> Ingo-Molnar/string-Improve-the-generic-strlcpy-implementation
> commit 5f6f0801f5fdfce4984c6a14f99dbfbb417acb66 ("string: Improve the generic
> strlcpy() implementation")
Hm, there'
On 10/12/2015 04:40 AM, yalin wang wrote:
Remove unlikely(order), because we are sure order is not zero if
code reach here, also add if (page == NULL), only allocate page again if
__rmqueue_smallest() failed or alloc_flags & ALLOC_HARDER == 0
The second mentioned change is actually more importa
Hi, Andy
Thanks for your comments.
[Andy] Don't see a relationship between PCI driver and this ACPI stuff.
Although this is a pci driver, we may enumerate the i2c devices from
DSDT table while i2c controllers are enumerated via PCI. In this
scenario, in DSDT, there are descriptions of i2c devices
* Josh Poimboeuf wrote:
> Hi Ingo,
>
> Do you have any more objections to these patches? Would you be willing
> to apply them?
So I still don't like the tool namespace you picked: Git-alike generic naming
plus
subcommands work so much better that I'm not sure why we are even having that
di
Ingo Molnar writes:
> * kernel test robot wrote:
>
>> FYI, we noticed the below changes on
>>
>> git://internal_mailing_list_patch_tree
>> Ingo-Molnar/string-Improve-the-generic-strlcpy-implementation
>> commit 5f6f0801f5fdfce4984c6a14f99dbfbb417acb66 ("string: Improve the
>> generic strlcpy(
On Mon, 2015-10-12 at 09:23 +0200, Peter Zijlstra wrote:
> On Sun, Oct 11, 2015 at 07:42:01PM +0200, Mike Galbraith wrote:
> > (change subject, CCs)
> >
> > On Sun, 2015-10-11 at 04:25 +0200, Mike Galbraith wrote:
> >
> > > > Is the interactivity the same (horrible) at fe32d3cd5e8e (ie, before th
Commit-ID: e9c40d257fdd58c5cc97d3fe3aa141dd23ee5e9d
Gitweb: http://git.kernel.org/tip/e9c40d257fdd58c5cc97d3fe3aa141dd23ee5e9d
Author: Minfei Huang
AuthorDate: Tue, 6 Oct 2015 02:35:55 +0800
Committer: Ingo Molnar
CommitDate: Mon, 12 Oct 2015 09:43:11 +0200
x86/kexec: Remove obsolete '
Commit 7bd3e239d6c6 ("locking: Remove atomicy checks from
{READ,WRITE}_ONCE") removed said warning.
Signed-off-by: Rasmus Villemoes
---
include/linux/compiler.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/compiler.h b/include/linux/compiler.h
index c836eb2
Hi Alexandre,
> -Original Message-
> From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com]
> Sent: 2015年10月12日 14:53
> To: Yang, Wenyou
> Cc: Alessandro Zummo; Ferre, Nicolas; Desroches, Ludovic; rtc-
> li...@googlegroups.com; linux-kernel@vger.kernel.org; linux-arm-
> ker.
Hi, Rafael
The bug has been fixed.
The root cause is the previous commit doesn't cover a hidden logic:
acpi_enable() should rely on the existence of FADT while currently it relies
on the number of loaded tables.
The fix that removes the hidden logic is an ACPICA commit.
Shall we wait until it is
>> I'm not thrilled with incrementing the pointer from i to len, but mixing
>> at positions i+k to i+k+len. The whole LFSR scheme relies on a regular
>> pass structure.
> That part I'm not worried about. We still have a regular pass
> structure --- since for each CPU, we are still iterating over
Hi Sylvain,
The rest of the series looks good to me, one comment below:
On 08/10/2015 at 23:34:34 +0200, Sylvain Rochet wrote :
> watchdog_init_timeout function doesn't try to get the "timeout-sec" DT
> property if timeout_parm is not zero. This change makes this DT property
> working for the sam
On Mon, Oct 12, 2015 at 09:33:55AM +0200, Ingo Molnar wrote:
>
> * kernel test robot wrote:
>
> > FYI, we noticed the below changes on
> >
> > git://internal_mailing_list_patch_tree
> > Ingo-Molnar/string-Improve-the-generic-strlcpy-implementation
> > commit 5f6f0801f5fdfce4984c6a14f99dbfbb417
On 12/10/2015 at 07:48:18 +, Yang, Wenyou wrote :
> > On 12/10/2015 at 09:17:57 +0800, Wenyou Yang wrote :
> > > This patch is to clear the RTC alarm status flag prior to suspending
> > > to avoid the erroneous wake-up activity.
> > >
> >
> > Is this a new issue appearing with the sama5d2 or w
Grygorii,
can you please provide a patch set against 4.1-RT? That stuff rejects
left and right.
Thanks,
tglx
--
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 http://vger.kernel.org/maj
> -Original Message-
> From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com]
> Sent: 2015年10月12日 15:51
> To: Yang, Wenyou
> Cc: Alessandro Zummo; Ferre, Nicolas; Desroches, Ludovic; rtc-
> li...@googlegroups.com; linux-kernel@vger.kernel.org; linux-arm-
> ker...@lists.infr
Commit-ID: 9babcd7929bc8967ae3bb6093f603b93c2f9958f
Gitweb: http://git.kernel.org/tip/9babcd7929bc8967ae3bb6093f603b93c2f9958f
Author: Daniel Bristot de Oliveira
AuthorDate: Thu, 8 Oct 2015 15:36:06 -0300
Committer: Ingo Molnar
CommitDate: Mon, 12 Oct 2015 09:45:25 +0200
sched, tracing
901 - 992 of 992 matches
Mail list logo
