This patch modifies the dlock-list to use the per-subnode APIs to
manage the distributed lists. As a result, the number of lists that
need to be iterated in dlock_list_iterate() will be reduced at least
by half making the iteration a bit faster.
Signed-off-by: Waiman Long
---
From: Jan Kara
fsnotify_unmount_inodes() played complex tricks to pin next inode in the
sb->s_inodes list when iterating over all inodes. If we switch to
keeping current inode pinned somewhat longer, we can make the code much
simpler and standard.
Signed-off-by: Jan Kara
Signed-off-by: Waiman
When many threads are trying to add or delete inode to or from
a superblock's s_inodes list, spinlock contention on the list can
become a performance bottleneck.
This patch changes the s_inodes field to become a dlock list which
is a distributed set of lists with per-list spinlocks. As a result,
When many threads are trying to add or delete inode to or from
a superblock's s_inodes list, spinlock contention on the list can
become a performance bottleneck.
This patch changes the s_inodes field to become a dlock list which
is a distributed set of lists with per-list spinlocks. As a result,
From: Boqun Feng
Add __percpu modifier properly to help:
1. Differ pointers to actual structures with those to percpu
structures, which could improve readability.
2. Prevent sparse from complaining about "different address spaces"
Signed-off-by: Boqun
Linked list is used everywhere in the Linux kernel. However, if many
threads are trying to add or delete entries into the same linked list,
it can create a performance bottleneck.
This patch introduces a new list APIs that provide a set of distributed
lists (one per CPU), each of which is
The percpu APIs are extensively used in the Linux kernel to reduce
cacheline contention and improve performance. For some use cases, the
percpu APIs may be too fine-grain for distributed resources whereas
a per-node based allocation may be too coarse as we can have dozens
of CPUs in a NUMA node in
From: Boqun Feng
Add __percpu modifier properly to help:
1. Differ pointers to actual structures with those to percpu
structures, which could improve readability.
2. Prevent sparse from complaining about "different address spaces"
Signed-off-by: Boqun Feng
Signed-off-by:
Linked list is used everywhere in the Linux kernel. However, if many
threads are trying to add or delete entries into the same linked list,
it can create a performance bottleneck.
This patch introduces a new list APIs that provide a set of distributed
lists (one per CPU), each of which is
The percpu APIs are extensively used in the Linux kernel to reduce
cacheline contention and improve performance. For some use cases, the
percpu APIs may be too fine-grain for distributed resources whereas
a per-node based allocation may be too coarse as we can have dozens
of CPUs in a NUMA node in
On 07/11/2016 06:51 PM, Paul Gortmaker wrote:
The Kconfig currently controlling compilation of this code is:
init/Kconfig:config BPF_SYSCALL
init/Kconfig: bool "Enable bpf() system call"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of
On 07/11/2016 06:51 PM, Paul Gortmaker wrote:
The Kconfig currently controlling compilation of this code is:
init/Kconfig:config BPF_SYSCALL
init/Kconfig: bool "Enable bpf() system call"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of
With the move to iov_iter handling two issues merged
for the ko2iblnd driver. The first fix address a simple
typo of the wrong flag being used with iov_iter_kvec.
The second fix adds the payload offset to the payload
size.
Signed-off-by: James Simmons
---
With the move to iov_iter handling two issues merged
for the ko2iblnd driver. The first fix address a simple
typo of the wrong flag being used with iov_iter_kvec.
The second fix adds the payload offset to the payload
size.
Signed-off-by: James Simmons
---
> On Sun, Jul 10, 2016 at 07:14:18PM +0100, James Simmons wrote:
>
> > [ 111.210818] [] kiblnd_send+0x51d/0x9e0 [ko2iblnd]
>
> Mea culpa - in kiblnd_send() this
> if (payload_kiov)
> iov_iter_bvec(, ITER_BVEC | WRITE,
> payload_kiov,
> On Sun, Jul 10, 2016 at 07:14:18PM +0100, James Simmons wrote:
>
> > [ 111.210818] [] kiblnd_send+0x51d/0x9e0 [ko2iblnd]
>
> Mea culpa - in kiblnd_send() this
> if (payload_kiov)
> iov_iter_bvec(, ITER_BVEC | WRITE,
> payload_kiov,
On Sat, Jul 9, 2016 at 16:15 Paul Gortmaker
wrote:
>
> [Re: [PATCH 14/14] PCI: xgene: make it explicitly non-modular] On 07/07/2016
> (Thu 15:42) Duc Dang wrote:
>
> > On Thu, Jul 7, 2016 at 3:35 PM, Tanmay Inamdar wrote:
> > >
> > >
> > > On Sat,
On Sat, Jul 9, 2016 at 16:15 Paul Gortmaker
wrote:
>
> [Re: [PATCH 14/14] PCI: xgene: make it explicitly non-modular] On 07/07/2016
> (Thu 15:42) Duc Dang wrote:
>
> > On Thu, Jul 7, 2016 at 3:35 PM, Tanmay Inamdar wrote:
> > >
> > >
> > > On Sat, Jul 2, 2016 at 4:13 PM, Paul Gortmaker
> > >
Hello,
On Mon, Jul 11, 2016 at 02:14:31PM +0300, Topi Miettinen wrote:
> [ 28.443674] audit: type=1327 audit(1468234333.144:520):
> proctitle=6D6B6E6F64002F6465762F7A5F343639006300310032
> [ 28.465888] audit: type=1330 audit(1468234333.144:520):
> cap_used=0800
> [ 28.482080]
Hello,
On Mon, Jul 11, 2016 at 02:14:31PM +0300, Topi Miettinen wrote:
> [ 28.443674] audit: type=1327 audit(1468234333.144:520):
> proctitle=6D6B6E6F64002F6465762F7A5F343639006300310032
> [ 28.465888] audit: type=1330 audit(1468234333.144:520):
> cap_used=0800
> [ 28.482080]
On Mon, Jul 11, 2016 at 3:53 PM, Vignesh R wrote:
>
>
> On Monday 11 July 2016 02:49 PM, prahlad venkata wrote:
>> On Mon, Jul 11, 2016 at 2:45 PM, Vignesh R wrote:
> [...]
> diff --git a/drivers/spi/spi-ti-qspi.c b/drivers/spi/spi-ti-qspi.c
>
On Mon, Jul 11, 2016 at 3:53 PM, Vignesh R wrote:
>
>
> On Monday 11 July 2016 02:49 PM, prahlad venkata wrote:
>> On Mon, Jul 11, 2016 at 2:45 PM, Vignesh R wrote:
> [...]
> diff --git a/drivers/spi/spi-ti-qspi.c b/drivers/spi/spi-ti-qspi.c
> index 29ea8d2..6c61f54 100644
On 07/11/2016 11:36 AM, Jiri Kosina wrote:
On Tue, 5 Jul 2016, Mark Hounschell wrote:
From: Jiri Kosina
Commit 09954bad4 ("floppy: refactor open() flags handling"), as a
side-effect, causes open(/dev/fdX, O_ACCMODE) to fail. It turns out that
this is being used setfdprm
On 07/11/2016 11:36 AM, Jiri Kosina wrote:
On Tue, 5 Jul 2016, Mark Hounschell wrote:
From: Jiri Kosina
Commit 09954bad4 ("floppy: refactor open() flags handling"), as a
side-effect, causes open(/dev/fdX, O_ACCMODE) to fail. It turns out that
this is being used setfdprm userspace for
On 11/07/2016 18:53, r...@redhat.com wrote:
> From: Rik van Riel
>
> Paolo pointed out that irqs are already blocked when irqtime_account_irq
> is called. That means there is no reason to call local_irq_save/restore
> again.
>
> Signed-off-by: Rik van Riel
>
On 11/07/2016 18:53, r...@redhat.com wrote:
> From: Rik van Riel
>
> Paolo pointed out that irqs are already blocked when irqtime_account_irq
> is called. That means there is no reason to call local_irq_save/restore
> again.
>
> Signed-off-by: Rik van Riel
> Suggested-by: Paolo Bonzini
>
On Mon, Jul 11, 2016 at 08:40:58PM +0800, 廖崇榮 wrote:
> > +
> > + error = data->ops->get_sm_version(client, >ic_type,
> > + >sm_version);
> > + if (error)
> > + return false;
>
> That means we'd be fetching product ID and IC type twice when
On Mon, Jul 11, 2016 at 08:40:58PM +0800, 廖崇榮 wrote:
> > +
> > + error = data->ops->get_sm_version(client, >ic_type,
> > + >sm_version);
> > + if (error)
> > + return false;
>
> That means we'd be fetching product ID and IC type twice when
On Mon, Jul 11, 2016 at 11:31:47AM -0400, Stephen Smalley wrote:
[..]
> > +static inline int security_inode_copy_up_xattr(const char *name)
> > +{
> > + -EOPNOTSUPP;
>
> return?
Yes, this one I fixed it in my patches now. kbuild also flagged this.
Vivek
On Mon, Jul 11, 2016 at 11:31:47AM -0400, Stephen Smalley wrote:
[..]
> > +static inline int security_inode_copy_up_xattr(const char *name)
> > +{
> > + -EOPNOTSUPP;
>
> return?
Yes, this one I fixed it in my patches now. kbuild also flagged this.
Vivek
On 07/11/2016 12:07 PM, Coelho, Luciano wrote:
> On Mon, 2016-07-11 at 11:18 -0400, Prarit Bhargava wrote:
>> Didn't get any feedback or review comments on this patch. Resending
>> ...
>>
>> P.
>
> Sorry, this got flooded down my inbox.
NP, Luciano -- My worry was that it hadn't been seen or
On 07/11/2016 12:07 PM, Coelho, Luciano wrote:
> On Mon, 2016-07-11 at 11:18 -0400, Prarit Bhargava wrote:
>> Didn't get any feedback or review comments on this patch. Resending
>> ...
>>
>> P.
>
> Sorry, this got flooded down my inbox.
NP, Luciano -- My worry was that it hadn't been seen or
2016-06-21 21:32 GMT+03:00 Rik van Riel :
> On Tue, 2016-06-21 at 10:13 -0700, Kees Cook wrote:
>> On Tue, Jun 21, 2016 at 9:59 AM, Andy Lutomirski > > wrote:
>> >
>> > I'm tempted to explicitly disallow VM_NO_GUARD in the vmalloc
>> > range.
>> > It has no
2016-06-21 21:32 GMT+03:00 Rik van Riel :
> On Tue, 2016-06-21 at 10:13 -0700, Kees Cook wrote:
>> On Tue, Jun 21, 2016 at 9:59 AM, Andy Lutomirski > > wrote:
>> >
>> > I'm tempted to explicitly disallow VM_NO_GUARD in the vmalloc
>> > range.
>> > It has no in-tree users for non-fixed addresses
On Mon, Jul 11, 2016 at 11:31:47AM -0400, Stephen Smalley wrote:
> On 07/08/2016 12:19 PM, Vivek Goyal wrote:
> > Provide a security hook which is called when xattrs of a file are being
> > copied up. This hook is called once for each xattr and LSM can return 0
> > to access the xattr, 1 to reject
On Mon, Jul 11, 2016 at 11:31:47AM -0400, Stephen Smalley wrote:
> On 07/08/2016 12:19 PM, Vivek Goyal wrote:
> > Provide a security hook which is called when xattrs of a file are being
> > copied up. This hook is called once for each xattr and LSM can return 0
> > to access the xattr, 1 to reject
On Fri, 8 Jul 2016 14:56:12 +0900
Namhyung Kim wrote:
> When a task was migrated to other cpu in the middle of a function, the
> fgraph_exit record will be in a different cpu than the enter record.
> But currently fgraph_ent_handler() only peeks at the same cpu so it
> could
On Fri, 8 Jul 2016 14:56:12 +0900
Namhyung Kim wrote:
> When a task was migrated to other cpu in the middle of a function, the
> fgraph_exit record will be in a different cpu than the enter record.
> But currently fgraph_ent_handler() only peeks at the same cpu so it
> could read an incorrect
From: Rik van Riel
Paolo pointed out that irqs are already blocked when irqtime_account_irq
is called. That means there is no reason to call local_irq_save/restore
again.
Signed-off-by: Rik van Riel
Suggested-by: Paolo Bonzini
---
From: Rik van Riel
Paolo pointed out that irqs are already blocked when irqtime_account_irq
is called. That means there is no reason to call local_irq_save/restore
again.
Signed-off-by: Rik van Riel
Suggested-by: Paolo Bonzini
---
kernel/sched/cputime.c | 4
1 file changed, 4
From: Rik van Riel
The CONFIG_VIRT_CPU_ACCOUNTING_GEN irq time tracking code does not
appear to currently work right.
On CPUs without nohz_full=, only tick based irq time sampling is
done, which breaks down when dealing with a nohz_idle CPU.
On firewalls and similar systems,
From: Rik van Riel
The CONFIG_VIRT_CPU_ACCOUNTING_GEN irq time tracking code does not
appear to currently work right.
On CPUs without nohz_full=, only tick based irq time sampling is
done, which breaks down when dealing with a nohz_idle CPU.
On firewalls and similar systems, no ticks may
Currently irq time accounting only works in these cases:
1) purely ticke based accounting
2) nohz_full accounting, but only on housekeeping & nohz_full CPUs
3) architectures with native vtime accounting
On nohz_idle CPUs, which are probably the majority nowadays,
irq time accounting is currently
Currently irq time accounting only works in these cases:
1) purely ticke based accounting
2) nohz_full accounting, but only on housekeeping & nohz_full CPUs
3) architectures with native vtime accounting
On nohz_idle CPUs, which are probably the majority nowadays,
irq time accounting is currently
On Mon, Jul 11, 2016 at 11:24:26AM -0400, Stephen Smalley wrote:
> On 07/08/2016 12:19 PM, Vivek Goyal wrote:
> > Provide a security hook to label new file correctly when a file is copied
> > up from lower layer to upper layer of a overlay/union mount.
> >
> > This hook can prepare a new set of
On Mon, Jul 11, 2016 at 11:24:26AM -0400, Stephen Smalley wrote:
> On 07/08/2016 12:19 PM, Vivek Goyal wrote:
> > Provide a security hook to label new file correctly when a file is copied
> > up from lower layer to upper layer of a overlay/union mount.
> >
> > This hook can prepare a new set of
From: Rik van Riel
Currently, if there was any irq or softirq time during 'ticks'
jiffies, the entire period will be accounted as irq or softirq
time.
This is inaccurate if only a subset of the time was actually spent
handling irqs, and could conceivably mis-count all of the
From: Rik van Riel
Currently, if there was any irq or softirq time during 'ticks'
jiffies, the entire period will be accounted as irq or softirq
time.
This is inaccurate if only a subset of the time was actually spent
handling irqs, and could conceivably mis-count all of the ticks during
a
Hi,
On Mon, Jul 11, 2016 at 12:02 AM, Thierry Reding
wrote:
> On Sat, Jul 09, 2016 at 11:47:18AM +0200, Mark Brown wrote:
>> On Fri, Jul 08, 2016 at 05:43:02PM +0200, Thierry Reding wrote:
>>
>> > Mark, do you want me to provide a stable branch with the PWM regulator
>>
Hi,
On Mon, Jul 11, 2016 at 12:02 AM, Thierry Reding
wrote:
> On Sat, Jul 09, 2016 at 11:47:18AM +0200, Mark Brown wrote:
>> On Fri, Jul 08, 2016 at 05:43:02PM +0200, Thierry Reding wrote:
>>
>> > Mark, do you want me to provide a stable branch with the PWM regulator
>> > patches and resolve
The Kconfig currently controlling compilation of this code is:
init/Kconfig:config BPF_SYSCALL
init/Kconfig: bool "Enable bpf() system call"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so that
when reading
The Kconfig currently controlling compilation of this code is:
init/Kconfig:config BPF_SYSCALL
init/Kconfig: bool "Enable bpf() system call"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so that
when reading
On 07/08/2016 08:56 AM, Jon Mason wrote:
> Add device tree entries for the ethernet devices present on the
> Broadcom Northstar Plus SoCs
>
> Signed-off-by: Jon Mason
Applied to devicetree/next, with s/bgmac/AMAC/ in the subject, thanks!
--
Florian
On 07/08/2016 08:56 AM, Jon Mason wrote:
> Add device tree entries for the ethernet devices present on the
> Broadcom Northstar Plus SoCs
>
> Signed-off-by: Jon Mason
Applied to devicetree/next, with s/bgmac/AMAC/ in the subject, thanks!
--
Florian
On 07/07/2016 04:08 PM, Jon Mason wrote:
> Signed-off-by: Jon Mason
Applied to devicetree/next, thanks
--
Florian
On 07/07/2016 04:08 PM, Jon Mason wrote:
> Signed-off-by: Jon Mason
Applied to devicetree/next, thanks
--
Florian
Hi,
On Sun, Jul 10, 2016 at 11:56 PM, Stephen Rothwell
wrote:
> Hi Thierry,
>
> Today's linux-next merge of the pwm tree got a conflict in:
>
> drivers/regulator/pwm-regulator.c
>
> between commit:
>
> 830583004e61 ("regulator: pwm: Drop unneeded pwm_enable() call")
>
Hi,
On Sun, Jul 10, 2016 at 11:56 PM, Stephen Rothwell
wrote:
> Hi Thierry,
>
> Today's linux-next merge of the pwm tree got a conflict in:
>
> drivers/regulator/pwm-regulator.c
>
> between commit:
>
> 830583004e61 ("regulator: pwm: Drop unneeded pwm_enable() call")
> 27bfa8893b15
Hi Mark,
On Mon, Jul 11, 2016 at 4:39 AM, Mark Rutland wrote:
> Please add some commit messge text, e.g.
>
> This patch adds a driver for the SoC-wide (AKA uncore) PMU hardware
> found in APM X-Gene SoCs.
>
> On Wed, Jul 06, 2016 at 05:07:24PM -0700, Tai Nguyen wrote:
>>
Hi Mark,
On Mon, Jul 11, 2016 at 4:39 AM, Mark Rutland wrote:
> Please add some commit messge text, e.g.
>
> This patch adds a driver for the SoC-wide (AKA uncore) PMU hardware
> found in APM X-Gene SoCs.
>
> On Wed, Jul 06, 2016 at 05:07:24PM -0700, Tai Nguyen wrote:
>> Signed-off-by: Tai
diff --git a/Makefile b/Makefile
index c62b531d5a85..cd374426114a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 6
-SUBLEVEL = 3
+SUBLEVEL = 4
EXTRAVERSION =
NAME = Charred Weasel
diff --git a/crypto/crypto_user.c b/crypto/crypto_user.c
index
diff --git a/Makefile b/Makefile
index c62b531d5a85..cd374426114a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 6
-SUBLEVEL = 3
+SUBLEVEL = 4
EXTRAVERSION =
NAME = Charred Weasel
diff --git a/crypto/crypto_user.c b/crypto/crypto_user.c
index
diff --git a/Makefile b/Makefile
index fadbb9d73c6d..979088079338 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 14
+SUBLEVEL = 15
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/crypto/crypto_user.c b/crypto/crypto_user.c
index
I'm announcing the release of the 4.6.4 kernel.
All users of the 4.6 kernel series must upgrade.
The updated 4.6.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.6.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.4.15 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.6.4 kernel.
All users of the 4.6 kernel series must upgrade.
The updated 4.6.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.6.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.4.15 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index fadbb9d73c6d..979088079338 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 14
+SUBLEVEL = 15
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/crypto/crypto_user.c b/crypto/crypto_user.c
index
On Mon, Jul 11, 2016 at 9:31 AM, Mark Rutland wrote:
>>
>> So until you do the wire that actually disables preemption you can
>> schedule away as much as you want, and after that write you no longer
>> will.
>
> I was assuming a percpu pointer to current (or preempt count).
On Mon, Jul 11, 2016 at 9:31 AM, Mark Rutland wrote:
>>
>> So until you do the wire that actually disables preemption you can
>> schedule away as much as you want, and after that write you no longer
>> will.
>
> I was assuming a percpu pointer to current (or preempt count).
So for the same
Hi,
Last round of commits for v4.8.
Best regards,
Krzysztof
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
Hi,
Last round of commits for v4.8. On top of previous tag.
Best regards,
Krzysztof
The following changes since commit 1c03274d68f4744afe582fcff1c2e5b1c5c34b5b:
MAINTAINERS: Extend Samsung SoC entry with S3C/S5P drivers (2016-06-23
08:12:08 +0200)
are available in the git repository at:
Hi,
Last round of commits for v4.8. On top of previous tag.
Best regards,
Krzysztof
The following changes since commit 187364b6fcabb9f4bfefcb62fab4fcda019b5810:
cpufreq: s5pv210: use relaxed IO accesors (2016-06-22 14:00:21 +0200)
are available in the git repository at:
Hi,
Last round of commits for v4.8.
Best regards,
Krzysztof
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
Hi,
Last round of commits for v4.8. On top of previous tag.
Best regards,
Krzysztof
The following changes since commit 1c03274d68f4744afe582fcff1c2e5b1c5c34b5b:
MAINTAINERS: Extend Samsung SoC entry with S3C/S5P drivers (2016-06-23
08:12:08 +0200)
are available in the git repository at:
Hi,
Last round of commits for v4.8. On top of previous tag.
Best regards,
Krzysztof
The following changes since commit 187364b6fcabb9f4bfefcb62fab4fcda019b5810:
cpufreq: s5pv210: use relaxed IO accesors (2016-06-22 14:00:21 +0200)
are available in the git repository at:
Hi,
Last round of commits for v4.8.
Best regards,
Krzysztof
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
Hi,
Last round of commits for v4.8.
Best regards,
Krzysztof
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
On Mon, 2016-07-11 at 18:17 +0300, Andrey Utkin wrote:
[]
> diff --git a/drivers/media/pci/tw5864/tw5864-core.c
> b/drivers/media/pci/tw5864/tw5864-core.c
[]
> +static const char * const artifacts_warning =
> +"BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY\n"
> +"\n"
> +"This driver was developed by
On Mon, 2016-07-11 at 18:17 +0300, Andrey Utkin wrote:
[]
> diff --git a/drivers/media/pci/tw5864/tw5864-core.c
> b/drivers/media/pci/tw5864/tw5864-core.c
[]
> +static const char * const artifacts_warning =
> +"BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY\n"
> +"\n"
> +"This driver was developed by
On 07/11/2016 04:44 PM, Abhilash Kesavan wrote:
>>> + /*
>>> >> +* Set clock freeze cycle count to 0 before and after arm clamp
>>> >> or
>>> >> +* reset signal transition
>>> >> +*/
>>> >> + node = of_find_compatible_node(NULL, NULL,
>>> >> +
On Mon, 11 Jul 2016, Lee Jones wrote:
> On Tue, 05 Jul 2016, Olof Johansson wrote:
>
> > On Tue, Jul 5, 2016 at 2:00 PM, Dmitry Torokhov
> > wrote:
> > > On July 5, 2016 1:55:44 PM PDT, Olof Johansson wrote:
> > >>On Tue, Jul 5, 2016 at 1:54 PM, Olof
On 07/11/2016 04:44 PM, Abhilash Kesavan wrote:
>>> + /*
>>> >> +* Set clock freeze cycle count to 0 before and after arm clamp
>>> >> or
>>> >> +* reset signal transition
>>> >> +*/
>>> >> + node = of_find_compatible_node(NULL, NULL,
>>> >> +
On Mon, 11 Jul 2016, Lee Jones wrote:
> On Tue, 05 Jul 2016, Olof Johansson wrote:
>
> > On Tue, Jul 5, 2016 at 2:00 PM, Dmitry Torokhov
> > wrote:
> > > On July 5, 2016 1:55:44 PM PDT, Olof Johansson wrote:
> > >>On Tue, Jul 5, 2016 at 1:54 PM, Olof Johansson wrote:
> > >>> On Fri, Jul 1,
On Tue, 05 Jul 2016, Olof Johansson wrote:
> On Tue, Jul 5, 2016 at 2:00 PM, Dmitry Torokhov
> wrote:
> > On July 5, 2016 1:55:44 PM PDT, Olof Johansson wrote:
> >>On Tue, Jul 5, 2016 at 1:54 PM, Olof Johansson wrote:
> >>> On Fri, Jul
On Tue, 05 Jul 2016, Olof Johansson wrote:
> On Tue, Jul 5, 2016 at 2:00 PM, Dmitry Torokhov
> wrote:
> > On July 5, 2016 1:55:44 PM PDT, Olof Johansson wrote:
> >>On Tue, Jul 5, 2016 at 1:54 PM, Olof Johansson wrote:
> >>> On Fri, Jul 1, 2016 at 2:07 AM, Enric Balletbo i Serra
> >>> wrote:
>
On Mon, Jul 11, 2016 at 09:06:58AM -0700, Linus Torvalds wrote:
> On Jul 11, 2016 7:55 AM, "Andy Lutomirski" <[1]l...@amacapital.net> wrote:
> >
> > How do you intend to find 'current' to get to the preempt count
> > without first disabling preemption?
>
> Actually, that is the classic case of
On Mon, Jul 11, 2016 at 09:06:58AM -0700, Linus Torvalds wrote:
> On Jul 11, 2016 7:55 AM, "Andy Lutomirski" <[1]l...@amacapital.net> wrote:
> >
> > How do you intend to find 'current' to get to the preempt count
> > without first disabling preemption?
>
> Actually, that is the classic case of
On 11/07/16 11:18, Peter Zijlstra wrote:
> On Wed, Jun 22, 2016 at 06:03:17PM +0100, Morten Rasmussen wrote:
>> @@ -6905,11 +6906,19 @@ static int build_sched_domains(const struct cpumask
>> *cpu_map,
>> /* Attach the domains */
>> rcu_read_lock();
>> for_each_cpu(i, cpu_map) {
>>
On 11/07/16 11:18, Peter Zijlstra wrote:
> On Wed, Jun 22, 2016 at 06:03:17PM +0100, Morten Rasmussen wrote:
>> @@ -6905,11 +6906,19 @@ static int build_sched_domains(const struct cpumask
>> *cpu_map,
>> /* Attach the domains */
>> rcu_read_lock();
>> for_each_cpu(i, cpu_map) {
>>
Commit-ID: b8be15d588060a03569ac85dc4a0247460988f5b
Gitweb: http://git.kernel.org/tip/b8be15d588060a03569ac85dc4a0247460988f5b
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:57 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016
Commit-ID: b8be15d588060a03569ac85dc4a0247460988f5b
Gitweb: http://git.kernel.org/tip/b8be15d588060a03569ac85dc4a0247460988f5b
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:57 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016 16:44:01 +0200
x86/fpu/xstate: Re-enable
Commit-ID: 5060b91513b866f774da15dfd82157864c4b1683
Gitweb: http://git.kernel.org/tip/5060b91513b866f774da15dfd82157864c4b1683
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:55 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016
Commit-ID: 35ac2d7ba787eb4b7418a5a6f5919c25e10a780a
Gitweb: http://git.kernel.org/tip/35ac2d7ba787eb4b7418a5a6f5919c25e10a780a
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:56 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016
Commit-ID: 5060b91513b866f774da15dfd82157864c4b1683
Gitweb: http://git.kernel.org/tip/5060b91513b866f774da15dfd82157864c4b1683
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:55 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016 16:44:00 +0200
x86/fpu/xstate: Return NULL
Commit-ID: 35ac2d7ba787eb4b7418a5a6f5919c25e10a780a
Gitweb: http://git.kernel.org/tip/35ac2d7ba787eb4b7418a5a6f5919c25e10a780a
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:56 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016 16:44:00 +0200
x86/fpu/xstate: Fix
Hi Thomas,
On ven., juil. 08 2016, Thomas Petazzoni
wrote:
> Hello,
>
> On Fri, 8 Jul 2016 00:37:46 +0200, Gregory CLEMENT wrote:
>
>> +gpio1: gpio@13800 {
>> +compatible = "marvell,mvebu-gpio-3700", "syscon", "simple-mfd";
>
> I find this compatible
Hi Thomas,
On ven., juil. 08 2016, Thomas Petazzoni
wrote:
> Hello,
>
> On Fri, 8 Jul 2016 00:37:46 +0200, Gregory CLEMENT wrote:
>
>> +gpio1: gpio@13800 {
>> +compatible = "marvell,mvebu-gpio-3700", "syscon", "simple-mfd";
>
> I find this compatible string not very consistent with what
Commit-ID: 1fc2b67b43d5001b92b3a002b94ad0137e99
Gitweb: http://git.kernel.org/tip/1fc2b67b43d5001b92b3a002b94ad0137e99
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:54 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016
Commit-ID: 1fc2b67b43d5001b92b3a002b94ad0137e99
Gitweb: http://git.kernel.org/tip/1fc2b67b43d5001b92b3a002b94ad0137e99
Author: Yu-cheng Yu
AuthorDate: Mon, 11 Jul 2016 09:18:54 -0700
Committer: Ingo Molnar
CommitDate: Mon, 11 Jul 2016 16:43:59 +0200
x86/fpu/xstate: Fix
601 - 700 of 1694 matches
Mail list logo