Mehmet Kayaalp wrote:
> + /* TODO: update CRC */
Is this bit missing?
David
Mehmet Kayaalp wrote:
> + /* TODO: update CRC */
Is this bit missing?
David
Masami,
Am 27.04.2017 um 05:15 schrieb Masami Hiramatsu:
> Since read_initrd() invokes alloc_bootmem() for allocating
> memory to load initrd image, it must be called after init_bootmem.
>
> This makes read_initrd() called directly from setup_arch()
> after init_bootmem() and mem_total_pages().
Masami,
Am 27.04.2017 um 05:15 schrieb Masami Hiramatsu:
> Since read_initrd() invokes alloc_bootmem() for allocating
> memory to load initrd image, it must be called after init_bootmem.
>
> This makes read_initrd() called directly from setup_arch()
> after init_bootmem() and mem_total_pages().
On 04/13/2017 05:49 PM, SeongJae Park wrote:
> A comment in `run_vmtests` is wrong because it is saying `128MB + 128MB
> == 258MB`. This commit fixes the comment.
>
> Signed-off-by: SeongJae Park
> ---
> tools/testing/selftests/vm/run_vmtests | 2 +-
> 1 file changed, 1
On 04/13/2017 05:49 PM, SeongJae Park wrote:
> A comment in `run_vmtests` is wrong because it is saying `128MB + 128MB
> == 258MB`. This commit fixes the comment.
>
> Signed-off-by: SeongJae Park
> ---
> tools/testing/selftests/vm/run_vmtests | 2 +-
> 1 file changed, 1 insertion(+), 1
On 04/13/2017 05:47 PM, SeongJae Park wrote:
> `selftests/Makefile` is defining only `install` as entire PHONY target
> though there are few more PHONY targets including `run_tests`. This
> commit defines them as the PHONY targets.
>
> Signed-off-by: SeongJae Park
> ---
>
On 04/13/2017 05:47 PM, SeongJae Park wrote:
> `selftests/Makefile` is defining only `install` as entire PHONY target
> though there are few more PHONY targets including `run_tests`. This
> commit defines them as the PHONY targets.
>
> Signed-off-by: SeongJae Park
> ---
>
On 04/13/2017 05:43 PM, SeongJae Park wrote:
> A comment for make command usage in `selftets/Makefile` has opening `"`
> but no closing `"`. This commit adds the missed `"` in the comment.
>
> Signed-off-by: SeongJae Park
> ---
> tools/testing/selftests/Makefile | 2 +-
>
On 04/13/2017 05:43 PM, SeongJae Park wrote:
> A comment for make command usage in `selftets/Makefile` has opening `"`
> but no closing `"`. This commit adds the missed `"` in the comment.
>
> Signed-off-by: SeongJae Park
> ---
> tools/testing/selftests/Makefile | 2 +-
> 1 file changed, 1
On 04/19/2017 11:32 AM, Fathi Boudra wrote:
> gentle ping
>
> On 4 April 2017 at 03:52, Bamvor Zhang Jian
> wrote:
>> Hi,
>>
>> On 31 March 2017 at 16:41, Fathi Boudra wrote:
>>> The gpio test requires to insert the gpio mockup module
>>>
On 04/19/2017 11:32 AM, Fathi Boudra wrote:
> gentle ping
>
> On 4 April 2017 at 03:52, Bamvor Zhang Jian
> wrote:
>> Hi,
>>
>> On 31 March 2017 at 16:41, Fathi Boudra wrote:
>>> The gpio test requires to insert the gpio mockup module
>>> (CONFIG_GPIO_MOCKUP).
>>> The gpio mockup driver
Dan Williams writes:
> On Wed, Apr 26, 2017 at 1:38 PM, Jeff Moyer wrote:
>> Dan Williams writes:
>>
>>> The nvdimm_flush() mechanism helps to reduce the impact of an ADR
>>> (asynchronous-dimm-refresh) failure. The ADR
Dan Williams writes:
> On Wed, Apr 26, 2017 at 1:38 PM, Jeff Moyer wrote:
>> Dan Williams writes:
>>
>>> The nvdimm_flush() mechanism helps to reduce the impact of an ADR
>>> (asynchronous-dimm-refresh) failure. The ADR mechanism handles flushing
>>> platform WPQ (write-pending-queue) buffers
On 04/19/2017 11:31 AM, Fathi Boudra wrote:
> gentle ping
>
> On 22 March 2017 at 20:04, Fathi Boudra wrote:
>> To build breakpoint_test_arm64, ARCH value is only tested for "aarch64".
>> It covers only the native build because it's computed from uname -m output.
>> For
On 04/19/2017 11:31 AM, Fathi Boudra wrote:
> gentle ping
>
> On 22 March 2017 at 20:04, Fathi Boudra wrote:
>> To build breakpoint_test_arm64, ARCH value is only tested for "aarch64".
>> It covers only the native build because it's computed from uname -m output.
>> For cross-compilation, ARCH
On Wed 26-04-17 18:29:08, Igor Stoppa wrote:
[...]
> If you prefer to have this patch only as part of the larger patchset,
> I'm also fine with it.
I agree that the situation is not ideal. If a larger set of changes
would benefit from this change then it would clearly add arguments...
> Also, if
On Wed 26-04-17 18:29:08, Igor Stoppa wrote:
[...]
> If you prefer to have this patch only as part of the larger patchset,
> I'm also fine with it.
I agree that the situation is not ideal. If a larger set of changes
would benefit from this change then it would clearly add arguments...
> Also, if
On 27.04.17 17:16:21, Geetha sowjanya wrote:
> From: Geetha
>
> Cavium CN99xx SMMUv3 implementation has two Silicon Erratas.
> 1. Errata ID #74
>SMMU register alias Page 1 is not implemented
> 2. Errata ID #126
>SMMU doesnt support unique IRQ lines for gerror, eventq
On 27.04.17 17:16:21, Geetha sowjanya wrote:
> From: Geetha
>
> Cavium CN99xx SMMUv3 implementation has two Silicon Erratas.
> 1. Errata ID #74
>SMMU register alias Page 1 is not implemented
> 2. Errata ID #126
>SMMU doesnt support unique IRQ lines for gerror, eventq and cmdq-sync
>
>
On Mon 2017-04-24 11:17:47, Sergey Senozhatsky wrote:
> On (04/21/17 14:06), Petr Mladek wrote:
> [..]
> > > I agree that this_cpu_read(printk_context) covers slightly more than
> > > logbuf_lock scope, so we may get positive this_cpu_read(printk_context)
> > > with unlocked logbuf_lock, but I
On Mon 2017-04-24 11:17:47, Sergey Senozhatsky wrote:
> On (04/21/17 14:06), Petr Mladek wrote:
> [..]
> > > I agree that this_cpu_read(printk_context) covers slightly more than
> > > logbuf_lock scope, so we may get positive this_cpu_read(printk_context)
> > > with unlocked logbuf_lock, but I
On Thu, Apr 27, 2017 at 03:12:34PM +0800, Huang, Ying wrote:
> Minchan Kim writes:
> > On Tue, Apr 25, 2017 at 08:56:56PM +0800, Huang, Ying wrote:
> >> @@ -178,20 +192,12 @@ int add_to_swap(struct page *page, struct list_head
> >> *list)
> >>
On Thu, Apr 27, 2017 at 03:12:34PM +0800, Huang, Ying wrote:
> Minchan Kim writes:
> > On Tue, Apr 25, 2017 at 08:56:56PM +0800, Huang, Ying wrote:
> >> @@ -178,20 +192,12 @@ int add_to_swap(struct page *page, struct list_head
> >> *list)
> >>VM_BUG_ON_PAGE(!PageLocked(page), page);
> >>
On Thu 27-04-17 15:16:47, Igor Stoppa wrote:
> On 26/04/17 18:29, Igor Stoppa wrote:
>
> > On 26/04/17 17:47, Michal Hocko wrote:
>
> [...]
>
> >> Also the current mm tree has ___GFP_NOLOCKDEP which is not addressed
> >> here so I suspect you have based your change on the Linus tree.
>
> > I
On Thu 27-04-17 15:16:47, Igor Stoppa wrote:
> On 26/04/17 18:29, Igor Stoppa wrote:
>
> > On 26/04/17 17:47, Michal Hocko wrote:
>
> [...]
>
> >> Also the current mm tree has ___GFP_NOLOCKDEP which is not addressed
> >> here so I suspect you have based your change on the Linus tree.
>
> > I
Hi,
On 4/26/2017 9:45 PM, Ralph Sennhauser wrote:
> Hi Sricharan R,
>
> Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time
> for platform/amba/pci bus devices") causes a kernel panic as in the log
> below on an armada-385. Reverting the commit fixes the issue.
>
> Regards
>
Hi,
On 4/26/2017 9:45 PM, Ralph Sennhauser wrote:
> Hi Sricharan R,
>
> Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time
> for platform/amba/pci bus devices") causes a kernel panic as in the log
> below on an armada-385. Reverting the commit fixes the issue.
>
> Regards
>
Hello Alexandre,
This series might also be of interest for the linux-pm mailing list.
2017-04-26 18:04 GMT+02:00 Alexandre Belloni
:
> The sama5d2 has a mode were it is possible to cut power to the SoC while
> keeping the RAM in self refresh.
> Resuming from
Hello Alexandre,
This series might also be of interest for the linux-pm mailing list.
2017-04-26 18:04 GMT+02:00 Alexandre Belloni
:
> The sama5d2 has a mode were it is possible to cut power to the SoC while
> keeping the RAM in self refresh.
> Resuming from that mode needs support in the
On Thu, 2017-04-27 at 13:21 +, Eugeniy Paltsev wrote:
> On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote:
> > On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote:
> > > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote:
> > > > On Mon, 2017-04-24 at 19:56 +0300, Andy
On Thu, 2017-04-27 at 13:21 +, Eugeniy Paltsev wrote:
> On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote:
> > On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote:
> > > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote:
> > > > On Mon, 2017-04-24 at 19:56 +0300, Andy
Devices, like stm32 timer, could be triggered by hardware events which
are not buffer or software events. However it could be necessary to
validate the triggers like it is done for buffer or event triggered modes.
This patch add a new INDIO_HARDWARE_TRIGGERED operating mode for this
kind of
Devices, like stm32 timer, could be triggered by hardware events which
are not buffer or software events. However it could be necessary to
validate the triggers like it is done for buffer or event triggered modes.
This patch add a new INDIO_HARDWARE_TRIGGERED operating mode for this
kind of
Add validate function to be use to use the correct trigger.
Add an attribute to configure device mode like for quadrature and
enable modes
Signed-off-by: Benjamin Gaignard
---
.../ABI/testing/sysfs-bus-iio-timer-stm32 | 15 ++
Add validate function to be use to use the correct trigger.
Add an attribute to configure device mode like for quadrature and
enable modes
Signed-off-by: Benjamin Gaignard
---
.../ABI/testing/sysfs-bus-iio-timer-stm32 | 15 ++
drivers/iio/trigger/stm32-timer-trigger.c | 61
Those patches aim to complete stm32 timer features support.
The last missing part is to be able to chain to timer blocks
which mean that one of timerX's trigger could be used as clock for timerY.
Since this operating is neither event or buffer triggered mode I would
like to introduce a hardware
Those patches aim to complete stm32 timer features support.
The last missing part is to be able to chain to timer blocks
which mean that one of timerX's trigger could be used as clock for timerY.
Since this operating is neither event or buffer triggered mode I would
like to introduce a hardware
On Wed, Apr 26, 2017 at 11:20:14PM +0800, Icenowy Zheng wrote:
> Allwinner A64 have a RSB controller like the one on A23/A33 SoCs.
>
> Add it and its pinmux.
>
> Signed-off-by: Icenowy Zheng
> Acked-by: Chen-Yu Tsai
> ---
> Changes in v2:
> - Removed bonus
On Wed, Apr 26, 2017 at 11:20:14PM +0800, Icenowy Zheng wrote:
> Allwinner A64 have a RSB controller like the one on A23/A33 SoCs.
>
> Add it and its pinmux.
>
> Signed-off-by: Icenowy Zheng
> Acked-by: Chen-Yu Tsai
> ---
> Changes in v2:
> - Removed bonus properties in pio node.
> - Added
Am 27.04.2017 um 14:50 schrieb Jean Delvare:
> On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote:
>> From: Markus Elfring
>> Date: Thu, 27 Apr 2017 11:18:22 +0200
>>
>> A few update suggestions were taken into account
>> from static source code analysis.
Am 27.04.2017 um 14:50 schrieb Jean Delvare:
> On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote:
>> From: Markus Elfring
>> Date: Thu, 27 Apr 2017 11:18:22 +0200
>>
>> A few update suggestions were taken into account
>> from static source code analysis.
>>
>> Markus Elfring (4):
>>
On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote:
> On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote:
> > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote:
> > > On Mon, 2017-04-24 at 19:56 +0300, Andy Shevchenko wrote:
> > > > On Mon, 2017-04-24 at 15:55 +, Eugeniy
On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote:
> On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote:
> > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote:
> > > On Mon, 2017-04-24 at 19:56 +0300, Andy Shevchenko wrote:
> > > > On Mon, 2017-04-24 at 15:55 +, Eugeniy
> Also, this code in drop_other_mm_ref() looks dubious to me:
>
> /* If this cpu still has a stale cr3 reference, then make sure
>it has been flushed. */
> if (this_cpu_read(xen_current_cr3) == __pa(mm->pgd))
> load_cr3(swapper_pg_dir);
>
> Also, this code in drop_other_mm_ref() looks dubious to me:
>
> /* If this cpu still has a stale cr3 reference, then make sure
>it has been flushed. */
> if (this_cpu_read(xen_current_cr3) == __pa(mm->pgd))
> load_cr3(swapper_pg_dir);
>
On Thu, Apr 27, 2017 at 4:07 AM, Rusty Russell wrote:
> Djalal Harouni writes:
>> Hi Rusty,
>>
>> On Mon, Apr 24, 2017 at 6:29 AM, Rusty Russell wrote:
>>> Djalal Harouni writes:
When value is (1), task must
On Thu, Apr 27, 2017 at 4:07 AM, Rusty Russell wrote:
> Djalal Harouni writes:
>> Hi Rusty,
>>
>> On Mon, Apr 24, 2017 at 6:29 AM, Rusty Russell wrote:
>>> Djalal Harouni writes:
When value is (1), task must have CAP_SYS_MODULE to be able to trigger a
module auto-load operation, or
On Thu, Apr 27, 2017 at 02:04:15PM +0200, Arnd Bergmann wrote:
> On Thu, Apr 27, 2017 at 1:55 PM, Leon Romanovsky wrote:
> > On Thu, Apr 27, 2017 at 01:04:02PM +0200, Arnd Bergmann wrote:
> >> The previous patch addressed a sparse warning but replaced it with a
> >> compiler
On Thu, Apr 27, 2017 at 02:04:15PM +0200, Arnd Bergmann wrote:
> On Thu, Apr 27, 2017 at 1:55 PM, Leon Romanovsky wrote:
> > On Thu, Apr 27, 2017 at 01:04:02PM +0200, Arnd Bergmann wrote:
> >> The previous patch addressed a sparse warning but replaced it with a
> >> compiler warning when
On Thu, Apr 27, 2017 at 03:00:29PM +0800, Mark yao wrote:
> On 2017年04月27日 14:54, Jeffy Chen wrote:
> > We need to set vop config done after update line flag config, it's a
> > new requirement for chips newer than rk3368.
> >
> > Since we would only use line flag irq for vact_end, let's move it
On Thu, Apr 27, 2017 at 03:00:29PM +0800, Mark yao wrote:
> On 2017年04月27日 14:54, Jeffy Chen wrote:
> > We need to set vop config done after update line flag config, it's a
> > new requirement for chips newer than rk3368.
> >
> > Since we would only use line flag irq for vact_end, let's move it
On Thu, 2017-04-27 at 14:46 +0200, Borislav Petkov wrote:
> On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote:
> > > #ifdef CONFIG_ACPI_APEI_PCIEAER
> > > - else if (!uuid_le_cmp(*(uuid_le *)gdata-
> > > >section_type,
> > > - CPER_SEC_PCIE))
On Thu, 2017-04-27 at 14:46 +0200, Borislav Petkov wrote:
> On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote:
> > > #ifdef CONFIG_ACPI_APEI_PCIEAER
> > > - else if (!uuid_le_cmp(*(uuid_le *)gdata-
> > > >section_type,
> > > - CPER_SEC_PCIE))
Replace all the parts of register polling code with
dwc2_hsotg_wait_bit_set function calls.
Signed-off-by: Sevak Arakelyan
---
drivers/usb/dwc2/core.c | 61 +--
drivers/usb/dwc2/gadget.c | 24 ---
Replace all the parts of register polling code with
dwc2_hsotg_wait_bit_set function calls.
Signed-off-by: Sevak Arakelyan
---
drivers/usb/dwc2/core.c | 61 +--
drivers/usb/dwc2/gadget.c | 24 ---
drivers/usb/dwc2/hcd.c| 18
Move polling function to core.c so it can be used
anywhere in the code.
Signed-off-by: Sevak Arakelyan
---
drivers/usb/dwc2/core.c | 23 +++
drivers/usb/dwc2/core.h | 4
drivers/usb/dwc2/gadget.c | 14 --
3 files changed, 27
Move polling function to core.c so it can be used
anywhere in the code.
Signed-off-by: Sevak Arakelyan
---
drivers/usb/dwc2/core.c | 23 +++
drivers/usb/dwc2/core.h | 4
drivers/usb/dwc2/gadget.c | 14 --
3 files changed, 27 insertions(+), 14
This series moves dwc2_hsotg_wait_bit_set polling function to core.c and
replaces all the
register polling parts of code with function calls
Tested on HAPS platform with DWC_hsotg IP version 3.30a.
Sevak Arakelyan (2):
usb: dwc2: Move polling function to core.c.
usb: dwc2: Use common
This series moves dwc2_hsotg_wait_bit_set polling function to core.c and
replaces all the
register polling parts of code with function calls
Tested on HAPS platform with DWC_hsotg IP version 3.30a.
Sevak Arakelyan (2):
usb: dwc2: Move polling function to core.c.
usb: dwc2: Use common
On Thu, Apr 27, 2017 at 5:16 PM, Geetha sowjanya
wrote:
> From: Geetha
>
> Add MIDR values for Cavium cn99xx SoCs
>
> Signed-off-by: Geetha
> ---
> arch/arm64/include/asm/cputype.h | 3 +++
> 1 file changed, 3 insertions(+)
>
>
On Thu, Apr 27, 2017 at 5:16 PM, Geetha sowjanya
wrote:
> From: Geetha
>
> Add MIDR values for Cavium cn99xx SoCs
>
> Signed-off-by: Geetha
> ---
> arch/arm64/include/asm/cputype.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/include/asm/cputype.h
>
On 04/27/2017 08:30 PM, Steven Rostedt wrote:
On Thu, 27 Apr 2017 11:52:14 +0900
Taeung Song wrote:
On 04/27/2017 11:47 AM, Steven Rostedt wrote:
On Thu, 27 Apr 2017 08:46:21 +0900
Taeung Song wrote:
Even though PyRun_String() failed,
On 04/27/2017 08:30 PM, Steven Rostedt wrote:
On Thu, 27 Apr 2017 11:52:14 +0900
Taeung Song wrote:
On 04/27/2017 11:47 AM, Steven Rostedt wrote:
On Thu, 27 Apr 2017 08:46:21 +0900
Taeung Song wrote:
Even though PyRun_String() failed,
just 0 will be returned but we need to return -1
On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 27 Apr 2017 11:18:22 +0200
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (4):
> Use devm_kcalloc() in
On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 27 Apr 2017 11:18:22 +0200
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (4):
> Use devm_kcalloc() in nct6683_create_attr_group()
>
On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote:
> > #ifdef CONFIG_ACPI_APEI_PCIEAER
> > - else if (!uuid_le_cmp(*(uuid_le *)gdata->section_type,
> > - CPER_SEC_PCIE)) {
> > + else if (!uuid_le_cmp_p(sec_type, CPER_SEC_PCIE)) {
On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote:
> > #ifdef CONFIG_ACPI_APEI_PCIEAER
> > - else if (!uuid_le_cmp(*(uuid_le *)gdata->section_type,
> > - CPER_SEC_PCIE)) {
> > + else if (!uuid_le_cmp_p(sec_type, CPER_SEC_PCIE)) {
On Thu 2017-04-27 14:30:05, Jiri Slaby wrote:
> Hi,
>
> On 04/27/2017, 01:53 PM, Pavel Machek wrote:
> >> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel)
> >>
> >> .data
> >> ALIGN
> >> -ENTRY(saved_magic).long 0
> >> -ENTRY(saved_eip) .long 0
> >> +SYM_DATA_SIMPLE(saved_magic,
On Thu 2017-04-27 14:30:05, Jiri Slaby wrote:
> Hi,
>
> On 04/27/2017, 01:53 PM, Pavel Machek wrote:
> >> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel)
> >>
> >> .data
> >> ALIGN
> >> -ENTRY(saved_magic).long 0
> >> -ENTRY(saved_eip) .long 0
> >> +SYM_DATA_SIMPLE(saved_magic,
Change to use different bits of cpc->reason to indicate different status,
so cpc->reason can indicate more than one reason.
Signed-off-by: Chao Yu
---
fs/f2fs/checkpoint.c | 14 +++---
fs/f2fs/f2fs.h | 16 +++-
fs/f2fs/segment.c| 8
3
Change to use different bits of cpc->reason to indicate different status,
so cpc->reason can indicate more than one reason.
Signed-off-by: Chao Yu
---
fs/f2fs/checkpoint.c | 14 +++---
fs/f2fs/f2fs.h | 16 +++-
fs/f2fs/segment.c| 8
3 files changed, 18
On 27 April 2017 at 13:46, Bryan O'Donoghue
wrote:
> On 25/04/17 16:08, Ard Biesheuvel wrote:
>>
>> On 25 April 2017 at 16:07, Bryan O'Donoghue
>>>
>>> I'm OOO until Thursday however, I could test this out on a Galileo for
>>> you with the CSH stripped out. As Jan
On 27 April 2017 at 13:46, Bryan O'Donoghue
wrote:
> On 25/04/17 16:08, Ard Biesheuvel wrote:
>>
>> On 25 April 2017 at 16:07, Bryan O'Donoghue
>>>
>>> I'm OOO until Thursday however, I could test this out on a Galileo for
>>> you with the CSH stripped out. As Jan has pointed out Galileo aka
Introduce CP_TRIMMED_FLAG to indicate all invalid block were trimmed
before umount, so once we do mount with image which contain the flag,
we don't record invalid blocks as undiscard one, when fstrim is being
triggered, we can avoid issuing redundant discard commands.
Signed-off-by: Chao Yu
Introduce CP_TRIMMED_FLAG to indicate all invalid block were trimmed
before umount, so once we do mount with image which contain the flag,
we don't record invalid blocks as undiscard one, when fstrim is being
triggered, we can avoid issuing redundant discard commands.
Signed-off-by: Chao Yu
---
On 25/04/17 16:08, Ard Biesheuvel wrote:
On 25 April 2017 at 16:07, Bryan O'Donoghue
I'm OOO until Thursday however, I could test this out on a Galileo for
you with the CSH stripped out. As Jan has pointed out Galileo aka Quark
x1000 non-secure (not to be called insecure) will just skips past
On 25/04/17 16:08, Ard Biesheuvel wrote:
On 25 April 2017 at 16:07, Bryan O'Donoghue
I'm OOO until Thursday however, I could test this out on a Galileo for
you with the CSH stripped out. As Jan has pointed out Galileo aka Quark
x1000 non-secure (not to be called insecure) will just skips past
On Thu, Apr 27, 2017 at 07:44:00AM +0200, Mike Galbraith wrote:
> On Wed, 2017-04-26 at 22:32 -0700, Paul E. McKenney wrote:
> > On Thu, Apr 27, 2017 at 06:15:56AM +0200, Mike Galbraith wrote:
> > > On Wed, 2017-04-26 at 21:11 -0700, Paul E. McKenney wrote:
> > >
> > > > This is with
On Thu, Apr 27, 2017 at 07:44:00AM +0200, Mike Galbraith wrote:
> On Wed, 2017-04-26 at 22:32 -0700, Paul E. McKenney wrote:
> > On Thu, Apr 27, 2017 at 06:15:56AM +0200, Mike Galbraith wrote:
> > > On Wed, 2017-04-26 at 21:11 -0700, Paul E. McKenney wrote:
> > >
> > > > This is with
On Tue, Apr 25, 2017 at 6:36 PM, Jingoo Han wrote:
> On Monday, April 24, 2017 1:56 PM, Olimpiu Dejeu wrote:
>>
>> On Mon, April 24, 2017 11:10 AM, Rob Herring < r...@kernel.org> wrote:
>>
>> > On Wed, Mar 15, 2017 at 2:45 PM, Olimpiu Dejeu
>> wrote:
On Tue, Apr 25, 2017 at 6:36 PM, Jingoo Han wrote:
> On Monday, April 24, 2017 1:56 PM, Olimpiu Dejeu wrote:
>>
>> On Mon, April 24, 2017 11:10 AM, Rob Herring < r...@kernel.org> wrote:
>>
>> > On Wed, Mar 15, 2017 at 2:45 PM, Olimpiu Dejeu
>> wrote:
>> >> backlight: Add arc to vendor prefixes
On 26/04/2017 22:32, Radim Krčmář wrote:
> v2: replaces [v1 1/6]
> Ugh, KVM_ARCH_REQ_WAIT_NO_WAKEUP looks a weird ...
Yeah, let's drop patch 7 and just use bits for now. I think using
KVM_ARCH_REQ_FLAGS directly should be fine, especially after the default
is flipped from "no wakeup" to
On 26/04/2017 22:32, Radim Krčmář wrote:
> v2: replaces [v1 1/6]
> Ugh, KVM_ARCH_REQ_WAIT_NO_WAKEUP looks a weird ...
Yeah, let's drop patch 7 and just use bits for now. I think using
KVM_ARCH_REQ_FLAGS directly should be fine, especially after the default
is flipped from "no wakeup" to
> > Which is the sudo case and why sudo uses a separate pty/tty pair as it's
> > not just TIOCSTI that's an issue but there are a load of ioctls that do
> > things like cause signals to the process or are just annoying -
> > vhangup(), changing the speed etc
> >
> > (And for console changing the
> > Which is the sudo case and why sudo uses a separate pty/tty pair as it's
> > not just TIOCSTI that's an issue but there are a load of ioctls that do
> > things like cause signals to the process or are just annoying -
> > vhangup(), changing the speed etc
> >
> > (And for console changing the
On arm32, the machine model specified in the device tree is printed
during boot-up, courtesy of of_flat_dt_match_machine().
On arm64, of_flat_dt_match_machine() is not called, and the machine
model information is not available from the kernel log.
Print the machine model to make it easier to
Hi Andrzej,
Thanks for your answer!
On 27-04-2017 11:05, Andrzej Hajda wrote:
> Hi Jose,
>
> On 26.04.2017 12:48, Jose Abreu wrote:
>> Some crtc's may have restrictions in the mode they can display. In
>> this patch a new callback (crtc->mode_valid()) is introduced that
>> is called at the
On arm32, the machine model specified in the device tree is printed
during boot-up, courtesy of of_flat_dt_match_machine().
On arm64, of_flat_dt_match_machine() is not called, and the machine
model information is not available from the kernel log.
Print the machine model to make it easier to
Hi Andrzej,
Thanks for your answer!
On 27-04-2017 11:05, Andrzej Hajda wrote:
> Hi Jose,
>
> On 26.04.2017 12:48, Jose Abreu wrote:
>> Some crtc's may have restrictions in the mode they can display. In
>> this patch a new callback (crtc->mode_valid()) is introduced that
>> is called at the
On implementing of nested pid namespaces support in CRIU
(checkpoint-restore in userspace tool) we run into
the situation, that it's impossible to create a task with
specific NSpid effectively. After commit 49f4d8b93ccf
"pidns: Capture the user namespace and filter ns_last_pid"
it is impossible to
On implementing of nested pid namespaces support in CRIU
(checkpoint-restore in userspace tool) we run into
the situation, that it's impossible to create a task with
specific NSpid effectively. After commit 49f4d8b93ccf
"pidns: Capture the user namespace and filter ns_last_pid"
it is impossible to
On Thu, Apr 27, 2017 at 12:01:57PM +0200, Thomas Gleixner wrote:
> On Thu, 27 Apr 2017, Mark Rutland wrote:
>
> > On Thu, Apr 27, 2017 at 10:27:20AM +0200, Sebastian Siewior wrote:
> > > On 2017-04-26 11:32:36 [+0100], Mark Rutland wrote:
> > > > > So we could end up calling
On Thu, Apr 27, 2017 at 12:01:57PM +0200, Thomas Gleixner wrote:
> On Thu, 27 Apr 2017, Mark Rutland wrote:
>
> > On Thu, Apr 27, 2017 at 10:27:20AM +0200, Sebastian Siewior wrote:
> > > On 2017-04-26 11:32:36 [+0100], Mark Rutland wrote:
> > > > > So we could end up calling
Hi,
On 04/27/2017, 01:53 PM, Pavel Machek wrote:
>> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel)
>>
>> .data
>> ALIGN
>> -ENTRY(saved_magic) .long 0
>> -ENTRY(saved_eip).long 0
>> +SYM_DATA_SIMPLE(saved_magic, .long 0)
>> +SYM_DATA_SIMPLE_LOCAL(saved_eip, .long 0)
>>
>> #
Hi,
On 04/27/2017, 01:53 PM, Pavel Machek wrote:
>> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel)
>>
>> .data
>> ALIGN
>> -ENTRY(saved_magic) .long 0
>> -ENTRY(saved_eip).long 0
>> +SYM_DATA_SIMPLE(saved_magic, .long 0)
>> +SYM_DATA_SIMPLE_LOCAL(saved_eip, .long 0)
>>
>> #
We now have a few of this device's definitions. Let's avoid magic numbers
and use them.
Signed-off-by: Martin Kepplinger
---
drivers/input/touchscreen/ar1021_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
We now have a few of this device's definitions. Let's avoid magic numbers
and use them.
Signed-off-by: Martin Kepplinger
---
drivers/input/touchscreen/ar1021_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/ar1021_i2c.c
The device could as well be in command mode, in which this driver cannot
handle the device. When opening the device, let's make sure the device
will be in the mode we expect it to be for this driver.
Signed-off-by: Martin Kepplinger
---
The device could as well be in command mode, in which this driver cannot
handle the device. When opening the device, let's make sure the device
will be in the mode we expect it to be for this driver.
Signed-off-by: Martin Kepplinger
---
drivers/input/touchscreen/ar1021_i2c.c | 15
901 - 1000 of 1396 matches
Mail list logo