Hi David,
On Thu, Aug 13, 2015 at 04:50:40AM +0100, David Long wrote:
> On 08/11/15 13:31, Will Deacon wrote:
> > On Tue, Aug 11, 2015 at 01:52:38AM +0100, David Long wrote:
> >> + REG_OFFSET_NAME(x30),
> >
> > Does this interact badly with perf tools, which expect to pass "lr" for
> > x30? (see
Add new charger driver support for BQ24261 charger IC.
Signed-off-by: Ramakrishna Pallala
---
drivers/power/Kconfig |6 +
drivers/power/Makefile|1 +
drivers/power/bq24261_charger.c | 1127 +
Hi
On 18 August 2015 at 16:31, Will Deacon wrote:
> On Tue, Aug 18, 2015 at 12:19:13AM +0100, Zhang, Jonathan Zhixiong wrote:
>> On 8/17/2015 3:01 AM, Will Deacon wrote:
>> > On Fri, Aug 14, 2015 at 01:35:53PM +0100, fu@linaro.org wrote:
>> >> diff --git a/arch/arm64/include/asm/acpi.h
The tsl4531_check_id() function returned 1 on "found" and 0 on "not
found" and negative error codes on failure. This was non-standard and
bug prone. The caller treated all non-zero values including error codes
as "found".
This patch fixes it by changing the tsl4531_check_id() to return zero on
On Mon 17-08-15 16:02:54, Tejun Heo wrote:
> Hello, Jan.
>
> On Fri, Aug 14, 2015 at 01:14:09PM +0200, Jan Kara wrote:
> > So the patch looks good to me. But the fact that is fixes Eryu's problem
> > means there is something fishy going on. Either inodes get wrongly attached
>
> Seriously, it
To be honest, I have lost track of this patchset. If you are planning
to redo the other patches can you send it in a new thread?
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
On 18/08/15 09:39, Adrian Hunter wrote:
> On 17/08/15 22:58, Arnaldo Carvalho de Melo wrote:
>> Em Mon, Aug 17, 2015 at 10:09:26PM +0300, Adrian Hunter escreveu:
>>> On 17/08/2015 8:58 p.m., Arnaldo Carvalho de Melo wrote:
Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu:
In a couple of cases the 'comm' member of 'union event' has
been used instead of the correct member ('fork') when processing
exit events.
In the cases where it has been used incorrectly, only the 'pid'
and 'tid' are affected. The 'pid' value would be correct anyway
because it is in the same
On 12-08-15, 15:59, Viresh Kumar wrote:
> Hi Jiri,
>
> Andrew Morton suggested to take these patches through your tree and so
> another resend.
>
> This cleans up the usage of IS_ERR(_OR_NULL)(), where the callers have
> added additional unlikely compiler flag to them. It also fixes the
>
Reviewed-by: Eric Auger
Tested-by: Eric Auger
Best Regards
Eric
On 08/06/2015 07:42 PM, Alex Williamson wrote:
> When a physical I/O device is assigned to a virtual machine through
> facilities like VFIO and KVM, the interrupt for the device generally
> bounces through the host system before
Hi,
On Mon, Aug 17, 2015 at 09:03:38PM +0200, Robert Jarzmik wrote:
> Ezequiel Garcia writes:
>
> > On 16 August 2015 at 19:22, Robert Jarzmik wrote:
> >> Ezequiel Garcia writes:
> >>
> >>> On 11 Aug 09:57 PM, Robert Jarzmik wrote:
> The cases of READID detection are broken on pxa3xx.
When keeping the configuration set by the bootloader (by using
the marvell,nand-keep-config property), the pxa3xx_nand_detect_config()
function is called and set the chunk size to 512 as a default value if
NDCR_PAGE_SZ is not set.
In the other case, when not keeping the bootloader configuration,
On Mon, 17 Aug 2015, Shaohua Li wrote:
> On Mon, Aug 17, 2015 at 03:17:28PM -0700, John Stultz wrote:
> > That said, I agree the "should"s and other vague qualifiers in the
> > commit description you point out should have more specifics to back
> > things up. And I'm fine delaying this (and the
On Tue, Aug 18, 2015 at 12:16:57PM +0530, Ronit Halder wrote:
> This patch fixes the warning generated by sparse
> "cast removes address space of expression" by using ioread16
> function insted of directly dereferencing I/O memory.
>
> Signed-off-by: Ronit halder
Are these really iomem
On Mon, Aug 17, 2015 at 06:01:06PM +0100, Mark Salter wrote:
> The use of mem= could leave part or all of the initrd outside of
> the kernel linear map. This will lead to an error when unpacking
> the initrd and a probable failure to boot. This patch catches that
> situation and relocates the
On 08/06/15 at 07:13pm, Toshi Kani wrote:
> On Thu, 2015-08-06 at 16:12 +0800, Baoquan He wrote:
> E820_PMEM cannot be emulated by the "memmap=" option. Do you have to use
> the "memmap=" options to pass the ranges for kdump kernel? If so, I'd
> rather ignore E820_PMEM and let it be passed as
On Mon, Aug 17, 2015 at 09:06:59AM -0700, Andy Lutomirski wrote:
> >> expected course of actions is:
> >> 1) CPU hits 'test_function'
> >> 2) DB exception is triggered, with RFLAGS.RF=0
> >> 3) DB exception handler sets regs->RFLAGS.RF=1 and perf handler
> >> triggers irq_work pending
Hi!
On 08/18/2015 04:02 PM, Pavel Machek wrote:
Hi!
A bug is reported(https://bugzilla.redhat.com/show_bug.cgi?id=1227208)
Access denied :-(
Might need to register for accessing.
What HW is this on?
Intel Braswell and Broadwell, detail for Broadwell:
Platform: MayanCity
Processor: 2x
If we can reuse nids as many as possible, we can mitigate producing obsolete
node pages in the page cache.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/node.c | 4
1 file changed, 4 insertions(+)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 6e10c2a..3cc32b8 100644
--- a/fs/f2fs/node.c
+++
We should not call unlock_new_inode when insert_inode_locked failed.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/namei.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
index 97e97c4..a680bf3 100644
--- a/fs/f2fs/namei.c
+++ b/fs/f2fs/namei.c
If FG_GC failed to reclaim one section, let's retry with another section
from the start, since we can get anoterh good candidate.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/gc.c | 42 +++---
1 file changed, 19 insertions(+), 23 deletions(-)
diff --git
This patch adds a routine which checks the block address of newly allocated nid.
If an nid has already allocated by other thread due to subtle data races, it
will result in filesystem corruption.
So, it needs to check whether its block address was already allocated or not
in prior to nid
Hi Andrew,
On Tue, 18 Aug 2015 18:44:48 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> mm/Kconfig
Also
mm/Makefile
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
To unsubscribe from this list: send the
Previously, update_inode_page is not called under f2fs_lock_op.
Instead we should call with f2fs_write_inode.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 016ed3b..7faafb5 100644
---
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
mm/Kconfig
between commit:
8025e5ddf9c1 ("[media] mm: Provide new get_vaddr_frames() helper")
from the v4l-dvb tree and commit:
f0b1a174238f ("proc: add kpageidle file")
from the akpm-current tree.
I
On Mon, Aug 17, 2015 at 08:28:16AM -0700, Paul E. McKenney wrote:
> On Mon, Aug 17, 2015 at 11:39:34AM +0100, Alexander Gordeev wrote:
> > Hi Paul,
> >
> > Currently RCU tree distributes CPUs to leafs based on consequent CPU
> > IDs. That means CPUs from remote caches and even nodes might end up
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/net/built-in.o: In function `.vnic_wq_devcmd2_alloc':
(.text+0x49fe40): multiple definition of `.vnic_wq_devcmd2_alloc'
drivers/scsi/built-in.o:(.text+0xb4318): first defined here
On Mon, 17 Aug 2015, John Stultz wrote:
> On Mon, Aug 17, 2015 at 3:04 PM, Thomas Gleixner wrote:
> > On Mon, 17 Aug 2015, John Stultz wrote:
> >
> >> From: Shaohua Li
> >>
> >> >From time to time we saw TSC is marked as unstable in our systems, while
> >
> > Stray '>'
> >
> >> the CPUs declare
On Tue, Aug 18, 2015 at 02:50:55AM +0100, Michael Ellerman wrote:
> On Mon, 2015-08-17 at 09:57 +0100, Will Deacon wrote:
> > On Mon, Aug 17, 2015 at 07:15:01AM +0100, Paul E. McKenney wrote:
> > > On Mon, Aug 17, 2015 at 02:06:07PM +1000, Michael Ellerman wrote:
> > > > On Wed, 2015-08-12 at
Hi Toshi,
Sorry for replying late.
On 08/06/15 at 07:13pm, Toshi Kani wrote:
> On Thu, 2015-08-06 at 16:12 +0800, Baoquan He wrote:
> > Hi Toshi,
> >
> > Does this patch work for you?
>
> Hi Baoquan,
>
> I have tested the patch with both E820_PMEM and E820_PRAM setups, and
> confirmed it
Hi,
On Wed, Jul 29, 2015 at 04:22:45PM +0200, Ludovic Desroches wrote:
> Hi,
>
> This set of patches introduce a driver for the new Atmel SDMMC device avaible
> on SAMA5D2 SoC.
>
> There is also a resend of an old patch which has not been taken. Ulf asked
> for some reviews since it could
On Tue, 18 Aug 2015 09:13:34 +0100
Russell King - ARM Linux wrote:
> On Mon, Aug 17, 2015 at 08:09:17PM -0700, santosh.shilim...@oracle.com wrote:
> > From the logs this seems to be mostly clock related issue for some
> > peripheral. If the bootloader clock enable all hack still exists,
> > may
On Tue, Aug 18, 2015 at 12:19:13AM +0100, Zhang, Jonathan Zhixiong wrote:
> On 8/17/2015 3:01 AM, Will Deacon wrote:
> > On Fri, Aug 14, 2015 at 01:35:53PM +0100, fu@linaro.org wrote:
> >> diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h
> >> index a17b623..ced6e25
Sehr geehrter Post Bank Kunde,
Bitte beachten Sie, dass Ihr online-Banking-Zugang bald ablaeuft. Um diesen
Dienst weiterhin nutzen zu koennen, klicken Sie bitte auf den untenstehenden
Link um Ihren Zugang manuell mit unserem Sicherheits-Update zu aktualisieren.
Am Dienstag, den 18.08.2015, 09:13 +0100 schrieb Russell King - ARM
Linux:
> On Mon, Aug 17, 2015 at 08:09:17PM -0700, santosh.shilim...@oracle.com wrote:
> > From the logs this seems to be mostly clock related issue for some
> > peripheral. If the bootloader clock enable all hack still exists,
>
Hi Marc,
On 08/13/2015 10:28 AM, Marc Zyngier wrote:
> Commit 0a4377de3056 ("genirq: Introduce irq_set_vcpu_affinity() to
> target an interrupt to a VCPU") added just what we needed at the
> lowest level to allow an interrupt to be deactivated by a guest.
>
> When such a request reaches the GIC,
commit bb8175a8aa42 ("mmc: sdhci: clarify DDR timing mode between
SD-UHS and eMMC") added MMC_DDR52 as eMMC's DDR mode to be
distinguished from SD-UHS, but it missed setting driver type for
MMC_DDR52 timing mode.
So sometimes we get the following error on Marvell BG2Q DMP board:
[1.559598]
On Mon, Aug 17, 2015 at 07:07:00AM +0100, AKASHI Takahiro wrote:
> On 08/12/2015 02:03 AM, Will Deacon wrote:
> > On Tue, Aug 04, 2015 at 08:44:06AM +0100, AKASHI Takahiro wrote:
> >> A stack frame pointer may be used in a different way depending on
> >> cpu architecture. Thus it is not always
Since 16 bit half word exchange was not there and MCS based qspinlock by
Waiman's xchg_tail() requires an atomic exchange on a half word, here is a
small modification to __xchg() code to support the exchange.
ARMv6 and lower does not have support for LDREXH, so we need to make sure
things do
On Mon, Aug 17, 2015 at 08:09:17PM -0700, santosh.shilim...@oracle.com wrote:
> From the logs this seems to be mostly clock related issue for some
> peripheral. If the bootloader clock enable all hack still exists,
> may be you can try that out.
>
> Another way to debug this is to start disabling
Hello Krzysztof,
On 08/18/2015 10:09 AM, Krzysztof Kozlowski wrote:
> On 18.08.2015 17:05, Javier Martinez Canillas wrote:
>> Hello Krzysztof,
>>
>> On 08/18/2015 09:57 AM, Krzysztof Kozlowski wrote:
>>> On 18.08.2015 16:01, Javier Martinez Canillas wrote:
The ChromeOS mfd driver
Hello,
On 2015-06-10 10:41, Nicholas Mc Guire wrote:
All architectures except arm that define DMA_ERROR_CODE are casting it
to (dma_addr_t) - as it is always compared to dma_addr_t in arm as well
this could be harmonized.
Signed-off-by: Nicholas Mc Guire
Acked-by: Marek Szyprowski
---
On 18.08.2015 17:05, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 08/18/2015 09:57 AM, Krzysztof Kozlowski wrote:
>> On 18.08.2015 16:01, Javier Martinez Canillas wrote:
>>> The ChromeOS mfd driver (MFD_CROS_EC) select the CROS_EC_PROTO config
>>> symbol because the driver uses some
* NeilBrown [150729 17:29]:
> Now that twl4030_bci_probe can safely return -EPROBE_DEFER,
> do so when devm_usb_get_phy_by_node returns that error.
>
> Signed-off-by: NeilBrown
> ---
> drivers/power/twl4030_charger.c |6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff
Dear Customer,
Your access has been placed on hold. Click on the account reactivation form
attached to unlock your account.
Thank you
OCBC
customer_unlock.pdf
Description: Binary data
Hello Krzysztof,
On 08/18/2015 09:57 AM, Krzysztof Kozlowski wrote:
> On 18.08.2015 16:01, Javier Martinez Canillas wrote:
>> The ChromeOS mfd driver (MFD_CROS_EC) select the CROS_EC_PROTO config
>> symbol because the driver uses some communication helper functions in
>>
On Mon, 2015-08-17 at 16:46 -0700, Tim Bird wrote:
> Sorry - I mistyped Ivan's e-mail the first time.
>
> On 08/17/2015 04:43 PM, Tim Bird wrote:
> > Ivan,
> >
> > I'm seeing a bug in the phy-msm-usb.c code, when I get an EPROBE defer
> > during probing the driver.
> > The code is statically
Hi!
> >>>A bug is reported(https://bugzilla.redhat.com/show_bug.cgi?id=1227208)
> >
> >Access denied :-(
> >
> Might need to register for accessing.
> >
> >What HW is this on?
> >
> Intel Braswell and Broadwell, detail for Broadwell:
> Platform: MayanCity
> Processor: 2x BROADWELL BDX_EP A0 QHPR
On 18.08.2015 16:01, Javier Martinez Canillas wrote:
> The ChromeOS mfd driver (MFD_CROS_EC) select the CROS_EC_PROTO config
> symbol because the driver uses some communication helper functions in
> drivers/platform/chrome/cros_ec_proto.c but other drivers depends on
> CROS_EC_PROTO instead.
* Linus Torvalds wrote:
> On Mon, Aug 17, 2015 at 3:59 AM, Denys Vlasenko wrote:
> >
> > I have it running linux 2.6.20 and busybox here:
> >
> > http://busybox.net/live_bbox/live_bbox.html
> >
> > (or rather, *you* will have it running linux 2.6.20 inside your browser,
> > after you click on
Signed-off-by: Tomer Barletz
---
drivers/usb/host/xhci-pci.c | 90 ++---
1 file changed, 45 insertions(+), 45 deletions(-)
diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index 5590eac..c79d336 100644
---
Right now even if driver failed to probe extcon framework will
still deliver its VBUS and ID events, which will lead to random
exception codes.
Fix this by removing driver interest for VBUS and ID events when
probe fail.
Fixes: 591fc116f330 ("usb: phy: msm: Use extcon framework for VBUS and ID
* Andy Lutomirski wrote:
> On Mon, Aug 17, 2015 at 1:01 AM, Ingo Molnar wrote:
>
> > So when I re-introduced static allocations math-emu started working again,
> > to
> > a limited degree: on a modern distro, trying to boot /bin/bash I got a
> > prompt,
> > but various programs would
* Andrew Morton wrote:
> On Tue, 18 Aug 2015 07:38:25 +0200 Christoph Hellwig wrote:
>
> > On Mon, Aug 17, 2015 at 02:24:29PM -0700, Andrew Morton wrote:
> > > 110254 bytes saved, shrinking the kernel by a whopping 0.17%.
> > > Thoughts?
> >
> > Sounds fine to me.
>
> OK, I'll clean it up
On Mon, Aug 17, 2015 at 05:07:06PM -0400, Jarod Wilson wrote:
> On 2015-08-14 7:41 PM, Jarod Wilson wrote:
> >
> >Yeah, my thinking was that it should mean "there's at least one lro
> >capable slave". If we just leave things the way they are though, I think
> >its confusing on the user side -- it
Hi,
I have bisected the issue down to
[045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem
Bisecting has been a painful job due to the fact that the bug may show only many
hours after the system boot.
The commit above in fact is not the culprit, but a fix to an issue
On Tue, Aug 18, 2015 at 3:37 AM, Nicholas Krause wrote:
> This fixes error handling in the function max732x_irq_bus_sync_unlock
> by checking if the internal call in this function's while loop to the
> function max732x_gpio_direction_input failed by returning a error code
> and if so break out of
Your commit subject is missing a space after "gpio:"
On Tue, Aug 18, 2015 at 2:07 AM, Nicholas Krause wrote:
> This fixes the incorrect variable assignment in the function
> __gpiod_request of not assigning the variable status to the
> return value of the function gpiod_get_direction before this
* Jiang Liu wrote:
> With current implementation, all CPUs within a NUMA node will be
> assocaited with another NUMA node if the node has no memory installed.
typo.
>
> For example, on a four-node system, CPUs on node 2 and 3 are associated
> with node 0 when are no memory install on node 2
Document the device-tree binding of MediaTek display PWM.
The PWM has one channel to control the backlight brightness for display.
It supports MT8173 and MT6595.
Signed-off-by: YH Huang
---
.../devicetree/bindings/pwm/pwm-mtk-disp.txt | 42
1 file changed, 42
Add display PWM node in mt8173-evb.dts and mt8173.dtsi.
Signed-off-by: YH Huang
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 13 +
arch/arm64/boot/dts/mediatek/mt8173.dtsi| 22 ++
2 files changed, 35 insertions(+)
diff --git
Add display PWM driver support to modify backlight for MT8173 and MT6595.
The PWM has one channel to control the brightness of the display.
When the (high_width / period) is closer to 1, the screen is brighter;
otherwise, it is darker.
Signed-off-by: YH Huang
---
drivers/pwm/Kconfig|
This patch series add the use of display PWM driver, documentation
and device tree for Mediatek SoCs. The driver is used to support
the backlight of the panel. This is based on v4.2-rc1.
The clock definitions (CLK_MM_DISP_PWM*) are added by James Liao's patch:
clk: mediatek: Add subsystem
The linux/audit.h header uses EM_MICROBLAZE in order to define
AUDIT_ARCH_MICROBLAZE, but it's only available in the microblaze
asm headers. Move it to the common elf-em.h header so that the
define can be used on non-microblaze systems. Otherwise we get
build errors that EM_MICROBLAZE isn't
Hi Vaishali,
On 08/18/2015 07:46 AM, Vaishali Thakkar wrote:
On Mon, Aug 17, 2015 at 2:02 PM, Vaishali Thakkar
wrote:
On 17 Aug 2015 13:57, "Jacek Anaszewski" wrote:
Hi Vaishali,
Thanks for the patch. Unfortunately it causes build break.
Please fix the issues and resubmit.
Oops! I am
Ping?
> -Original Message-
> From: Anurag Kumar Vulisha [mailto:anurag.kumar.vuli...@xilinx.com]
> Sent: Wednesday, August 05, 2015 5:18 PM
> To: dan.j.willi...@intel.com; vinod.k...@intel.com; Michal Simek; Soren
> Brinkmann; srikanth.thok...@xilinx.com; maxime.ripard@free-
>
On Mon, Aug 17, 2015 at 6:32 PM, Vaishali Thakkar
wrote:
> On Mon, Aug 17, 2015 at 12:47 PM, Alexandre Courbot wrote:
>> On Thu, Aug 13, 2015 at 4:29 PM, Vaishali Thakkar
>> wrote:
>>> Use managed resource functions devm_clk_put and
>>> devm_snd_soc_register_component to simplify error
Sehr geehrter Post Bank Kunde,
Bitte beachten Sie, dass Ihr online-Banking-Zugang bald ablaeuft. Um diesen
Dienst weiterhin nutzen zu koennen, klicken Sie bitte auf den untenstehenden
Link um Ihren Zugang manuell mit unserem Sicherheits-Update zu aktualisieren.
of_clk_set_defaults uses the type 'bool', but clk-conf.h does not
include its definition.
This results in a compile error when only clk-conf.h is used.
Signed-off-by: Chen-Yu Tsai
Cc: sta...@vger.kernel.org
---
include/linux/clk/clk-conf.h | 2 ++
1 file changed, 2 insertions(+)
diff --git
The boolean CROS_EC_PROTO symbol is selected by MFD_CROS_EC but that can
cause Kconfig circular dependencies so is better to change the select to
a depends on. But in order to be able to change that, the CROS_EC_PROTO
symbol has to be one that can be selected by the user.
Signed-off-by: Javier
Il 18/08/2015 05:25, Han Xu ha scritto:
i.MX6QP and i.MX7D BCH module integrated a new feature to detect the
bitflip number for erased NAND page. So for these two platform, set the
erase threshold to gf/2 and if bitflip detected, GPMI driver will
correct the data to all 0xFF.
Please also fix
The ChromeOS mfd driver (MFD_CROS_EC) select the CROS_EC_PROTO config
symbol because the driver uses some communication helper functions in
drivers/platform/chrome/cros_ec_proto.c but other drivers depends on
CROS_EC_PROTO instead. Mixing select and depends can lead to circular
Kconfig
The ChromeOS mfd driver (MFD_CROS_EC) select the CROS_EC_PROTO config
symbol because the driver uses some communication helper functions in
drivers/platform/chrome/cros_ec_proto.c but other drivers depends on
CROS_EC_PROTO instead. Mixing select and depends can lead to circular
Kconfig
On 18.08.2015 15:29, Pankaj Dubey wrote:
> From: Yadwinder Singh Brar
>
> With default config on smdk5250 latest tree throws below message :
>
> [2.226049] thermal thermal_zone0: critical temperature reached(224
> C),shutting down
> [2.227840] reboot: Failed to start orderly shutdown:
From: Naresh Kamboju
zram: Compressed RAM based block devices
The zram module creates RAM based block devices named /dev/zram
( = 0, 1, ...). Pages written to these disks are compressed and stored
in memory itself. These disks allow very fast I/O and
The ChromeOS mfd driver (MFD_CROS_EC) select the CROS_EC_PROTO config
symbol because the driver uses some communication helper functions in
drivers/platform/chrome/cros_ec_proto.c but other drivers depends on
CROS_EC_PROTO instead. Mixing select and depends can lead to circular
Kconfig
On Mon, Aug 17, 2015 at 10:25:07PM -0500, Han Xu wrote:
> support GPMI NAND on i.MX6UL
>
> Signed-off-by: Han Xu
> ---
> drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 9 +
> drivers/mtd/nand/gpmi-nand/gpmi-nand.h | 6 --
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git
Hi Linus,
After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/media/i2c/tc358743.c: In function 'tc358743_probe_of':
drivers/media/i2c/tc358743.c:1786:22: error: too few arguments to function
'devm_gpiod_get'
state->reset_gpio =
On Mon, Aug 17, 2015 at 10:25:01PM -0500, Han Xu wrote:
> i.MX6QP and i.MX7D BCH module integrated a new feature to detect the
> bitflip number for erased NAND page. So for these two platform, set the
> erase threshold to gf/2 and if bitflip detected, GPMI driver will
> correct the data to all
Instead of having each i2c driver individually parse device tree data in
case it or platform supports separate wakeup interrupt, and handle
enabling and disabling wakeup interrupts in their power management
routines, let's have i2c core do that for us.
Platforms wishing to specify separate wakeup
On Mon, Aug 17, 2015 at 10:24:55PM -0500, Han Xu wrote:
> support GPMI NAND on i.MX7D
>
> Signed-off-by: Han Xu
> ---
> drivers/mtd/nand/gpmi-nand/bch-regs.h | 14 +++---
> drivers/mtd/nand/gpmi-nand/gpmi-lib.c | 10 ++
> drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 24
This patch fixes the warning generated by sparse
"cast removes address space of expression" by using ioread16
function insted of directly dereferencing I/O memory.
Signed-off-by: Ronit halder
---
drivers/staging/fbtft/fb_agm1264k-fl.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
On 17/08/15 22:58, Arnaldo Carvalho de Melo wrote:
> Em Mon, Aug 17, 2015 at 10:09:26PM +0300, Adrian Hunter escreveu:
>> On 17/08/2015 8:58 p.m., Arnaldo Carvalho de Melo wrote:
>>> Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu:
On 17/08/2015 6:52 p.m., Arnaldo Carvalho de
On Mon, Aug 17, 2015 at 10:24:49PM -0500, Han Xu wrote:
> By default NAND driver will choose the highest ecc strength that oob
> could contain, in this case, for some 8K+744 NAND flash, the ecc
> strength will be up to 52bit, which beyonds the i.MX6QDL BCH capability
> (40bit).
>
> This patch
13.08.2015 23:07, Linus Torvalds пишет:
On Thu, Aug 13, 2015 at 12:59 PM, Stas Sergeev wrote:
It doesn't: fedora provides a "sanitized up" version of sigcontext.h
in /usr/include/bits, which comes from glibc-headers-2.21-7.fc22.x86_64.
So it seems the "sanitized up" headers come from glibc,
Sebastian Herbszt writes:
> Johannes Thumshirn wrote:
>> If the bf_get() call in lpfc_mbx_cmpl_rdp_page_a2() does succeeds, execution
>> continues normally and mp gets kfree()d.
>>
>> If the subsequent call to lpfc_sli_issue_mbox() fails execution jumps to the
>> error label where
On Mon, Aug 17, 2015 at 10:26:23AM -0700, Mark Brown wrote:
> On Mon, Aug 17, 2015 at 09:07:08AM +0800, Peter Chen wrote:
> > On Fri, Aug 14, 2015 at 05:47:46PM +0800, Baolin Wang wrote:
>
> > > + 1500,
> > > + 1800,
> > > + 550,
> > > +};
>
> > Why 550 is the last, but not 1800?
>
> You'd have
13.08.2015 20:00, Brian Gerst пишет:
On Thu, Aug 13, 2015 at 11:43 AM, Andy Lutomirski wrote:
On Thu, Aug 13, 2015 at 8:37 AM, Linus Torvalds
wrote:
On Tue, Aug 11, 2015 at 5:17 PM, Stas Sergeev wrote:
I realize this patch may be good to have in general, but
breaking userspace without a
From: Yadwinder Singh Brar
With default config on smdk5250 latest tree throws below message :
[2.226049] thermal thermal_zone0: critical temperature reached(224
C),shutting down
[2.227840] reboot: Failed to start orderly shutdown: forcing the issue
and hangs randomly because it reads
This fixes the following error:
drivers/dma/pxa_dma.c: In function ‘dbg_show_requester_chan’:
drivers/dma/pxa_dma.c:192:2: error: void value not ignored as it ought to be
pos += seq_printf(s, "DMA channel %d requester :\n", phy->idx);
^
drivers/dma/pxa_dma.c:197:8: error: void value not
14.08.2015 04:37, Andy Lutomirski пишет:
On Thu, Aug 13, 2015 at 6:32 PM, Stas Sergeev wrote:
14.08.2015 04:21, Andy Lutomirski пишет:
On Thu, Aug 13, 2015 at 5:50 PM, Stas Sergeev wrote:
14.08.2015 03:27, Linus Torvalds пишет:
On Thu, Aug 13, 2015 at 5:17 PM, Stas Sergeev wrote:
For
On Tue, Aug 18, 2015 at 02:02:49AM -0400, Raphaël Beamonte wrote:
> 2015-08-18 1:44 GMT-04:00 Sudip Mukherjee :
> > I think that will be better, since you are sending the patch for
> > consistent spacing.
>
> Actually, going through the bunch of patches, it seems that the
> whitespace neatening
Hi Liu,
On 08/17/2015 11:19 AM, Jiang Liu wrote:
..
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index b3a1a5d77d92..5d7ad70ace0d 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -2069,6 +2069,9 @@ config USE_PERCPU_NUMA_NODE_ID
def_bool y
depends on NUMA
On Tue, Aug 18, 2015 at 01:27:31AM -0400, Raphaël Beamonte wrote:
> 2015-08-18 0:24 GMT-04:00 Sudip Mukherjee :
> >> + netdev_err("[Sendconfigpkt]Get Timed out\n");
> > This will not compile. you can not just replace printk with
> > netdev_*, you need to mention a
Hi Andrew,
On Tue, 18 Aug 2015 07:53:15 +0200 Christoph Hellwig wrote:
>
> On Mon, Aug 17, 2015 at 10:45:52PM -0700, Andrew Morton wrote:
> > > >
> > > > I'll merge these 5 patches for 4.3. That means I'll release them into
> > > > linux-next after 4.2 is released.
> > >
> > > So you only add
This patch moves the data allocated using dma_alloc_coherent to the
corresponding managed interface. To be compatible with the change,
various gotos are replaced with direct returns and unneeded labels
are dropped.
Signed-off-by: Vaishali Thakkar
---
drivers/crypto/sahara.c | 46
> rt2500usb_validate_eeprom() read data up to 0x6e (EEPROM_CALIBRATE_OFFSET)
> but only 0x6a bytes has been allocated and read from the eeprom.
>
> This lead to out-of-bound accesses and invalid values for
> EEPROM_BBPTUNE_R17 and EEPROM_CALIBRATE_OFFSET.
>
> Change the EEPROM_SIZE to 0x6e in
2015-08-18 1:44 GMT-04:00 Sudip Mukherjee :
> I think that will be better, since you are sending the patch for
> consistent spacing.
Actually, going through the bunch of patches, it seems that the
whitespace neatening one is taking care of that. That one patch was
mostly about taking care of the
Hi Greg,
After merging the tty tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
make[2]: *** No rule to make target 'arch/arm/boot/dts/imx6sl-fox-p1.dtb',
needed by '__build'. Stop.
Caused by commit
189550b8644e ("serial: imx: introduce serial_imx_enable_wakeup()")
On Mon, Aug 17, 2015 at 10:45:52PM -0700, Andrew Morton wrote:
> > >
> > > I'll merge these 5 patches for 4.3. That means I'll release them into
> > > linux-next after 4.2 is released.
> >
> > So you only add for-4.3 code to -next after 4.2 is odd? Isn't thast the
> > wrong way around?
>
>
501 - 600 of 1202 matches
Mail list logo