On Mon, May 19, 2014 at 7:03 PM, Thierry Reding
wrote:
> On Mon, May 19, 2014 at 11:22:11AM +0200, Lucas Stach wrote:
>> Am Montag, den 19.05.2014, 11:02 +0200 schrieb Thierry Reding:
>> > On Mon, May 19, 2014 at 04:10:58PM +0900, Alexandre Courbot wrote:
>> > > Some architectures (e.g. ARM) need
On 22 May 2014 17:18, Peter Griffin wrote:
> This patch adds the device tree binding documentation for ST
> SDHCI driver. It contains the differences between the core properties
> in mmc.txt and the properties used by the sdhci-st driver.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe
Lan Tianyu wrote:
> On 05/20/2014 10:17 PM, Rolf Eike Beer wrote:
> > It may be that I have taken the wrong ACPI files. This is the result of a
> > fresh run of acpidump, together with the most recent dmesg.log, just in
> > case I messed it up.
>
> I have check the log. I2C ACPI operation r
On 05/23/2014 04:53 AM, Sasha Levin wrote:
> ping?
I've reproduced it and plan to look at it soon.
Regards,
Hans
>
> On 05/05/2014 11:49 AM, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running latest -next
>> kernel I've stumbled on the follo
Hi Uwe
Le 22/05/2014 20:10, Uwe Kleine-König a écrit :
[...]
Today all imx machines should get their devices from an oftree, so
the various functions to add devices started to bitrot. Moreover
there is no reason to remove a device once it was successfully
added.
Note that platform_device_regist
On 23 May 2014 00:16, Sebastian Hesselbarth
wrote:
> Commit f8ec589b86f6
> "mmc: sdhci-dove: allow GPIOs to be used for card detection on Dove"
> added a gpio based card detect interrupt handler that was hooked up
> into card_tasket.
>
> Commit 3560db8e247a
> "mmc: sdhci: push card_tasklet int
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/arm64/mm/mmu.c between commit a501e32430d4 ("arm64: Clean up the
default pgprot setting") and 206a2a73a62d ("arm64: mm: Create gigabyte
kernel logical mappings where possible") from the arm64 tree and commit
d7ecbddf4cae ("arm
On 5/22/2014 7:03 PM, Nicolas Dichtel wrote:
Le 22/05/2014 17:10, Horia Geanta a écrit :
From: Lei Xu
Currently the sha256 icv truncation length is set to 96bit
while the length is defined as 128bit in RFC4868.
This may result in somer errors when working with other IPsec devices
with the stan
On Tue, Apr 29, 2014 at 01:57:14AM +0200, Andres Freund wrote:
> Hi Dave,
>
> On 2014-04-29 09:47:56 +1000, Dave Chinner wrote:
> > ping?
>
> I'd replied at http://marc.info/?l=linux-mm&m=139730910307321&w=2
I missed it, sorry.
I've had a bit more time to look at this behaviour now and tweaked
On 05/23/2014 04:34 AM, Mike Turquette wrote:
Quoting Sylwester Nawrocki (2014-04-11 05:25:49)
+==Assigned clock parents and rates==
+
+Some platforms require static initial configuration of parts of the clocks
+controller. Such a configuration can be specified in a clock consumer node
+through
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/arm64/include/asm/thread_info.h between commit 449f81a4da4d
("arm64: make a single hook to syscall_trace() for all syscall
features") from the arm64 tree and commit 842514849a61 ("arm64: Remove
TIF_POLLING_NRFLAG") from the ti
On 23.05.2014 06:32, Huang Shijie wrote:
This patch disables the receiver ready interrupt for imx_stop_rx.
It reduces the interrupt numbers when the uart is going to close
or suspend.
Signed-off-by: Huang Shijie
---
drivers/tty/serial/imx.c |4
1 files changed, 4 insertions(+), 0 de
Hi Pete,
On 22/05/14 16:18, Peter Griffin wrote:
ifeq ($(CONFIG_CB710_DEBUG),y)
CFLAGS-cb710-mmc+= -DDEBUG
diff --git a/drivers/mmc/host/sdhci-st.c b/drivers/mmc/host/sdhci-st.c
new file mode 100644
index 000..1790fa7
--- /dev/null
+++ b/drivers/mmc/host/sdhci-st.c
@@ -0,
On Fri, May 23, 2014 at 2:57 PM, George Cherian wrote:
> Currently irq_domain_cleanup is called twice if irq_domain_init fails.
> This causes the following crash.
>
> Unable to handle kernel paging request at virtual address 00100104
> pgd = c0004000
> [00100104] *pgd=
> Internal error: Oo
On Mon, May 19, 2014 at 6:31 PM, Lucas Stach wrote:
> Am Montag, den 19.05.2014, 16:10 +0900 schrieb Alexandre Courbot:
>> From: Lucas Stach
>>
>> Signed-off-by: Lucas Stach
>> [acour...@nvidia.com: make conditional and platform-friendly]
>> Signed-off-by: Alexandre Courbot
>> ---
>> drivers/g
On Mon, May 19, 2014 at 5:46 PM, Thierry Reding
wrote:
> On Mon, May 19, 2014 at 04:10:57PM +0900, Alexandre Courbot wrote:
>> From: Lucas Stach
>>
>> Signed-off-by: Lucas Stach
>> [acour...@nvidia.com: make conditional and platform-friendly]
>> Signed-off-by: Alexandre Courbot
>
> Perhaps havi
The DMA wait queue makes the code very complicated:
For RX, the @->stop_rx hook does not really stop the RX;
For TX, the @->stop_tx hook does not really stop the TX.
The above make the imx_shutdown has to wait the RX/TX DMA to be finished.
In order to make code more simple, this patch removes
Currently irq_domain_cleanup is called twice if irq_domain_init fails.
This causes the following crash.
Unable to handle kernel paging request at virtual address 00100104
pgd = c0004000
[00100104] *pgd=
Internal error: Oops: 805 [#1] SMP ARM
Modules linked in:
CPU: 0 PID: 6 Comm: kworker/u
It's quite possible that multiple pcf857x can be hooked up
to the same interrupt line with the processor. So add IRQF_SHARED
in request irq..
Signed-off-by: George Cherian
---
drivers/gpio/gpio-pcf857x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-pcf857
On 23.5.2014 6:21, Sasha Levin wrote:
On 05/22/2014 09:58 AM, Dave Jones wrote:
Not sure if Sasha has already reported this on -next (It's getting hard
to keep track of all the VM bugs he's been finding), but I hit this overnight
on .15-rc6. First time I've seen this one.
Unfortunately I had t
This patch disables the receiver ready interrupt for imx_stop_rx.
It reduces the interrupt numbers when the uart is going to close
or suspend.
Signed-off-by: Huang Shijie
---
drivers/tty/serial/imx.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/tty/serial/i
The DMA wait queue makes the code very complicated:
For RX, the @->stop_rx hook does not really stop the RX;
For TX, the @->stop_tx hook does not really stop the TX.
The above make the imx_shutdown has to wait the RX/TX DMA to be finished.
In order to make code more simple, this patch removes
On Mon, May 19, 2014 at 5:33 PM, Thierry Reding
wrote:
> On Mon, May 19, 2014 at 04:10:56PM +0900, Alexandre Courbot wrote:
>> From: Lucas Stach
>>
>> On arches with non-coherent PCI,
>
> I guess since this applies to gk20a
>
>> we need to flush caches ourselfes at
>
> "ourselves". Or perhaps eve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One question about this patch.
Why don't you use the devices cgroup check if the root user in that namespace
is allowed to use this device?
This way you can be sure that the root in that namespace can not access devices
to which the host system did
On 22 May 2014 16:00, Mark Brown wrote:
> On Thu, May 22, 2014 at 02:47:07PM +0530, Tushar Behera wrote:
>
>> + max98090->mclk = devm_clk_get(codec->dev, "mclk");
>> + if (!IS_ERR(max98090->mclk))
>> + clk_prepare_enable(max98090->mclk);
>> +
>
> Ths doesn't handle deferred pro
ard_tasklet'
Caused by commit 3560db8e247a ("mmc: sdhci: push card_tasklet into
threaded irq handler").
I have used the mmc tree from next-20140522 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
signature.asc
Description: PGP signature
Hi Chris,
Today's linux-next merge of the mmc tree got a conflict in
include/linux/omap-dma.h between commit a8246fedacad ("dmaengine: omap:
hide filter_fn for built-in drivers") from the slave-dma tree and
commit ee526d515ad1 ("mmc: omap_hsmmc: split omap-dma header file")
from the mmc tree.
I f
Regset active hooks provide a way to query how many registers in the
register set are active at any point of time. Currently this information
is being ignored while creating core dump sections corresponding to any
core note register set. This way the core dump will contain data which are
not part o
On Wed, May 21, 2014 at 12:36:46PM +0900, Jaegeuk Kim wrote:
> Hi Chao,
>
> 2014-05-16 (금), 17:14 +0800, Chao Yu:
> > Previously we allocate pages with no mapping in ra_sum_pages(), so we may
> > encounter a crash in event trace of f2fs_submit_page_mbio where we access
> > mapping data of the page
> - Original Message -
> > From: "Toshiaki Makita"
> > To: "Jon Maxwell" , step...@networkplumber.org
> > Cc: da...@davemloft.net, vyase...@redhat.com,
> > bri...@lists.linux-foundation.org, net...@vger.kernel.org,
> > linux-kernel@vger.kernel.org, jpi...@redhat.com, jmaxw...@redhat.com
On Thu, May 22, 2014 at 5:37 AM, Paul Bolle wrote:
> Checks for CONFIG_EXYNOS_ASV were added in v3.3. But the related Kconfig
> symbol has never been added to the tree. Remove these checks, as they
> always evaluate to false.
>
> Signed-off-by: Paul Bolle
Thanks for pointing this out.
ASV was s
slic_config_get() can fail. Change the return type from void to
int and handle the error in slic_card_init(). So now, instead of
silently failing (and then timing out waiting for the config data),
the driver will fail loudly at request time.
Signed-off-by: David Matlack
---
drivers/staging/slico
This patchset fixes two bugs in slic_card_init(). They are grouped in
a series because the second patch depends on the first (for a merge
without conflicts). In content, they are completely separate changes.
They just touch a few of the same lines.
David Matlack (2):
staging: slicoss: fix dma m
Fix memory leak in slic_card_init. If the driver fails to poll for an
interrupt after requesting config data from the device the dma memory
is never freed.
Signed-off-by: David Matlack
---
This patch was originally sent here https://lkml.org/lkml/2014/5/6/7 with
my google.com email address. But d
Hi, All.
This patch is working on progress?
I want to merge this patch for fixing dw-mmc controller problem.
If this patch didn't work on progress, i will send the patch based-on this
patch.
Best Regards,
Jaehoon Chung
On 05/14/2014 06:53 PM, Ulf Hansson wrote:
> On 7 May 2014 12:06, Ludovic D
On 22 May 2014 20:22, Eduardo Valentin wrote:
> However, on CPUs that needs thermal managment, it makes sense to have
> such dependency, from functional perspective. Mainly because scaling
> frequency and voltage up would be allowed only when thermal management
> is enabled.
AFAIK, dependencies i
Remove the private linked list of netdev structs. This list isn't
being used anyway.
This patch has no noticable effect.
Signed-off-by: David Matlack
---
drivers/staging/slicoss/slic.h| 1 -
drivers/staging/slicoss/slicoss.c | 4
2 files changed, 5 deletions(-)
diff --git a/drivers/st
Fix a use-after-free bug that can cause a kernel oops. If
slic_card_init fails then slic_entry_probe() (the pci probe()
function for this device) will return error without cleaning
up memory (including the registered netdev struct).
Signed-off-by: David Matlack
---
This patch was originally sent
Removes two fields from the private "struct adapter".
memorybase duplicate of slic_regs
memorylengthwritten once and never read. This field is trivially
computed with pci_resource_len if it's ever needed in
the future.
This patch has no noticable effect.
Fix a use-after-free bug that causes a null pointer dereference in
slic_entry_halt().
Since unregister_netdev() will ultimately call slic_entry_halt() (the
net_device ndo_stop() virtual function for this device), we should
call it before freeing the memory that is used by slic_entry_halt().
Specif
First, don't print pci device information or driver prefixes, this
is already printed by dev_err. Next, don't report error messages
via dev_err when the failing function already reports all errors
via dev_err.
Signed-off-by: David Matlack
---
drivers/staging/slicoss/slicoss.c | 28 +-
Fix a bug that only manifests when the physical address of the
interrupt status register is >4GB. Specifically, the driver was only
telling the device about the lower 32 bits of the ISR. This patch adds
the upper 32 bits.
Without this patch, polling the ISR times out whenever the physical
address
As per the TODO file, this patch removes the gratuitous debug
infrastructure. As an extra incentive for removing this code,
the debugfs files are not cleaned up properly. For example, if
register_netdev() fails in slic_entry_probe() then all debugfs
files get left behind, even after the driver modu
Fix two trivial free-after-free bugs in slic_entry_remove.
1. Don't iounmap() the same address twice. adapter->slic_regs
(iounmap()'ed in slic_unmap_mmio_space()) and dev->base_addr
(iounmap()'ed in slic_entry_remove()) are the same region.
2. Don't call release_mem_region() and pci_release_regio
On 22 May 2014 22:07, Stephen Warren wrote:
> It seems rather odd to set both freqs->old and freqs->new to the
> intermediate frequency upon success. It feels like it would make more
> sense to remove that final else clause above, and do the following where
> this function is called:
>
> i
On 05/22/2014 09:58 AM, Dave Jones wrote:
> Not sure if Sasha has already reported this on -next (It's getting hard
> to keep track of all the VM bugs he's been finding), but I hit this overnight
> on .15-rc6. First time I've seen this one.
Unfortunately I had to disable transhuge/hugetlb in my t
On 22 May 2014 22:09, Stephen Warren wrote:
> I think the call to tegra_target_intermediate() is wrong here; shouldn't
> the cpufreq core guarantee that tegra_target_intermediate() has always
> been called before tegra_target(), so there's no need to repeat that
> call here?
That's what Doug requ
On 05/22/2014 02:59 AM, Peter Zijlstra wrote:
> On Wed, May 21, 2014 at 10:34:44PM -0400, Sasha Levin wrote:
>> On 05/21/2014 12:49 PM, Peter Zijlstra wrote:
>>> On Wed, May 21, 2014 at 03:19:48PM +0200, Peter Zijlstra wrote:
> On Wed, May 21, 2014 at 09:08:26AM -0400, Sasha Levin wrote:
>>
On Tue, May 20, 2014 at 09:28:00AM -0700, Luck, Tony wrote:
> When a thread in a multi-threaded application hits a machine
> check because of an uncorrectable error in memory - we want to
> send the SIGBUS with si.si_code = BUS_MCEERR_AR to that thread.
> Currently we fail to do that if the active
ttm_tt_cache_flush's implementation was removed in 2009 by commit
c9c97b8c, but its declaration has been hiding in ttm_bo_driver.h since
then.
It has been surviving in the dark for too long now ; give it the mercy
blow.
Signed-off-by: Alexandre Courbot
Reviewed-by: Thierry Reding
---
include/d
The kerneldoc header of ttm_bo_create() was referring to another
(nonexisting) function and had a few obsolete or incorrect arguments.
Signed-off-by: Alexandre Courbot
---
include/drm/ttm/ttm_bo_api.h | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/include/drm/ttm/ttm_bo
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/bonding/bond_alb.c between commit d0c21d43a5a1 ("bonding:
Send ALB learning packets using the right source") from the net tree
and commit 8557cd74ca8a ("bonding: replace SLAVE_IS_OK() with
bond_slave_can_tx()") fro
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/wireless/iwlwifi/mvm/mac80211.c between commit 7bacc782270f
("iwlwifi: mvm: disable beacon filtering") from the wireless tree and
commit 73e5f2c5d762 ("iwlwifi: remove IWL_UCODE_TLV_FLAGS_BF_UPDATED
flag") from the
Various parts of the kernel acquire and release this mutex,
so add i_mmap_lock_write() and immap_unlock_write() helper
functions that will encapsulate this logic. The next patch
will make use of these.
Signed-off-by: Davidlohr Bueso
---
include/linux/fs.h | 10 ++
1 file changed, 10 inse
Convert all open coded mutex_lock/unlock calls to the
i_mmap_[lock/unlock]_write() helpers.
Signed-off-by: Davidlohr Bueso
---
fs/hugetlbfs/inode.c| 4 ++--
kernel/events/uprobes.c | 4 ++--
kernel/fork.c | 4 ++--
mm/filemap_xip.c| 4 ++--
mm/hugetlb.c| 12
On Wed, May 21, 2014 at 6:16 PM, Linus Walleij wrote:
> On Sat, May 17, 2014 at 7:54 AM, Alexandre Courbot
> wrote:
>
>> of_get_named_gpiod_flags() is visible and directly usable by GPIO
>> consumers, but it really should not as the gpiod interface relies
>> on the simpler gpiod_get() to provide
using this lock, and we can therefore
safely do the conversion. Tests show no throughput regressions in aim7 or
pgbench runs, and we can see gains from sharing the lock, in disk workloads
~+15% for over 1000 users on a 8-socket Westmere system.
This patchset applies on linux-next-20140522.
Thanks
Update the lock to i_mmap_rwsem throughout the kernel.
All changes are in comments and documentation.
Signed-off-by: Davidlohr Bueso
---
include/linux/mmu_notifier.h | 2 +-
kernel/events/uprobes.c | 2 +-
mm/filemap.c | 10 +-
mm/hugetlb.c | 10 +++
The i_mmap_mutex is a close cousin of the anon vma lock,
both protecting similar data, one for file backed pages
and the other for anon memory. To this end, this lock can
also be a rwsem.
This conversion is straightforward. For now, all users take
the write lock.
Signed-off-by: Davidlohr Bueso
-
Similarly to rmap_walk_anon() and collect_procs_anon(),
there is opportunity to share the lock in rmap_walk_file()
and collect_procs_file() for file backed pages.
Signed-off-by: Davidlohr Bueso
---
include/linux/fs.h | 10 ++
mm/memory-failure.c | 4 ++--
mm/rmap.c | 4 ++--
On Thursday 22 May 2014 05:18 PM, Lee Jones wrote:
The TPS65917 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- Over Temperature warning and Shut down.
This patch adds support for tps65917 mfd
On 23 May 2014 01:51, Rickard Strandqvist
wrote:
> Removal of null pointer checks that could never happen
>
> Signed-off-by: Rickard Strandqvist
> ---
The subject should probably be (at least should start with "ASoC: samsung:")
"ASoC: samsung: Remove redundant null pointer check from dma.c"
Wit
On Thu, May 22, 2014 at 5:39 PM, Suravee Suthikulanit
wrote:
> On 5/22/2014 3:20 PM, Bjorn Helgaas wrote:
>> On Thu, May 22, 2014 at 1:17 PM, Borislav Petkov wrote:
>>> On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
I chose Fam16h (0x16) because it looks like that's the
ping?
On 05/05/2014 11:49 AM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel I've stumbled on the following:
>
>
> [ 2179.111265] ==
> [ 2179.112228] [ INFO: possible circular
free the lock, schedule and retake the lock. When aborting, cc->contended is
>> set to signal the contended state to the caller. Two problems have been
>> identified in this mechanism.
>
> This patch (or later version) has hit next-20140522 (in the form
> commit 645ceea933
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/23/2014 02:04 AM, Andy Lutomirski wrote:
> It would be nice to have a way for new programs to declare that they don't
> need vsyscalls. What's the right way to
> do this? An ELF header entry in the loader? An ELF header entry in the
> progra
On Thu, May 22, 2014 at 05:30:51PM +0100, Mel Gorman wrote:
> On Fri, May 23, 2014 at 12:14:16AM +0800, Yuanhan Liu wrote:
> > On Thu, May 22, 2014 at 10:09:36AM +0100, Mel Gorman wrote:
> > > This series is aimed at regressions noticed during reclaim activity. The
> > > first two patches are shrin
On Thu, May 22, 2014 at 07:15:11PM +0200, Robert ABEL wrote:
> I sent this patch to the list on 15 Apr 14.
> However, no activity since. Should I have sent this patch somewhere else?
I have it in my todo queue, sorry for the delay, I've been on the road
for 3 weeks and will be home next week and s
On Thu, May 22, 2014 at 12:22:40AM -0700, Guenter Roeck wrote:
> On 05/22/2014 12:14 AM, Greg Kroah-Hartmann wrote:
> > On Wed, May 21, 2014 at 03:59:58PM -0700, Guenter Roeck wrote:
> >> On Wed, May 21, 2014 at 01:04:04PM -0700, Francesco Ruggeri wrote:
> >>> I have been using an x86 platform.
> >
On Thu, May 22, 2014 at 06:32:03PM +0900, Magnus Damm wrote:
> Hi Dan,
>
> On Thu, May 22, 2014 at 6:17 PM, Dan Carpenter
> wrote:
> > Generally we take things as is into staging so there is no need for a
> > re-work if you don't want to. But we do need a TODO file. Read the
> > TODO files for
On Thu, May 22, 2014 at 07:34:34PM +0200, Fabian Frederick wrote:
> devm_request_and_ioremap was the only function to use device
> instead of dev(this fixes kernel-doc warning).
>
> Also fix some checkpatch warnings.
Each patch should just do 1 thing. Please break this up into a bug fix
patch an
Stephen Rothwell wrote:
>
> Hi Kukjin,
>
Hi Stephen,
> Today's linux-next merge of the samsung tree got a conflict in
> arch/arm/mach-exynos/exynos.c between commit 46bfc99c9225 ("ARM: l2c:
> exynos: convert to generic l2c OF initialisation (and thereby fix it)")
> from the arm tree and commit 3
Devices based on Intel SoC products such as Baytrail have a Power
Management IC. In the PMIC there are subsystems for voltage regulation,
A/D conversion, GPIO and PWMs. The PMIC in Baytrail-T platform is called
Crystal Cove.
This patch adds support for the GPIO function in Crystal Cove.
v2:
- Use
On 05/23/2014 07:13 AM, Stephen Warren wrote:
On 05/21/2014 09:10 PM, f...@marvell.com wrote:
From: Fan Wu
What the patch did:
1.To call pinmux_disable_setting ahead of pinmux_enable_setting in each time of
calling pinctrl_select_state
2.Remove the HW disable operation in in pinmux_disable_
Hyper-V hosts can support multiple targets and multiple channels and larger
number of
LUNs per target. Update the code to reflect this. With this patch we can
correctly
enumerate all the paths in a multi-path storage environment.
MS-TFS: 173725
Signed-off-by: K. Y. Srinivasan
Cc:
---
drivers
On Thu, 22 May 2014, Florian Fainelli wrote:
> +static void brcmstb_l2_intc_irq_handle(unsigned int irq, struct irq_desc
> *desc)
> +{
> + struct brcmstb_l2_intc_data *b = irq_desc_get_handler_data(desc);
> + struct irq_chip *chip = irq_get_chip(irq);
irq_desc_get_chip() is what you want
On 05/23/2014 07:58 AM, 管雪涛 wrote:
>
> - David Miller 写道：
>> From: Chen Gang
>> Date: Wed, 21 May 2014 08:19:34 +0800
>>
>>> 'dccp_timestamp_seed' is initialized once by ktime_get_real() in
>>> dccp_timestamping_init(). It is always less than ktime_get_real()
>>> in dccp_timestamp().
>>>
>>>
Quoting Sylwester Nawrocki (2014-05-19 10:22:51)
> diff --git a/Documentation/devicetree/bindings/clock/clock-bindings.txt
> b/Documentation/devicetree/bindings/clock/clock-bindings.txt
> index 700e7aa..bee649b 100644
> --- a/Documentation/devicetree/bindings/clock/clock-bindings.txt
> +++ b/Docum
On Wed, 2014-05-21 at 21:09 +, Luck, Tony wrote:
> Please do give us more detail on the scenario that you see that would
> make your new version behave better.
>
> I'm sure the current code has no races w.r.t. clearing mces_seen. The
> monarch clears them all in mce_reign() before clearing mc
Quoting Sylwester Nawrocki (2014-04-11 05:25:49)
> >> +==Assigned clock parents and rates==
> >> +
> >> +Some platforms require static initial configuration of parts of the clocks
> >> +controller. Such a configuration can be specified in a clock consumer node
> >> +through clock-parents and clock-
Tested-by: George Spelvin
(I'm running the whole series, but 1b4b:9172 are the devices I have.)
--
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/majordomo-info.html
Pleas
On Thu, May 22, 2014 at 6:07 PM, Guenter Roeck wrote:
> On 05/22/2014 05:43 PM, Linus Torvalds wrote:
>>
>>
>> only s390 seems to need a compat wrapper, and s390 is kind of odd in
>> many respects, so I suspect renameat2 should just use ENTRY_SAME() on
>> parisc, but without any way to *test* it I
On 5/22/2014 7:15 PM, Mika Westerberg wrote:
> I suppose this is dependent on the MFD driver right? If so, this should
> probably be merged along with that patch.
>
The MFD driver has been submitted on LKML as well. I think these two
drivers can be pulled into corresponding trees, and meet each
Hi Kukjin,
Today's linux-next merge of the samsung tree got a conflict in
arch/arm/mach-exynos/exynos.c between commit 46bfc99c9225 ("ARM: l2c:
exynos: convert to generic l2c OF initialisation (and thereby fix it)")
from the arm tree and commit 3919fb954b3a ("ARM: EXYNOS: Remove
exynos_subsys regi
On 5/21/2014 6:16 PM, Grant Likely wrote:
> On Tue, 20 May 2014 19:41:22 -0700, Frank Rowand
> wrote:
>> On 5/18/2014 2:27 AM, Grant Likely wrote:
>>> On Fri, 16 May 2014 11:54:44 +0100, Grant Likely
>>> wrote:
On Thu, 15 May 2014 19:51:17 -0700, Frank Rowand
wrote:
> On 5/13/20
On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys
wrote:
> There are certain client bugs (double unmap, for example) that can cause
> the handle->kmap_cnt (an unsigned int) to wrap around from zero. This
> causes problems when the handle is destroyed because we have:
>
> while (handle->km
On 05/22/2014 05:43 PM, Linus Torvalds wrote:
Miklos,
this is from your commit 18e480aa07f78 ("parisc: add renameat2
syscall") which was acked by Helge Deller:
On Thu, May 22, 2014 at 10:20 AM, Guenter Roeck wrote:
Unfortunately it appears that the parisc changes cause build failures
with pa
On 5/21/2014 8:13 PM, Grant Likely wrote:
> On Tue, 20 May 2014 19:46:19 -0700, Frank Rowand
> wrote:
>> On 5/20/2014 7:41 PM, Frank Rowand wrote:
>> < snip >
>>> I will reply to this email with an additional patch that restores the
>>> original behavior.
>> < snip >
>> From: Frank Rowand
>>
>>
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mach-vexpress/v2m.c between commit 86cb8830d957 ("ARM: l2c:
vexpress: convert to generic l2c OF initialisation") from the arm tree
and commits 3b9334ac835b ("mfd: vexpress: Convert custom func API to
regmap") and d2606
There are certain client bugs (double unmap, for example) that can cause
the handle->kmap_cnt (an unsigned int) to wrap around from zero. This
causes problems when the handle is destroyed because we have:
while (handle->kmap_cnt)
ion_handle_kmap_put(handle);
which takes a
On 05/22/2014 08:03 PM, Daniel Lezcano wrote:
On 05/22/2014 03:50 AM, Yang,Wei wrote:
Hi Daniel,
What do you think of it?
Regards
Wei
On 05/13/2014 11:10 AM, wei.y...@windriver.com wrote:
From: Yang Wei
We do not need to trace read_sched_clock function,
so add notrace attribute for this fun
The false positive lockdep warning is as follows:
=
[ INFO: possible irq lock inversion dependency detected ]
3.10.10+ #1 Not tainted
-
kswapd0/627 just changed the state of lock:
(
[Resending due to mail client crashing]
On 5/21/2014 6:17 PM, Bjorn Helgaas wrote:
[resending because I forgot to copy the lists, sorry guys]
Hi Suravee,
Sorry it took me so long to get to these patches. Here's my proposal. I
reordered them and added some comments in the code and changelogs,
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mach-mvebu/board-v7.c between commit 8ae2473d96f1 ("ARM: l2c:
mvebu: convert to generic l2c OF initialisation") from the arm tree and
commit 5686a1e5aa43 ("bus: mvebu: pass the coherency availability
information at ini
On 5/21/2014 6:17 PM, Bjorn Helgaas wrote:
[resending because I forgot to copy the lists, sorry guys]
Hi Suravee,
Sorry it took me so long to get to these patches. Here's my proposal. I
reordered them and added some comments in the code and changelogs, but I
think your patches look fine as-is
Miklos,
this is from your commit 18e480aa07f78 ("parisc: add renameat2
syscall") which was acked by Helge Deller:
On Thu, May 22, 2014 at 10:20 AM, Guenter Roeck wrote:
>
> Unfortunately it appears that the parisc changes cause build failures
> with parisc 64 bit builds.
>
> Building parisc:a500
This patch provides the common code for the intel_soc_pmic MFD driver,
such as read/write register and set up IRQ.
v2:
- Use regmap instead of our own callbacks for read/write.
- Add one missing EXPORT_SYMBOL.
- Remove some duplicate code and put them into pmic_regmap_load_from_hw.
Signed-off-by:
Crystal Cove is the PMIC in Baytrail-T platform. This patch provides
chip-specific support for Crystal Cove.
v2:
- Add regmap_config for Crystal Cove.
Signed-off-by: Yang, Bin
Signed-off-by: Zhu, Lejun
---
drivers/mfd/intel_soc_pmic_crc.c | 165 +++
1 file c
The Intel SoC PMIC devices are connected to the CPU via the I2C
interface. This patch provides support of the related I2C operations.
v2:
- Use regmap instead of creating our own I2C read/write callbacks.
Signed-off-by: Yang, Bin
Signed-off-by: Zhu, Lejun
---
drivers/mfd/intel_soc_pmic_i2c.c |
Devices based on Intel SoC products such as Baytrail have a Power
Management IC. In the PMIC there are subsystems for voltage regulation,
A/D conversion, GPIO and PWMs. The PMIC in Baytrail-T platform is called
Crystal Cove.
This series contains common code for these PMICs, and device specific
sup
1 - 100 of 795 matches
Mail list logo
