On Wed, Mar 16, 2016 at 5:33 PM, Eric Sandeen wrote:
> I may have lost the thread at this point, with poor Darrick's original
> patch submission devolving into a long thread about a NO_HIDE_STALE patch
> used at Google, but I don't *think* Ceph ever asked for NO_HIDE_STALE.
>
> At least I can't
Hi Jitao,
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.5 next-20160316]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
Hi,
can you try this:
diff --git a/sound/soc/codecs/tpa6130a2.c b/sound/soc/codecs/tpa6130a2.c
index 11d85c5c787a..7f5881bff5d9 100644
--- a/sound/soc/codecs/tpa6130a2.c
+++ b/sound/soc/codecs/tpa6130a2.c
@@ -386,6 +386,8 @@ static int tpa6130a2_probe(struct i2c_client *client,
Hi,
can you try this:
diff --git a/sound/soc/codecs/tpa6130a2.c b/sound/soc/codecs/tpa6130a2.c
index 11d85c5c787a..7f5881bff5d9 100644
--- a/sound/soc/codecs/tpa6130a2.c
+++ b/sound/soc/codecs/tpa6130a2.c
@@ -386,6 +386,8 @@ static int tpa6130a2_probe(struct i2c_client *client,
On Wed, Mar 16, 2016 at 03:59:18PM +0100, Rafael J. Wysocki wrote:
> +static unsigned int get_next_freq(struct cpufreq_policy *policy,
> + unsigned long util, unsigned long max)
> +{
> + unsigned int freq = arch_scale_freq_invariant() ?
> +
On Wed, Mar 16, 2016 at 03:59:18PM +0100, Rafael J. Wysocki wrote:
> +static unsigned int get_next_freq(struct cpufreq_policy *policy,
> + unsigned long util, unsigned long max)
> +{
> + unsigned int freq = arch_scale_freq_invariant() ?
> +
On 3/10/2016 11:14 AM, John Youn wrote:
> On 3/9/2016 11:06 AM, Doug Anderson wrote:
>> Stefan,
>>
>> On Wed, Mar 9, 2016 at 11:01 AM, Stefan Wahren
>> wrote:
>>>
Doug Anderson hat am 7. März 2016 um 22:30
geschrieben:
On Thu, Mar 17, 2016 at 03:46:35PM +, Olu Ogunbowale wrote:
> On Thu, Mar 17, 2016 at 03:37:16PM +0100, Jerome Glisse wrote:
> > What other driver do for non-buffer region is have the userspace side
> > of the device driver mmap the device driver file and use vma range you
> > get from that
On 03/09/2016 04:18 AM, Yangbo Lu wrote:
> +#ifdef CONFIG_FSL_GUTS
> +u32 fsl_guts_get_svr(void);
> +int fsl_guts_init(void);
> +#endif
Don't ifdef prototypes (when not providing a stub alternative).
-Scott
On 3/10/2016 11:14 AM, John Youn wrote:
> On 3/9/2016 11:06 AM, Doug Anderson wrote:
>> Stefan,
>>
>> On Wed, Mar 9, 2016 at 11:01 AM, Stefan Wahren
>> wrote:
>>>
Doug Anderson hat am 7. März 2016 um 22:30
geschrieben:
Stefan,
On Mon, Mar 7, 2016 at 10:40 AM,
On Thu, Mar 17, 2016 at 03:46:35PM +, Olu Ogunbowale wrote:
> On Thu, Mar 17, 2016 at 03:37:16PM +0100, Jerome Glisse wrote:
> > What other driver do for non-buffer region is have the userspace side
> > of the device driver mmap the device driver file and use vma range you
> > get from that
On 03/09/2016 04:18 AM, Yangbo Lu wrote:
> +#ifdef CONFIG_FSL_GUTS
> +u32 fsl_guts_get_svr(void);
> +int fsl_guts_init(void);
> +#endif
Don't ifdef prototypes (when not providing a stub alternative).
-Scott
On 03/17/2016 10:24 AM, Hanjun Guo wrote:
On 2016/3/17 14:54, Joonsoo Kim wrote:
On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote:
On 2016/3/14 15:18, Joonsoo Kim wrote:
On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote:
On 03/14/2016 07:49 AM, Joonsoo Kim wrote:
On
Hi! We found out that tpa6130a2 device is being initialized before i2c_2
bus is initialized. So that is reason why tpa6130a2 fails...
Any idea why kernel first try to initialize one i2c device even before
bus itself is initialized?
On Monday 14 March 2016 11:59:13 Peter Ujfalusi wrote:
> Does
On 03/17/2016 10:24 AM, Hanjun Guo wrote:
On 2016/3/17 14:54, Joonsoo Kim wrote:
On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote:
On 2016/3/14 15:18, Joonsoo Kim wrote:
On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote:
On 03/14/2016 07:49 AM, Joonsoo Kim wrote:
On
Hi! We found out that tpa6130a2 device is being initialized before i2c_2
bus is initialized. So that is reason why tpa6130a2 fails...
Any idea why kernel first try to initialize one i2c device even before
bus itself is initialized?
On Monday 14 March 2016 11:59:13 Peter Ujfalusi wrote:
> Does
Hi Linus,
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi.git
tags/hsi-for-4.6
for you to fetch changes up to
Hi Linus,
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi.git
tags/hsi-for-4.6
for you to fetch changes up to
v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let
me know.
---8<
From: "Michael S. Tsirkin"
commit 8160c4e455820d5008a1116d2dca35f0363bb062 upstream.
Calling return copy_to_user(...) in
v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let
me know.
---8<
From: "Michael S. Tsirkin"
commit 8160c4e455820d5008a1116d2dca35f0363bb062 upstream.
Calling return copy_to_user(...) in an ioctl will not
This is a patch to the rtllib_softmac.c file that fixes up all instances of
the 'line over 80 characters' warnings found by the checkpatch.pl tool.
Signed-off-by: Yousof El-Sayed
---
drivers/staging/rtl8192e/rtllib_softmac.c | 35
From: "Aneesh Kumar K.V"
This feature flag selects richacl instead of POSIX ACL support on the
filesystem. When this feature is off, the "acl" and "noacl" mount options
control whether POSIX ACLs are enabled. When it is on, richacls are
automatically enabled
This is a patch to the rtllib_softmac.c file that fixes up all instances of
the 'line over 80 characters' warnings found by the checkpatch.pl tool.
Signed-off-by: Yousof El-Sayed
---
drivers/staging/rtl8192e/rtllib_softmac.c | 35 +++
1 file changed, 22
From: "Aneesh Kumar K.V"
This feature flag selects richacl instead of POSIX ACL support on the
filesystem. When this feature is off, the "acl" and "noacl" mount options
control whether POSIX ACLs are enabled. When it is on, richacls are
automatically enabled and using the "noacl" mount option
Am 16.03.2016 um 11:58 schrieb Andreas Färber:
> Am 11.03.2016 um 00:04 schrieb Julien Chauveau:
>>> @@ -70,6 +71,19 @@
>>> pinctrl-0 = <_int>;
>>> };
>>>
>>> + keys: gpio-keys {
[...]
>>> + compatible = "gpio-keys";
>>> + pinctrl-names = "default";
>>> +
Am 16.03.2016 um 11:58 schrieb Andreas Färber:
> Am 11.03.2016 um 00:04 schrieb Julien Chauveau:
>>> @@ -70,6 +71,19 @@
>>> pinctrl-0 = <_int>;
>>> };
>>>
>>> + keys: gpio-keys {
[...]
>>> + compatible = "gpio-keys";
>>> + pinctrl-names = "default";
>>> +
v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let
me know.
---8<
From: Harvey Hunt
commit 4ee34ea3a12396f35b26d90a094c75db95080baa upstream.
The id buffer in ata_device is a DMA
v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let
me know.
---8<
From: Harvey Hunt
commit 4ee34ea3a12396f35b26d90a094c75db95080baa upstream.
The id buffer in ata_device is a DMA target, but it isn't
On Fri, 2016-03-18 at 16:35 +, Luis de Bethencourt wrote:
> Fix order of mac80211_rx_flags description to match the enum.
>
> Signed-off-by: Luis de Bethencourt
> ---
> Hi,
>
> I want ahead and fixed the order of the descriptions. checkpatch.pl
> was giving
> a
On Fri, 2016-03-18 at 16:35 +, Luis de Bethencourt wrote:
> Fix order of mac80211_rx_flags description to match the enum.
>
> Signed-off-by: Luis de Bethencourt
> ---
> Hi,
>
> I want ahead and fixed the order of the descriptions. checkpatch.pl
> was giving
> a warning to my previous patch
2016-03-18 01:09-0500, Suravee Suthikulpanit:
> From: Suravee Suthikulpanit
>
> When a vcpu is loaded/unloaded to a physical core, we need to update
> host physical APIC ID information in the Physical APIC-ID table
> accordingly.
>
> Also, when vCPU is
2016-03-18 01:09-0500, Suravee Suthikulpanit:
> From: Suravee Suthikulpanit
>
> When a vcpu is loaded/unloaded to a physical core, we need to update
> host physical APIC ID information in the Physical APIC-ID table
> accordingly.
>
> Also, when vCPU is blocking/un-blocking (due to halt
КЛИЕНТСКИЕ БАЗЫ!
Соберем для Вас по интернет базу данных потенциальных клиентов
для Вашего Бизнеса!
Много! Быстро! Недорого!
Узнайте об этом подробнее по
Тел: +79139393506
Viber: +79139393506
Whatsapp: +79139393506
Skype: prodawez389
Email: mnoskova...@gmail.com
КЛИЕНТСКИЕ БАЗЫ!
Соберем для Вас по интернет базу данных потенциальных клиентов
для Вашего Бизнеса!
Много! Быстро! Недорого!
Узнайте об этом подробнее по
Тел: +79139393506
Viber: +79139393506
Whatsapp: +79139393506
Skype: prodawez389
Email: mnoskova...@gmail.com
Hi James,
On 16/03/2016:10:27:22 AM, James Morse wrote:
> Hi Pratyush,
>
> On 16/03/16 05:43, Pratyush Anand wrote:
> > On 15/03/2016:06:47:52 PM, James Morse wrote:
> >> If I understand this correctly - you can't kprobe these ldr/str
> >> instructions
> >> as the fault handler wouldn't find
Hi James,
On 16/03/2016:10:27:22 AM, James Morse wrote:
> Hi Pratyush,
>
> On 16/03/16 05:43, Pratyush Anand wrote:
> > On 15/03/2016:06:47:52 PM, James Morse wrote:
> >> If I understand this correctly - you can't kprobe these ldr/str
> >> instructions
> >> as the fault handler wouldn't find
The new shutdown controller compatible with sama5d2 has a new binding
documentation and properties.
Signed-off-by: Nicolas Ferre
Cc: devicet...@vger.kernel.org
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
The new shutdown controller compatible with sama5d2 has a new binding
documentation and properties.
Signed-off-by: Nicolas Ferre
Cc: devicet...@vger.kernel.org
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
doc
---
Changes in v5:
- change naming for this driver: instead
On 3/16/2016 1:35 AM, David Lechner wrote:
I've implemented some proper clocks for the USB PHY clocks on da8xx. For those
not familiar with the architecture, the SoC has one USB 1.1 OHCI port and one
USB 2.O OTG port. The USB 1.1 PHY clock can optionally be supplied by the PLL
in the USB 2.0
On 3/16/2016 1:35 AM, David Lechner wrote:
I've implemented some proper clocks for the USB PHY clocks on da8xx. For those
not familiar with the architecture, the SoC has one USB 1.1 OHCI port and one
USB 2.O OTG port. The USB 1.1 PHY clock can optionally be supplied by the PLL
in the USB 2.0
On Thu, 17 Mar 2016, Axel Lin wrote:
> Export irq_domain_free_irqs_common so it can be used by modules.
>
> Signed-off-by: Axel Lin
> ---
> kernel/irq/irqdomain.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
>
On Thu, 17 Mar 2016, Axel Lin wrote:
> Export irq_domain_free_irqs_common so it can be used by modules.
>
> Signed-off-by: Axel Lin
> ---
> kernel/irq/irqdomain.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> index 3a519a0..245a485
Hi Chanwoo,
On 03/18/2016 03:52 PM, Chanwoo Choi wrote:
> Hi Baolu,
>
> On 2016년 03월 18일 15:32, Lu Baolu wrote:
>> Several Intel PCHs and SOCs have an internal mux that is used to
>> share one USB port between device controller and host controller.
>>
>> A usb port mux could be abstracted as the
Hi Chanwoo,
On 03/18/2016 03:52 PM, Chanwoo Choi wrote:
> Hi Baolu,
>
> On 2016년 03월 18일 15:32, Lu Baolu wrote:
>> Several Intel PCHs and SOCs have an internal mux that is used to
>> share one USB port between device controller and host controller.
>>
>> A usb port mux could be abstracted as the
On 16.3.2016 16:03, Tomas Henzl wrote:
> On 15.3.2016 22:40, Arnd Bergmann wrote:
>> The qlt_check_reserve_free_req() function produces an incorrect warning
>> when CONFIG_PROFILE_ANNOTATED_BRANCHES is set:
>>
>> drivers/scsi/qla2xxx/qla_target.c: In function 'qlt_check_reserve_free_req':
>>
On 16.3.2016 16:03, Tomas Henzl wrote:
> On 15.3.2016 22:40, Arnd Bergmann wrote:
>> The qlt_check_reserve_free_req() function produces an incorrect warning
>> when CONFIG_PROFILE_ANNOTATED_BRANCHES is set:
>>
>> drivers/scsi/qla2xxx/qla_target.c: In function 'qlt_check_reserve_free_req':
>>
On Wed, Mar 16, 2016 at 04:51:20PM +, Ben Hutchings wrote:
> The binding definition for the PCF857x GPIO expanders doesn't mention
> a "ti,pcf8575" compatible string. This is apparently because TI is
> only a second source - there is no functional difference between
> PCF8575 chips
On Wed, Mar 16, 2016 at 04:51:20PM +, Ben Hutchings wrote:
> The binding definition for the PCF857x GPIO expanders doesn't mention
> a "ti,pcf8575" compatible string. This is apparently because TI is
> only a second source - there is no functional difference between
> PCF8575 chips
On 03/04/2016 09:19 AM, Thierry Reding wrote:
From: Thierry Reding
Add device-tree binding documentation for the XUSB controller present
on Tegra124 and later SoCs. This controller supports USB 3.0 via an xHCI
compliant interface.
Based on work by Andrew Bresticker
On 03/04/2016 09:19 AM, Thierry Reding wrote:
From: Thierry Reding
Add device-tree binding documentation for the XUSB controller present
on Tegra124 and later SoCs. This controller supports USB 3.0 via an xHCI
compliant interface.
Based on work by Andrew Bresticker .
diff --git
On Mon, Mar 07, 2016 at 04:41:57PM -0500, valdis.kletni...@vt.edu wrote:
>
> lspci says:
> 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port
> SATA Controller [AHCI mode] (rev 04)
>
> Not sure why I only see it on reboots - that means that when powering up, the
> kernel
On Mon, Mar 07, 2016 at 04:41:57PM -0500, valdis.kletni...@vt.edu wrote:
>
> lspci says:
> 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port
> SATA Controller [AHCI mode] (rev 04)
>
> Not sure why I only see it on reboots - that means that when powering up, the
> kernel
On Thu, Mar 17, 2016 at 12:19:44PM +0800, Zhao Lei wrote:
> +static u64 __cpuusage_read(struct cgroup_subsys_state *css,
> +enum cpuacct_usage_index index)
> {
> struct cpuacct *ca = css_ca(css);
> u64 totalcpuusage = 0;
> int i;
>
>
On Thu, Mar 17, 2016 at 12:19:44PM +0800, Zhao Lei wrote:
> +static u64 __cpuusage_read(struct cgroup_subsys_state *css,
> +enum cpuacct_usage_index index)
> {
> struct cpuacct *ca = css_ca(css);
> u64 totalcpuusage = 0;
> int i;
>
>
On Thu, 2016-03-17 at 16:03 -0400, Linda Knippers wrote:
> On 3/17/2016 2:24 PM, Srinivas Pandruvada wrote:
> >
> > There are several reports of freeze on enabling HWP (Hardware
> > PStates)
> > feature on Skylake based systems by Intel P states driver. The root
> > cause is identified as the HWP
On Thu, 2016-03-17 at 16:03 -0400, Linda Knippers wrote:
> On 3/17/2016 2:24 PM, Srinivas Pandruvada wrote:
> >
> > There are several reports of freeze on enabling HWP (Hardware
> > PStates)
> > feature on Skylake based systems by Intel P states driver. The root
> > cause is identified as the HWP
Commit 22e0f8b9322c ("net: sched: make bstats per cpu and estimator RCU safe")
added the argument cpu_bstats to functions gen_new_estimator and
gen_replace_estimator and now the descriptions of these are missing for the
documentation. Adding them.
Signed-off-by: Luis de Bethencourt
Commit 22e0f8b9322c ("net: sched: make bstats per cpu and estimator RCU safe")
added the argument cpu_bstats to functions gen_new_estimator and
gen_replace_estimator and now the descriptions of these are missing for the
documentation. Adding them.
Signed-off-by: Luis de Bethencourt
---
Hi,
On 03/19/2016 01:59 PM, Greg Kroah-Hartman wrote:
> On Sat, Mar 19, 2016 at 01:40:21PM -0700, Brian Bloniarz wrote:
>> Hi, I haven't heard anything after sending this latest patch -- is there
>> anything I can do to help get this fixed?
>
> I wanted to get an ack or reviewed-by from Peter before
On 03/19/2016 01:59 PM, Greg Kroah-Hartman wrote:
> On Sat, Mar 19, 2016 at 01:40:21PM -0700, Brian Bloniarz wrote:
>> Hi, I haven't heard anything after sending this latest patch -- is there
>> anything I can do to help get this fixed?
>
> I wanted to get an ack or reviewed-by from Peter before
Function gnet_stats_copy_basic is missing the description of the cpu
argument in the documentation. Adding it.
Signed-off-by: Luis de Bethencourt
---
Hi,
Noticed this issue when running make htmldocs. I got the following warning:
.//net/core/gen_stats.c:155: warning: No
Function gnet_stats_copy_basic is missing the description of the cpu
argument in the documentation. Adding it.
Signed-off-by: Luis de Bethencourt
---
Hi,
Noticed this issue when running make htmldocs. I got the following warning:
.//net/core/gen_stats.c:155: warning: No description found for
Currently, in mb_find_order_for_block(), there's a loop like the following:
while (order <= e4b->bd_blkbits + 1) {
...
bb += 1 << (e4b->bd_blkbits - order);
}
Note that the updated bb is used in the loop's next iteration only.
However, at the last iteration, that is at order ==
Please drop in favour of v2.
Thank you and sorry for the noise,
Nicolai
v1 can be found here:
http://lkml.kernel.org/g/1458417247-3164-1-git-send-email-nicsta...@gmail.com
Unfortunately, I failed to recognize that the very same issue fixed by v1
appears again at another place in fs/ext4/mballoc.c.
Hence a v2 with the [2/2] addressing that second occurence.
Currently, in mb_find_order_for_block(), there's a loop like the following:
while (order <= e4b->bd_blkbits + 1) {
...
bb += 1 << (e4b->bd_blkbits - order);
}
Note that the updated bb is used in the loop's next iteration only.
However, at the last iteration, that is at order ==
Please drop in favour of v2.
Thank you and sorry for the noise,
Nicolai
v1 can be found here:
http://lkml.kernel.org/g/1458417247-3164-1-git-send-email-nicsta...@gmail.com
Unfortunately, I failed to recognize that the very same issue fixed by v1
appears again at another place in fs/ext4/mballoc.c.
Hence a v2 with the [2/2] addressing that second occurence.
Currently, in ext4_mb_init(), there's a loop like the following:
do {
...
offset += 1 << (sb->s_blocksize_bits - i);
i++;
} while (i <= sb->s_blocksize_bits + 1);
Note that the updated offset is used in the loop's next iteration only.
However, at the last iteration, that is at i
Currently, in ext4_mb_init(), there's a loop like the following:
do {
...
offset += 1 << (sb->s_blocksize_bits - i);
i++;
} while (i <= sb->s_blocksize_bits + 1);
Note that the updated offset is used in the loop's next iteration only.
However, at the last iteration, that is at i
This makes the code easier to read and it avoids a dynamic memory
allocation.
Signed-off-by: Maarten ter Huurne
---
drivers/regulator/act8865-regulator.c | 28
include/linux/regulator/act8865.h | 2 ++
2 files changed, 14 insertions(+),
This makes the code easier to read and it avoids a dynamic memory
allocation.
Signed-off-by: Maarten ter Huurne
---
drivers/regulator/act8865-regulator.c | 28
include/linux/regulator/act8865.h | 2 ++
2 files changed, 14 insertions(+), 16 deletions(-)
diff
Move efi_status_to_err() to the architecture independent code as it's
generally useful in all bits of EFI code where there is a need to
convert an efi_status_t to a kernel error value.
Cc: Kweh Hock Leong
Cc: Borislav Petkov
Cc: Ard Biesheuvel
Move efi_status_to_err() to the architecture independent code as it's
generally useful in all bits of EFI code where there is a need to
convert an efi_status_t to a kernel error value.
Cc: Kweh Hock Leong
Cc: Borislav Petkov
Cc: Ard Biesheuvel
Signed-off-by: Matt Fleming
---
Made comments not break coding style guidlines and easier to read.
Signed-off-by: Gavin O'Leary
---
drivers/staging/unisys/visornic/visornic_main.c | 29 +++--
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git
Made comments not break coding style guidlines and easier to read.
Signed-off-by: Gavin O'Leary
---
drivers/staging/unisys/visornic/visornic_main.c | 29 +++--
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git a/drivers/staging/unisys/visornic/visornic_main.c
__module_put_and_exit() is makred noreturn in module.h declaration, but is
lacking the attribute in the definition, which makes some tools (such as
sparse) unhappy. Amend the definition with the attribute as well (and
reformat the declaration so that it uses more common format).
Signed-off-by:
__module_put_and_exit() is makred noreturn in module.h declaration, but is
lacking the attribute in the definition, which makes some tools (such as
sparse) unhappy. Amend the definition with the attribute as well (and
reformat the declaration so that it uses more common format).
Signed-off-by:
Hello, again.
On Wed, Mar 16, 2016 at 07:24:14AM -0700, Tejun Heo wrote:
> I could be mistaken but AFAICS there doesn't seem to be anything
> requiring bothering with the more specialized exit methods. Given
> that no css iteration is used and everything is lock protected, the
Ooh, missed the
Hello, again.
On Wed, Mar 16, 2016 at 07:24:14AM -0700, Tejun Heo wrote:
> I could be mistaken but AFAICS there doesn't seem to be anything
> requiring bothering with the more specialized exit methods. Given
> that no css iteration is used and everything is lock protected, the
Ooh, missed the
Add a driver for the Tegra-AGIC interrupt controller which is compatible
with the ARM GIC-400 interrupt controller.
The Tegra AGIC (Audio GIC) is part of the Audio Processing Engine (APE) on
Tegra210 and can route interrupts to either the GIC for the CPU subsystem
or the Audio DSP (ADSP) within
On 3/17/2016 7:27 AM, Catalin Marinas wrote:
On Wed, Mar 16, 2016 at 10:26:08AM -0500, Timur Tabi wrote:
Catalin Marinas wrote:
Why do you need your own defconfig? If it's just on the short term until
all your code is upstream, that's fine, but this goes against the single
Image aim. I would
Add a driver for the Tegra-AGIC interrupt controller which is compatible
with the ARM GIC-400 interrupt controller.
The Tegra AGIC (Audio GIC) is part of the Audio Processing Engine (APE) on
Tegra210 and can route interrupts to either the GIC for the CPU subsystem
or the Audio DSP (ADSP) within
On 3/17/2016 7:27 AM, Catalin Marinas wrote:
On Wed, Mar 16, 2016 at 10:26:08AM -0500, Timur Tabi wrote:
Catalin Marinas wrote:
Why do you need your own defconfig? If it's just on the short term until
all your code is upstream, that's fine, but this goes against the single
Image aim. I would
On Fri, 18 Mar 2016, kan.li...@intel.com wrote:
> +static struct intel_rapl_init_fun knl_rapl_init = {
Same const __initconst issue as in the other patch
> static const struct x86_cpu_id rapl_cpu_match[] __initconst = {
Yep, that one is correct.
Other than the above:
Reviewed-by: Thomas
On Fri, 18 Mar 2016, kan.li...@intel.com wrote:
> +static struct intel_rapl_init_fun knl_rapl_init = {
Same const __initconst issue as in the other patch
> static const struct x86_cpu_id rapl_cpu_match[] __initconst = {
Yep, that one is correct.
Other than the above:
Reviewed-by: Thomas
On Wed, Mar 16, 2016 at 05:10:34PM +, Olu Ogunbowale wrote:
> From: Olujide Ogunbowale
>
> Export the memory management functions, unmapped_area() &
> unmapped_area_topdown(), as GPL symbols; this allows the kernel to
> better support process address space
On Wed, Mar 16, 2016 at 05:10:34PM +, Olu Ogunbowale wrote:
> From: Olujide Ogunbowale
>
> Export the memory management functions, unmapped_area() &
> unmapped_area_topdown(), as GPL symbols; this allows the kernel to
> better support process address space mirroring on both CPU and device
>
From: David Decotigny
This removes the requirement that ethtool be tied to the support
of a specific L3 protocol, also updates a comment.
# Patch Set Summary:
David Decotigny (2):
ethtool: minor doc update
netlink: add
From: David Decotigny
This removes the requirement that ethtool be tied to the support
of a specific L3 protocol, also updates a comment.
# Patch Set Summary:
David Decotigny (2):
ethtool: minor doc update
netlink: add support for NIC driver
Sorry, for late.
Ingo Molnar writes:
> * kernel test robot wrote:
>
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 65d8fc777f6dcfee12785c057a6b57f679641c90
Sorry, for late.
Ingo Molnar writes:
> * kernel test robot wrote:
>
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 65d8fc777f6dcfee12785c057a6b57f679641c90 ("futex: Remove requirement
>> for
>> lock_page()
Sorry for the noise, just sent twice the same patch :-/.
Please ignore this one.
On Thu, 17 Mar 2016 10:47:11 +0100
Boris Brezillon wrote:
> Forward devm_ioremap_resource() error code instead of returning
> -ENOMEM.
>
> Signed-off-by: Boris Brezillon
On 03/04/2016 09:19 AM, Thierry Reding wrote:
From: Thierry Reding
Extend the binding to cover the set of feature found in Tegra210.
Acked-by: Stephen Warren
diff --git
a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt
Sorry for the noise, just sent twice the same patch :-/.
Please ignore this one.
On Thu, 17 Mar 2016 10:47:11 +0100
Boris Brezillon wrote:
> Forward devm_ioremap_resource() error code instead of returning
> -ENOMEM.
>
> Signed-off-by: Boris Brezillon
> Reported-by: Russell King - ARM Linux
>
On 03/04/2016 09:19 AM, Thierry Reding wrote:
From: Thierry Reding
Extend the binding to cover the set of feature found in Tegra210.
Acked-by: Stephen Warren
diff --git
a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt
On Fri, Mar 18, 2016 at 04:55:26PM +0100, Alexander Graf wrote:
>
>
> On 18.03.16 16:49, Yury Norov wrote:
> > On Fri, Mar 18, 2016 at 06:28:29PM +0800, Zhangjian (Bamvor) wrote:
> >>
> >> For the glibc part, I found that there are 11 patches of ilp32 in top,
> >> but the original 28 patches of
On Fri, Mar 18, 2016 at 04:55:26PM +0100, Alexander Graf wrote:
>
>
> On 18.03.16 16:49, Yury Norov wrote:
> > On Fri, Mar 18, 2016 at 06:28:29PM +0800, Zhangjian (Bamvor) wrote:
> >>
> >> For the glibc part, I found that there are 11 patches of ilp32 in top,
> >> but the original 28 patches of
On 16/03/2016 at 14:19:50 +0100, Nicolas Ferre wrote :
> Sama5d2 SoC has a completely new shutdown controller with new features and
> register layout. It thus makes sense to add a new driver for this new
> peripheral.
>
> This driver is Device Tree only and handles events from the wake-up pin and
On 16/03/2016 at 14:19:50 +0100, Nicolas Ferre wrote :
> Sama5d2 SoC has a completely new shutdown controller with new features and
> register layout. It thus makes sense to add a new driver for this new
> peripheral.
>
> This driver is Device Tree only and handles events from the wake-up pin and
801 - 900 of 3664 matches
Mail list logo