CC linux-arch
https://lkml.org/lkml/2013/12/11/141
On Tue, Jan 14, 2014 at 5:19 PM, H. Peter Anvin wrote:
> On 01/14/2014 05:17 AM, Geert Uytterhoeven wrote:
>>>
>>> This seems terribly broken, the *futex_value*() ops should not need
>>> that; they are supposed to access userspace without any
On Tue, Jan 14, 2014 at 05:22:03PM +0100, Ingo Molnar wrote:
> Absolutely. I think moving arch/x86/kernel/cpu/ to arch/x86/cpu/
> would be a first good step. It's all kernel code, there's other
> subdirectories there that are kernel code ('pci/', 'platform/', etc.),
> so there's little point in
* Rik van Riel wrote:
> On 01/13/2014 12:14 PM, atom...@redhat.com wrote:
> > From: Aaron Tomlin
> >
> > Enable hung_task_warnings to display every hung
> > task warning when set to -1.
> >
> > Signed-off-by: Aaron Tomlin
>
> Aaron and I talked on IRC, and after some talking these patches
Commit-ID: 03ad9747c5f2169556467101e96bc390c5aa4b83
Gitweb: http://git.kernel.org/tip/03ad9747c5f2169556467101e96bc390c5aa4b83
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 3 Jan 2014 15:56:06 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 13 Jan 2014 10:06:21 -0300
Commit-ID: 3e2be2da8f76ef5b2e8e59c3dc8acd24640b4af4
Gitweb: http://git.kernel.org/tip/3e2be2da8f76ef5b2e8e59c3dc8acd24640b4af4
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 3 Jan 2014 15:03:26 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 13 Jan 2014 10:06:21 -0300
Commit-ID: 6af206fd911c825b83dd4efb2534a3a34ce77072
Gitweb: http://git.kernel.org/tip/6af206fd911c825b83dd4efb2534a3a34ce77072
Author: Arnaldo Carvalho de Melo
AuthorDate: Sat, 28 Dec 2013 15:45:08 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 13 Jan 2014 10:06:21 -0300
Commit-ID: 735f7e0bbebe755d707182188c4a5e88c581fc1c
Gitweb: http://git.kernel.org/tip/735f7e0bbebe755d707182188c4a5e88c581fc1c
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 3 Jan 2014 14:56:49 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 13 Jan 2014 10:06:21 -0300
On 01/14/2014 08:27 AM, Borislav Petkov wrote:
> From: Borislav Petkov
>
> This adds the workaround for erratum 793 as a precaution in case not
> every BIOS implements it. This addresses CVE-2013-6885.
>
> Signed-off-by: Borislav Petkov
> +
> +#define MSR_AMD_LS_CFG 0xc0011020
> +
On 01/09/2014 05:49 PM, Vladimir Barinov wrote:
Add Maxim ModelGauge ICs gauge driver for MAX17040/41/43/44/48/49/58/59 chips
Signed-off-by: Vladimir Barinov
---
drivers/power/Kconfig|8
drivers/power/Makefile |1
On 01/09/2014 05:49 PM, Vladimir Barinov wrote:
Hello.
This adds the folowing:
- Maxim ModelGauge ICs gauge driver for MAX17040/41/43/44/48/49/58/59 chips
- Document DT bindings
- Remove superseded Maxim MAX17040 gauge driver
Vladimir Barinov (3):
[1/3] power_supply: modelgauge_battery:
* Mike Travis wrote:
>
> v2: Update patch 2/3 to include which problems fixed. Other minor
> changes detailed in the patches.
>
> * 1/3: Change the fix for 'KDB not defined' build problem by changing
> the kgdb_nmicallin() interface to include the KDB specific reason code.
> This
At Tue, 14 Jan 2014 16:12:44 +,
Matthew Garrett wrote:
>
> On Mon, Jan 13, 2014 at 12:14:18PM +0100, Takashi Iwai wrote:
> > The BIOS on recent HP laptops behaves differently with Win8 OSI,
> > e.g. no backlight control and no rfkill are available. List them in
> > the blacklist as a
On Tuesday, January 14, 2014 04:12:44 PM Matthew Garrett wrote:
> On Mon, Jan 13, 2014 at 12:14:18PM +0100, Takashi Iwai wrote:
> > The BIOS on recent HP laptops behaves differently with Win8 OSI,
> > e.g. no backlight control and no rfkill are available. List them in
> > the blacklist as a
From: Borislav Petkov
This adds the workaround for erratum 793 as a precaution in case not
every BIOS implements it. This addresses CVE-2013-6885.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/amd.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
On Mon, 2014-01-13 at 19:04 -0700, Toshi Kani wrote:
> On Sun, 2014-01-12 at 10:06 +0100, Borislav Petkov wrote:
> > On Sun, Jan 12, 2014 at 01:30:23AM +0100, Rafael J. Wysocki wrote:
> > > I don't see any adverse effects of the patch below on a couple of my test
> > > boxes, but (a) they are
v2: Update patch 2/3 to include which problems fixed. Other minor
changes detailed in the patches.
* 1/3: Change the fix for 'KDB not defined' build problem by changing
the kgdb_nmicallin() interface to include the KDB specific reason code.
This removes the dependency on KDB in the debug
* Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 14, 2014 at 02:41:01PM +0100, Ingo Molnar escreveu:
> > * Arnaldo Carvalho de Melo wrote:
>
> > > Andi Kleen (2):
> > > perf stat: Fix --delay option in man page
> > > perf record: Add --initial-delay option
>
> > Hm, so we now have
Fix UV call into kgdb to depend only on whether KGDB is defined and not
both KGDB and KDB. This allows the power nmi command to use the gdb
remote connection if enabled. Note new action of 'kgdb' needs to be set
as well to indicate user wants to wait for gdb to be connected. If it's
set to
Make uv_register_nmi_notifier() and uv_handle_nmi_ping() static to
address sparse warnings.
Fix problem where uv_nmi_kexec_failed is unused when CONFIG_KEXEC
is not defined.
Signed-off-by: Mike Travis
Reviewed-by: Hedi Berriche
---
v2: update the description to include problems fixed.
---
Some code added to the debug_core module had KDB dependencies that it
shouldn't have. Move the KDB dependent REASON back to the caller to
remove the dependency in the debug core code.
Update the call from the UV NMI handler to conform to the new interface.
Signed-off-by: Mike Travis
Hi Alan,
Quoting One Thousand Gnomes :
Maybe we should unset the low_latency flag as soon as DMA fails? There
are two flags, one is state->uart_port->flags and the other is
port->low_latency. I guess we need to unset both.
Well low latency and DMA are pretty much exclusive in the real
On Tue, Jan 14, 2014 at 12:16:39PM +, One Thousand Gnomes wrote:
> On Tue, 14 Jan 2014 16:23:23 +0800
> Dave Young wrote:
>
> > In kdump kernel watchdog could interrupt vmcore capturing because we
> > have no way to disable/stop it while crashing happens.
>
> Lots of watchdogs cannot be
* H. Peter Anvin wrote:
> On 01/14/2014 05:58 AM, tip-bot for Borislav Petkov wrote:
> > Commit-ID: bad5fa631fca5466401cd4a48e30cc1f1cb6101e
> > Gitweb:
> > http://git.kernel.org/tip/bad5fa631fca5466401cd4a48e30cc1f1cb6101e
> > Author: Borislav Petkov
> > AuthorDate: Sun, 1 Dec 2013
On 14.01.2014 08:41, Ying Xue wrote:
> As cgw_create_job() is always under rtnl_lock protection,
> __dev_get_by_index() instead of dev_get_by_index() should be used to
> find interface handler in it having us avoid to change interface
> reference counter.
>
> Cc: Oliver Hartkopp
>
On 01/14/2014 05:17 AM, Geert Uytterhoeven wrote:
>>
>> This seems terribly broken, the *futex_value*() ops should not need
>> that; they are supposed to access userspace without any of that.
>
> Why don't they need set_fs(USER_DS)?
>
> Gr{oetje,eeting}s,
>
> Geert
On Tue, 14 Jan 2014 14:20:14 +
Mark Brown wrote:
> On Tue, Jan 14, 2014 at 12:36:06PM +0100, Jean-Francois Moine wrote:
> > This patch
> > - removes the fields of the platform data which are of no use to the
> > non-DT platform callers,
> > - uses a new private structure to handle all the
On Thu, Jan 02, 2014 at 03:37:57PM +0800, Lan Tianyu wrote:
> The aml method _BIX of NEC LZ750/LS returns a broken package which
> skip the first member "Revision" according ACPI 5.0 spec Table 10-234.
Why don't we just ignore an invalid _BIX and fall back to _BIF? That
seems more reasonable
On Mon, Jan 13, 2014 at 02:29:04PM -0700, Stephen Warren wrote:
> From: Stephen Warren
>
> The body of i2c_parent_is_i2c_adapter() is currently guarded by
> CONFIG_I2C_MUX instead.
This paragraph sounds strange to me. I'll update it a little. After that
I'll go looking for a brown paper bag...
On Mon, Jan 13, 2014 at 12:14:18PM +0100, Takashi Iwai wrote:
> The BIOS on recent HP laptops behaves differently with Win8 OSI,
> e.g. no backlight control and no rfkill are available. List them in
> the blacklist as a workaround.
What's the plan for fixing this properly?
--
Matthew Garrett |
cppcheck detected following warning in ixgbe_fcoe.c
(warning) %d in format string (no. 1) requires 'int' but the
argument type is 'unsigned int'.
Signed-off-by: Masanari Iida
---
drivers/net/ethernet/intel/ixgbe/ixgbe_fcoe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 01/14/2014 05:58 AM, tip-bot for Borislav Petkov wrote:
> Commit-ID: bad5fa631fca5466401cd4a48e30cc1f1cb6101e
> Gitweb: http://git.kernel.org/tip/bad5fa631fca5466401cd4a48e30cc1f1cb6101e
> Author: Borislav Petkov
> AuthorDate: Sun, 1 Dec 2013 18:09:58 +0100
> Committer: Borislav
On Tue, Jan 07, 2014 at 02:50:35PM -0800, Feng Kan wrote:
> Enable X-Gene platform driver for the X-Gene platform. Remove the
> use of the mask attribute from the reboot dts node. Add support
> for using the ACPI and DTS resource for the reboot driver.
Why can't you just use the standard ACPI
On Tue, 2014-01-14 at 17:05 +0100, Gmane Remailer wrote:
> This message was created automatically by mail delivery software (TMDA).
>
> Your message attached below is being held because the address
> has not been verified.
>
> To release your message for delivery, please send an empty
Signed-off-by: Sébastien Szymanski
---
arch/arm/boot/dts/imx28-apf28dev.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/imx28-apf28dev.dts
b/arch/arm/boot/dts/imx28-apf28dev.dts
index 334dea5..221cac4 100644
--- a/arch/arm/boot/dts/imx28-apf28dev.dts
+++
On 01/14/2014 05:31 AM, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> commit 82fa9637a2ba285bcc7c5050c73010b2c1b3d803
> Author: Kees Cook
> AuthorDate: Thu Oct 10 17:18:16 2013 -0700
> Commit: H. Peter Anvin
> CommitDate: Sun Oct 13 03:12:19
On Mon, Jan 06, 2014 at 11:25:53PM +0100, Rafael J. Wysocki wrote:
> Queued up as a fix for 3.13 (I fixed up the indentation).
Ah, sorry, I missed this chunk of the thread. If the system provides
valid _BIF data then we should possibly just fall back to that rather
than adding another quirk
On Mon, Jan 13, 2014 at 04:50:37PM +0100, Frederic Weisbecker wrote:
> On Sat, Jan 04, 2014 at 07:22:32PM +0100, Alexander Gordeev wrote:
> > Hello,
> >
> > This is version 2 of RFC "perf: IRQ-bound performance events". That is an
> > introduction of IRQ-bound performance events - ones that only
On 01/09/2014 05:49 PM, Vladimir Barinov wrote:
This adds the folowing:
- Maxim ModelGauge ICs gauge driver for MAX17040/41/43/44/48/49/58/59 chips
- Document DT bindings
- Remove superseded Maxim MAX17040 gauge driver
Vladimir Barinov (3):
[1/3] power_supply: modelgauge_battery: Maxim
On Tuesday 14 January 2014, Jonas Jensen wrote:
> Thanks for the replies, you led me to a new solution,
>
>
> I now think build_skb() is not the right choice, my motivation for
> using it in the first place, that I thought it meant getting away with
> not copying memory.
>
> build_skb() is
On Tue, 2014-01-14 at 11:06 +0100, Unai Uribarri wrote:
> This scancode is used in new 2013 models like Satellite P75-A7200.
Just to check - this is generated by a key that otherwise does nothing,
right? Ie, hitting the key generates the scancode but doesn't
automatically change the wireless
On 01/14/2014 05:14 AM, Taras Kondratiuk wrote:
> On 13 January 2014 17:23, Nishanth Menon wrote:
>> On 01/13/2014 09:03 AM, Taras Kondratiuk wrote:
>>> From: Victor Kamensky
>>>
>>> Assembler functions defined in sleep44xx.S need to byteswap values
>>> after read / before write from h/w
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/ptp/ptp_pch.c: In function ‘pch_remove’:
drivers/ptp/ptp_pch.c:571:3: error: implicit declaration of function ‘iounmap’
[-Werror=implicit-function-declaration]
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/built-in.o: In function `exynos_mipi_video_phy_probe':
drivers/phy/phy-exynos-mipi-video.c:130: undefined reference to
`devm_ioremap_resource'
Signed-off-by: Richard
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/built-in.o: In function `orion_mdio_probe':
drivers/net/ethernet/marvell/mvmdio.c:228: undefined reference to `devm_ioremap'
Signed-off-by: Richard Weinberger
---
On Sat, Jan 11, 2014 at 12:23:15AM +0200, Kirill A. Shutemov wrote:
> On Fri, Jan 10, 2014 at 04:01:55PM -0600, Alex Thorlton wrote:
> > On Fri, Jan 10, 2014 at 10:23:10PM +0200, Kirill A. Shutemov wrote:
> > > Do you know what cause the difference? I prefer to fix THP instead of
> > > adding new
On 01/14/2014 07:41 AM, Peter Zijlstra wrote:
>>>
>>> I am *guessing* that m68k is has get_fs() == KERNEL_DS at the point that
>>> futex_init() is called. This would seem a bit of a peculiarity to m68k,
>>> and as such it would seem like it would be better for it to belong in
>>> the
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/built-in.o: In function `lpc32xx_adc_probe':
drivers/staging/iio/adc/lpc32xx_adc.c:149: undefined reference to `devm_ioremap'
Signed-off-by: Richard Weinberger
---
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/staging/iio/adc/spear_adc.c: In function ‘spear_adc_probe’:
drivers/staging/iio/adc/spear_adc.c:393:2: error: implicit declaration of
function ‘iounmap’
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/built-in.o: In function `goldfish_battery_probe':
drivers/power/goldfish_battery.c:181: undefined reference to `devm_ioremap'
Signed-off-by: Richard Weinberger
---
On Tue, Jan 14, 2014 at 04:20:36PM +0100, Geert Uytterhoeven wrote:
> On Tue, Jan 14, 2014 at 4:15 PM, H. Peter Anvin wrote:
> > On 01/14/2014 04:51 AM, Peter Zijlstra wrote:
> >> On Tue, Jan 14, 2014 at 03:53:31PM +1100, Stephen Rothwell wrote:
> >>> Hi Andrew,
> >>>
> >>> Today's linux-next
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/staging/dgap/dgap_driver.c: In function ‘dgap_cleanup_board’:
drivers/staging/dgap/dgap_driver.c:457:3: error: implicit declaration of
function ‘iounmap’
re-sent as requested by David M.
(I understand the concerns about portability that were raised. At the moment, I
don't have a possiblity to do
further rework and testing)
Add an explicit cast to fix the following warning
(seen on Debian Wheezy, gcc 4.7.2)
CC [M]
Tomasz Figa writes:
> This patch introduces generic code to perform power domain look-up using
> device tree and automatically bind devices to their power domains.
> Generic device tree binding is introduced to specify power domains of
> devices in their device tree nodes.
>
> Backwards
On Fri, Jan 10, 2014 at 04:39:09PM -0600, Alex Thorlton wrote:
> On Fri, Jan 10, 2014 at 11:10:10PM +0100, Peter Zijlstra wrote:
> > We already have the information to determine if a page is shared across
> > nodes, Mel even had some prototype code to do splits under those
> > conditions.
>
> I'm
If a new callchain branch doesn't match a single entry of the node that
it is given against comparison in append_chain(), then the cursor is
expected to be at the same position as it was before the comparison loop.
As such, there is no need to restore the cursor position on exit in case
of non
The comm overriding API ignores memory allocation failures by silently
keeping the previous and out of date comm.
As a result, the user may get buggy events without ever being notified
about the problem and its source.
Lets start to fix this by propagating the error from the API. Not all
callers
On Tue, 2014-01-14 at 10:26 -0500, Vivek Goyal wrote:
> On Tue, Jan 14, 2014 at 06:05:15AM -0500, Prarit Bhargava wrote:
>
> [..]
> > >>> As mentioned, self-NAK. I have seen a system that I needed to specify
> > >>> memmap=exactmap & had hotplug memory. I will only keep the
> > >>>
When a new callchain child branch matches an existing one in the rbtree,
the comparison of its first entry is performed twice:
1) From append_chain_children() on branch lookup
2) If 1) reports a match, append_chain() then compares all entries of
the new branch against the matching node in the
Hi,
Just a bunch of non critical cleanups for comm and callchains. Based on latest
acme:perf/core
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
perf/core-cleanups-for-acme
Thanks,
Frederic
---
Frederic Weisbecker (3):
perf tools: Do proper
On Tue, Jan 14, 2014 at 07:14:48AM -0800, H. Peter Anvin wrote:
> Seriously, though, if this MSR can be set at runtime without problems
> (which covers 98% of all workarounds, but not 100%) then it seems
> like a no-brainer to just do it as long as the offending CPUs can be
> identified by the
On 01/14/2014 06:03 AM, Peter Zijlstra wrote:
On Tue, Jan 14, 2014 at 10:28:23AM +0800, Daniel J Blueman wrote:
Peter,
I found out that the build failure was caused by the fact that the
__native_word() macro (used internally by compiletime_assert_atomic())
allows only a size of 4 or 8 for
Tuesday, January 14, 2014, 6:54:17 AM, you wrote:
> Hi Sander,
>>It's calling the "pci_fixup_video" quirk ... and it's calling it twice ..
>>which if i read the comment correctly .. shouldn't be the case:
> I think that there is only one bridge VGA Enable bit is set on normal machine.
> I
On 14 January 2014 13:26, Arnd Bergmann wrote:
>> > > Are you suggesting that I should #ifndef ARM in common code, or that I
>> > > should neglect to document what the common code will do with data it is
>> > > given by UEFI?
>> >
>> > It would probably be good to document the fact that it won't
On Tue, Jan 14, 2014 at 06:05:15AM -0500, Prarit Bhargava wrote:
[..]
> >>> As mentioned, self-NAK. I have seen a system that I needed to specify
> >>> memmap=exactmap & had hotplug memory. I will only keep the
> >>> acpi_no_memhotplug
> >>> option in the next version of the patch.
> >>
> >>
>
Thanks for the replies, you led me to a new solution,
I now think build_skb() is not the right choice, my motivation for
using it in the first place, that I thought it meant getting away with
not copying memory.
build_skb() is replaced by netdev_alloc_skb_ip_align() and memcpy()
(derived from
On Tue, Jan 14, 2014 at 4:15 PM, H. Peter Anvin wrote:
> On 01/14/2014 04:51 AM, Peter Zijlstra wrote:
>> On Tue, Jan 14, 2014 at 03:53:31PM +1100, Stephen Rothwell wrote:
>>> Hi Andrew,
>>>
>>> Today's linux-next merge of the akpm-current tree got a conflict in
>>> kernel/futex.c between commit
On Tue, Jan 14, 2014 at 03:47:34PM +0800, rogera...@realtek.com wrote:
> From: Roger Tseng
>
> Realtek USB card reader provides a channel to transfer command or data to
> flash
> memory cards. This driver exports host instances for mmc and memstick
> subsystems
> and handles basic works.
>
>
On Tue, 2014-01-14 at 11:43 +0900, Yasuaki Ishimatsu wrote:
> (2014/01/14 10:41), Toshi Kani wrote:
> > On Tue, 2014-01-14 at 10:11 +0900, Yasuaki Ishimatsu wrote:
> > :
> I think we need a knob manually enable mem-hotplug when specify memmap.
> But
> it is another story.
>
On 14/01/14 14:53, Olaf Hering wrote:
> On Mon, Jan 13, David Vrabel wrote:
>
>> Can we have a patch to blkif.h that clarifies this?
>
> What about this change?
>
> diff --git a/xen/include/public/io/blkif.h b/xen/include/public/io/blkif.h
> index 84eb7fd..56e2faa 100644
> ---
Hi Mark,
On Tue, Jan 14, 2014 at 3:50 PM, Mark Brown wrote:
> On Tue, Jan 14, 2014 at 03:44:43PM +0100, Geert Uytterhoeven wrote:
>> On Tue, Jan 14, 2014 at 2:45 PM, Mark Brown wrote:
>> >> > when calling set_cs() is probably OK though.
>
>> >> Just flipping the sense of enable still needs a
At Thu, 2 Jan 2014 13:07:47 +0100,
Arnd Bergmann wrote:
>
> We want to remove all sleep_on variants from the kernel because they are
> racy. In case of the pinnacle driver, we can replace
> interruptible_sleep_on_timeout with wait_event_interruptible_timeout
> by changing the meaning of a few
On Monday 13 January 2014, Ravi Patel wrote:
> > Examples for local resource management (I had to think about this
> > a long time, but probably some of these are wrong) would be
> > * balancing between multiple non-busmaster devices connected to
> > a dma-engine
> > * distributing incoming
On 01/14/2014 04:51 AM, Peter Zijlstra wrote:
> On Tue, Jan 14, 2014 at 03:53:31PM +1100, Stephen Rothwell wrote:
>> Hi Andrew,
>>
>> Today's linux-next merge of the akpm-current tree got a conflict in
>> kernel/futex.c between commit a52b89ebb6d4 ("futexes: Increase hash table
>> size for better
On 01/14/2014 03:55 AM, Borislav Petkov wrote:
> On Tue, Jan 14, 2014 at 09:41:33AM -0200, Henrique de Moraes Holschuh wrote:
>> I just got this assigned to amd64-microcode in Debian, but it is something
>> that needs to be worked around by the EFI/BIOS and/or the kernel.
>>
>> Since we all know
On Mon, Jan 13, 2014 at 7:11 PM, Minchan Kim wrote:
> Hello Dan,
>
> Sorry for the late response and I didn't look at the code yet
> because I am not convinced. :(
>
> On Thu, Dec 19, 2013 at 08:23:27AM -0500, Dan Streetman wrote:
>> Currently, zswap is writeback cache; stored pages are not sent
On 14.01.14 09:52:11, Weng Meiling wrote:
> On 2014/1/13 16:45, Robert Richter wrote:
> > On 20.12.13 15:49:01, Weng Meiling wrote:
> >> The problem was once triggered on kernel 2.6.34, the main information:
> >> <3>BUG: soft lockup - CPU#0 stuck for 60005ms! [opcontrol:8673]
> >>
> >> Pid: 8673,
From: Srinivas Kandagatla
Hi Linus W,
This series of patches add interrupt controller support to ST pinctrl driver.
ST pin controller GPIO bank can have one of the two possible types of
interrupt-wirings.
First type is via irqmux, single interrupt is used by multiple gpio
banks. This reduces
From: Srinivas Kandagatla
This patch adds interrupt support for STiH415 pin controllers.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/stih415-pinctrl.dtsi | 75
1 files changed, 75 insertions(+), 0 deletions(-)
diff --git
From: Srinivas Kandagatla
ST pin controller does not have hardware support for detecting edge
triggered interrupts, It only has level triggering support.
This patch attempts to fake up edge triggers from hw level trigger
support in software. With this facility now the gpios can be easily used
From: Srinivas Kandagatla
This patch add interrupt support to the pincontroller driver.
ST Pincontroller GPIO bank can have one of the two possible types of
interrupt-wirings.
First type is via irqmux, single interrupt is used by multiple gpio
banks. This reduces number of overall interrupts
From: Srinivas Kandagatla
This patch adds interrupt support for STiH416 pin controllers.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/stih416-pinctrl.dtsi | 81
1 files changed, 81 insertions(+), 0 deletions(-)
diff --git
On Thu, Jan 09, 2014 at 11:37:34AM -0700, Stephen Warren wrote:
> From: Stephen Warren
>
> This stashes away the EDID data so that the sysfs per-connector file
> "edid" can display it. Without this change, the "edid" file is always
> empty.
>
> Signed-off-by: Stephen Warren
> ---
>
From: Srinivas Kandagatla
Probe function had commas instead of semi-colons on some of the lines.
This patch just fixes those lines. No functional chagnes done in this
patch.
Signed-off-by: Srinivas Kandagatla
---
drivers/pinctrl/pinctrl-st.c |8
1 files changed, 4 insertions(+),
On 12/30/2013 11:43 AM, Daniel Lezcano wrote:
Hi Thomas and Ingo,
here is a pull request for a single fix for 3.13. It is based on the
latest timers/urgent update.
* Soren Brinkmann fixed the cadence_ttc driver where a call to
clk_get_rate happens in an interrupt context. More precisely in
On 14/01/2014 15:20, Jean-Jacques Hiblot :
> 2014/1/11 boris brezillon :
>> On 09/01/2014 22:04, Jean-Jacques Hiblot wrote:
>>>
>>> Hi Boris,
>>>
>>> 2014/1/9 boris brezillon :
Hello JJ,
On 09/01/2014 13:31, Jean-Jacques Hiblot wrote:
>
> The EBI/SMC external
When kernfs_seq_start() fails to obtain an active reference, it
returns ERR_PTR(-ENODEV). kernfs_seq_stop() is then invoked with the
error pointer value; however, it still proceeds to invoke
kernfs_put_active() on the node leading to unbalanced put.
If kernfs_seq_stop() is called even after
On Mon, Jan 13, David Vrabel wrote:
> Can we have a patch to blkif.h that clarifies this?
What about this change?
diff --git a/xen/include/public/io/blkif.h b/xen/include/public/io/blkif.h
index 84eb7fd..56e2faa 100644
--- a/xen/include/public/io/blkif.h
+++ b/xen/include/public/io/blkif.h
@@
On Tue, Jan 14, 2014 at 03:44:43PM +0100, Geert Uytterhoeven wrote:
> On Tue, Jan 14, 2014 at 2:45 PM, Mark Brown wrote:
> > If we're manually setting /CS it really makes no difference what the
> > chip thinks the polarity is - something that is controlling /CS
> > autonomously can't implement
On Tue, Jan 14, 2014 at 2:45 PM, Mark Brown wrote:
> On Tue, Jan 14, 2014 at 02:23:37PM +0100, Geert Uytterhoeven wrote:
>> On Tue, Jan 14, 2014 at 1:52 PM, Mark Brown wrote:
>> >On Tue, Jan 14, 2014 at 12:36:51PM +0100, Geert Uytterhoeven wrote:
>
>> > This also pushes the handling of CS_HIGH
On Mon, 2014-01-13 at 19:49 +0100, Arnd Bergmann wrote:
> On Friday 10 January 2014, Mark Salter wrote:
> > This patch adds PE/COFF header fields to the start of the Image
> > so that it appears as an EFI application to EFI firmware. An EFI
> > stub is included to allow direct booting of the
At Mon, 13 Jan 2014 16:27:21 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.12.8 release.
> There are 77 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
Hi Jean-Francios,
I do think split the muti-issues into deferent patches will be easier to
upstream code, and the risk will be lower.
So this patch is just the first step.
Thanks,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, 14 Jan 2014, Daniel Vetter wrote:
> On Mon, Jan 13, 2014 at 03:16:42PM -0500, Alan Stern wrote:
> > On Wed, 8 Jan 2014, Daniel Vetter wrote:
> >
> > > On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
> > > > On Wed, 8 Jan 2014, Daniel Vetter wrote:
> > > >
> > > > > On Wed,
On Tue, Jan 14, 2014 at 04:00:17PM +0800, Zhang Rui wrote:
> On Mon, 2014-01-13 at 17:35 +, Mark Brown wrote:
> > On Mon, Jan 13, 2014 at 09:48:31PM +0800, Zhang Rui wrote:
> > > ACPI enumerated devices has ACPI style _HID and _CID strings,
> > > all of these strings can be used for both
On Tue, Jan 07, 2014 at 06:31:52PM +0530, Kishon Vijay Abraham I wrote:
> > In any case, having two device names to deal with does not add any
> > more risk. These associations should always be made in the place where
> > the phy device is created so you will always know it's device name.
>
>
On Tue, Jan 14, 2014 at 06:05:15AM -0500, Prarit Bhargava wrote:
>
>
> On 01/13/2014 08:41 PM, Toshi Kani wrote:
> > On Tue, 2014-01-14 at 10:11 +0900, Yasuaki Ishimatsu wrote:
> > :
> I think we need a knob manually enable mem-hotplug when specify memmap.
> But
> it is another
On Tue, 2014-01-14 at 14:51 +0400, Andrew Vagin wrote:
> I think __nf_conntrack_alloc must use atomic_inc instead of
> atomic_set. And we must be sure, that the first object from a new page is
> zeroized.
No you can not do that, and we do not need.
If a new page is allocated, then you have the
On Tue, Jan 14, 2014 at 12:34:56PM +0100, Geert Uytterhoeven wrote:
> + * @transfer_one: transfer a single spi_transfer.
> + *Synchronous transfer methods must return 0 on success.
> + *Asynchronous transfer methods must return a strict-positive
> + *
On Tuesday 14 January 2014 08:17 AM, Grygorii Strashko wrote:
> Hi Philipp,
>
> On 01/13/2014 03:03 PM, Philipp Hachtmann wrote:
>> Add a new memory state "nomap" to memblock. This can be used to truncate
>> the usable memory in the system without forgetting about what is really
>> installed.
>
Hey, Michal.
On Tue, Jan 14, 2014 at 02:30:05PM +0100, Michal Hocko wrote:
> On Mon 13-01-14 17:54:04, Hugh Dickins wrote:
> > It is surprising that the mem_cgroup iterator can return memcgs which
> > have not yet been fully initialized. By accident (or trial and error?)
> > this appears not to
601 - 700 of 1818 matches
Mail list logo
