On Thu, Mar 26, 2015 at 02:04:35PM +0200, Octavian Purdila wrote:
> On Thu, Mar 26, 2015 at 12:16 PM, Mika Westerberg
> wrote:
> > On Wed, Mar 25, 2015 at 11:12:16PM +0200, Octavian Purdila wrote:
> >> On Wed, Mar 25, 2015 at 3:21 PM, Mika Westerberg
> >> wrote:
> >> > On Wed, Mar 25, 2015 at
Add a Console Private CSI sequence to specify the current console's
cursor blink interval. The interval is specified as a number of
milliseconds until the next cursor display state toggle, from 50 to
65535.
Signed-off-by: Scot Doyle
---
man4/console_codes.4 | 1 +
1 file changed, 1 insertion(+)
On Thu, 26 Mar 2015, Andy Shevchenko wrote:
> On Thu, 2015-03-26 at 08:29 +, Lee Jones wrote:
> > On Wed, 25 Mar 2015, Andy Shevchenko wrote:
> >
> > > dmi_get_system_info() may return NULL either when CONFIG_DMI is not set
> > > or when
> > > board has an old firmware. The patch prevents a
vt now provides a cursor blink interval via vc_data. Use this
interval instead of the currently hardcoded 200 msecs. Store it in
fbcon_ops to avoid locking the console in cursor_timer_handler().
Signed-off-by: Scot Doyle
Acked-by: Pavel Machek
---
drivers/video/console/fbcon.c | 10 +-
UTMI+ Low Pin Interface (ULPI) is a commonly used PHY
interface for USB 2.0. The ULPI specification describes a
standard set of registers which the vendors can extend for
their specific needs. ULPI PHYs provide often functions
such as charger detection and ADP sensing and probing.
There are two
On Wed, Mar 25, 2015 at 06:07:45AM -0700, Guenter Roeck wrote:
> On 03/25/2015 06:03 AM, Guenter Roeck wrote:
> >On 03/25/2015 01:30 AM, Greg Kroah-Hartman wrote:
> >>On Tue, Mar 24, 2015 at 07:50:07PM -0700, Guenter Roeck wrote:
> >>>On 03/24/2015 08:45 AM, Greg Kroah-Hartman wrote:
> This is
On Thu, Mar 26, 2015 at 1:01 AM, Christoph Hellwig wrote:
> On Wed, Mar 25, 2015 at 07:15:42PM -0700, Dan Williams wrote:
>> Random thought, type-12 memory happens to correspond to "legacy"
>> NVDIMM systems with smaller capacities. Perhaps "new NVDIMM" should
>> not be is_e820_ram() by default?
On 03/26/2015 08:01 AM, Greg Kroah-Hartman wrote:
I need an ack from Benjamin and/or David before I can take these, as
they are the maintainers of the driver, and have the ability to test
these patches.
I'll just wait to apply them until that happens.
Ben/David?
I'll test them today. :)
--
>> - I also played with lockdep detection. With lglock-v0 applied
>>some tests like flock02 and posix02 get considerable worse
>>results. The difference between flock01 and flock02 is that
>>the children of flock01 fight over one file lock versus
>>the children of flock02 lock and
Add an escape sequence to specify the current console's cursor blink
interval. The interval is specified as a number of milliseconds until
the next cursor display state toggle, from 50 to 65535. /proc/loadavg
did not show a difference with a one msec interval, but the lower
bound is set to 50
On Thu, 26 Mar 2015, Beomho Seo wrote:
> On 03/24/2015 05:38 PM, Krzysztof Kozlowski wrote:
> > 2015-03-24 9:01 GMT+01:00 Beomho Seo :
> >> On 03/10/2015 10:44 PM, Beomho Seo wrote:
> >>> On 03/09/2015 09:13 PM, Krzysztof Kozlowski wrote:
> On pon, 2015-03-09 at 20:46 +0900, Beomho Seo wrote:
On Thu, 26 Mar 2015 07:27:30 +0100
Mike Galbraith wrote:
> On Thu, 2015-03-26 at 06:23 +0100, Mike Galbraith wrote:
>
> > I plan on taking a poke at getting "don't raise timer unconditionally"
> > working again when I get myself unburied, and see if I can come up with
> > a somewhat less icky
On Thu, Mar 26, 2015 at 06:41:36AM -0700, Kevin Cernekee wrote:
> http://patchwork.linux-mips.org/patch/8254/
>
> We wound up configuring this through DT rather than Kconfig.
>
> Ralf, would you prefer an incremental patch or a whole new submission?
Whatever you prefer.
Ralf
--
To
On Wed, 25 Mar 2015, Geert Uytterhoeven wrote:
> Hi Lee,
>
> On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote:
> > On Fri, 06 Mar 2015, Mike Turquette wrote:
> >> Quoting Lee Jones (2015-03-04 04:00:03)
> >> > Mike,
> >> >
> >> > Do you want me to resend this set with Robert's Reviewed-by
v2: Add documentation to console_codes man page (man-pages repo)
This patch series adds an escape sequence to specify the current console's
cursor blink interval. The default interval is set to fbcon's currently
hardcoded 200 msecs.
Scot Doyle (3):
vt: add cursor blink interval escape
On Thu, Mar 26, 2015 at 12:10:55AM +, Stephen Rothwell wrote:
> On Wed, 25 Mar 2015 17:20:03 + Will Deacon wrote:
> > We've got a series of patches introducing ACPI support for arm64 that
> > are tentatively targetting the 4.1 merge window. Whilst there are
> > face-to-face discussions
From: yuanzhichang
In the patch whose title is "add better page protections to arm64"
(commit da141706aea52c1a9fbd28cb8d289b78819f5436), The direct mapping
page table entries for HEAD_TEXT segment were configured as PAGE_KERNEL,
without the executable attribute. But when the secondary CPUs are
On Thu, Mar 26, 2015 at 01:22:59PM +, Russell King - ARM Linux wrote:
> On Thu, Mar 26, 2015 at 12:30:29PM +, Mel Gorman wrote:
> > On Thu, Mar 26, 2015 at 11:46:12AM +, Russell King - ARM Linux wrote:
> > >
> > >
> > > Looking at Mel's commit, I don't see a reason why we couldn't
Commit-ID: 6e206020324c50a95486f6b279a53512febed92d
Gitweb: http://git.kernel.org/tip/6e206020324c50a95486f6b279a53512febed92d
Author: Maxime Ripard
AuthorDate: Thu, 26 Mar 2015 10:27:09 +0100
Committer: Ingo Molnar
CommitDate: Thu, 26 Mar 2015 10:59:40 +0100
Commit-ID: 11bc26fe372fa6da81c82c68f755d2795838a640
Gitweb: http://git.kernel.org/tip/11bc26fe372fa6da81c82c68f755d2795838a640
Author: Richard Weinberger
AuthorDate: Thu, 26 Mar 2015 10:27:06 +0100
Committer: Ingo Molnar
CommitDate: Thu, 26 Mar 2015 10:59:40 +0100
clocksource/drivers:
On Tue, Feb 24, 2015 at 12:01:52PM +0200, Robert Dolca wrote:
> +static struct i2c_device_id fdp_nci_i2c_id_table[] = {
> + {"INT339A", 0},
If this is ACPI only device you can remove the above line.
> + {}
> +};
> +
> +MODULE_DEVICE_TABLE(i2c, fdp_nci_i2c_id_table);
And this as well.
>
On Thu, 26 Mar 2015 02:50:50 +
Pádraig Brady wrote:
> >> echo 'sched:sched_switch' > set_event
> >> -usleep 1
> >> +sleep 0.001
> >
> > We had patches out about this, because sleep 0.001 is not always
> > supported either.
>
> really?
> In that edge case you might:
It's not too much of
On Thu, Mar 26, 2015 at 3:47 AM, Valentin Rothberg
wrote:
> Hi Kevin,
>
> your commit dd6d84812b1a ("MIPS: BMIPS: Enable additional peripheral
> and CPU support in defconfig") adds a select on the Kconfig symbol
> RAW_IRQ_ACCESORS. However, this symbol is not defined in Kconfig so
> that the
On 03/06/2015 08:50 PM, Andy Lutomirski wrote:
I broke 32-bit kernels. The implementation of sp0 was correct as
far as I can tell, but sp0 was much weirder on x86_32 than I
realized. It has the following issues:
- Init's sp0 is inconsistent with everything else's: non-init tasks
are
On Wed 25-03-15 02:17:10, Johannes Weiner wrote:
> The zonelist locking and the oom_sem are two overlapping locks that
> are used to serialize global OOM killing against different things.
>
> The historical zonelist locking serializes OOM kills from allocations
> with overlapping zonelists
Here are two panic logs from smart phone test, and the kernel version is v3.10.
log1 is "Unable to handle kernel paging request at virtual address c0704da020",
it should be ffc0704da020, right?
and log2 is "Unable to handle kernel paging request at virtual address
1e000796", it should be
On Thu, Mar 26, 2015 at 10:34:42AM +, Peter Zijlstra wrote:
> On Thu, Mar 26, 2015 at 07:31:12PM +1100, Stephen Rothwell wrote:
> > Hi Christian,
> >
> > After merging the access_once tree, today's linux-next build (arm
> > multi_v7_defconfig) produced lots of this warning:
> >
> > In file
On 03/24/2015 05:38 PM, Krzysztof Kozlowski wrote:
> 2015-03-24 9:01 GMT+01:00 Beomho Seo :
>> On 03/10/2015 10:44 PM, Beomho Seo wrote:
>>> On 03/09/2015 09:13 PM, Krzysztof Kozlowski wrote:
On pon, 2015-03-09 at 20:46 +0900, Beomho Seo wrote:
> On 03/09/2015 08:02 PM, Krzysztof
On Thu, Mar 26, 2015 at 12:30:29PM +, Mel Gorman wrote:
> On Thu, Mar 26, 2015 at 11:46:12AM +, Russell King - ARM Linux wrote:
> >
> >
> > Looking at Mel's commit, I don't see a reason why we couldn't use that
> > solution - it gets rid of walking the page array, which has been fraught
On Thu 26-03-15 12:51:40, Michal Hocko wrote:
> On Wed 25-03-15 17:51:31, David Rientjes wrote:
> > On Wed, 25 Mar 2015, Johannes Weiner wrote:
> >
> > > Setting oom_killer_disabled to false is atomic, there is no need for
> > > further synchronization with ongoing allocations trying to OOM-kill.
On Thu, 26 Mar 2015 11:11:19 +0100
Daniel Wagner wrote:
> Hi Jeff,
>
> Sorry for the long delay. Was I week on holiday and the testing
> took a bit longer than I expected.
>
> On 03/14/2015 01:40 PM, Jeff Layton wrote:
> > On Tue, 10 Mar 2015 09:20:24 +0100
> > Daniel Wagner wrote:
> >> On
Hi Matt,
Le Thursday 26 March 2015 à 13:06 +, Matt Fleming a écrit :
> On Fri, 20 Mar, at 09:59:47AM, Jean Delvare wrote:
> > dmi_num is a u16, dmi_len is a u32, so this construct:
> >
> > dmi_num = dmi_len / 4;
> >
> > would result in an integer overflow for a DMI table larger than
> >
diff --git a/Makefile b/Makefile
index e49665a2b5ac..713bf263952f 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 19
-SUBLEVEL = 2
+SUBLEVEL = 3
EXTRAVERSION =
NAME = Diseased Newt
diff --git a/arch/arm/boot/dts/am33xx-clocks.dtsi
I'm announcing the release of the 3.19.3 kernel.
All users of the 3.19 kernel series must upgrade.
The updated 3.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.19.y
and can be browsed at the normal kernel.org git web browser:
On Fri, 20 Mar, at 09:59:47AM, Jean Delvare wrote:
> dmi_num is a u16, dmi_len is a u32, so this construct:
>
> dmi_num = dmi_len / 4;
>
> would result in an integer overflow for a DMI table larger than
> 256 kB. I've never see such a large table so far, but SMBIOS 3.0
> makes it possible
Change to using endian agnostic _relaxed IO accessors instead of __raw
Signed-off-by: Ben Dooks
--
CC: Andrew Victor
CC: Nicolas Ferre
CC: Jean-Christophe Plagniol-Villard
CC: Mike Turquette (maintainer:COMMON CLK FRAMEWORK)
CC: Stephen Boyd (maintainer:COMMON CLK FRAMEWORK)
CC:
On 26.03.15 15:05, Matt Fleming wrote:
On Mon, 16 Mar, at 11:02:29PM, Ivan.khoronzhuk wrote:
Matt, I've sent new patch that replaces this one.
"[Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs"
It can take a while to go via review.
OK, thanks Ivan. I've dropped commit
The slock spinlock in the cx23885_dev struct is only initialised if analogue
video is being used, but is used in other places too, leading to the attached
lockdep complaint.
Move the lock initialisation so that it is done unconditionally.
INFO: trying to register non-static key.
the code is fine
On Wed, Mar 25, 2015 at 3:45 PM, David Howells wrote:
> Supply two functions to test whether a filesystem's own dentries are positive
> or negative (d_really_is_positive() and d_really_is_negative()).
>
> The problem is that the DCACHE_ENTRY_TYPE field of dentry->d_flags may be
> overridden by
On Mon, 16 Mar, at 11:02:29PM, Ivan.khoronzhuk wrote:
>
> Matt, I've sent new patch that replaces this one.
> "[Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs"
> It can take a while to go via review.
OK, thanks Ivan. I've dropped commit ("firmware: dmi-sysfs: Add SMBIOS
entry point
On Wed 25-03-15 02:17:09, Johannes Weiner wrote:
> It turns out that the mechanism to wait for exiting OOM victims is
> less generic than it looks: it won't issue wakeups unless the OOM
> killer is disabled.
>
> The reason this check was added was the thought that, since only the
> OOM disabling
When a CPU is kicked to do nohz idle balancing, it wakes up to do load
balancing on itself, followed by load balancing on behalf of idle CPUs.
But it may end up with load after the load balancing attempt on itself.
This aborts nohz idle balancing. As a result several idle CPUs are left
without
On Thu 26-03-15 13:53:48, Michal Hocko wrote:
> On Wed 25-03-15 02:17:08, Johannes Weiner wrote:
> > Disabling the OOM killer needs to exclude allocators from entering,
> > not existing victims from exiting.
>
> The idea was that exit_oom_victim doesn't miss a waiter.
>
> exit_oom_victim is
Changes v1-v2:
* Rebased to v4.0-rc5
* Converted domain-types to a bit-field
Hi,
here is patch-set to replace the existing domain_init and
domain_destroy iommu-ops with the new domain_alloc and
domain_free callbacks
The new callbacks move the allocation of iommu domains into
On Wed 25-03-15 02:17:08, Johannes Weiner wrote:
> Disabling the OOM killer needs to exclude allocators from entering,
> not existing victims from exiting.
The idea was that exit_oom_victim doesn't miss a waiter.
exit_oom_victim is doing
atomic_dec_return(_victims) &&
X
Sent from my BlackBerry 10 smartphone on the TELUS network.
Original Message
From: Joerg Roedel
Sentuv: Thursday, March 26, 2015 8:51 AM
To: io...@lists.linux-foundation.org
Cc: Will Deacon; Kukjin Kim; David Woodhouse; Heiko Stuebner; Hiroshi Doyu;
Stephen Warren; Thierry Reding;
From: Joerg Roedel
Get rid of domain_init and domain_destroy and implement
domain_alloc/domain_free instead.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 48 ++---
1 file changed, 28 insertions(+), 20 deletions(-)
diff --git
From: Joerg Roedel
Implement the new iommu-ops function pointers and remove the
obsolete domain_init and domain_destroy functions.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 84 ++---
drivers/iommu/amd_iommu_types.h | 7 ++--
2 files
From: Joerg Roedel
This allows to handle domains differently based on their
type in the future. An IOMMU driver can implement certain
optimizations for DMA-API domains for example.
The domain types can be extended later and some of the
existing domain attributes can be migrated to become domain
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/exynos-iommu.c | 87
1 file changed, 47 insertions(+), 40 deletions(-)
diff --git
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/tegra-smmu.c | 41 +++--
1 file changed, 23 insertions(+), 18 deletions(-)
diff --git
On Wed, Mar 25, 2015 at 12:36:34PM -0400, Mark Hounschell wrote:
> BTW, so far the first 2 patches are working well. I was going to
> wait until the end of the day to report but so far I have been
> unable to produce the problems I was seeing. And I am in the middle
> of some driver work so lots
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/arm-smmu.c | 46 +++---
1 file changed, 27 insertions(+), 19 deletions(-)
diff --git
From: Joerg Roedel
Implement the new domain_alloc and domain_free call-backs
and remove the old domain_init/destroy ones.
Signed-off-by: Joerg Roedel
---
drivers/iommu/omap-iommu.c | 49 +++---
1 file changed, 29 insertions(+), 20 deletions(-)
diff
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/ipmmu-vmsa.c | 41 +++--
1 file changed, 23 insertions(+), 18 deletions(-)
diff --git
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/tegra-gart.c | 67 +++---
1 file changed, 46 insertions(+), 21 deletions(-)
diff --git
From: Joerg Roedel
All drivers have been converted to the new domain_alloc and
domain_free iommu-ops. So remove the old ones and get rid of
iommu_domain->priv too, as this is no longer needed when the
struct iommu_domain is embedded in the private structures of
the iommu drivers.
Signed-off-by:
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/msm_iommu.c | 73 +++
1 file changed, 36 insertions(+), 37 deletions(-)
diff --git
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/rockchip-iommu.c | 40
1 file changed, 24 insertions(+), 16 deletions(-)
diff --git
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/fsl_pamu_domain.c | 60 ++---
drivers/iommu/fsl_pamu_domain.h | 2 +-
2 files changed, 33
From: Joerg Roedel
Implement domain_alloc and domain_free iommu-ops as a
replacement for domain_init/domain_destroy.
Signed-off-by: Joerg Roedel
---
drivers/iommu/shmobile-iommu.c | 39 +++
1 file changed, 23 insertions(+), 16 deletions(-)
diff --git
From: Joerg Roedel
Check for the new __IOMMU_DOMAIN_PAGING flag before calling
into the iommu drivers ->map and ->unmap call-backs.
Signed-off-by: Joerg Roedel
---
drivers/iommu/iommu.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
From: Joerg Roedel
These new call-backs defer the allocation and destruction of
'struct iommu_domain' to the iommu driver. This allows
drivers to embed this struct into their private domain
structures and to get rid of the domain_init and
domain_destroy call-backs when all drivers have been
This change makes the check exact (no more false positives
on kernel addresses).
It isn't really important to be fully correct here -
almost all addresses we'll ever see will be userspace ones,
but OTOH it looks to be cheap enough:
the new code uses two more ALU ops but preserves %rcx,
allowing
On 25/03/2015 19:01, Joe Perches wrote:
On Wed, 2015-03-25 at 18:56 +0100, Mason wrote:
AFAIU, functions only used at system init are tagged __init to have
the linker store them in a separate .init.text section, so memory can
be reclaimed once initialization is complete. Is that correct?
The
2015-03-26 17:02 GMT+08:00 :
> From: Fu Wei
>
> This is a Chinese translated version of
> Documentation/arm64/legacy_instructions.txt
>
> It is based on the modifications of
> Documentation/arm64/legacy_instructions.txt in submission:
> "587064b6", "bd35a4ad", "2d888f48", "c852f320".
>
>
On 2015/3/26 19:37, Michael S. Tsirkin wrote:
> pci_msi_init_pci_dev and pci_msi_off share a lot of code.
> This used to be justified since pci_msi_init_pci_dev
> wasn't compiled in when CONFIG_PCI_MSI is off.
> Now that it is, let's reuse code.
It's not correct, pci_msi_off() would be used in
On 03/26/2015 12:57 PM, Vinod Koul wrote:
> On Wed, Mar 11, 2015 at 03:23:27PM +0200, Peter Ujfalusi wrote:
>> Instead of magic numbers in the code, use define for number of logical DMA
>> channels and DMA requests.
>>
>> Signed-off-by: Peter Ujfalusi
>> ---
>> drivers/dma/omap-dma.c | 7 +--
On 03/26/2015 12:56 PM, Vinod Koul wrote:
>> +#define TI_XBAR_OUTPUTS 127
>> +#define TI_XBAR_INPUTS 256
> Ideally this should be moved to DT. Will next revision of this chip always
> support these output and inputs?
They are coming from DT. I'm using these as fall back values in case we
On Thu, Mar 26, 2015 at 11:46:12AM +, Russell King - ARM Linux wrote:
>
>
> Looking at Mel's commit, I don't see a reason why we couldn't use that
> solution - it gets rid of walking the page array, which has been fraught
> in the past due to ARM having platforms which have holes in their
>
That code is a relict from the early days of UML.
ia64 support was never completed nor worked.
Let's rip it out.
Signed-off-by: Richard Weinberger
---
arch/um/Makefile-ia64 | 1 -
arch/um/sys-ia64/Makefile | 11 ---
arch/um/sys-ia64/sysdep/ptrace.h | 16
At times where UML used the TT mode to operate it had
kind of SMP support. It never got finished nor was
stable.
Let's rip out that cruft and stop confusing developers
which do tree-wide SMP cleanups.
If someone wants SMP support UML it has do be done from scratch.
Signed-off-by: Richard
Currently hostfs issues every time a seekdir(), in fact
it has to do this only upon the first call.
Also telldir() can be omitted as we can obtain the directory
offset from readdir().
Signed-off-by: Richard Weinberger
---
fs/hostfs/hostfs.h | 3 ++-
fs/hostfs/hostfs_kern.c | 1 +
Before we had SKAS0 UML had two modes of operation
TT (tracing thread) and SKAS3/4 (separated kernel address space).
TT was known to be insecure and got removed a long time ago.
SKAS3/4 required a few (3 or 4) patches on the host side which never went
mainline. The last host patch is 10 years old.
Highmem was always buggy and experimental on UML(i386).
In times where 64 bit computers are default we can
remove that experimental code.
Signed-off-by: Richard Weinberger
---
arch/um/Kconfig.um| 12
arch/um/include/asm/fixmap.h | 4 ---
arch/um/include/asm/pgtable.h | 6
That code is a relict from the early days of UML.
ppc support was never completed nor worked.
Let's rip it out.
Signed-off-by: Richard Weinberger
---
arch/um/Makefile-ppc| 9 ---
arch/um/sys-ppc/Makefile| 65
Remove left over code from commit 970e51feaddb
(um: Add support for CONFIG_STACKTRACE)
Signed-off-by: Richard Weinberger
---
arch/um/kernel/sysrq.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/arch/um/kernel/sysrq.c b/arch/um/kernel/sysrq.c
index 894c8d3..aa1b56f
On Thu, Mar 19, 2015 at 12:39:04AM -0400, M. Vefa Bicakci wrote:
> Adjust the whitespace in the signature, local variable declaration and
> initialization parts of a number of functions to increase readability
> in rtl8723au's rtw_security.c.
>
> v2: Make sure that the arcfour_encrypt function's
There are several place using gnttab async unmap and wait for
completion, so move the common code to a function
gnttab_unmap_refs_async_wait_completion().
Signed-off-by: Bob Liu
---
drivers/block/xen-blkback/blkback.c | 31 +++
drivers/xen/gntdev.c|
Commit c43cf3ea8385 ("xen-blkback: safely unmap grants in case they are still
in use") use gnttab_unmap_refs_async() to wait until the mapped pages are no
longer in use before unmapping them, but that commit missed the persistent case.
Purge persistent pages can't be unmapped either unless no
On Thu, Mar 26, 2015 at 10:10:17AM +0100, Jiri Slaby wrote:
> This is a trivial port from kGraft. Module relocations are not
> supported.
>
> Signed-off-by: Jiri Slaby
> ---
> [v2] return ENOSYS
> [v3] proper return value from klp_check_compiler_support
>
> arch/s390/Kconfig |
On Thu, 26 Mar 2015, Daniel Vetter wrote:
> On Thu, Mar 26, 2015 at 4:29 AM, Dave Airlie wrote:
>> I've pushed a drm-fixes-staging branch that backport's Daniel's
>> drm-next fix from 9 hours ago,
>>
>> However it isn't tested yet, so if you want to give it a whirl grab it.
>>
>> Hopefully when
On 2015/3/25 15:22, Huang Ying wrote:
> [ 28.745155] genirq: Flags mismatch irq 8. 0080 (mmc0) vs.
> (rtc0)
okay, I replicated this on my side now.
Firstly, I don't think the patch did anything wrong. However, the patch
exposes a few issues FWICT currently:
- Should we enable
On 03/26/2015 12:50 PM, Vinod Koul wrote:
> On Wed, Mar 11, 2015 at 03:23:24PM +0200, Peter Ujfalusi wrote:
>> DMA routers are transparent devices used to mux DMA requests from
>> peripherals to DMA controllers. They are used when the SoC integrates more
>> devices with DMA requests then their
On Wed, Mar 25, 2015 at 01:28:43AM +0530, Niranjan Dighe wrote:
> Removed unused block of code guarded by #ifdef SLIC_TRACE_DUMP_ENABLED
> And removed redundant static char *slic_banner and replaced actual string in
> place of format string.
That's multiple things you are doing all in the same
On Thu, Mar 26, 2015 at 11:49:25AM +0100, Gerd Hoffmann wrote:
> virtio-input is basically evdev-events-over-virtio, so this driver isn't
> much more than reading configuration from config space and forwarding
> incoming events to the linux input layer.
>
> Signed-off-by: Gerd Hoffmann
Still a
On Wed, 25 Mar 2015, Daniel Vetter wrote:
> This is a very similar bug in the load detect code fixed in
>
> commit 9128b040eb774e04bc23777b005ace2b66ab2a85
> Author: Daniel Vetter
> Date: Tue Mar 3 17:31:21 2015 +0100
>
> drm/i915: Fix modeset state confusion in the load detect code
>
>
On Wed, 25 Mar 2015, Josh Boyer wrote:
> On Wed, Mar 25, 2015 at 1:17 PM, Daniel Vetter wrote:
>> On Wed, Mar 25, 2015 at 12:42:46PM -0400, Josh Boyer wrote:
>>> > I'll try that a bit later today. Out of sheer curiosity, I folded
>>> > commit5ba76c41e55c (drm/i915: Put update_state_fb() next to
On Thu, Mar 26, 2015 at 12:16 PM, Mika Westerberg
wrote:
> On Wed, Mar 25, 2015 at 11:12:16PM +0200, Octavian Purdila wrote:
>> On Wed, Mar 25, 2015 at 3:21 PM, Mika Westerberg
>> wrote:
>> > On Wed, Mar 25, 2015 at 02:25:05PM +0200, Mika Westerberg wrote:
>> >> I think we can do the same for
On 03/26/2015 04:25 PM, Peter Zijlstra wrote:
> On Fri, Feb 27, 2015 at 04:54:13PM +0100, Vincent Guittot wrote:
>> Add the SD_PREFER_SIBLING flag for SMT level in order to ensure that
>> the scheduler will put at least 1 task per core.
>>
>> Signed-off-by: Vincent Guittot
>> Reviewed-by: Preeti
On Wed, 25 Mar 2015, Daniel Vetter wrote:
> On Tue, Mar 24, 2015 at 12:10:28PM -0400, Josh Boyer wrote:
>> OK, with that commit applied I no longer get the kref.h splat and the
>> NUC machine boots headless. I still see the backtrace below on both
>> the NUC and the macbook. I have a copy of it
On Tue, Mar 24, 2015 at 08:47:26PM +0530, Sudip Mukherjee wrote:
> remove the variable "registered", which was used in the cleanup() to
> detect if the driver has successfully initialized. the cleanup()
> is called from module_exit, so its obvious that the module has
> successfully initialized. if
$(always) is added to targets by scripts/Makefile.build.
Moreover, filechk does not need .*.cmd files.
Adding these two files to targets is redundant.
Signed-off-by: Masahiro Yamada
---
Kbuild | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Kbuild b/Kbuild
index
On 16 March 2015 at 14:44, Viresh Kumar wrote:
> On 10 March 2015 at 18:35, Ingo Molnar wrote:
>
>> Yeah, so I'd like PeterZ to ACK/NAK this approach before I move
>> forward with the patches - but he's on the road right now, so it
>> will take a week I suspect.
>
> Hi Ingo,
>
> Now that Peter
On Wed 25-03-15 02:17:07, Johannes Weiner wrote:
> exit_oom_victim() already knows that TIF_MEMDIE is set, and nobody
> else can clear it concurrently. Use clear_thread_flag() directly.
Yeah. This is a left over from the review process. I originally did
unmarking unconditionally but Tejun
On Wed, 25 Mar 2015, David Rientjes wrote:
> I looked at this thread at http://marc.info/?t=14139250881 since I
> didn't have it in my mailbox, and I didn't get a chance to actually run
> your test code.
>
> In short, I think what you're saying is that
>
> ptr = mmap(..., 4KB, ...,
Around Thu 26 Mar 2015 11:45:51 + or thereabout, Ben Dooks wrote:
> Use to provide IO accessors which work on both
> AVR32 and ARM for on-chip peripherals.
>
> Signed-off-by: Ben Dooks
Acked-by: Hans-Christian Egtvedt
> --
> CC: Daniel Lezcano
> CC: Thomas Gleixner
> CC: Linux Kernel
On Mon, Mar 16, 2015 at 02:27:10PM -0400, Milosz Tanski wrote:
> This patchset introduces two new syscalls preadv2 and pwritev2. They are the
> same syscalls as preadv and pwrite but with a flag argument. Additionally,
> preadv2 implements an extra RWF_NONBLOCK flag.
There was some arugment that
On Wed 25-03-15 02:17:06, Johannes Weiner wrote:
> Rename unmark_oom_victim() to exit_oom_victim(). Marking and
> unmarking are related in functionality, but the interface is not
> symmetrical at all: one is an internal OOM killer function used during
> the killing, the other is for an OOM victim
On Thu, Mar 26, 2015 at 12:38:43PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > Absolutely, it's pretty common to mix regions in a BAR.
> > For example, we have virtio kick (ioeventfd backed,
> > handled in kernel) in same BAR as common and device
> > specific configuration.
>
> > We did the same
501 - 600 of 1610 matches
Mail list logo
