Hi,
On Wed, Apr 29, 2015 at 11:31:49AM +0300, Vladimir Davydov wrote:
> On Wed, Apr 29, 2015 at 01:57:59PM +0900, Minchan Kim wrote:
> > On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> > > @@ -69,6 +69,14 @@ There are four components to pagemap:
> > > memory cgroup each pag
Hi Ram,
I added some comment.
If you fix minor issue according to comment, I'll apply it.
On 04/30/2015 10:43 AM, 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 s
On (04/30/15 15:44), Minchan Kim wrote:
> > > I think the problem of deadlock is that you are trying to remove sysfs
> > > file
> > > in sysfs handler.
> > >
> > > #> echo 1 > /sys/xxx/zram_remove
> > >
> > > kernfs_fop_write - hold s_active
> > > -> zram_remove_store
> > > -> zram_remove
On Thu, Apr 30, 2015 at 03:34:57PM +0900, Sergey Senozhatsky wrote:
> Hello Minchan,
>
> On (04/30/15 14:47), Minchan Kim wrote:
> [..]
> >
> > Isn't it related to bd_mutex?
>
> I think it is:
>
> [ 216.713922] Possible unsafe locking scenario:
> [ 216.713923]CPU0
On (04/30/15 15:34), Sergey Senozhatsky wrote:
> > Isn't it related to bd_mutex?
>
> I think it is:
>
I meant: I think it's related
> [ 216.713922] Possible unsafe locking scenario:
> [ 216.713923]CPU0CPU1
> [ 216.713924]
> [
On Tue, Apr 28, 2015 at 5:23 PM, Yingjoe Chen wrote:
>
> The 8173 pinctrl node doesn't follow dts convention. Fix them.
> Also add a comment to explain pinctrl register usage to make it
> more clear.
>
> Signed-off-by: Yingjoe Chen
Thanks for the fix.
Reviewed-by: Daniel Kurtz
>
> ---
> arch
Hello Minchan,
On (04/30/15 14:47), Minchan Kim wrote:
[..]
>
> Isn't it related to bd_mutex?
I think it is:
[ 216.713922] Possible unsafe locking scenario:
[ 216.713923]CPU0CPU1
[ 216.713924]
[ 216.713925] lock(&bdev->bd_mu
Adds a OP-TEE driver which also can be compiled as a loadable module.
* Targets ARM and ARM64
* Supports using reserved memory from OP-TEE as shared memory
* CMA as shared memory is optional and only tried if OP-TEE doesn't
supply a reserved shared memory region
* Probes OP-TEE version using SMC
Hi,
This patch set introduces a generic TEE subsystem. The TEE subsystem will be
able contain drivers for various TEE implementations. A TEE (Trusted
Execution Environment) is a trusted OS running in some secure environment,
for example, TrustZone on ARM cpus, or a separate secure co-processor etc
Initial patch for generic TEE subsystem.
This subsystem provides:
* Registration/un-registration of TEE drivers.
* Shared memory between normal world and secure world.
* Ioctl interface for interaction with user space.
A TEE (Trusted Execution Environment) driver is a driver that interfaces
with a
On Thu, Apr 30, 2015 at 1:59 AM, Benjamin Poirier wrote:
> Signed-off-by: Benjamin Poirier
> Fixes: 9e311e7 ("net/mlx4_en: Use affinity hint")
> ---
Good catch.
Acked-by: Amir Vadai
Thanks,
Amir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messag
On Fri, Apr 24, 2015 at 12:15:59PM +1000, NeilBrown wrote:
> On Thu, 23 Apr 2015 14:55:59 +0800 Huang Ying wrote:
>
> > FYI, we noticed the below changes on
> >
> > git://neil.brown.name/md for-next
> > commit 878ee6792799e2f88bdcac329845efadb205252f ("RAID5: batch adjacent
> > full stripe writ
Some clocks are so critical to the system that they must never be turned
off unless explicitly requested. Normally unused clocks get disabled in
the clk_disable_unused initcall. Currently there are two ways for
keeping clocks enabled even if they are unused, both with their own
drawbacks:
- The CL
On 04/15/15 11:52, Hugh Dickins wrote:
We are using kernel-3.10.49 and I have gone through patches of ksm above this
>kernel version but didn't find anything relevant w.r.t issue. The latest
>patch which we have for KSM on our tree is
>
>668f9abb: mm: close PageTail race
I agree, I don't think 3
Method ABRT is to be used by driver to disable BIOS handling of radio
button. So the changes in behaviours observed by Gabriele is expected.
I have seen other systems behave the same way.
I do also see firmware only sends Notify(RBTN, 0x80) and no hard block
whether ABRT(1) is called or not. Thus
On Wed, Apr 29, 2015 at 12:40:15PM -0400, Pranith Kumar wrote:
> On Wed, Apr 29, 2015 at 10:59 AM, mancha security
> wrote:
> >
> > The problem is that ICC defines __GNUC__ so barrier() gets defined
> > in compiler-gcc.h. Your commit removed an #undef from
> > compiler-intel.h so compiler.h will n
Hi Jean,
On Thu, 30 Apr 2015 07:28:33 +0200 Jean Delvare wrote:
>
> Sorry I forgot to notify you. There is a permanent redirect from the
> latter to the former so both are the same, no worry. Feel free to
> update your source to the new location whenever you want.
Done.
--
Cheers,
Stephen Roth
On Tue, Apr 28, 2015 at 12:17:50PM +0200, Geert Uytterhoeven wrote:
> As of commit 914d7d148411997c ("ARM: shmobile: r8a73a4: Remove legacy
> code"), the Renesas R-Mobile/R-Car interrupt controller is used with DT
> only, and interrupt numbers are thus always assigned automatically.
>
> Drop the p
Hello Sergey,
On Wed, Apr 29, 2015 at 04:23:28PM +0900, Sergey Senozhatsky wrote:
> On (04/29/15 16:02), Sergey Senozhatsky wrote:
> > sure. I was talking about this one:
> >
> > CPU0CPU1
> > umount
> > zram_remove()
> > lock ->bd_mutex
> > zram_reset_devic
>From a6615937bcd9234e6d6bb817c3701fce44d0a84d Mon Sep 17 00:00:00 2001
From: Felipe Balbi
Date: Tue, 30 Sep 2014 16:08:03 -0500
Subject: [PATCH] usb: gadget: composite: enable BESL support
commit a6615937bcd9234e6d6bb817c3701fce44d0a84d upstream.
According to USB 2.0 ECN Errata for Link Power
M
Hi Stephen,
On Thu, 30 Apr 2015 10:44:49 +1000, Stephen Rothwell wrote:
> I noticed commit a95d7600d9c4 ("hwmon: Update the location of my quilt
> tree") in the hwmon-staging tree. It says that the quilt series is at
> http://jdelvare.nerim.net/devel/linux/jdelvare-hwmon/ but inlinux-next
> I am
From: Geert Uytterhoeven
Signed-off-by: Geert Uytterhoeven
Signed-off-by: Simon Horman
---
drivers/sh/pm_runtime.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/sh/pm_runtime.c b/drivers/sh/pm_runtime.c
index 89b7785de1fc..fe8875f0d7be 100644
--- a/drivers/sh/pm
From: Geert Uytterhoeven
If the default PM domain using PM_CLK is used for PM runtime, the real PM
domain(s) cannot be registered from DT later.
Hence do not enable it when running a multi-platform kernel with genpd
support on an sh73a0. The R-Mobile PM domain driver will take care of
PM runtime
From: Geert Uytterhoeven
If the default PM domain using PM_CLK is used for PM runtime, the real PM
domain(s) cannot be registered from DT later.
Hence do not enable it when running a multi-platform kernel with genpd
support on an r8a73a4. The R-Mobile PM domain driver will take care of
PM runtim
On 04/30/2015 02:05 PM, Guenter Roeck wrote:
> On 04/29/2015 09:07 PM, Beomho Seo wrote:
>> This patch adds support for the ntc thermistor NCPXXWF104 serises.
>>
>
> series :-)
>
>> Cc: Jean Delvare
>> Cc: Guenter Roeck
>> Signed-off-by: Beomho Seo
>
> Applied to -next.
>
> Thanks,
> Guenter
Hi Linus,
Please consider these SH drivers updates for v4.1.
I am sending this change after v4.1-rc1 has been released
as it depends on SoC changes which are present in that rc release.
The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
Linux 4.1-rc1 (2015-04-26 17:
Hi all,
Changes since 20150429:
The sound-asoc tree gained a build failure so I used the version from
next-20150429.
The akpm-current tree gained a conflict against the livepatching tree.
Non-merge commits (relative to Linus' tree): 1107
1110 files changed, 73625 insertions(+),
When checking for overflow, the code in mm/mmap.c compares the first byte
*after* the end of mapped region to the start of the region instead of the
last byte of the mapped region. This prevents mapping a region which abuts
the end of physical space, as mmap() incorrectly rejects the region with
-
On 04/29/2015 09:07 PM, Beomho Seo wrote:
This patch adds support for the ntc thermistor NCPXXWF104 serises.
series :-)
Cc: Jean Delvare
Cc: Guenter Roeck
Signed-off-by: Beomho Seo
Applied to -next.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-ker
On Tue, 2015-04-28 at 11:30 -0700, Mark Fasheh wrote:
> 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
/scm/linux/kernel/git/cmetcalf/linux-tile
# extra tests on tree/branch next/master
git bisect good 6b1330a4f1b25f474aa2b9bcaf941e26abfe30af # 23:50 60+
80 Add linux-next specific files for 20150429
This script ma
On Wed, 2015-04-29 at 21:32 +0200, Fabian Frederick wrote:
> typedef is not really useful here. Replace it by structure
> to improve readability.typedef should only be used in some cases.
> (See Documentation/CodingStyle Chapter 5 for details).
trivia:
> diff --git a/drivers/cpufreq/pxa2xx-cpufre
The struct clocksource 'mct_frc' is not exported and used outside so
make it static.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clocksource/exynos_mct.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/exynos_mct.c b/drivers/clocksource/exynos_mct.c
ind
Since commit 228e3023eb04 ("Merge tag 'mct-exynos-for-v3.10' of ...") the
mct_init() was superseded by mct_init_dt() and is not referenced
anywhere. Remove it.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clocksource/exynos_mct.c | 12
1 file changed, 12 deletions(-)
diff --git a
Return value of exynos4_mct_tick_clear() was never checked so it can
be safely changed to void.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clocksource/exynos_mct.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/clocksource/exynos_mct.c b/drivers/clocksour
On Thursday 30 April 2015 10:06 AM, Preeti Murthy wrote:
> On Wed, Apr 29, 2015 at 10:49 PM, Shreyas B Prabhu
> wrote:
>>
>>
>> On Wednesday 29 April 2015 10:38 PM, Steven Rostedt wrote:
I am not sure if its worth the effort now. It doesn't look like any
other trace point apart from th
On Thu, Apr 30, 2015 at 12:58:12PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 01:18 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:39PM +1000, Alexey Kardashevskiy wrote:
> >>The pnv_pci_ioda_tce_invalidate() helper invalidates TCE cache. It is
> >>supposed to be called on IODA1/2
On Wed, 2015-04-29 at 14:12 -0700, Daniel Phillips wrote:
> Btrfs appears to optimize tiny files by storing them in its big btree,
> the equivalent of our itree, and Tux3 doesn't do that yet, so we are a
> bit hobbled for a make load.
That's not a build load, it's a git load. btrfs beat all othe
An IO port or MMIO resource assigned to a PCI host bridge may be
consumed by the host bridge itself or available to its child
bus/devices. The ACPI specification defines a bit (Producer/Consumer)
to tell whether the resource is consumed by the host bridge itself,
but firmware hasn't used that bit c
On Wed, Apr 29, 2015 at 07:12:37PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 02:39 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:44PM +1000, Alexey Kardashevskiy wrote:
> >>This is a part of moving TCE table allocation into an iommu_ops
> >>callback to support multiple IOMMU gro
On Wed, Apr 29, 2015 at 07:26:28PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 02:45 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:45PM +1000, Alexey Kardashevskiy wrote:
> >>This is a part of moving DMA window programming to an iommu_ops
> >>callback. pnv_pci_ioda2_set_window() t
On Wed, Apr 29, 2015 at 07:19:51PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 01:02 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:37PM +1000, Alexey Kardashevskiy wrote:
> >>This adds tce_iommu_take_ownership() and tce_iommu_release_ownership
> >>which call in a loop iommu_take_o
On Wed, Apr 29, 2015 at 07:00:30PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 01:25 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:40PM +1000, Alexey Kardashevskiy wrote:
> >>At the moment the DMA setup code looks for the "ibm,opal-tce-kill" property
> >>which contains the TCE kil
On Wed, Apr 29, 2015 at 07:51:21PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 02:18 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:42PM +1000, Alexey Kardashevskiy wrote:
> >>At the moment writing new TCE value to the IOMMU table fails with EBUSY
> >>if there is a valid entry alre
On Thu, Apr 30, 2015 at 12:29:30PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 12:16 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:33PM +1000, Alexey Kardashevskiy wrote:
> >>This is to make extended ownership and multiple groups support patches
> >>simpler for review.
> >>
> >>Th
On Wed, Apr 29, 2015 at 07:44:20PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 03:30 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:47PM +1000, Alexey Kardashevskiy wrote:
> >>This extends iommu_table_group_ops by a set of callbacks to support
> >>dynamic DMA windows management.
>
On Wed, Apr 29, 2015 at 10:49 PM, Shreyas B Prabhu
wrote:
>
>
> On Wednesday 29 April 2015 10:38 PM, Steven Rostedt wrote:
>>> I am not sure if its worth the effort now. It doesn't look like any
>>> other trace point apart from the above use case will benefit from it.
>>> Only smbus_write and smbu
Sorry for the top-posting; Josh Boyer suggested I re-mail this mail
from last month which didn't get any replies. I'm still having this
weird kernel bug affecting me and I've bisected it down to like 2-4
lines of code. (I've thought more about my theory regarding
unsigned/signed below and it's pr
This patch adds support for the ntc thermistor NCPXXWF104 serises.
Cc: Jean Delvare
Cc: Guenter Roeck
Signed-off-by: Beomho Seo
---
Changes in v2
- Fix typo.
- Update Documents and Kconfig.
- Use murata instead of ntc.
- add entry to the murata list.
---
.../devicetree/bindings/hwmon/ntc_ther
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
arch/x86/kernel/machine_kexec_64.c between commit 4545c8988013 ("x86:
introduce kaslr_offset()") from the livepatching tree and commit
22543072a261 ("kdump, vmcoreinfo: report actual value of phys_base")
from the akpm-c
gz-x86_64-rhel-01060bfb79987cf1b7b2012c5bfbc3ae6d7a7e78-1-20150429-10021-1gr1afy.yaml"
dequeue_time: 2015-04-29 09:57:54.469064783 +08:00
initrd: "/osimage/debian/debian-x86_64-2015-02-07.cgz"
bootloader_append:
- root=/dev/ram0
- user=lkp
-
job=/
On Thu, 2015-04-30 at 07:06 +0900, OGAWA Hirofumi wrote:
> Yeah, I also want to know hardware. Also, what size of partition? And
> each test was done by fresh FS (i.e. after mkfs), or same FS was used
> through all tests?
1TB rust bucket, with new fs each test.
-Mike
--
To unsubscribe
On Wed, 2015-04-29 at 13:40 -0700, Daniel Phillips wrote:
> On Wednesday, April 29, 2015 9:42:43 AM PDT, Mike Galbraith wrote:
> >
> > [dbench bakeoff]
> >
> > With dbench v4.00, tux3 seems to be king of the max_latency hill, but
> > btrfs took throughput on my box. With v3.04, tux3 took 1st place
At Wed, 29 Apr 2015 10:07:45 -0700,
Guenter Roeck wrote:
>
> On Wed, Apr 29, 2015 at 03:22:40PM +0900, Yoshinori Sato wrote:
> [ ... ]
> >
> > OK.
> > I made h8300-*-linux target patch for release version.
> > Please apply and rebuild to "h8300-unknown-linux"
> > http://sourceforge.jp/projects/uc
On Mon, 2015-04-27 at 16:57 +0200, Michael Grzeschik wrote:
> Hi!
>
> On Fri, Apr 24, 2015 at 11:58:53PM -0400, David Miller wrote:
> > From: Marc Kleine-Budde
> > Date: Fri, 24 Apr 2015 23:14:41 +0200
> >
> > > On 04/24/2015 08:47 PM, Joe Perches wrote:
> > >> On Fri, 2015-04-24 at 19:20 +0200,
On 04/29/2015 07:37 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 335f49196fd6 (sched/idle: Use explicit broadcast oneshot
> control function) replaced clockevents_notify() invocations in
> cpuidle_idle_call() with direct calls to tick_broadcast_enter()
> and tick_broadcast_ex
On 04/29/2015 06:34 AM, Rafael J. Wysocki wrote:
> On Wednesday, April 29, 2015 02:50:22 AM Rafael J. Wysocki wrote:
>> On Tuesday, April 28, 2015 02:58:37 PM Sudeep Holla wrote:
>>>
>>> On 28/04/15 15:14, Rafael J. Wysocki wrote:
On Tuesday, April 28, 2015 03:37:44 PM Rafael J. Wysocki 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
>
> When you send next versions, the conventi
On Thu, 2015-04-30 at 10:20 +1000, Dave Chinner wrote:
> IOWS, XFS just hates your disk. Spend $50 and buy a cheap SSD and
> the problem goes away. :)
I'd love to. Too bad sorry sack of sh*t MB manufacturer only applied
_connectors_ to 4 of 6 available ports, and they're all in use :)
>
>
Le 04/28/15 10:52, Kevin Cernekee a écrit :
> 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
Acked-by: Florian Fainelli
> ---
>
>
> Ralf - c
On 04/29/2015 07:25 PM, Beomho Seo wrote:
This patch adds support for the ntc thermistor NCPXXWF104 serise.
s/serise/series
Cc: Jean Delvare
Cc: Guenter Roeck
Signed-off-by: Beomho Seo
---
drivers/hwmon/ntc_thermistor.c | 45 ++
include/linux/plat
We currently try to register the 24x7 PMU unconditionally. Not all
Power systems support 24x7 counters (eg: Power7). On these systems
we get a backtrace during boot when trying to register the 24x7 PMU.
Check if the hypervisor supports 24x7 counters before attempting to
register the 24x7 PMU.
Rep
On 04/29/2015 01:18 PM, David Gibson wrote:
On Sat, Apr 25, 2015 at 10:14:39PM +1000, Alexey Kardashevskiy wrote:
The pnv_pci_ioda_tce_invalidate() helper invalidates TCE cache. It is
supposed to be called on IODA1/2 and not called on p5ioc2. It receives
start and end host addresses of TCE table
Gobinda Maji writes:
> Hi Rusty,
Hi Gobinda,
> I have a small doubt about the permission restriction (User perms >=
> group perms >= other perms) in VERIFY_OCTAL_PERMISSIONS(). Please Note
> that permission field of User, Group or Other consists of three bits.
> LSB is EXECUTE permission, MSB is
Hi Guys,
On Wed, Apr 22, 2015 at 02:12:43PM +0800, Dong Aisheng wrote:
> On Wed, Apr 15, 2015 at 10:26:34PM +0800, Dong Aisheng wrote:
> > This patch series adds support in clock framework for clocks which
> > operations
> > requires its parent clock is on.
> >
> > Such clock type is initially m
On 30 April 2015 at 01:02, Fabian Frederick wrote:
> typedef is not really useful here. Replace it by structure
> to improve readability.typedef should only be used in some cases.
Space after full stop. (Maybe Rafael can fix that while applying)..
> (See Documentation/CodingStyle Chapter 5 for d
On 04/29/2015 06:55 PM, James Morris wrote:
> On Tue, 21 Apr 2015, Casey Schaufler wrote:
>
>>
>> James, do you want to take the module stacking changes in through
>> the security tree? Are there remaining objections or concerns? What
>> procedure would you like to follow?
>
> What's the overall
On 04/29/2015 12:49 PM, David Gibson wrote:
On Sat, Apr 25, 2015 at 10:14:36PM +1000, Alexey Kardashevskiy wrote:
Modern IBM POWERPC systems support multiple (currently two) TCE tables
per IOMMU group (a.k.a. PE). This adds a iommu_table_group container
for TCE tables. Right now just one table i
On 04/29/2015 12:16 PM, David Gibson wrote:
On Sat, Apr 25, 2015 at 10:14:33PM +1000, Alexey Kardashevskiy wrote:
This is to make extended ownership and multiple groups support patches
simpler for review.
This should cause no behavioural change.
Um.. this doesn't appear to be true. Previousl
This patch adds support for the ntc thermistor NCPXXWF104 serise.
Cc: Jean Delvare
Cc: Guenter Roeck
Signed-off-by: Beomho Seo
---
drivers/hwmon/ntc_thermistor.c | 45 ++
include/linux/platform_data/ntc_thermistor.h |1 +
2 files changed, 46 insertio
Hi Peter,
On Tue, Apr 28, 2015 at 5:20 AM, Peter Chen wrote:
> Current chipidea usb driver supports role switch function well, if you
> have a gpio or id pin for it.
On mx6 we are able to perform OTG role-switch funtion as they have the
OTG_ID pins.
We are talking about mx53 here, which does n
-Wunused-function] static int
> rt5645_irq_detection(struct rt5645_priv *rt5645)
> ^
>
> Caused by commit 6e747d5311fc ("ASoC: rt5645: Adds push button
> support for rt5650").
>
> I have used the sound-asoc tree from next-20150429 for today.
> --
> Cheers
On 27.04.2015 21:31, Chanwoo Choi wrote:
This patch change the name of various dock devices as 'DOCK' because the name of
various dock devices have not the standard naming rules. The name of dock
devices
include the differenct word but it is ambiguous and never important information
on user-spac
On 27.04.2015 21:31, Chanwoo Choi wrote:
This patch alters the MHL-TA cable name to TA cable name because MHL-TA is not
standard name. The MHL-TA is MHL cable with charger cable (TA or USB). So, this
patch use the TA cable instead of MHL-TA to inform the charger cable state.
- MHL-TA -> TA
Cc: J
On Thu, Apr 30, 2015 at 11:55:51AM +1000, James Morris wrote:
> On Tue, 21 Apr 2015, Casey Schaufler wrote:
>
> >
> > James, do you want to take the module stacking changes in through
> > the security tree? Are there remaining objections or concerns? What
> > procedure would you like to follow?
>
On 28.04.2015 17:40, Chanwoo Choi wrote:
On Tue, Apr 28, 2015 at 12:43 PM, Krzysztof Kozlowski
wrote:
On 27.04.2015 21:31, Chanwoo Choi wrote:
This patchset alter the unused name of external connector (jig/dock/MHL)
as
following. The name of jig cable and dock device include the non-standard
tic int rt5645_irq_detection(struct rt5645_priv *rt5645)
^
Caused by commit 6e747d5311fc ("ASoC: rt5645: Adds push button support
for rt5650").
I have used the sound-asoc tree from next-20150429 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpW1G00KRmUk.pgp
Description: OpenPGP digital signature
On 04/30/2015 11:00 AM, Krzysztof Kozlowski wrote:
> On 27.04.2015 21:31, Chanwoo Choi wrote:
>> This patch change the name of various jig cables as 'JIG' because the name of
>> various jig cables are strange and ambiguous on user-space aspect. They
>> include
>> the different information of eithe
On 27.04.2015 21:31, Chanwoo Choi wrote:
This patch change the name of various jig cables as 'JIG' because the name of
various jig cables are strange and ambiguous on user-space aspect. They include
the different information of either USB and UART state. It is never important
for user-space proce
On Tue, 21 Apr 2015, Casey Schaufler wrote:
>
> James, do you want to take the module stacking changes in through
> the security tree? Are there remaining objections or concerns? What
> procedure would you like to follow?
What's the overall consensus on this -- do people generally see it as
use
From: Chao Xie
Timer has external fast clock, and it is a mux clock.
Add the timer clock type for timer driver.
Signed-off-by: Chao Xie
---
drivers/clk/mmp/clk-of-mmp2.c | 6 ++
drivers/clk/mmp/clk-of-pxa168.c| 7 +++
drivers/clk/mmp/clk-of-pxa910.c
On Wed, 22 Apr 2015, Hagen Paul Pfeifer wrote:
> On 22 April 2015 at 11:28, Ingo Molnar wrote:
> > So I think the original patch makes sense (and I already applied it),
> > we want known-simple and performance critical methods (such as atomic
> > ops) always inlined.
>
> Right. As I wrote I will
From: Chao Xie
USB will drive clock from USB_PLL.
Signed-off-by: Chao Xie
---
drivers/clk/mmp/clk-of-pxa168.c| 1 +
drivers/clk/mmp/clk-of-pxa910.c| 1 +
include/dt-bindings/clock/marvell,pxa168.h | 1 +
include/dt-bindings/clock/marvell,pxa910.h | 1 +
4 files changed,
From: Chao Xie
The suggested value in the mmp2 manual is wrong.
There are only 13 bits for numerator, but some suggested
value has 14 bits.
Fix the factor tabled and remove the unused items.
Signed-off-by: Chao Xie
---
drivers/clk/mmp/clk-mmp2.c| 4 +---
drivers/clk/mmp/clk-of-mmp2.c | 4 +
From: Chao Xie
There are three patches
First two are fix patches.
The last one will add the timer clock for pxa168/mmp2/pxa910.
The timer driver will make use of the timer clock.
Chao Xie (3):
clk: mmp: add fixed clock UBS_PLL for pxa910/pxa168
clk: mmp: Fix the wrong factor table for uart
On 2015/4/29 18:12, Will Deacon wrote:
Hello,
On Tue, Apr 28, 2015 at 02:20:48PM +0100, Hou Pengyang wrote:
For ARM64, when tracing with tracepoint events, the IP and cpsr are set
to 0, preventing the perf code parsing the callchain and resolving the
symbols correctly.
./perf record -e sched
On Tue, Apr 28, 2015 at 04:13:18PM -0700, Daniel Phillips wrote:
> Greetings,
>
> This post is dedicated to Ted, who raised doubts a while back about
> whether Tux3 can ever have a fast fsync:
>
> https://lkml.org/lkml/2013/5/11/128
> "Re: Tux3 Report: Faster than tmpfs, what?"
[snip]
> I m
> "David" == David Herrmann writes:
David> Hi
David> On Wed, Apr 29, 2015 at 10:43 PM, David Lang wrote:
>> If the justification for why this needs to be in the kernel is that you
>> can't reliably prevent apps from exiting if there are pending messages, [...]
David> It's not.
>> the answe
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Thursday, April 30, 2015 5:31 AM
> To: Chao Yu
> Cc: Changman Lee; linux-f2fs-de...@lists.sourceforge.net;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/2] f2fs: support FALLOC_FL_COLLAPSE_RA
This patch add device tree bindings for the pdata needed to configure
the Accessory Detect Mode select when Headphone detection.
Signed-off-by: Inha Song
---
Documentation/devicetree/bindings/mfd/arizona.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindi
This set of patches adds support for select accessory detect mode to HPDETL or
HPDETR.
Changes in v4:
- Set the hpdet_channel default value to HPDETL in variable declaration.
- Fix the indentation in binding documentation.
Changes in v3:
- Set the hpdet_channel default value to HPDETL If t
This patch add support for select accessory detect mode to HPDETL or HPDETR.
Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
to measure the impedance of an external load connected to the headphone.
Depending on board design, headphone detect pins can change to HPDETR o
>>>
>>> I've had Enterprise systems where I could hit power on two boxes, and
>>> finish
>>> the OS install on one before the other has even finished POST and look
>>> for
>>> the boot media. I did this 5 years ago, before the "let's speed up boot"
>>> push started.
>>>
>>> Admittedly, this wasn't
On Wed, Apr 29, 2015 at 11:50 AM, Andy Lutomirski wrote:
> On Apr 29, 2015 2:09 AM, "Peter Zijlstra" wrote:
>>
>> On Tue, Apr 28, 2015 at 02:25:37PM -0700, Andy Lutomirski wrote:
>> > diff --git a/arch/x86/kernel/cpu/Makefile b/arch/x86/kernel/cpu/Makefile
>> > index 80091ae54c2b..fadc822efc90 10
Hi all,
I noticed commit a95d7600d9c4 ("hwmon: Update the location of my quilt
tree") in the hwmon-staging tree. It says that the quilt series is at
http://jdelvare.nerim.net/devel/linux/jdelvare-hwmon/ but inlinux-next
I am using http://jdelvare.nerim.net/devel/linux-3/jdelvare-hwmon/ . I
hope
Hello Kukjin,
On 04/15/2015 10:07 AM, Javier Martinez Canillas wrote:
>
> On 04/07/2015 05:09 PM, Doug Anderson wrote:
>> Javier,
>>
>> On Tue, Apr 7, 2015 at 6:03 AM, Javier Martinez Canillas
>> wrote:
>>> The Marvell mwifiex driver prevents the system to enter into a suspend
>>> state if the
On Wed, Apr 29, 2015 at 07:02:17PM +1000, Alexey Kardashevskiy wrote:
> On 04/29/2015 02:04 PM, David Gibson wrote:
> >On Sat, Apr 25, 2015 at 10:14:41PM +1000, Alexey Kardashevskiy wrote:
> >>This replaces direct accesses to TCE table with a helper which
> >>returns an TCE entry address. This does
Hello,
On 04/29/2015 09:45 PM, Sjoerd Simons wrote:
> On Wed, 2015-04-29 at 10:40 -0700, Kevin Hilman wrote:
>> Javier Martinez Canillas writes:
>
>> Tested-by: Kevin Hilman
>>
>> FWIW, this patch fixes the boot panics when using MMC rootfs on
>> exynos5800-peach-pi with current linux-next tha
gt; >
> > [0]:
> > http://arm-soc.lixom.net/bootlogs/next/next-20150415/pit-arm-exynos_defconfig.html
> >
>
> It has been many weeks since this patch has been posted and linux-next
> is still broken:
>
> http://arm-soc.lixom.net/bootlogs/next/next-20150429/pi-arm-exy
bdi_unregister() now contains very little functionality.
It contains a "WARN_ON" if bdi->dev is NULL. This warning is of no
real consequence as bdi->dev isn't needed by anything else in the function,
and it triggers if
blk_cleanup_queue() -> bdi_destroy()
is called before bdi_unregister, whic
1 - 100 of 841 matches
Mail list logo
