On Wed, Sep 17, 2014 at 03:54:12PM +0300, Nadav Amit wrote:
> Adding structs that reflect various cpuid fields in x86 architecture. Structs
> were added only for functions that are not pure bitmaps.
>
> Signed-off-by: Nadav Amit
> ---
> arch/x86/include/asm/cpuid_def.h | 163
> +
On Wed, Sep 17, 2014 at 9:05 AM, Marc Dietrich wrote:
> Hi,
>
> I get this roughly once in a week. Hard to reproduce.
>
> Sep 17 14:44:21 fb07-iapwap2 kernel: [ cut here ]
> Sep 17 14:44:21 fb07-iapwap2 kernel: kernel BUG at fs/dcache.c:1619!
> Sep 17 14:44:22 fb07-iapwap2
On Tue, Sep 09, 2014 at 01:49:41PM +0200, Pavel Machek wrote:
> Hi!
>
> > > The problem is still there in 3.17-rc2. 3.16 does not have the
> > > problem. Messages are still similar:
> > >
> > > mmc0: new high speed SDHC card at address b368
> > > mmcblk0: mmc0:b368 USD 7.45 GiB
> > > mmcblk0: p
On Tue, Sep 16, 2014 at 1:39 AM, Oleg Nesterov wrote:
> On 09/15, Roman Pen wrote:
>>
>> +static DECLARE_COMPLETION(rootfs_mounted);
>> +
>> +void wait_for_rootfs(void)
>> +{
>> + /* Avoid waiting for ourselves */
>> + if (is_global_init(current))
>> + pr_warn("it is not a good
On Tue, 16 Sep 2014 13:41:56 -0700
"Paul E. McKenney" wrote:
> On Mon, Sep 15, 2014 at 10:05:24AM -0500, Clark Williams wrote:
> > Paul,
> >
> > Here's the result of our conversation Friday, regarding the per-CPU and
> > boost priorities:
> >
> > Rename CONFIG_RCU_BOOST_PRIO to CONFIG_RCU_KTHRE
On Wed, Sep 17, 2014 at 03:11:42PM +0800, Lan Tianyu wrote:
> On 2014年08月29日 03:47, Paul E. McKenney wrote:
> > Currently, the expedited grace-period primitives do get_online_cpus().
> > This greatly simplifies their implementation, but means that calls to
> > them holding locks that are acquired b
Get voltage & duty table from device tree might be better, other platforms can
also use this
driver without any modify.
Signed-off-by: Chris Zhong
---
drivers/regulator/Kconfig |1 -
drivers/regulator/st-pwm.c | 80 +++-
2 files changed, 42 insert
Document the st-pwm regulator
Signed-off-by: Chris Zhong
---
.../devicetree/bindings/regulator/st-pwm.txt | 35
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/st-pwm.txt
diff --git a/Documentation/devicetree/bindin
get voltage & duty table from device tree might be better, other platforms can
also use this
driver without any modify.
Tested on a rk3288 sdk board as logic voltage regulator.
Chris Zhong (2):
regulator: st-pwm: get voltage and duty table from dts
dt-bindings: add devicetree bindings for st
Recently aded the use of skb_frag_dma_map to 3c59x, but didn't realize it
automatically included the frag_offset internally, as well as provided an option
to specify an extra offset in the parameter list. We need to specify an offset
of 0 in the parameter list to avoid skb corruption that results
On 09/17/2014 03:30 PM, Loic Poulain wrote:
> Direct Irq En bit can be initialized to a bad value.
> This bit has to be cleared for io access mode.
>
> Signed-off-by: Loic Poulain
> ---
> drivers/pinctrl/pinctrl-baytrail.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
Hi,
I get this roughly once in a week. Hard to reproduce.
Sep 17 14:44:21 fb07-iapwap2 kernel: [ cut here ]
Sep 17 14:44:21 fb07-iapwap2 kernel: kernel BUG at fs/dcache.c:1619!
Sep 17 14:44:22 fb07-iapwap2 kernel: invalid opcode: [#1] PREEMPT SMP
Sep 17 14:44:22 fb07
Noted that 3c59x has no checks on transmit for failed DMA mappings, and no
ability to unmap fragments when a single map fails in the middle of a transmit.
This patch provides error checking to ensure that dma mappings work properly,
and unrolls an skb mapping if a fragmented skb transmission has a
On Wed, Sep 17, 2014 at 03:43:54PM +0300, mr...@linux.ee wrote:
> > Shit, you're right, sorry about that. Its odd, I'm running it here, and
> > its not
> > causing problems, but thats obviously wrong. Meelis, please add the above
> > fix
> > to your test and confirm that it sovles the problem.
On Tue, Sep 16, 2014 at 01:17:44AM -0700, Dave Hansen wrote:
> >> This also fixes sysfs because CPUs with the same 'physical_package_id'
> >> in /sys/devices/system/cpu/cpu*/topology/ are not listed together
> >> in the same 'core_siblings_list'. This violates a statement from
> >> Documentation/A
Using cpuid structs in KVM to eliminate cryptic code with many bit operations.
The code does not introduce functional changes.
Signed-off-by: Nadav Amit
---
arch/x86/kvm/cpuid.c | 36 ++--
1 file changed, 22 insertions(+), 14 deletions(-)
diff --git a/arch/x86/kv
Adding structs that reflect various cpuid fields in x86 architecture. Structs
were added only for functions that are not pure bitmaps.
Signed-off-by: Nadav Amit
---
arch/x86/include/asm/cpuid_def.h | 163 +++
1 file changed, 163 insertions(+)
create mode 1006
The current code that decodes cpuid fields is somewhat cryptic, since it uses
many bit operations. Using cpuid structs instead for clarifying the code.
Introducign no functional change.
Signed-off-by: Nadav Amit
---
arch/x86/kernel/cpu/common.c | 56 +++-
The code that deals with x86 cpuid fields is hard to follow since it performs
many bit operations and does not refer to cpuid field explicitly. To
eliminate the need of openning a spec whenever dealing with cpuid fields, this
patch-set introduces structs that reflect the various cpuid functions.
On Wed, 17 Sep 2014, Jan van den Berg wrote:
> I will try and make _real_ contribution next time. (With this being my
> first ever submission to the kernel: at least now I understand the kernel
> workflow.)
There's nothing wrong with your patch by itself. And git does try to help
us take such pat
On Wed, Sep 17, 2014 at 02:37:10PM +0200, Ingo Molnar wrote:
> Opinions, objections?
Can I see those patches please? I can't find them on lkml or on the net
- I only see this sub-thread...
Thanks.
--
Regards/Gruss,
Boris.
--
--
To unsubscribe from this list: send the line "unsubscribe linux
> Shit, you're right, sorry about that. Its odd, I'm running it here, and its
> not
> causing problems, but thats obviously wrong. Meelis, please add the above fix
> to your test and confirm that it sovles the problem. If you could keep the
> previous patch in place too that would be great, as
* Nadav Amit wrote:
>
>
> On 9/16/14 4:22 PM, Ingo Molnar wrote:
> >
> > * Nadav Amit wrote:
> >
> >> The code that deals with x86 cpuid fields is hard to follow since it
> >> performs
> >> many bit operations and does not refer to cpuid field explicitly. To
> >> eliminate the need of ope
This series adds ti,system-power-controller to Documentation and the
driver seperately as per maintainer preference.
Based on v3.17-rc1
Changes since V1: update in documentation, picked up Tony's ack for patch #2.
V1: http://marc.info/?l=devicetree&m=140977126218800&w=2
Nishanth Menon (2):
Do
ti,system-power-controller is more or less the standard way of
indicating that the PMIC is the system wide power controller and hence
may be used to switch off the system. Almost ALL TI PMIC drivers and
many Maxim PMIC drivers follow the same style.
So support 'ti,system-power-controller' in addit
ti,system-power-controller is more or less the standard way of
indicating that the PMIC is the system wide power controller and hence
may be used to switch off the system. Almost ALL TI PMIC drivers and
many Maxim PMIC drivers follow the same style.
So support 'ti,system-power-controller' in addit
* Greg Kroah-Hartman wrote:
> On Tue, Sep 16, 2014 at 10:08:14AM +0200, Ingo Molnar wrote:
> >
> > * Peter Hurley wrote:
> >
> > > An interface may need to assert a lock invariant and not flood the
> > > system logs; add a lockdep helper macro equivalent to
> > > lockdep_assert_held() which o
* David E. Box wrote:
> Moves Kconfig option to "Processor type and features" menu from main
> configuration menu.
>
> Signed-off-by: David E. Box
> ---
> arch/x86/Kconfig | 29 ++---
> 1 file changed, 14 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/Kconfi
Direct Irq En bit can be initialized to a bad value.
This bit has to be cleared for io access mode.
Signed-off-by: Loic Poulain
---
drivers/pinctrl/pinctrl-baytrail.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-baytrail.c
b/drivers/pinctrl/pinct
Hi
On Tue, Sep 16, 2014 at 12:59 AM, Pranith Kumar wrote:
> Remove the dependence on x86 to run the memfd test. Verfied on 32-bit powerpc.
>
> Signed-off-by: Pranith Kumar
Now that most archs have __NR_memfd_create, this is:
Reviewed-by: David Herrmann
Thanks
David
> ---
> tools/testing/se
* David E. Box wrote:
> Signed-off-by: David E. Box
> ---
> arch/x86/Kconfig | 6 ++
> arch/x86/kernel/iosf_mbi.c | 8 ++--
> 2 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 2db4b1d..3afcac3 100644
> --- a/arch/x
On Wed, Sep 17, 2014 at 07:42:54AM +1000, Dave Chinner wrote:
> [Please don't top post!]
>
> On Tue, Sep 16, 2014 at 03:45:52PM -0400, Milosz Tanski wrote:
> > On Tue, Sep 16, 2014 at 3:27 PM, Jeff Moyer wrote:
> > > Christoph Hellwig writes:
> > >
> > > Hrm, you're not Christoph...
> >
> > I am
* Martin Kelly wrote:
> When compiling with CONFIG_DEBUG_FS=n, gcc emits an unused variable
> warning for pmc_atom.c because "ret" is used only within the
> CONFIG_DEBUG_FS block. This patch adds a dummy #ifdef for
> pmc_dbgfs_register when CONFIG_DEBUG_FS=n to simplify the code and
> remove the
On 09/16/2014 12:55 PM, Sebastian Andrzej Siewior wrote:
> On 09/15/2014 07:01 PM, Sebastian Andrzej Siewior wrote:
>> On 09/11/2014 04:35 PM, Peter Hurley wrote:
>>> I do need to find out if omap hardware sets UART_MSR_DCTS when auto CTS
>>> is on. Would you mind running the debug patch below with
On Wed, Sep 17, 2014 at 5:43 PM, Vivek Gautam wrote:
> Hi Kukjin,
>
>
> On Wed, Sep 17, 2014 at 5:39 PM, Kukjin Kim wrote:
>> Doug Anderson wrote:
>>>
>>> Vivek,
>>>
>> Hi,
>>
>>> On Tue, Sep 16, 2014 at 1:50 AM, Vivek Gautam
>>> wrote:
>>> > From: Naveen Krishna Chatradhi
>>> >
>>> > MMC capa
On Wed, Sep 17, 2014 at 01:57:16PM +0200, Geert Uytterhoeven wrote:
> If power area D4, which contains the Coresight-ETM hardware block, is
> powered down on R-Mobile A1 (r8a7740), the kernel crashes when
> suspending from s2ram with:
>
> Internal error: Oops - undefined instruction: 0 [#1] AR
On 16:05-20140916, Lee Jones wrote:
> On Mon, 08 Sep 2014, Tony Lindgren wrote:
>
> > * Nishanth Menon [140903 12:07]:
> > > ti,system-power-controller is more or less the standard way of
> > > indicating that the PMIC is the system wide power controller and hence
> > > may be used to switch off
Hi Kukjin,
On Wed, Sep 17, 2014 at 5:39 PM, Kukjin Kim wrote:
> Doug Anderson wrote:
>>
>> Vivek,
>>
> Hi,
>
>> On Tue, Sep 16, 2014 at 1:50 AM, Vivek Gautam
>> wrote:
>> > From: Naveen Krishna Chatradhi
>> >
>> > MMC capability for HS200 is parsed in mmc/core/host.c as
>> > dts string "mmc-h
On Wed, Sep 17, 2014 at 08:01:08AM -0400, Peter Hurley wrote:
> On 09/16/2014 04:50 AM, Frans Klaver wrote:
> > On Mon, Sep 15, 2014 at 01:31:56PM -0400, Peter Hurley wrote:
> >> On 09/15/2014 11:39 AM, Peter Hurley wrote:
> >>> On 09/15/2014 10:00 AM, Frans Klaver wrote:
> At 3.6Mbaud, with s
Doug Anderson wrote:
>
> Vivek,
>
Hi,
> On Tue, Sep 16, 2014 at 1:50 AM, Vivek Gautam
> wrote:
> > From: Naveen Krishna Chatradhi
> >
> > MMC capability for HS200 is parsed in mmc/core/host.c as
> > dts string "mmc-hs200-1_8v".
> >
> > This patch corrects the dts string for Exynos5420 based p
On Wednesday, September 17, 2014 8:18 PM, Vivek Gautam wrote:
>
> Now that we have completely moved from older USB-PHY drivers
> to newer GENERIC-PHY drivers for PHYs available with USB controllers
> on Exynos series of SoCs, we can remove the support for the same
> in our host drivers too.
>
> S
On Wednesday, September 17, 2014 8:18 PM, Vivek Gautam wrote:
>
> Now that we have completely moved from older USB-PHY drivers
> to newer GENERIC-PHY drivers for PHYs available with USB controllers
> on Exynos series of SoCs, we can remove the support for the same
> in our host drivers too.
>
> S
On 09/16/2014 04:50 AM, Frans Klaver wrote:
> On Mon, Sep 15, 2014 at 01:31:56PM -0400, Peter Hurley wrote:
>> On 09/15/2014 11:39 AM, Peter Hurley wrote:
>>> On 09/15/2014 10:00 AM, Frans Klaver wrote:
At 3.6Mbaud, with slightly over 2Mbit/s data coming in, we see 1600 uart
rx buffer ove
> >>> Does anyone have an idea?
> >>> The request itself is completely filled with cc
> >>
> >> That is very weird, the 'rq' is got from hctx->tags, and rq should be
> >> valid, and rq->q shouldn't have been changed even though it was
> >> double free or double allocation.
> >>
> >>> I am currentl
The vendor-id gathered from the dt match-data was cast to int but assigned
to an unsigned long, producing warnings on at least sparc, like
drivers/regulator/fan53555.c: In function 'fan53555_regulator_probe':
>> drivers/regulator/fan53555.c:373:16: warning: cast from pointer to integer
>> of d
On Wed, Sep 17, 2014 at 08:34:46PM +0900, Chanho Min wrote:
> sp804 may not be added to the tick device if the higher device is
> already registered. In this case, If pending interrupt is existed
> (usually It will be passed from the boot loader), inetrrupt is occured
> without event_handler then i
On Wed, Sep 17, 2014 at 12:34 PM, Henrique de Moraes Holschuh
wrote:
> On Tue, 16 Sep 2014, Darren Hart wrote:
>> - When reading and writing sysfs device attribute files, avoid dependency
>> on specific error codes wherever possible. This minimizes coupling to
>> the error handling implemement
If power area D4, which contains the Coresight-ETM hardware block, is
powered down on R-Mobile A1 (r8a7740), the kernel crashes when
suspending from s2ram with:
Internal error: Oops - undefined instruction: 0 [#1] ARM
This happens because dbg_cpu_pm_notify() calls reset_ctrl_regs(), which
can
commit 546b117fdf17 ("rtc: s3c: add support for RTC of Exynos3250 SoC")
added an "rtc_src" DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that uses the RTC as its
source clock. In the case of the Peach Pit and Pi machines, the Maxim
77802 32kHz AP c
commit 546b117fdf17 ("rtc: s3c: add support for RTC of Exynos3250 SoC")
added an "rtc_src" DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that uses the RTC as its
source clock. In the case of the Exynos5250 based Snow board, the Maxim
77686 32kHz AP
Hello Kukjin,
commit 546b117fdf17 ("rtc: s3c: add support for RTC of Exynos3250 SoC")
added an "rtc_src" DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that uses the RTC as
its source clock but this breaks the s3c RTC on Exynos Chromebooks
because
On 2014년 09월 09일 22:16, Andrzej Hajda wrote:
> This set of patches contains fixes of initialization and deinitialization
> code of exynos_drm core and components.
> It is based on exynos-drm-next branch.
>
> Patchset has been tested on trats and universal_c210 platforms.
Applied all patches excep
On Wed, 17 Sep 2014, Geert Uytterhoeven wrote:
> Hi Mikulas,
>
> On Tue, Sep 16, 2014 at 6:38 PM, Mikulas Patocka wrote:
> > The patch also removes the references to fb_memmove in the code that is
> > commented out because fb_memmove was removed from framebuffer subsystem.
>
> I'd leave it as
On Wed, Sep 17, 2014 at 01:27:14PM +0200, Radim Krčmář wrote:
> 2014-09-17 13:26+0300, Gleb Natapov:
> > For async_pf_execute() you do not need to even retry. Next guest's page
> > fault
> > will retry it for you.
>
> Wouldn't that be a waste of vmentries?
This is how it will work with or without
Since do_sync_work() is a deferred function it can block indefinitely by
design. At present do_sync_work() is added to the global system_wq.
As such a deadlock is theoretically possible between sys_unmount() and
sync_filesystems():
* The current work fn on the system_wq (do_sync_work()) is block
[Repost for lists, the last mail was eaten by a security troll.]
2014-09-16 14:01-0700, Andres Lagar-Cavilla:
> On Tue, Sep 16, 2014 at 1:51 PM, Radim Krčmář
> wrote:
> > 2014-09-15 13:11-0700, Andres Lagar-Cavilla:
> >> +int kvm_get_user_page_retry(struct task_struct *tsk, struct
> >> mm_struct
sp804 may not be added to the tick device if the higher device is
already registered. In this case, If pending interrupt is existed
(usually It will be passed from the boot loader), inetrrupt is occured
without event_handler then it cause kernel panic. So Interrupts
should be cleared before clockev
On Wed, Sep 17, 2014 at 02:15:40PM +0300, Dmitry Kasatkin wrote:
> On 17/09/14 12:22, Herbert Xu wrote:
> > On Mon, Sep 15, 2014 at 12:30:23AM -0700, beh...@converseincode.com wrote:
> >> From: Behan Webster
> >>
> >> Add a macro which replaces the use of a Variable Length Array In Struct
> >> (V
2014-09-17 13:26+0300, Gleb Natapov:
> For async_pf_execute() you do not need to even retry. Next guest's page fault
> will retry it for you.
Wouldn't that be a waste of vmentries?
The guest might be able to handle interrupts while we are waiting, so if
we used async-io-done notifier, this could
On Mon, 2014-09-15 at 15:07 -0700, Kamal Mostafa wrote:
> 3.13.11.7 -stable review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Andy Lutomirski
>
> commit 7209a75d2009dbf7745e2fd354abf25c3deb3ca3 upstream.
>
> This moves the espfix64 logic into
Hi,
On Wednesday, September 17, 2014, Dong Aisheng Wrote,
> >
> > +static struct syscon *of_syscon_register(struct device_node *np) {
> > + struct syscon *syscon;
> > + struct regmap *regmap;
> > + void __iomem *base;
> > +
> > + if (!of_device_is_compatible(np, "syscon"))
> > +
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
Signed-off-by: Vivek Gautam
---
drivers/usb/host/ehci-exynos.c | 81 ++
Hi Kumar,
On Tuesday, September 16, 2014 2:59pm, "Kumar Gala" said:
>
> On Sep 16, 2014, at 4:45 AM, Kiran Padwal
> wrote:
>
>> Add support for i2c controller on the DB8074 board.
>> It also adds necessary DT support for i2c eeprom which is present on
>> DB8074 board.
>>
>> Signed-off-by: Ki
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
Signed-off-by: Vivek Gautam
---
drivers/usb/host/ohci-exynos.c | 89 ++
Cleaning up the phy getting sequence in ehci-exynos and ohci-exynos
drivers.
Hi Alan, Jingoo,
I have not imported the Acked-by and Reviewed-by from you guys, from V2 version
of this patch series, since this version is now rebased on the already available
commit in usb-next - "usb: ehci/ohci-exyno
On Mon, 2014-09-15 at 12:26 -0700, Greg Kroah-Hartman wrote:
> 3.14-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Tejun Heo
>
> commit 2a1b4cf2331d92bc009bf94fa02a24604cdaf24c upstream.
This is a duplicate of commit 0b462c89e31f which
On 17/09/14 12:22, Herbert Xu wrote:
> On Mon, Sep 15, 2014 at 12:30:23AM -0700, beh...@converseincode.com wrote:
>> From: Behan Webster
>>
>> Add a macro which replaces the use of a Variable Length Array In Struct
>> (VLAIS)
>> with a C99 compliant equivalent. This macro instead allocates the ap
On Mon, 2014-09-15 at 15:08 -0700, Kamal Mostafa wrote:
> 3.13.11.7 -stable review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Theodore Ts'o
>
> commit 86f0afd463215fc3e58020493482faa4ac3a4d69 upstream.
>
> If there is a failure while allocatin
Hi,
Robin Gong wrote:
> This driver register pm_power_off with snvs power off function. If
> your boards NOT use PMIC_ON_REQ to turn on/off external pmic, or use
> other pin to do, please disable the driver in dts, otherwise, your
> pm_power_off maybe overwrote by this driver.
>
> Signed-off-by:
Hi Maciej,
On Fri, Sep 12, 2014 at 6:19 PM, Maciej Matraszek
wrote:
>> > (though 'runtime status' alignment seems odd).
>>
>> What's wrong with it?
>
> Nothing big, just for such short device names it doesn't look aesthetic to me
> :).
In legacy mode, using platform code (without DT), the devic
On Mon, 2014-09-15 at 15:08 -0700, Kamal Mostafa wrote:
> 3.13.11.7 -stable review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Paul Moore
>
> commit 2873ead7e46694910ac49c3a8ee0f54956f96e0c upstream.
>
> This reverts commit 4da6daf4d3df5a977e46
On Fri, 12 Sep 2014 10:36:07 -0700
"David E. Box" wrote:
> +#if IS_ENABLED(CONFIG_I2C_SHARED_CONTROLLER)
> +extern int i2c_acquire_ownership(struct device *dev);
> +extern int i2c_release_ownership(struct device *dev);
> +#endif
You can just have the prototypes anyway - no need for more ifdefs t
Am 17.09.2014 10:51, schrieb Robin Gong:
On Tue, Sep 16, 2014 at 11:41:55AM +0200, Alexander Holler wrote:
Am 16.09.2014 05:52, schrieb Robin Gong:
On Mon, Sep 15, 2014 at 01:50:02PM +0200, Alexander Holler wrote:
Am 10.09.2014 07:30, schrieb Robin Gong:
There is one weird data in rxfifo afte
On Tue, Sep 16, 2014 at 07:24:28AM +0200, Johannes Thumshirn wrote:
> 16z135 IP Core has changed so the driver needs to be updated to respect
> these changes. The following changes have been made:
>
> * Don't invert the 16z135 modem status register when reading.
> * Add module parameter to configur
> What if someone doesn't know about that intention one day and inserts
> some field in the structure at the "wrong place" ?
Then we have code review. Also they are much more likely to simply change
the code elsewhere and break it. Nobody afaik ever got this wrong, while
the litany of other broken
On Tue, 16 Sep 2014, Darren Hart wrote:
> On Wed, Sep 17, 2014 at 12:01:08AM +0200, Jan van den Berg wrote:
> > Fixed 22 similar coding style issues: "ERROR: spaces required around that
> > '?'"
> >
> > Signed-off-by: Jan van den Berg
>
> Queued, thanks.
I usually refuse "fix whitespace" patch
Firstly provide some useful information about the hardware. It's no good
wavng your arms at a document that requires agreeing to a giant ARM T&C
to get access to. Most of don't work for ARM and we'd have to get our own
corporate legal to approve the legal garbage involved.
Secondly explain why yo
On Tue, Sep 16, 2014 at 05:05:51PM -0700, Richard Larocque wrote:
> + case PR_SET_VDSO:
> + if (arg2 == PR_VDSO_ENABLE)
> + me->signal->disable_vdso = 0;
> + else if (arg2 == PR_VDSO_DISABLE)
> + me->signal->disable_vdso = 1;
> +
On Tue, 16 Sep 2014, Darren Hart wrote:
> - When reading and writing sysfs device attribute files, avoid dependency
> on specific error codes wherever possible. This minimizes coupling to
> the error handling implemementation within the kernel.
>
> In general, failures to read or write sysfs
This patch adds i2c pinctrl DT node for IFC6410 board.
It also adds necessary DT support for i2c eeprom which is present on
IFC6410.
Tested on IFC6410 board.
Signed-off-by: Kiran Padwal
---
Changes since v3:
- Removed pinctrl DT node.
Changes since v2:
- Renamed pinmux i2c subnode "i2c1_pinmu
Hi,
Yesterday's testing was a bit messy. So here goes again.
On Mon, Sep 15, 2014 at 06:42:04PM +0200, Sebastian Andrzej Siewior wrote:
> On 09/12/2014 12:28 PM, Frans Klaver wrote:
> > port config is 115200 8N1. I don't recall doing anything special. I
> > boot, login, less file and get a lock.
On Tue, Sep 16, 2014 at 04:29:23PM -0400, David Miller wrote:
> From: Neil Horman
> Date: Tue, 16 Sep 2014 06:17:04 -0400
>
> > I'm guessing the above change has uncovered another bug,
>
> Neil, read your patch carefully, I think it added the bug.
>
> The ->page_offset of the frag gets applied
On Tuesday, September 16, 2014 3:00pm, "Kumar Gala" said:
>
> On Sep 16, 2014, at 5:36 AM, kiran.pad...@smartplayin.com wrote:
>
>>
>>
>> On Monday, September 15, 2014 10:39pm, "Andy Gross"
>> said:
>>
>>> On Tue, Aug 26, 2014 at 05:00:45PM +0530, Kiran Padwal wrote:
This patch adds pin
On Mon, Sep 15, 2014 at 01:11:25PM -0700, Andres Lagar-Cavilla wrote:
> When KVM handles a tdp fault it uses FOLL_NOWAIT. If the guest memory has been
> swapped out or is behind a filemap, this will trigger async readahead and
> return immediately. The rationale is that KVM will kick back the guest
On Wed, Sep 17, 2014 at 05:57:58PM +0800, Robin Gong wrote:
> All chips of i.mx6 can be powered off by programming SNVS.
> For example :
> On i.mx6q-sabresd board, PMIC_ON_REQ connect with external
> pmic ON/OFF pin, that will cause the whole PMIC powered off
> except VSNVS. And system can restart
On 09/16/2014 12:51 AM, Andrew Bresticker wrote:
The current MIPS GIC driver and the platform code using it are rather
ugly and could use a good cleanup before adding device-tree support [0].
This major issues addressed in this series are converting the GIC (and
platforms using it) to use IRQ dom
We no longer clear kn->priv in cgroup_rmdir(), so we don't need
to get an extra refcnt.
Signed-off-by: Zefan Li
---
kernel/cgroup.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 0ce9d9e..26b8cb9 100644
--- a/kernel/cgroup.c
+++ b/kernel/cgroup.c
@@
Currently we use a global work to schedule release agent on removable
cgroups. We can change to reuse css->destroy_work to do this, which
saves a few lines of code.
Signed-off-by: Zefan Li
---
include/linux/cgroup.h | 7
kernel/cgroup.c| 108 ++-
We never grab cgroup mutex in fork and exit paths no matter whether
notify_on_release is set or not.
Signed-off-by: Zefan Li
---
kernel/cgroup.c | 8
1 file changed, 8 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 26b8cb9..1abb554 100644
--- a/kernel/cgroup.c
+++ b/
Signed-off-by: Zefan Li
---
include/linux/cgroup.h | 1 -
kernel/cgroup.c| 2 --
2 files changed, 3 deletions(-)
diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
index b5223c5..f7898e0 100644
--- a/include/linux/cgroup.h
+++ b/include/linux/cgroup.h
@@ -27,7 +27,6 @@
stru
On Wed, Sep 17, 2014 at 12:44 PM, Johan Hovold wrote:
>> + /*
>> + * Buffer to hold the packet for read or write transfers. One
>> + * is enough since we can't have multiple transfers in
>> + * parallel on the i2c adapter.
>> + */
>> + union {
>> + struct
On Wed, Sep 17, 2014 at 3:59 PM, Christian Borntraeger
wrote:
> On 09/12/2014 10:09 PM, Christian Borntraeger wrote:
>> On 09/12/2014 01:54 PM, Ming Lei wrote:
>>> On Thu, Sep 11, 2014 at 6:26 PM, Christian Borntraeger
>>> wrote:
Folks,
we have seen the following bug with 3.16 as a
On Mon, Sep 15, 2014 at 08:15:54PM +0200, Fabian Frederick wrote:
>
>
> > On 15 September 2014 at 01:13 One Thousand Gnomes
> >
> > wrote:
> >
> >
> > On Sun, 14 Sep 2014 18:40:13 +0200
> > Fabian Frederick wrote:
> >
> > > Small patchset using container_of instead of casting on first structur
On Wed, Sep 17, 2014 at 12:01:50PM +0530, Pankaj Dubey wrote:
> Currently a syscon entity can be only registered directly through a
> platform device that binds to a dedicated syscon driver. However in
> certain use cases it is desirable to make a device used with another
> driver a syscon interfac
Add simple power off driver for i.mx6, including:
- add basic imx-snvs-poweroff driver in drivers/power/reset
- add device node in all dts files of i.mx6.
- enable in config file
Change from v2:
- remove useless included head files
- split device binding doc from dts patch
- add description for th
This driver register pm_power_off with snvs power off function. If
your boards NOT use PMIC_ON_REQ to turn on/off external pmic, or use
other pin to do, please disable the driver in dts, otherwise, your
pm_power_off maybe overwrote by this driver.
Signed-off-by: Robin Gong
---
.../bindings/power
Add power off driver in config file.
Signed-off-by: Robin Gong
---
arch/arm/configs/imx_v6_v7_defconfig |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/imx_v6_v7_defconfig
b/arch/arm/configs/imx_v6_v7_defconfig
index 16cfec4..a310e61 100644
--- a/arch/arm/configs/imx_
All chips of i.mx6 can be powered off by programming SNVS.
For example :
On i.mx6q-sabresd board, PMIC_ON_REQ connect with external
pmic ON/OFF pin, that will cause the whole PMIC powered off
except VSNVS. And system can restart once PMIC_ON_REQ goes
high by push POWRER key.
Signed-off-by: Robin G
On 09/16/2014 12:51 AM, Andrew Bresticker wrote:
The MIPS GIC supports 7 local interrupts, 2 of which are the GIC
local watchdog and count/compare timer. The remainder are CPU
interrupts which may optionally be re-routed through the GIC.
GIC hardware IRQs 0-6 are now used for local interrupts wh
Hi,
The first patch trys to fix one race between timeout and queue_rq.
And the second one removes two unnecessary blk_clear_rq_complete().
Thanks,
--
Ming Lei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More ma
601 - 700 of 796 matches
Mail list logo
