This patch adds HMAC-SHA3 test modes in tcrypt module
and related test vectors.
Signed-off-by: Raveendra Padasalagi
---
crypto/tcrypt.c | 16 +++
crypto/testmgr.c | 40 ++
crypto/testmgr.h | 388 +++
3
This patch adds HMAC-SHA3 test modes in tcrypt module
and related test vectors.
Signed-off-by: Raveendra Padasalagi
---
crypto/tcrypt.c | 16 +++
crypto/testmgr.c | 40 ++
crypto/testmgr.h | 388 +++
3 files changed, 444 insertions(+)
On Thu, Jun 30, 2016 at 9:39 PM, Dave Hansen wrote:
>
> I think what you suggest will work if we don't consider A/D in
> pte_none(). I think there are a bunch of code path where assume that
> !pte_present() && !pte_none() means swap.
Yeah, we would need to change pte_none() to
On Thu, Jun 30, 2016 at 9:39 PM, Dave Hansen wrote:
>
> I think what you suggest will work if we don't consider A/D in
> pte_none(). I think there are a bunch of code path where assume that
> !pte_present() && !pte_none() means swap.
Yeah, we would need to change pte_none() to mask off D/A, but
On Fri, 1 Jul 2016 02:50:57 +0200
Ondřej Jirman wrote:
> > Since this is really specific, I guess you could simply make the
> > clk_ops for the nkmp clocks public, and just re-implement set_rate
> > using that logic.
>
> I would argue that this may be necessary for other PLL
On Fri, 1 Jul 2016 02:50:57 +0200
Ondřej Jirman wrote:
> > Since this is really specific, I guess you could simply make the
> > clk_ops for the nkmp clocks public, and just re-implement set_rate
> > using that logic.
>
> I would argue that this may be necessary for other PLL clocks too, if
>
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
fs/ext4/fsync.c
between commit:
78d962510796 ("ext4: respect the nobarrier mount option in nojournal mode")
from the ext4 tree and commit:
045d9e206ac0 ("fs/ext4/fsync.c: generic_file_fsync call based on
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
fs/ext4/fsync.c
between commit:
78d962510796 ("ext4: respect the nobarrier mount option in nojournal mode")
from the ext4 tree and commit:
045d9e206ac0 ("fs/ext4/fsync.c: generic_file_fsync call based on
Hi all,
After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/fadump.c: In function 'fadump_invalidate_dump':
arch/powerpc/kernel/fadump.c:1014:2: error: expected ';' before '}' token
}
^
Caused by commit
4a03749f140c
Hi Gavin,
On 2016/7/1 8:39, Gavin Shan wrote:
On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote:
VF BARs are read-only zeroes according to SRIOV spec,
the normal way(writing BARs) of allocating resources wouldn't
be applied to VFs. The VFs' resources would be allocated
when we enable
Hi Gavin,
On 2016/7/1 8:39, Gavin Shan wrote:
On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote:
VF BARs are read-only zeroes according to SRIOV spec,
the normal way(writing BARs) of allocating resources wouldn't
be applied to VFs. The VFs' resources would be allocated
when we enable
Hi all,
After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/fadump.c: In function 'fadump_invalidate_dump':
arch/powerpc/kernel/fadump.c:1014:2: error: expected ';' before '}' token
}
^
Caused by commit
4a03749f140c
On Fri, 2016-07-01 at 11:06 +0800, Ding Tianhong wrote:
> I debug this problem, and found that the __fib6_clean_all() would not
> hold the cpu more than 1 second event though there
> is a lot of ipv6 address to deal with, but the notifier_chian would
> call the ipv6 notifier several times and
On Fri, 2016-07-01 at 11:06 +0800, Ding Tianhong wrote:
> I debug this problem, and found that the __fib6_clean_all() would not
> hold the cpu more than 1 second event though there
> is a lot of ipv6 address to deal with, but the notifier_chian would
> call the ipv6 notifier several times and
Enable perf to build on libc implementations where sysconf() doesn't
support _SC_LEVEL1_DCACHE_LINESIZE as a parameter.
For example, the Bionic implementation does not support this as a
paremter. Older versions of Bionic will throw an error when this is passed
in as a parameter, and more recent
This enables the workaround for compilers that generate warnings when
compiling libapi.
Signed-off-by: Chris Phlipot
---
tools/lib/api/Makefile | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/lib/api/Makefile b/tools/lib/api/Makefile
index
Enable perf to build on libc implementations where sysconf() doesn't
support _SC_LEVEL1_DCACHE_LINESIZE as a parameter.
For example, the Bionic implementation does not support this as a
paremter. Older versions of Bionic will throw an error when this is passed
in as a parameter, and more recent
This enables the workaround for compilers that generate warnings when
compiling libapi.
Signed-off-by: Chris Phlipot
---
tools/lib/api/Makefile | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/lib/api/Makefile b/tools/lib/api/Makefile
index 67ff93e..c7ceea6
this enables the workaround for compilers that generate warnings when
compiling libsubcmd.
Signed-off-by: Chris Phlipot
---
tools/lib/subcmd/Makefile | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/lib/subcmd/Makefile
this enables the workaround for compilers that generate warnings when
compiling libsubcmd.
Signed-off-by: Chris Phlipot
---
tools/lib/subcmd/Makefile | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/lib/subcmd/Makefile b/tools/lib/subcmd/Makefile
index
It looks like the tools/perf/Documentation/android.txt hasn't been updated
in a while. Following the instructions in this document to cross-compile
perf for Android results in several build errors.
This patch-set aims to fix/workaround the incompatibilities introduced
since the android perf build
It looks like the tools/perf/Documentation/android.txt hasn't been updated
in a while. Following the instructions in this document to cross-compile
perf for Android results in several build errors.
This patch-set aims to fix/workaround the incompatibilities introduced
since the android perf build
Update the android build documentation according to recent android build
fixes. The instructions for step 1a and step 2 were updated to work with
NDK version 11(oldest supported version) and NDK version 12(current
version).
Signed-off-by: Chris Phlipot
---
Update the android build documentation according to recent android build
fixes. The instructions for step 1a and step 2 were updated to work with
NDK version 11(oldest supported version) and NDK version 12(current
version).
Signed-off-by: Chris Phlipot
---
tools/perf/Documentation/android.txt |
Hi,
I'm not sure whether there is any demand for kexec_file_load
support on arm64, but anyhow I'm working on this and now
my early prototype code does work fine.
There is, however, one essential issue:
While arm64 kernel requires a device tree blob to be set up
correctly at boot time, the
Hi,
I'm not sure whether there is any demand for kexec_file_load
support on arm64, but anyhow I'm working on this and now
my early prototype code does work fine.
There is, however, one essential issue:
While arm64 kernel requires a device tree blob to be set up
correctly at boot time, the
Hi Al,
Please pull the most recent version of the patch series
[PATCH v3 00/24] Delete CURRENT_TIME_SEC and replace current_fs_time()
https://lkml.org/lkml/2016/6/29/648
This is rebased onto v4.7-rc5.
These patches are in preparation to transition vfs timestamps to use
Hi Al,
Please pull the most recent version of the patch series
[PATCH v3 00/24] Delete CURRENT_TIME_SEC and replace current_fs_time()
https://lkml.org/lkml/2016/6/29/648
This is rebased onto v4.7-rc5.
These patches are in preparation to transition vfs timestamps to use
Hi Gavin,
On 2016/7/1 8:28, Gavin Shan wrote:
On Thu, Jun 30, 2016 at 06:53:07PM +0800, Yongji Xie wrote:
PCI resources allocator will use firmware setup and not try to
reassign resource when PCI_PROBE_ONLY or IORESOURCE_PCI_FIXED
is set.
The enforced alignment in
Hi Gavin,
On 2016/7/1 8:28, Gavin Shan wrote:
On Thu, Jun 30, 2016 at 06:53:07PM +0800, Yongji Xie wrote:
PCI resources allocator will use firmware setup and not try to
reassign resource when PCI_PROBE_ONLY or IORESOURCE_PCI_FIXED
is set.
The enforced alignment in
On 07/01/16 at 12:06pm, Baoquan He wrote:
> On 06/30/16 at 05:24pm, Yinghai Lu wrote:
> > On Wed, Jun 29, 2016 at 11:58 PM, Ye Xiaolong wrote:
> > > On Wed, Jun 29, 2016 at 09:49:12PM -0700, Yinghai Lu wrote:
> > >>On Wed, Jun 29, 2016 at 1:29 PM, Huang, Ying
On 07/01/16 at 12:06pm, Baoquan He wrote:
> On 06/30/16 at 05:24pm, Yinghai Lu wrote:
> > On Wed, Jun 29, 2016 at 11:58 PM, Ye Xiaolong wrote:
> > > On Wed, Jun 29, 2016 at 09:49:12PM -0700, Yinghai Lu wrote:
> > >>On Wed, Jun 29, 2016 at 1:29 PM, Huang, Ying wrote:
> > >>> If you could provide
Hi,
On Thu, Jun 30, 2016 at 12:12 AM, Geert Uytterhoeven
wrote:
> CC devicetree
>
> On Thu, Jun 30, 2016 at 5:54 AM, wrote:
>> From: Andrey Pronin
>>
>> Some devices may need CS to be deasserted for some time
>> between
Hi,
On Thu, Jun 30, 2016 at 12:12 AM, Geert Uytterhoeven
wrote:
> CC devicetree
>
> On Thu, Jun 30, 2016 at 5:54 AM, wrote:
>> From: Andrey Pronin
>>
>> Some devices may need CS to be deasserted for some time
>> between transactions. Added a new capability to guarantee
>> a delay between SPI
On 06/30/2016 07:55 PM, Linus Torvalds wrote:
> On Thu, Jun 30, 2016 at 5:12 PM, Dave Hansen wrote:
>> From: Dave Hansen
>> The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights
>> Landing) has an erratum where a processor thread setting
On 06/30/2016 07:55 PM, Linus Torvalds wrote:
> On Thu, Jun 30, 2016 at 5:12 PM, Dave Hansen wrote:
>> From: Dave Hansen
>> The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights
>> Landing) has an erratum where a processor thread setting the Accessed
>> or Dirty bits may not do so
Hi,
On Wed, Jun 29, 2016 at 8:54 PM, wrote:
> From: Andrey Pronin
>
> Some devices may need CS to be deasserted for some time
> between transactions. Added a new capability to guarantee
> a delay between SPI transactions for the device.
>
>
Hi,
On Wed, Jun 29, 2016 at 8:54 PM, wrote:
> From: Andrey Pronin
>
> Some devices may need CS to be deasserted for some time
> between transactions. Added a new capability to guarantee
> a delay between SPI transactions for the device.
>
> Signed-off-by: Andrey Pronin
> ---
>
在 16/7/1 上午9:51, wangyijing 写道:
> Hi Coly, thanks to your review and comments.
>
> Commit 77b5a08427e875 ("bcache: don't embed 'return' statements in closure
> macros")
> remove the return in continue_at(), so I think we should update the document
> info
> about continue_at().
>
> Thanks!
>
在 16/7/1 上午9:51, wangyijing 写道:
> Hi Coly, thanks to your review and comments.
>
> Commit 77b5a08427e875 ("bcache: don't embed 'return' statements in closure
> macros")
> remove the return in continue_at(), so I think we should update the document
> info
> about continue_at().
>
> Thanks!
>
From: Elaine Zhang
In order to meet low power requirements, a power management unit (PMU) is
designed for controlling power resources in RK3399. The RK3399 PMU is
dedicated for managing the power of the whole chip.
1. add pd node for RK3399 Soc
2. create power domain
From: Elaine Zhang
In order to meet low power requirements, a power management unit (PMU) is
designed for controlling power resources in RK3399. The RK3399 PMU is
dedicated for managing the power of the whole chip.
1. add pd node for RK3399 Soc
2. create power domain tree
3. add qos node for
> -Original Message-
> From: Markus Mayer [mailto:markus.ma...@broadcom.com]
> Sent: Thursday, June 30, 2016 9:13 PM
> To: Moore, Robert
> Cc: Zheng, Lv; Wysocki, Rafael J; Len Brown; linux-a...@vger.kernel.org;
> de...@acpica.org; linux-kernel@vger.kernel.org; Box, David E
> Subject:
Hi,
On Thu, Jun 30, 2016 at 12:12 AM, Geert Uytterhoeven
wrote:
> CC devicetree
And Rob and Mark...
./scripts/get_maintainer.pl -f
Documentation/devicetree/bindings/spi/spi-bus.txt
Mark Brown (maintainer:SPI SUBSYSTEM)
Rob Herring
> -Original Message-
> From: Markus Mayer [mailto:markus.ma...@broadcom.com]
> Sent: Thursday, June 30, 2016 9:13 PM
> To: Moore, Robert
> Cc: Zheng, Lv; Wysocki, Rafael J; Len Brown; linux-a...@vger.kernel.org;
> de...@acpica.org; linux-kernel@vger.kernel.org; Box, David E
> Subject:
Hi,
On Thu, Jun 30, 2016 at 12:12 AM, Geert Uytterhoeven
wrote:
> CC devicetree
And Rob and Mark...
./scripts/get_maintainer.pl -f
Documentation/devicetree/bindings/spi/spi-bus.txt
Mark Brown (maintainer:SPI SUBSYSTEM)
Rob Herring (maintainer:OPEN FIRMWARE AND
FLATTENED DEVICE TREE
Andrey,
On Wed, Jun 29, 2016 at 8:54 PM, wrote:
> From: Andrey Pronin
>
> Some SPI devices may go to sleep after a period of inactivity
> on SPI. For such devices, if enough time has passed since the
> last SPI transaction, toggle CS and wait for the
Andrey,
On Wed, Jun 29, 2016 at 8:54 PM, wrote:
> From: Andrey Pronin
>
> Some SPI devices may go to sleep after a period of inactivity
> on SPI. For such devices, if enough time has passed since the
> last SPI transaction, toggle CS and wait for the device to
> start before communicating with
On Wed, Jun 29, 2016 at 09:52:31AM +0900, Namhyung Kim wrote:
> Hi Steve,
>
> On Tue, Jun 28, 2016 at 09:57:27AM -0400, Steven Rostedt wrote:
> > On Tue, 28 Jun 2016 15:33:18 +0900
> > Namhyung Kim wrote:
> >
> > > Send again to correct addresses, sorry!
> > >
> > > On
On Wed, Jun 29, 2016 at 09:52:31AM +0900, Namhyung Kim wrote:
> Hi Steve,
>
> On Tue, Jun 28, 2016 at 09:57:27AM -0400, Steven Rostedt wrote:
> > On Tue, 28 Jun 2016 15:33:18 +0900
> > Namhyung Kim wrote:
> >
> > > Send again to correct addresses, sorry!
> > >
> > > On Tue, Jun 28, 2016 at
在 16/7/1 上午10:09, wangyijing 写道:
>
>
> 在 2016/6/29 18:20, Coly Li 写道:
>> 在 16/6/22 上午10:10, Yijing Wang 写道:
>>> Cache_sb is not used in cache_alloc, and we have copied
>>> sb info to cache->sb already, remove it.
>>>
>>> Signed-off-by: Yijing Wang
>>> ---
>>>
在 16/7/1 上午10:09, wangyijing 写道:
>
>
> 在 2016/6/29 18:20, Coly Li 写道:
>> 在 16/6/22 上午10:10, Yijing Wang 写道:
>>> Cache_sb is not used in cache_alloc, and we have copied
>>> sb info to cache->sb already, remove it.
>>>
>>> Signed-off-by: Yijing Wang
>>> ---
>>> drivers/md/bcache/super.c |4
Crossrelease feature introduces new concept and data structure. Thus a
document helping understand it is necessary. So added it.
Signed-off-by: Byungchul Park
---
Documentation/locking/crossrelease.txt | 276 +
1 file changed, 276
Crossrelease feature introduces new concept and data structure. Thus a
document helping understand it is necessary. So added it.
Signed-off-by: Byungchul Park
---
Documentation/locking/crossrelease.txt | 276 +
1 file changed, 276 insertions(+)
create mode
On 30 June 2016 at 19:59, Moore, Robert wrote:
> This is linux-specific code, ACPICA is os-independent. So we cannot accept
> such patch.
Understood. I wasn't aware that this was shared code.
> From: Markus Mayer [mailto:markus.ma...@broadcom.com]
> Sent: Thursday, June
On 30 June 2016 at 19:59, Moore, Robert wrote:
> This is linux-specific code, ACPICA is os-independent. So we cannot accept
> such patch.
Understood. I wasn't aware that this was shared code.
> From: Markus Mayer [mailto:markus.ma...@broadcom.com]
> Sent: Thursday, June 30, 2016 7:50 PM
> To:
On 06/30/16 at 05:24pm, Yinghai Lu wrote:
> On Wed, Jun 29, 2016 at 11:58 PM, Ye Xiaolong wrote:
> > On Wed, Jun 29, 2016 at 09:49:12PM -0700, Yinghai Lu wrote:
> >>On Wed, Jun 29, 2016 at 1:29 PM, Huang, Ying wrote:
> >>> If you could provide a git
On 06/30/16 at 05:24pm, Yinghai Lu wrote:
> On Wed, Jun 29, 2016 at 11:58 PM, Ye Xiaolong wrote:
> > On Wed, Jun 29, 2016 at 09:49:12PM -0700, Yinghai Lu wrote:
> >>On Wed, Jun 29, 2016 at 1:29 PM, Huang, Ying wrote:
> >>> If you could provide a git branch for that, that will be easier for us
>
Hi Steve,
On Tue, Jun 28, 2016 at 09:26:52PM -0400, Steven Rostedt wrote:
> On Wed, 29 Jun 2016 09:57:41 +0900
> Minchan Kim wrote:
>
> > Hello,
> >
> > On Tue, Jun 28, 2016 at 06:46:34PM +0200, Rabin Vincent wrote:
> > > On Tue, Jun 28, 2016 at 03:33:18PM +0900, Namhyung
Hi Steve,
On Tue, Jun 28, 2016 at 09:26:52PM -0400, Steven Rostedt wrote:
> On Wed, 29 Jun 2016 09:57:41 +0900
> Minchan Kim wrote:
>
> > Hello,
> >
> > On Tue, Jun 28, 2016 at 06:46:34PM +0200, Rabin Vincent wrote:
> > > On Tue, Jun 28, 2016 at 03:33:18PM +0900, Namhyung Kim wrote:
> > > >
This patch fix some spelling typo found in
Documentation/x86.
Signed-off-by: Masanari Iida
---
Documentation/x86/intel_mpx.txt | 6 +++---
Documentation/x86/tlb.txt | 4 ++--
Documentation/x86/x86_64/machinecheck | 2 +-
3 files changed, 6 insertions(+),
This patch fix some spelling typo found in
Documentation/x86.
Signed-off-by: Masanari Iida
---
Documentation/x86/intel_mpx.txt | 6 +++---
Documentation/x86/tlb.txt | 4 ++--
Documentation/x86/x86_64/machinecheck | 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff
On Thu, Jun 30, 2016 at 06:53:10PM +0800, Yongji Xie wrote:
>When using resource_alignment kernel parameter, the current
>implement reassigns the alignment by changing resources' size
>which can potentially break some drivers. For example, the driver
>uses the size to locate some register whose
On Thu, Jun 30, 2016 at 06:53:10PM +0800, Yongji Xie wrote:
>When using resource_alignment kernel parameter, the current
>implement reassigns the alignment by changing resources' size
>which can potentially break some drivers. For example, the driver
>uses the size to locate some register whose
The second parameter of smp_cond_load_acquire() should be !p->on_cpu
cause remote wakeup need to ensure that: if the task is running on
prev cpu, it should be descheduled before doing the actual wakeup.
Signed-off-by: T.Zhou
---
kernel/sched/core.c | 2 +-
1 file changed, 1
The second parameter of smp_cond_load_acquire() should be !p->on_cpu
cause remote wakeup need to ensure that: if the task is running on
prev cpu, it should be descheduled before doing the actual wakeup.
Signed-off-by: T.Zhou
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1
On Thu, Jun 30, 2016 at 01:30:54PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-06-29 18:39:01)
> > On Wed, Jun 29, 2016 at 05:43:30PM -0700, Stephen Boyd wrote:
> > > Quoting Peter Chen (2016-06-28 23:46:00)
> > > > On Sun, Jun 26, 2016 at 12:28:29AM -0700, Stephen Boyd wrote:
> > > > >
On Thu, Jun 30, 2016 at 01:30:54PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-06-29 18:39:01)
> > On Wed, Jun 29, 2016 at 05:43:30PM -0700, Stephen Boyd wrote:
> > > Quoting Peter Chen (2016-06-28 23:46:00)
> > > > On Sun, Jun 26, 2016 at 12:28:29AM -0700, Stephen Boyd wrote:
> > > > >
If freezable workqueue aborts suspend flow, show
workqueue state for debug purpose.
Signed-off-by: Roger Lu
---
Changes in v2:
- remove prints in show_workqueue_state().
---
kernel/power/process.c | 3 +++
kernel/workqueue.c | 4 ++--
2 files changed, 5 insertions(+),
If freezable workqueue aborts suspend flow, show
workqueue state for debug purpose.
Signed-off-by: Roger Lu
---
Changes in v2:
- remove prints in show_workqueue_state().
---
kernel/power/process.c | 3 +++
kernel/workqueue.c | 4 ++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff
On Thu, Jun 30, 2016 at 02:47:10PM +0200, Arnd Bergmann wrote:
> When building this driver on arm64, we get a harmless type
> mismatch warning:
>
> drivers/dma/bcm2835-dma.c: In function 'bcm2835_dma_fill_cb_chain_with_sg':
> include/linux/kernel.h:743:17: warning: comparison of distinct pointer
On Thu, Jun 30, 2016 at 02:47:10PM +0200, Arnd Bergmann wrote:
> When building this driver on arm64, we get a harmless type
> mismatch warning:
>
> drivers/dma/bcm2835-dma.c: In function 'bcm2835_dma_fill_cb_chain_with_sg':
> include/linux/kernel.h:743:17: warning: comparison of distinct pointer
On 2016/6/28 14:27, Eric Dumazet wrote:
> On Tue, 2016-06-28 at 08:22 +0200, Eric Dumazet wrote:
>
>> Follow the stack trace and add another cond_resched() where it is needed
>> then ?
>>
>> Lot of this code was written decade ago where nobody expected a root
>> user was going to try hard to
On Thu, Jun 30, 2016 at 10:55 PM, Linus Torvalds
wrote:
> On Thu, Jun 30, 2016 at 5:12 PM, Dave Hansen wrote:
>>
>> From: Dave Hansen
>>
>> The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights
>> Landing)
On 2016/6/28 14:27, Eric Dumazet wrote:
> On Tue, 2016-06-28 at 08:22 +0200, Eric Dumazet wrote:
>
>> Follow the stack trace and add another cond_resched() where it is needed
>> then ?
>>
>> Lot of this code was written decade ago where nobody expected a root
>> user was going to try hard to
On Thu, Jun 30, 2016 at 10:55 PM, Linus Torvalds
wrote:
> On Thu, Jun 30, 2016 at 5:12 PM, Dave Hansen wrote:
>>
>> From: Dave Hansen
>>
>> The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights
>> Landing) has an erratum where a processor thread setting the Accessed
>> or Dirty
On Thu, Jun 30, 2016 at 06:59:13PM -0400, Jon Mason wrote:
> Signed-off-by: Jon Mason
> ---
> .../devicetree/bindings/net/brcm,bgmac-nsp.txt | 24
> ++
> 1 file changed, 24 insertions(+)
> create mode 100644
On Thu, Jun 30, 2016 at 5:12 PM, Dave Hansen wrote:
>
> From: Dave Hansen
>
> The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights
> Landing) has an erratum where a processor thread setting the Accessed
> or Dirty bits may not do so
On Thu, Jun 30, 2016 at 06:59:13PM -0400, Jon Mason wrote:
> Signed-off-by: Jon Mason
> ---
> .../devicetree/bindings/net/brcm,bgmac-nsp.txt | 24
> ++
> 1 file changed, 24 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/brcm,bgmac-nsp.txt
>
>
On Thu, Jun 30, 2016 at 5:12 PM, Dave Hansen wrote:
>
> From: Dave Hansen
>
> The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights
> Landing) has an erratum where a processor thread setting the Accessed
> or Dirty bits may not do so atomically against its checks for the
> Present
On Thu, Jun 30, 2016 at 07:12:55PM +0800, William Wu wrote:
> Add a quirk to clear the GUSB3PIPECTL.DELAYP1TRANS bit,
> which specifies whether disable delay PHY power change
> from P0 to P1/P2/P3 when link state changing from U0
> to U1/U2/U3 respectively.
>
> Signed-off-by: William Wu
On Thu, Jun 30, 2016 at 07:12:55PM +0800, William Wu wrote:
> Add a quirk to clear the GUSB3PIPECTL.DELAYP1TRANS bit,
> which specifies whether disable delay PHY power change
> from P0 to P1/P2/P3 when link state changing from U0
> to U1/U2/U3 respectively.
>
> Signed-off-by: William Wu
> ---
>
Dear Rob,
On 07/01/2016 10:38 AM, Rob Herring wrote:
On Thu, Jun 30, 2016 at 07:12:55PM +0800, William Wu wrote:
Add a quirk to clear the GUSB3PIPECTL.DELAYP1TRANS bit,
which specifies whether disable delay PHY power change
from P0 to P1/P2/P3 when link state changing from U0
to U1/U2/U3
Dear Rob,
On 07/01/2016 10:38 AM, Rob Herring wrote:
On Thu, Jun 30, 2016 at 07:12:55PM +0800, William Wu wrote:
Add a quirk to clear the GUSB3PIPECTL.DELAYP1TRANS bit,
which specifies whether disable delay PHY power change
from P0 to P1/P2/P3 when link state changing from U0
to U1/U2/U3
On Thu, Jun 30, 2016 at 05:50:30PM +0100, Kieran Bingham wrote:
> The FDP1 is a de-interlacing module which converts interlaced video to
> progressive video. It is also capable of performing pixel format conversion
> between YCbCr/YUV formats and RGB formats.
>
> Reviewed-by: Laurent Pinchart
On Thu, Jun 30, 2016 at 05:50:30PM +0100, Kieran Bingham wrote:
> The FDP1 is a de-interlacing module which converts interlaced video to
> progressive video. It is also capable of performing pixel format conversion
> between YCbCr/YUV formats and RGB formats.
>
> Reviewed-by: Laurent Pinchart
>
On Thu, Jun 30, 2016 at 05:50:29PM +0100, Kieran Bingham wrote:
> The power domain must be specified to bring the device out of module
> standby. Document this in the bindings provided, so that new additions
> are not missed.
>
> Signed-off-by: Kieran Bingham
> ---
>
Dear Rob,
On 07/01/2016 10:32 AM, Rob Herring wrote:
On Thu, Jun 30, 2016 at 07:12:53PM +0800, William Wu wrote:
Add a quirk to clear the GUSB2PHYCFG.U2_FREECLK_EXISTS bit,
which specifies whether the USB2.0 PHY provides a free-running
PHY clock, which is active when the clock control input is
On Thu, 2016-06-30 at 20:55 +0800, Garlic Tseng wrote:
> On Wed, 2016-06-29 at 20:15 +0100, Mark Brown wrote:
> > On Fri, Jun 17, 2016 at 03:43:58PM +0800, Garlic Tseng wrote:
> > > Add supports for 16k (wideband BT) and add a general compatible
> > > string "linux,bt-sco"
> >
> > This will claim
On Thu, Jun 30, 2016 at 05:50:29PM +0100, Kieran Bingham wrote:
> The power domain must be specified to bring the device out of module
> standby. Document this in the bindings provided, so that new additions
> are not missed.
>
> Signed-off-by: Kieran Bingham
> ---
>
Dear Rob,
On 07/01/2016 10:32 AM, Rob Herring wrote:
On Thu, Jun 30, 2016 at 07:12:53PM +0800, William Wu wrote:
Add a quirk to clear the GUSB2PHYCFG.U2_FREECLK_EXISTS bit,
which specifies whether the USB2.0 PHY provides a free-running
PHY clock, which is active when the clock control input is
On Thu, 2016-06-30 at 20:55 +0800, Garlic Tseng wrote:
> On Wed, 2016-06-29 at 20:15 +0100, Mark Brown wrote:
> > On Fri, Jun 17, 2016 at 03:43:58PM +0800, Garlic Tseng wrote:
> > > Add supports for 16k (wideband BT) and add a general compatible
> > > string "linux,bt-sco"
> >
> > This will claim
On Thu, Jun 30, 2016 at 11:58:45PM +0800, Chen-Yu Tsai wrote:
> Signed-off-by: Chen-Yu Tsai
> ---
> Changes since v3:
>
> - Fixed device node names and added labels.
> - Added clock output from codec and input to rtc.
>
> Changes since v2:
>
> - Fix interrupt line for
On Thu, Jun 30, 2016 at 11:58:45PM +0800, Chen-Yu Tsai wrote:
> Signed-off-by: Chen-Yu Tsai
> ---
> Changes since v3:
>
> - Fixed device node names and added labels.
> - Added clock output from codec and input to rtc.
>
> Changes since v2:
>
> - Fix interrupt line for ac100_codec in
On Thu, Jun 30, 2016 at 10:50:44AM +0200, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers GPF in get_task_ioprio if run in a parallel
> loop:
Dmitry,
Could you please try the below?
diff --git a/block/ioprio.c b/block/ioprio.c
index cc7800e9eb44..01b8116298a1 100644
---
On Thu, Jun 30, 2016 at 10:50:44AM +0200, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers GPF in get_task_ioprio if run in a parallel
> loop:
Dmitry,
Could you please try the below?
diff --git a/block/ioprio.c b/block/ioprio.c
index cc7800e9eb44..01b8116298a1 100644
---
On Thu, Jun 30, 2016 at 8:56 PM, Alexander Shishkin
wrote:
> There's a kerneldoc comment that'd been derived from another one by way
> of copying-and-pasting but hadn't been subsequently amended to replect
^
On Thu, Jun 30, 2016 at 8:56 PM, Alexander Shishkin
wrote:
> There's a kerneldoc comment that'd been derived from another one by way
> of copying-and-pasting but hadn't been subsequently amended to replect
^
s/replect/reflect/ ?
> the purpose of the
On Thu, Jun 30, 2016 at 07:12:54PM +0800, William Wu wrote:
> Add a quirk to configure the core to support the
> UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
> interface is hardware property, and it's platform
> dependent. Normall, the PHYIf can be configured
> during coreconsultant. But
On Thu, Jun 30, 2016 at 07:12:54PM +0800, William Wu wrote:
> Add a quirk to configure the core to support the
> UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
> interface is hardware property, and it's platform
> dependent. Normall, the PHYIf can be configured
> during coreconsultant. But
1 - 100 of 1638 matches
Mail list logo