On Tue, Aug 7, 2018 at 12:18 AM, Dmitry Torokhov
wrote:
> Some of fuzzers set panic_on_warn=1 so that they can handle WARN()ings
> the same way they handle full-blown kernel crashes. We used WARN() in
> input_alloc_absinfo() to get a better idea where memory allocation
> failed, but since then
On Tue, Aug 7, 2018 at 12:18 AM, Dmitry Torokhov
wrote:
> Some of fuzzers set panic_on_warn=1 so that they can handle WARN()ings
> the same way they handle full-blown kernel crashes. We used WARN() in
> input_alloc_absinfo() to get a better idea where memory allocation
> failed, but since then
This function splits and removes overlapping areas.
Maps in tree are ordered by start address thus we could find
first overlap and stop if next map does not overlap.
Signed-off-by: Konstantin Khlebnikov
---
v2:
* add comments
* replace map__overlap with minimal check
* remove remove
This function splits and removes overlapping areas.
Maps in tree are ordered by start address thus we could find
first overlap and stop if next map does not overlap.
Signed-off-by: Konstantin Khlebnikov
---
v2:
* add comments
* replace map__overlap with minimal check
* remove remove
On Tue, Aug 07, 2018 at 06:43:38PM +0800, Baolin Wang wrote:
> From: Lanqing Liu
>
> This patch adds the SPI controller driver for Spreadtrum SC9860 platform.
This all looks pretty clean, a few comments below but nothing too major:
> +static void sprd_spi_chipselect(struct spi_device *sdev,
On Tue, Aug 07, 2018 at 06:43:38PM +0800, Baolin Wang wrote:
> From: Lanqing Liu
>
> This patch adds the SPI controller driver for Spreadtrum SC9860 platform.
This all looks pretty clean, a few comments below but nothing too major:
> +static void sprd_spi_chipselect(struct spi_device *sdev,
On 07.08.2018 16:19, Oscar Salvador wrote:
> On Tue, Aug 07, 2018 at 04:16:35PM +0200, David Hildenbrand wrote:
>> On 07.08.2018 15:37, osalva...@techadventures.net wrote:
>>> From: Oscar Salvador
>>>
>>> This tries to fix [1], which was reported by David Hildenbrand, and also
>>> does some
On 07.08.2018 16:19, Oscar Salvador wrote:
> On Tue, Aug 07, 2018 at 04:16:35PM +0200, David Hildenbrand wrote:
>> On 07.08.2018 15:37, osalva...@techadventures.net wrote:
>>> From: Oscar Salvador
>>>
>>> This tries to fix [1], which was reported by David Hildenbrand, and also
>>> does some
On Tue, Aug 07, 2018 at 04:16:35PM +0200, David Hildenbrand wrote:
> On 07.08.2018 15:37, osalva...@techadventures.net wrote:
> > From: Oscar Salvador
> >
> > This tries to fix [1], which was reported by David Hildenbrand, and also
> > does some cleanups/refactoring.
> >
> > I am sending this
On Tue, Aug 07, 2018 at 04:16:35PM +0200, David Hildenbrand wrote:
> On 07.08.2018 15:37, osalva...@techadventures.net wrote:
> > From: Oscar Salvador
> >
> > This tries to fix [1], which was reported by David Hildenbrand, and also
> > does some cleanups/refactoring.
> >
> > I am sending this
On Sat 2018-07-28 09:39:57, Joe Perches wrote:
> Use %p pointer output instead of REG_FMT and cast the unsigned longs to
> (void *) to avoid exposing kernel addresses.
>
> Miscellanea:
>
> o Convert pr_cont to printk(KERN_DEFAULT as these uses are
> new logging lines and not previous line
On Sat 2018-07-28 09:39:57, Joe Perches wrote:
> Use %p pointer output instead of REG_FMT and cast the unsigned longs to
> (void *) to avoid exposing kernel addresses.
>
> Miscellanea:
>
> o Convert pr_cont to printk(KERN_DEFAULT as these uses are
> new logging lines and not previous line
On 07.08.2018 15:37, osalva...@techadventures.net wrote:
> From: Oscar Salvador
>
> This tries to fix [1], which was reported by David Hildenbrand, and also
> does some cleanups/refactoring.
>
> I am sending this as RFC to see if the direction I am going is right before
> spending more time
On 07.08.2018 15:37, osalva...@techadventures.net wrote:
> From: Oscar Salvador
>
> This tries to fix [1], which was reported by David Hildenbrand, and also
> does some cleanups/refactoring.
>
> I am sending this as RFC to see if the direction I am going is right before
> spending more time
On Tue, Aug 07, 2018 at 01:02:16PM +0800, Rong Chen wrote:
>
>
> On 08/01/2018 07:46 PM, J. Bruce Fields wrote:
> > On Fri, Jul 27, 2018 at 08:22:25AM +0800, Ye Xiaolong wrote:
> > > On 07/16, Ye Xiaolong wrote:
> > > > On 07/04, Huang, Ying wrote:
> > > > > "J. Bruce Fields" writes:
> > > > >
On Tue, Aug 07, 2018 at 01:02:16PM +0800, Rong Chen wrote:
>
>
> On 08/01/2018 07:46 PM, J. Bruce Fields wrote:
> > On Fri, Jul 27, 2018 at 08:22:25AM +0800, Ye Xiaolong wrote:
> > > On 07/16, Ye Xiaolong wrote:
> > > > On 07/04, Huang, Ying wrote:
> > > > > "J. Bruce Fields" writes:
> > > > >
On Mon, 6 Aug 2018, Ard Biesheuvel wrote:
> No that works fine for me. VDPAU acceleration works as well, but it
> depends on your chromium build whether it can actually use it, I
> think? In any case, mplayer can use vdpau to play 1080p h264 without
> breaking a sweat on this system.
>
> Note
On Mon, 6 Aug 2018, Ard Biesheuvel wrote:
> No that works fine for me. VDPAU acceleration works as well, but it
> depends on your chromium build whether it can actually use it, I
> think? In any case, mplayer can use vdpau to play 1080p h264 without
> breaking a sweat on this system.
>
> Note
Hi,
Recent commit 82ff27bc52a88cb5cc400bfa64e210d3ec8dfebd ("xfs: automatic
dfops buffer relogging") removed the assignment of variable error:
- error = xfs_defer_bjoin(tp->t_dfops, bp);
if (error) {
xfs_trans_bhold_release(tp, bp);
Hi,
Recent commit 82ff27bc52a88cb5cc400bfa64e210d3ec8dfebd ("xfs: automatic
dfops buffer relogging") removed the assignment of variable error:
- error = xfs_defer_bjoin(tp->t_dfops, bp);
if (error) {
xfs_trans_bhold_release(tp, bp);
On Mon, 6 Aug 2018, Dennis Zhou wrote:
> diff --git a/fs/proc/meminfo.c b/fs/proc/meminfo.c
> index 2fb04846ed11..ddd5249692e9 100644
> --- a/fs/proc/meminfo.c
> +++ b/fs/proc/meminfo.c
> @@ -7,6 +7,7 @@
> #include
> #include
> #include
> +#include
> #include
> #include
> #include
>
On Mon, 6 Aug 2018, Dennis Zhou wrote:
> diff --git a/fs/proc/meminfo.c b/fs/proc/meminfo.c
> index 2fb04846ed11..ddd5249692e9 100644
> --- a/fs/proc/meminfo.c
> +++ b/fs/proc/meminfo.c
> @@ -7,6 +7,7 @@
> #include
> #include
> #include
> +#include
> #include
> #include
> #include
>
On August 7, 2018 9:49:54 AM EDT, Steven Rostedt wrote:
>On Tue, 7 Aug 2018 06:33:35 -0700
>Joel Fernandes wrote:
>
>> Thanks, also one more thing I noticed in your patch,
>> lockdep_hardirqs_off needs to be called before all other probes but
>> you're calling it after. This is why I
On August 7, 2018 9:49:54 AM EDT, Steven Rostedt wrote:
>On Tue, 7 Aug 2018 06:33:35 -0700
>Joel Fernandes wrote:
>
>> Thanks, also one more thing I noticed in your patch,
>> lockdep_hardirqs_off needs to be called before all other probes but
>> you're calling it after. This is why I
On 08/06/2018 09:54 PM, Alexandre Belloni wrote:
Hello,
Because the designware IP was not able to handle the SDA hold time before
version 1.11a, MSCC has its own implementation. Add support for it and then add
i2c on ocelot boards.
I would expect patches 1 to 4 to go through the i2c tree and
On 08/06/2018 09:54 PM, Alexandre Belloni wrote:
Hello,
Because the designware IP was not able to handle the SDA hold time before
version 1.11a, MSCC has its own implementation. Add support for it and then add
i2c on ocelot boards.
I would expect patches 1 to 4 to go through the i2c tree and
On Tue, Aug 7, 2018 at 6:55 AM wrote:
>
> From: Patrice Chotard
>
> Fix the following DT dtc warnings for stm32f429 and
> stm32f469 boards:
>
> Warning (node_name_chars_strict): /soc/pin-controller/usbotg_fs@0: Character
> '_' not recommended in node name
> Warning (node_name_chars_strict):
On Tue, Aug 7, 2018 at 6:55 AM wrote:
>
> From: Patrice Chotard
>
> Fix the following DT dtc warnings for stm32f429 and
> stm32f469 boards:
>
> Warning (node_name_chars_strict): /soc/pin-controller/usbotg_fs@0: Character
> '_' not recommended in node name
> Warning (node_name_chars_strict):
On Mon, 6 Aug 2018, David Laight wrote:
> From: Mikulas Patocka
> > Sent: 05 August 2018 15:36
> > To: David Laight
> ...
> > There's an instruction movntdqa (and vmovntdqa) that can actually do
> > prefetch on write-combining memory type. It's the only instruction that
> > can do it.
> >
> >
On Mon, 6 Aug 2018, David Laight wrote:
> From: Mikulas Patocka
> > Sent: 05 August 2018 15:36
> > To: David Laight
> ...
> > There's an instruction movntdqa (and vmovntdqa) that can actually do
> > prefetch on write-combining memory type. It's the only instruction that
> > can do it.
> >
> >
> On Aug 7, 2018, at 4:04 AM, Dmitry Vyukov wrote:
>
>> On Tue, Aug 7, 2018 at 3:22 AM, Jann Horn wrote:
>> There have been multiple kernel vulnerabilities that permitted userspace to
>> pass completely unchecked pointers through to userspace accessors:
>>
>> - the waitid() bug - commit
> On Aug 7, 2018, at 4:04 AM, Dmitry Vyukov wrote:
>
>> On Tue, Aug 7, 2018 at 3:22 AM, Jann Horn wrote:
>> There have been multiple kernel vulnerabilities that permitted userspace to
>> pass completely unchecked pointers through to userspace accessors:
>>
>> - the waitid() bug - commit
Enable HS400 signaling on Tegra210 SDMMC4 controller.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
index f8e5f09..8fe47d6 100644
Enable HS400 signaling on Tegra210 SDMMC4 controller.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
index f8e5f09..8fe47d6 100644
Add the HS400 DQS trim value for Tegra186 SDMMC4.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dtsi
b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
index 6e9ef26..9e07bc6 100644
---
Add the HS400 DQS trim value for Tegra210 SDMMC4.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
index 14da98a..f8e5f09 100644
---
Enable HS400 signaling on Tegra186 SDMMC4 controller.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dtsi
b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
index 9e07bc6..2f3c8e2 100644
Add the HS400 DQS trim value for Tegra186 SDMMC4.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dtsi
b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
index 6e9ef26..9e07bc6 100644
---
Add the HS400 DQS trim value for Tegra210 SDMMC4.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
index 14da98a..f8e5f09 100644
---
Enable HS400 signaling on Tegra186 SDMMC4 controller.
Signed-off-by: Aapo Vienamo
---
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dtsi
b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
index 9e07bc6..2f3c8e2 100644
Document HS400 DQS trim value device tree property.
Signed-off-by: Aapo Vienamo
---
Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
Parse and program the HS400 DQS trim value from dt. Program a fallback
value in case the property is missing.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 32 +---
1 file changed, 29 insertions(+), 3 deletions(-)
diff --git
Implement HS400 specific delay line calibration procedure.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index d81143b..d0b68b7
Implement HS400 enhanced strobe.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index 426f7ea..d81143b 100644
---
Document HS400 DQS trim value device tree property.
Signed-off-by: Aapo Vienamo
---
Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
Parse and program the HS400 DQS trim value from dt. Program a fallback
value in case the property is missing.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 32 +---
1 file changed, 29 insertions(+), 3 deletions(-)
diff --git
Implement HS400 specific delay line calibration procedure.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index d81143b..d0b68b7
Implement HS400 enhanced strobe.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index 426f7ea..d81143b 100644
---
Hi all,
This series implements support for HS400 signaling on Tegra210 and
Tegra186. This includes programming the DQS trimmer values, implementing
enhanced strobe and HS400 delay line calibration.
This series depends on the "Tegra SDHCI add support for HS200 and UHS
signaling" series.
Aapo
Hi all,
This series implements support for HS400 signaling on Tegra210 and
Tegra186. This includes programming the DQS trimmer values, implementing
enhanced strobe and HS400 delay line calibration.
This series depends on the "Tegra SDHCI add support for HS200 and UHS
signaling" series.
Aapo
--
utente webmail
Tieni presente che il 95% delle tue e-mail ricevute dopo l'ultima
volta che hai bisogno di aggiornare il tuo server di versione webmail
nel nostro database sono state ritardate. Per ricevere e inviare i
tuoi messaggi su base regolare. Il nostro team tecnico di webmail
--
utente webmail
Tieni presente che il 95% delle tue e-mail ricevute dopo l'ultima
volta che hai bisogno di aggiornare il tuo server di versione webmail
nel nostro database sono state ritardate. Per ricevere e inviare i
tuoi messaggi su base regolare. Il nostro team tecnico di webmail
On Mon 06-08-18 15:59:27, Andrew Morton wrote:
> On Mon, 6 Aug 2018 12:22:03 +0200 Jan Kara wrote:
>
> > On Fri 20-07-18 16:14:29, Andrew Morton wrote:
> > > On Thu, 19 Jul 2018 10:58:12 +0200 Jan Kara wrote:
> > >
> > > > On Thu 19-07-18 16:17:26, Chengguang Xu wrote:
> > > > > When we try to
On Mon 06-08-18 15:59:27, Andrew Morton wrote:
> On Mon, 6 Aug 2018 12:22:03 +0200 Jan Kara wrote:
>
> > On Fri 20-07-18 16:14:29, Andrew Morton wrote:
> > > On Thu, 19 Jul 2018 10:58:12 +0200 Jan Kara wrote:
> > >
> > > > On Thu 19-07-18 16:17:26, Chengguang Xu wrote:
> > > > > When we try to
Hi Patrick,
On Monday 06 Aug 2018 at 17:39:38 (+0100), Patrick Bellasi wrote:
> diff --git a/kernel/sched/cpufreq_schedutil.c
> b/kernel/sched/cpufreq_schedutil.c
> index a7affc729c25..bb25ef66c2d3 100644
> --- a/kernel/sched/cpufreq_schedutil.c
> +++ b/kernel/sched/cpufreq_schedutil.c
> @@
Hi Patrick,
On Monday 06 Aug 2018 at 17:39:38 (+0100), Patrick Bellasi wrote:
> diff --git a/kernel/sched/cpufreq_schedutil.c
> b/kernel/sched/cpufreq_schedutil.c
> index a7affc729c25..bb25ef66c2d3 100644
> --- a/kernel/sched/cpufreq_schedutil.c
> +++ b/kernel/sched/cpufreq_schedutil.c
> @@
On Tue, Aug 07, 2018 at 03:37:56PM +0200, osalva...@techadventures.net wrote:
> From: Oscar Salvador
[...]
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 9bd629944c91..e33555651e46 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
[...]
> /**
> *
On Tue, Aug 07, 2018 at 03:37:56PM +0200, osalva...@techadventures.net wrote:
> From: Oscar Salvador
[...]
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 9bd629944c91..e33555651e46 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
[...]
> /**
> *
On Tue, 7 Aug 2018 06:33:35 -0700
Joel Fernandes wrote:
> Thanks, also one more thing I noticed in your patch,
> lockdep_hardirqs_off needs to be called before all other probes but
> you're calling it after. This is why I registered it with INT_MAX:
>
>
On Tue, 7 Aug 2018 06:33:35 -0700
Joel Fernandes wrote:
> Thanks, also one more thing I noticed in your patch,
> lockdep_hardirqs_off needs to be called before all other probes but
> you're calling it after. This is why I registered it with INT_MAX:
>
>
On Tue, Aug 07, 2018 at 06:43:37PM +0800, Baolin Wang wrote:
> +Optional properties:
> +- sprd,spi-interval: Specify the intervals of two SPI frames, which can be
> + converted to the delay clock cycles = interval number * 4 + 10.
What's a frame here, and does it overlap with any of the
On Tue, Aug 07, 2018 at 06:43:37PM +0800, Baolin Wang wrote:
> +Optional properties:
> +- sprd,spi-interval: Specify the intervals of two SPI frames, which can be
> + converted to the delay clock cycles = interval number * 4 + 10.
What's a frame here, and does it overlap with any of the
On Mon 2018-08-06 15:34:21, Bart Van Assche wrote:
> This patch avoids that gcc reports the following when building with W=1:
>
> lib/vsprintf.c:1941:3: warning: this statement may fall through
> [-Wimplicit-fallthrough=]
>switch (fmt[1]) {
>^~
>
> Fixes: ce4fecf1fe15 ("vsprintf:
On Mon 2018-08-06 15:34:21, Bart Van Assche wrote:
> This patch avoids that gcc reports the following when building with W=1:
>
> lib/vsprintf.c:1941:3: warning: this statement may fall through
> [-Wimplicit-fallthrough=]
>switch (fmt[1]) {
>^~
>
> Fixes: ce4fecf1fe15 ("vsprintf:
From: Oscar Salvador
This tries to fix [1], which was reported by David Hildenbrand, and also
does some cleanups/refactoring.
I am sending this as RFC to see if the direction I am going is right before
spending more time into it.
And also to gather feedback about hmm/zone_device stuff.
The code
From: Oscar Salvador
This patch is only a preparation for the following-up patches.
The idea is to remove the zone parameter and pass the nid instead.
The zone parameter was needed because down the chain we call
__remove_zone, which adjusts the spanned pages of a zone/node.
online_pages()
From: Oscar Salvador
This patch refactors shrink_zone_span and shrink_pgdat_span functions.
In case that find_smallest/biggest_section do not return any pfn,
it means that the zone/pgdat has no online sections left, so we can
set the respective values to 0:
zone case:
From: Oscar Salvador
This tries to fix [1], which was reported by David Hildenbrand, and also
does some cleanups/refactoring.
I am sending this as RFC to see if the direction I am going is right before
spending more time into it.
And also to gather feedback about hmm/zone_device stuff.
The code
From: Oscar Salvador
This patch is only a preparation for the following-up patches.
The idea is to remove the zone parameter and pass the nid instead.
The zone parameter was needed because down the chain we call
__remove_zone, which adjusts the spanned pages of a zone/node.
online_pages()
From: Oscar Salvador
This patch refactors shrink_zone_span and shrink_pgdat_span functions.
In case that find_smallest/biggest_section do not return any pfn,
it means that the zone/pgdat has no online sections left, so we can
set the respective values to 0:
zone case:
From: Oscar Salvador
Currently, we decrement zone/node spanned_pages when we
__remove__ the memory.
This is not really great.
Incrementing of spanned pages is done in online_pages() path,
decrementing spanned pages should be moved to offline_pages().
This, besides making the core more
From: Oscar Salvador
Currently, we decrement zone/node spanned_pages when we
__remove__ the memory.
This is not really great.
Incrementing of spanned pages is done in online_pages() path,
decrementing spanned pages should be moved to offline_pages().
This, besides making the core more
On Mon, Aug 6, 2018 at 6:43 PM, Steven Rostedt wrote:
> On Mon, 6 Aug 2018 17:43:19 -0700
> Joel Fernandes wrote:
>
>> On Mon, Aug 6, 2018 at 12:50 PM, Steven Rostedt wrote:
>> >
>> > With this patch applied, I'm constantly getting lockdep errors. Instead
>> > of doing a full revert of the
On Mon, Aug 6, 2018 at 6:43 PM, Steven Rostedt wrote:
> On Mon, 6 Aug 2018 17:43:19 -0700
> Joel Fernandes wrote:
>
>> On Mon, Aug 6, 2018 at 12:50 PM, Steven Rostedt wrote:
>> >
>> > With this patch applied, I'm constantly getting lockdep errors. Instead
>> > of doing a full revert of the
On Tue, Aug 07, 2018 at 03:00:48PM +0200, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> Add the ISO7816 ioctl and associated accessors and data structure.
> Drivers can then use this common implementation to handle ISO7816.
It would help a lot of you'd explain what ISO7816 is. Without
On Tue, Aug 07, 2018 at 03:00:48PM +0200, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> Add the ISO7816 ioctl and associated accessors and data structure.
> Drivers can then use this common implementation to handle ISO7816.
It would help a lot of you'd explain what ISO7816 is. Without
help
--
== Marcel J.E. MolMESA Consulting B.V.
===-ph. +31-(0)6-54724868
===-mar...@mesa.nl Nootdorp
__ www.mesa.nl ---U_n_i_x__I_n_t_e_r_n_e_t The Netherlands
They
help
--
== Marcel J.E. MolMESA Consulting B.V.
===-ph. +31-(0)6-54724868
===-mar...@mesa.nl Nootdorp
__ www.mesa.nl ---U_n_i_x__I_n_t_e_r_n_e_t The Netherlands
They
On 7 August 2018 at 13:28, Daniel Vetter wrote:
> On Tue, Aug 07, 2018 at 12:01:50PM +0100, Emil Velikov wrote:
>> On 3 August 2018 at 20:50, Sean Paul wrote:
>> > On Fri, Aug 03, 2018 at 06:03:50PM +0100, Emil Velikov wrote:
>> >> On 3 August 2018 at 16:06, Martin Fuzzey
>> >> wrote:
>> >> >
On 7 August 2018 at 13:28, Daniel Vetter wrote:
> On Tue, Aug 07, 2018 at 12:01:50PM +0100, Emil Velikov wrote:
>> On 3 August 2018 at 20:50, Sean Paul wrote:
>> > On Fri, Aug 03, 2018 at 06:03:50PM +0100, Emil Velikov wrote:
>> >> On 3 August 2018 at 16:06, Martin Fuzzey
>> >> wrote:
>> >> >
Hi,
On 06/08/18 17:39, Patrick Bellasi wrote:
[...]
> @@ -223,13 +224,25 @@ static unsigned long sugov_get_util(struct sugov_cpu
> *sg_cpu)
>* utilization (PELT windows are synchronized) we can directly add them
>* to obtain the CPU's actual utilization.
>*
> - *
Hi,
On 06/08/18 17:39, Patrick Bellasi wrote:
[...]
> @@ -223,13 +224,25 @@ static unsigned long sugov_get_util(struct sugov_cpu
> *sg_cpu)
>* utilization (PELT windows are synchronized) we can directly add them
>* to obtain the CPU's actual utilization.
>*
> - *
Em Mon, Aug 06, 2018 at 05:28:00PM -0500, Kim Phillips escreveu:
> The new syscall table support for arm64 mistakenly used the system's
> asm-generic/unistd.h file when processing the
> tools/arch/arm64/include/uapi/asm/unistd.h file's include directive:
>
> #include
>
> See "Committer
Em Mon, Aug 06, 2018 at 05:28:00PM -0500, Kim Phillips escreveu:
> The new syscall table support for arm64 mistakenly used the system's
> asm-generic/unistd.h file when processing the
> tools/arch/arm64/include/uapi/asm/unistd.h file's include directive:
>
> #include
>
> See "Committer
From: Colin Ian King
Array prox_curr_ma is declared but never used, hence it is redundant
and can be removed.
Cleans up clang warning:
warning: 'prox_curr_ma' defined but not used [-Wunused-const-variable=]
Signed-off-by: Colin Ian King
---
drivers/misc/bh1770glc.c | 3 ---
1 file changed, 3
From: Colin Ian King
Array prox_curr_ma is declared but never used, hence it is redundant
and can be removed.
Cleans up clang warning:
warning: 'prox_curr_ma' defined but not used [-Wunused-const-variable=]
Signed-off-by: Colin Ian King
---
drivers/misc/bh1770glc.c | 3 ---
1 file changed, 3
> Subject: Re: [PATCH 3/3] PCI/portdrv: Add support for sharing xilinx
> controller irq with AER
>
> On Wed, Aug 01, 2018 at 11:05:09AM -0700, Sinan Kaya wrote:
> > On 8/1/2018 9:44 AM, Bharat Kumar Gogada wrote:
> > > Xilinx ZynqMP PS PCIe does not report AER interrupts using Advanced
> > >
> Subject: Re: [PATCH 3/3] PCI/portdrv: Add support for sharing xilinx
> controller irq with AER
>
> On Wed, Aug 01, 2018 at 11:05:09AM -0700, Sinan Kaya wrote:
> > On 8/1/2018 9:44 AM, Bharat Kumar Gogada wrote:
> > > Xilinx ZynqMP PS PCIe does not report AER interrupts using Advanced
> > >
+CC linux-api
On 08/07/2018 02:56 AM, Dennis Zhou wrote:
> From: "Dennis Zhou (Facebook)"
>
> Currently, percpu memory only exposes allocation and utilization
> information via debugfs. This more or less is only really useful for
> understanding the fragmentation and allocation information at a
+CC linux-api
On 08/07/2018 02:56 AM, Dennis Zhou wrote:
> From: "Dennis Zhou (Facebook)"
>
> Currently, percpu memory only exposes allocation and utilization
> information via debugfs. This more or less is only really useful for
> understanding the fragmentation and allocation information at a
Array indirect_io_hosts[] is declared in acpi_is_indirect_io_slave() as a
const array, which means that the array will be re-built for each call.
Optimise by adding the static attribute, which means that the array is
added to const-data pool and not re-built per function call.
Reported-by: Hans
Array indirect_io_hosts[] is declared in acpi_is_indirect_io_slave() as a
const array, which means that the array will be re-built for each call.
Optimise by adding the static attribute, which means that the array is
added to const-data pool and not re-built per function call.
Reported-by: Hans
Em Tue, Aug 07, 2018 at 02:55:28PM +0200, Jiri Olsa escreveu:
> On Tue, Aug 07, 2018 at 12:09:05PM +0300, Konstantin Khlebnikov wrote:
> > This function splits and removes overlapping areas.
> >
> > Maps in tree are ordered by start address thus we could find
> > first overlap and stop if next
Em Tue, Aug 07, 2018 at 02:55:28PM +0200, Jiri Olsa escreveu:
> On Tue, Aug 07, 2018 at 12:09:05PM +0300, Konstantin Khlebnikov wrote:
> > This function splits and removes overlapping areas.
> >
> > Maps in tree are ordered by start address thus we could find
> > first overlap and stop if next
Em Tue, Aug 07, 2018 at 02:43:34PM +0200, Jiri Olsa escreveu:
> On Tue, Aug 07, 2018 at 12:09:01PM +0300, Konstantin Khlebnikov wrote:
> > Threads share map_groups, all map events are merged into it.
> >
> > Thus we could send mmaps only for thread group leader.
> > Otherwise it took ages to
Em Tue, Aug 07, 2018 at 02:43:34PM +0200, Jiri Olsa escreveu:
> On Tue, Aug 07, 2018 at 12:09:01PM +0300, Konstantin Khlebnikov wrote:
> > Threads share map_groups, all map events are merged into it.
> >
> > Thus we could send mmaps only for thread group leader.
> > Otherwise it took ages to
On 06/08/2018 23:39, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 81781b6884bd ("KVM/x86: Use CC_SET()/CC_OUT in arch/x86/kvm/vmx.c")
>
> is missing a Signed-off-by from its committer.
>
Stephen,
there is a semantic conflict between tip and kvm:
const __initconst struct hypervisor_x86
On 06/08/2018 23:39, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 81781b6884bd ("KVM/x86: Use CC_SET()/CC_OUT in arch/x86/kvm/vmx.c")
>
> is missing a Signed-off-by from its committer.
>
Stephen,
there is a semantic conflict between tip and kvm:
const __initconst struct hypervisor_x86
From: Nicolas Ferre
When mode is set in atmel_config_iso7816() we backup last RS232 mode
for coming back to this mode if requested.
Also allow setup of T=0 and T=1 parameter and basic support in set_termios
function as well.
Signed-off-by: Nicolas Ferre
[ludovic.desroc...@microchip.com:
From: Nicolas Ferre
Add the ISO7816 ioctl and associated accessors and data structure.
Drivers can then use this common implementation to handle ISO7816.
Signed-off-by: Nicolas Ferre
[ludovic.desroc...@microchip.com: squash and rebase, removal of gpios,
checkpatch fixes]
Signed-off-by:
1001 - 1100 of 1438 matches
Mail list logo
