Hi Corey,
On 08/24/2018 06:38 PM, Corey Minyard wrote:
On 08/24/2018 06:10 AM, George Cherian wrote:
Dont set ssif_info->intf to NULL before ipmi_unresgiter_smi.
shutdown_ssif will anyways free ssif_info.
This is correct, but it goes a little deeper. I just sent out a
patch yesterday
Hi Corey,
On 08/24/2018 06:38 PM, Corey Minyard wrote:
On 08/24/2018 06:10 AM, George Cherian wrote:
Dont set ssif_info->intf to NULL before ipmi_unresgiter_smi.
shutdown_ssif will anyways free ssif_info.
This is correct, but it goes a little deeper. I just sent out a
patch yesterday
On 08/07/18 at 02:50pm, Chao Fan wrote:
> If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
If CONFIG_MEMORY_HOTREMOVE is enabled,
> memory regions is not zero. Calculate the intersection between memory
> regions from e820/efi memory table and immovable memory regions.
> Or go
On 08/07/18 at 02:50pm, Chao Fan wrote:
> If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
If CONFIG_MEMORY_HOTREMOVE is enabled,
> memory regions is not zero. Calculate the intersection between memory
> regions from e820/efi memory table and immovable memory regions.
> Or go
On 22-08-18, 10:40, Huang Shijie wrote:
> The following patch introduced an issue.
> commit f6206f00d8c5 ("dmaengine: mic_x100_dma: use the new helper to
> simplify the code")
>
> This issue is :
>
> kfree(mic_dma_dev)
> .
>
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
Remove the workaround code.
It was the only user of cc-if-fullversion. Remove the macro as well.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile | 12
On 22-08-18, 10:40, Huang Shijie wrote:
> The following patch introduced an issue.
> commit f6206f00d8c5 ("dmaengine: mic_x100_dma: use the new helper to
> simplify the code")
>
> This issue is :
>
> kfree(mic_dma_dev)
> .
>
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
Remove the workaround code.
It was the only user of cc-if-fullversion. Remove the macro as well.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile | 12
On 08/07/18 at 02:50pm, Chao Fan wrote:
> If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
> memory regions is not zero. Calculate the intersection between memory
> regions from e820/efi memory table and immovable memory regions.
> Or go on the old code.
>
> Rename
On 08/07/18 at 02:50pm, Chao Fan wrote:
> If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
> memory regions is not zero. Calculate the intersection between memory
> regions from e820/efi memory table and immovable memory regions.
> Or go on the old code.
>
> Rename
Thanks Axel,
On Fri, Aug 24, 2018 at 07:16:12PM +0800, Axel Lin wrote:
> Set it once is enough.
> Also move n_voltages close to volt_table for better readability.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/bd71837-regulator.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Thanks Axel,
On Fri, Aug 24, 2018 at 07:16:12PM +0800, Axel Lin wrote:
> Set it once is enough.
> Also move n_voltages close to volt_table for better readability.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/bd71837-regulator.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
On 02-08-18, 16:10, Andrea Merello wrote:
> The AXIDMA and CDMA HW can be either direct-access or scatter-gather
> version. These are SW incompatible.
>
> The driver can handle both versions: a DT property was used to
> tell the driver whether to assume the HW is in scatter-gather mode.
>
> This
On 02-08-18, 16:10, Andrea Merello wrote:
> The AXIDMA and CDMA HW can be either direct-access or scatter-gather
> version. These are SW incompatible.
>
> The driver can handle both versions: a DT property was used to
> tell the driver whether to assume the HW is in scatter-gather mode.
>
> This
On 02-08-18, 16:10, Andrea Merello wrote:
> The width of the "length register" cannot be autodetected, and it is now
> specified with a DT property. Add DOC for it.
Add Documentation for it...
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Cc: Radhey Shyam Pandey
>
On 02-08-18, 16:10, Andrea Merello wrote:
> The width of the "length register" cannot be autodetected, and it is now
> specified with a DT property. Add DOC for it.
Add Documentation for it...
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Cc: Radhey Shyam Pandey
>
On 02-08-18, 16:10, Andrea Merello wrote:
s/cylic/cyclic in patch title
> Whenever a single or cyclic transaction is prepared, the driver
> could eventually split it over several SG descriptors in order
> to deal with the HW maximum transfer length.
>
> This could end up in DMA operations
On 02-08-18, 16:10, Andrea Merello wrote:
s/cylic/cyclic in patch title
> Whenever a single or cyclic transaction is prepared, the driver
> could eventually split it over several SG descriptors in order
> to deal with the HW maximum transfer length.
>
> This could end up in DMA operations
syzbot wrote on Sun, Aug 26, 2018:
> HEAD commit:e27bc174c9c6 Add linux-next specific files for 20180824
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15dc19a640
> kernel config: https://syzkaller.appspot.com/x/.config?x=28446088176757ea
>
syzbot wrote on Sun, Aug 26, 2018:
> HEAD commit:e27bc174c9c6 Add linux-next specific files for 20180824
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15dc19a640
> kernel config: https://syzkaller.appspot.com/x/.config?x=28446088176757ea
>
On Mon, Aug 27, 2018 at 09:30:45AM +0530, Naresh Kamboju wrote:
> On 26 August 2018 at 12:12, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.4.153 release.
> > There are 5 patches in this series, all will be posted as a response
> > to this one. If anyone
On Mon, Aug 27, 2018 at 09:30:45AM +0530, Naresh Kamboju wrote:
> On 26 August 2018 at 12:12, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.4.153 release.
> > There are 5 patches in this series, all will be posted as a response
> > to this one. If anyone
On 07-08-18, 13:42, Paul Cercueil wrote:
> Hi,
>
> This is the V4 of my Ingenic JZ47xx DMA patchset.
This does not apply for me. Please rebase on rc1, fix Rob's and my
comment and send
Also I noticed checkpatch gave warns on some style issues (--strict
option) please see if they make sense and
On 07-08-18, 13:42, Paul Cercueil wrote:
> Hi,
>
> This is the V4 of my Ingenic JZ47xx DMA patchset.
This does not apply for me. Please rebase on rc1, fix Rob's and my
comment and send
Also I noticed checkpatch gave warns on some style issues (--strict
option) please see if they make sense and
i have been trying to contact you
i have been trying to contact you
Hi Pavel,
On Sunday, August 26, 2018 3:52 PM, Pavel Machek wrote:
>
> > +++ b/Documentation/devicetree/bindings/input/dlg,da7280.txt
> > @@ -0,0 +1,101 @@
> > +Dialog Semiconductor DA7280 Haptics bindings
> > +
> > +Required properties:
> > +- compatible: Should be "dlg,da7280".
> > +- reg:
Hi Pavel,
On Sunday, August 26, 2018 3:52 PM, Pavel Machek wrote:
>
> > +++ b/Documentation/devicetree/bindings/input/dlg,da7280.txt
> > @@ -0,0 +1,101 @@
> > +Dialog Semiconductor DA7280 Haptics bindings
> > +
> > +Required properties:
> > +- compatible: Should be "dlg,da7280".
> > +- reg:
On 07-08-18, 13:42, Paul Cercueil wrote:
> From: Daniel Silsby
>
> The 'dtc' word in jz DMA descriptors contains two fields: The
> lowest 24 bits are the transfer count, and upper 8 bits are the DOA
> offset to next descriptor. The upper 8 bits are now correctly masked
> off when computing
On 07-08-18, 13:42, Paul Cercueil wrote:
> From: Daniel Silsby
>
> The 'dtc' word in jz DMA descriptors contains two fields: The
> lowest 24 bits are the transfer count, and upper 8 bits are the DOA
> offset to next descriptor. The upper 8 bits are now correctly masked
> off when computing
On Fri, 24 Aug 2018 13:39:53 +0200
Peter Zijlstra wrote:
> On Fri, Aug 24, 2018 at 01:32:14PM +0200, Peter Zijlstra wrote:
> > On Fri, Aug 24, 2018 at 10:47:17AM +0200, Peter Zijlstra wrote:
> > > On Thu, Aug 23, 2018 at 02:39:59PM +0100, Will Deacon wrote:
> > > > The only problem with this
On Fri, 24 Aug 2018 13:39:53 +0200
Peter Zijlstra wrote:
> On Fri, Aug 24, 2018 at 01:32:14PM +0200, Peter Zijlstra wrote:
> > On Fri, Aug 24, 2018 at 10:47:17AM +0200, Peter Zijlstra wrote:
> > > On Thu, Aug 23, 2018 at 02:39:59PM +0100, Will Deacon wrote:
> > > > The only problem with this
On 24-08-18, 08:56, Fabrizio Castro wrote:
> From: Biju Das
>
> This patch adds binding for r8a774a1 (RZ/G2M).
Acked-by: Vinod Koul
--
~Vinod
On 24-08-18, 08:56, Fabrizio Castro wrote:
> From: Biju Das
>
> This patch adds binding for r8a774a1 (RZ/G2M).
Acked-by: Vinod Koul
--
~Vinod
On Fri, 24 Aug 2018 16:52:43 +0100
Will Deacon wrote:
> From: Peter Zijlstra
>
> Some architectures require different TLB invalidation instructions
> depending on whether it is only the last-level of page table being
> changed, or whether there are also changes to the intermediate
>
On Fri, 24 Aug 2018 16:52:43 +0100
Will Deacon wrote:
> From: Peter Zijlstra
>
> Some architectures require different TLB invalidation instructions
> depending on whether it is only the last-level of page table being
> changed, or whether there are also changes to the intermediate
>
On Mon, 27 Aug 2018, Al Viro wrote:
> On Sun, Aug 26, 2018 at 11:35:17PM -0400, Julia Lawall wrote:
>
> > * x = \(kmalloc\|kzalloc\|devm_kmalloc\|devm_kzalloc\)(...)
>
> I can name several you've missed right off the top of my head -
> vmalloc, kvmalloc, kmem_cache_alloc, kmem_cache_zalloc,
On Mon, 27 Aug 2018, Al Viro wrote:
> On Sun, Aug 26, 2018 at 11:35:17PM -0400, Julia Lawall wrote:
>
> > * x = \(kmalloc\|kzalloc\|devm_kmalloc\|devm_kzalloc\)(...)
>
> I can name several you've missed right off the top of my head -
> vmalloc, kvmalloc, kmem_cache_alloc, kmem_cache_zalloc,
Commit 7634ccd2da (libata: maintainership update) added an invalid email
address. Fix that.
Signed-off-by: Baruch Siach
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a5b256b25905..9ae5cdef37a1 100644
--- a/MAINTAINERS
+++
Commit 7634ccd2da (libata: maintainership update) added an invalid email
address. Fix that.
Signed-off-by: Baruch Siach
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a5b256b25905..9ae5cdef37a1 100644
--- a/MAINTAINERS
+++
On Thu, Aug 16, 2018 at 03:28:40PM -0400, Michael Jin wrote:
> Add new device IDs for family 17h models 10h-2fh.
>
> This is required by amd64_edac_mod in order to properly detect PCI
> device functions 0 and 6.
>
> Link: https://lkml.kernel.org/r/20180815114107.29797-1-mikhail@gmail.com
>
On Thu, Aug 16, 2018 at 03:28:40PM -0400, Michael Jin wrote:
> Add new device IDs for family 17h models 10h-2fh.
>
> This is required by amd64_edac_mod in order to properly detect PCI
> device functions 0 and 6.
>
> Link: https://lkml.kernel.org/r/20180815114107.29797-1-mikhail@gmail.com
>
i have been trying to contact you
i have been trying to contact you
On Tue, Aug 21, 2018 at 8:29 PM Stanimir Varbanov
wrote:
>
> Hi Tomasz,
>
> On 08/08/2018 05:55 AM, Tomasz Figa wrote:
> > On Tue, Aug 7, 2018 at 4:37 PM Hans Verkuil wrote:
>
> >>> +7. If all the following conditions are met, the client may resume
> >>> the
> >>> +decoding
On Tue, Aug 21, 2018 at 8:29 PM Stanimir Varbanov
wrote:
>
> Hi Tomasz,
>
> On 08/08/2018 05:55 AM, Tomasz Figa wrote:
> > On Tue, Aug 7, 2018 at 4:37 PM Hans Verkuil wrote:
>
> >>> +7. If all the following conditions are met, the client may resume
> >>> the
> >>> +decoding
On Sun, Aug 26, 2018 at 08:23:48PM +0800, Jacek Tomaka wrote:
> I am trying to get microcode version from user space. Reading it
> from /proc/cpuinfo requires greping/awking to extract the bits of
> information that are readily available in microcode/version.
If the only reason is because you
On Sun, Aug 26, 2018 at 08:23:48PM +0800, Jacek Tomaka wrote:
> I am trying to get microcode version from user space. Reading it
> from /proc/cpuinfo requires greping/awking to extract the bits of
> information that are readily available in microcode/version.
If the only reason is because you
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
'$(call cc-option,-fno-unit-at-a-time)' is now dead code since
'$(cc-version) -lt 0400' is always false.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile.um |
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
'$(call cc-option,-fno-unit-at-a-time)' is now dead code since
'$(cc-version) -lt 0400' is always false.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile.um |
On Sun, Aug 26, 2018 at 11:35:17PM -0400, Julia Lawall wrote:
> * x = \(kmalloc\|kzalloc\|devm_kmalloc\|devm_kzalloc\)(...)
I can name several you've missed right off the top of my head -
vmalloc, kvmalloc, kmem_cache_alloc, kmem_cache_zalloc, variants
with _trace slapped on, and that is not to
On Sun, Aug 26, 2018 at 11:35:17PM -0400, Julia Lawall wrote:
> * x = \(kmalloc\|kzalloc\|devm_kmalloc\|devm_kzalloc\)(...)
I can name several you've missed right off the top of my head -
vmalloc, kvmalloc, kmem_cache_alloc, kmem_cache_zalloc, variants
with _trace slapped on, and that is not to
Hi Philipp,
On Tue, Aug 21, 2018 at 12:34 AM Philipp Zabel wrote:
>
> On Mon, 2018-08-20 at 23:27 +0900, Tomasz Figa wrote:
> [...]
> > +3. Start queuing buffers to ``OUTPUT`` queue containing stream data after
> > > > > > + the seek until a suitable resume point is found.
> > > > > > +
> > >
Hi Philipp,
On Tue, Aug 21, 2018 at 12:34 AM Philipp Zabel wrote:
>
> On Mon, 2018-08-20 at 23:27 +0900, Tomasz Figa wrote:
> [...]
> > +3. Start queuing buffers to ``OUTPUT`` queue containing stream data after
> > > > > > + the seek until a suitable resume point is found.
> > > > > > +
> > >
---
kernel: 4.4.153-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git branch: 4.4.153-rc1-hikey-20180826-270
git commit: 1d9b202cd56188353c13a49bf48f3f97383984ee
git describe: 4.4.153-rc1-hikey-20180826-270
Test details:
https://qa-reports.linaro.org/lkft/linaro
---
kernel: 4.4.153-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git branch: 4.4.153-rc1-hikey-20180826-270
git commit: 1d9b202cd56188353c13a49bf48f3f97383984ee
git describe: 4.4.153-rc1-hikey-20180826-270
Test details:
https://qa-reports.linaro.org/lkft/linaro
Hi Jens
On 08/25/2018 11:41 PM, Jens Axboe wrote:
> do {
> - set_current_state(TASK_UNINTERRUPTIBLE);
> + if (test_bit(0, ))
> + break;
>
> - if (!has_sleeper && rq_wait_inc_below(rqw, get_limit(rwb, rw)))
> +
Hi Jens
On 08/25/2018 11:41 PM, Jens Axboe wrote:
> do {
> - set_current_state(TASK_UNINTERRUPTIBLE);
> + if (test_bit(0, ))
> + break;
>
> - if (!has_sleeper && rq_wait_inc_below(rqw, get_limit(rwb, rw)))
> +
Kindly ping again... This is really pending too long...
Stephen & Shawn,
Any suggestion on how to proceed this patch set?
Regards
Dong Aisheng
> -Original Message-
> From: A.s. Dong
> Sent: Thursday, July 26, 2018 9:51 AM
> To: linux-...@vger.kernel.org; sb...@kernel.org
> Cc:
Kindly ping again... This is really pending too long...
Stephen & Shawn,
Any suggestion on how to proceed this patch set?
Regards
Dong Aisheng
> -Original Message-
> From: A.s. Dong
> Sent: Thursday, July 26, 2018 9:51 AM
> To: linux-...@vger.kernel.org; sb...@kernel.org
> Cc:
Hi Alexandre,
> -Original Message-
> From: Alexandre Bailon [mailto:abai...@baylibre.com]
> Sent: Wednesday, August 8, 2018 6:01 PM
> To: A.s. Dong ; linux-...@vger.kernel.org;
> sb...@kernel.org
> Cc: Jacky Bai ; Anson Huang ;
> mturque...@baylibre.com; linux-kernel@vger.kernel.org;
Hi Alexandre,
> -Original Message-
> From: Alexandre Bailon [mailto:abai...@baylibre.com]
> Sent: Wednesday, August 8, 2018 6:01 PM
> To: A.s. Dong ; linux-...@vger.kernel.org;
> sb...@kernel.org
> Cc: Jacky Bai ; Anson Huang ;
> mturque...@baylibre.com; linux-kernel@vger.kernel.org;
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
This effectively reverts commit da541b20021c ("objtool: Skip
unreachable warnings for GCC 4.4 and older"), which was a workaround
for GCC 4.4 or older.
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
This effectively reverts commit da541b20021c ("objtool: Skip
unreachable warnings for GCC 4.4 and older"), which was a workaround
for GCC 4.4 or older.
On Mon, 27 Aug 2018, Al Viro wrote:
> On Sun, Aug 26, 2018 at 10:00:46PM -0400, Julia Lawall wrote:
> >
> >
> > On Sun, 26 Aug 2018, Al Viro wrote:
> >
> > > On Sun, Aug 26, 2018 at 03:26:54PM -0700, Joe Perches wrote:
> > > > On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > > > > On Sun,
On Mon, 27 Aug 2018, Al Viro wrote:
> On Sun, Aug 26, 2018 at 10:00:46PM -0400, Julia Lawall wrote:
> >
> >
> > On Sun, 26 Aug 2018, Al Viro wrote:
> >
> > > On Sun, Aug 26, 2018 at 03:26:54PM -0700, Joe Perches wrote:
> > > > On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > > > > On Sun,
at 8:03 PM, Masami Hiramatsu wrote:
> On Sun, 26 Aug 2018 11:09:58 +0200
> Peter Zijlstra wrote:
>
>> On Sat, Aug 25, 2018 at 09:21:22PM -0700, Andy Lutomirski wrote:
>>> I just re-read text_poke(). It's, um, horrible. Not only is the
>>> implementation overcomplicated and probably buggy,
at 8:03 PM, Masami Hiramatsu wrote:
> On Sun, 26 Aug 2018 11:09:58 +0200
> Peter Zijlstra wrote:
>
>> On Sat, Aug 25, 2018 at 09:21:22PM -0700, Andy Lutomirski wrote:
>>> I just re-read text_poke(). It's, um, horrible. Not only is the
>>> implementation overcomplicated and probably buggy,
i have been trying to contact you
i have been trying to contact you
On Fri, Aug 24, 2018 at 5:57 PM Stanimir Varbanov
wrote:
>
> Hi Alex,
>
> On 08/24/2018 10:38 AM, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
> >>
> >> Add routine to reset the ARM9 and brings it out of reset. Also
> >> abstract the Venus CPU state
On Fri, Aug 24, 2018 at 5:57 PM Stanimir Varbanov
wrote:
>
> Hi Alex,
>
> On 08/24/2018 10:38 AM, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
> >>
> >> Add routine to reset the ARM9 and brings it out of reset. Also
> >> abstract the Venus CPU state
On Fri, Aug 24, 2018 at 6:01 PM Stanimir Varbanov
wrote:
>
> Hi Alex,
>
> On 08/24/2018 10:39 AM, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
> >>
> >> Separate firmware loading part into a new function.
> >>
> >> Signed-off-by: Vikash Garodia
> >>
On Fri, Aug 24, 2018 at 6:01 PM Stanimir Varbanov
wrote:
>
> Hi Alex,
>
> On 08/24/2018 10:39 AM, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
> >>
> >> Separate firmware loading part into a new function.
> >>
> >> Signed-off-by: Vikash Garodia
> >>
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
With GCC >= 4.6 assumed, 'upto_gcc44' is empty, 'atleast_gcc44' is y.
Signed-off-by: Masahiro Yamada
---
arch/arc/Makefile | 10 +-
1 file changed, 1
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
With GCC >= 4.6 assumed, 'upto_gcc44' is empty, 'atleast_gcc44' is y.
Signed-off-by: Masahiro Yamada
---
arch/arc/Makefile | 10 +-
1 file changed, 1
On 08/27/18 at 10:56am, Chao Fan wrote:
> >> +#ifdef CONFIG_MEMORY_HOTREMOVE
> >> +/*
> >> + * According to ACPI table, filter the immvoable memory regions
> >> + * and store them in immovable_mem[].
> >> + */
> >> +static void handle_immovable_mem(void)
> >
> >Can we change this function like
On 08/27/18 at 10:56am, Chao Fan wrote:
> >> +#ifdef CONFIG_MEMORY_HOTREMOVE
> >> +/*
> >> + * According to ACPI table, filter the immvoable memory regions
> >> + * and store them in immovable_mem[].
> >> + */
> >> +static void handle_immovable_mem(void)
> >
> >Can we change this function like
On Fri, Aug 24, 2018 at 9:26 PM Vikash Garodia wrote:
>
> Hi Alex,
>
> On 2018-08-24 13:09, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
>
> [snip]
>
> >> +struct video_firmware {
> >> + struct device *dev;
> >> + struct iommu_domain
On Fri, Aug 24, 2018 at 9:26 PM Vikash Garodia wrote:
>
> Hi Alex,
>
> On 2018-08-24 13:09, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
>
> [snip]
>
> >> +struct video_firmware {
> >> + struct device *dev;
> >> + struct iommu_domain
On Sun, 26 Aug 2018 11:09:58 +0200
Peter Zijlstra wrote:
> On Sat, Aug 25, 2018 at 09:21:22PM -0700, Andy Lutomirski wrote:
> > I just re-read text_poke(). It's, um, horrible. Not only is the
> > implementation overcomplicated and probably buggy, but it's SLOW.
> > It's totally the wrong
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> When requesting a gpio as an interrupt, we should make sure to mux the
> pin as the GPIO function and configure it to be an input so that various
> functions or output signals don't affect the interrupt state of the pin.
> So far, we've relied
On Sun, 26 Aug 2018 11:09:58 +0200
Peter Zijlstra wrote:
> On Sat, Aug 25, 2018 at 09:21:22PM -0700, Andy Lutomirski wrote:
> > I just re-read text_poke(). It's, um, horrible. Not only is the
> > implementation overcomplicated and probably buggy, but it's SLOW.
> > It's totally the wrong
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> When requesting a gpio as an interrupt, we should make sure to mux the
> pin as the GPIO function and configure it to be an input so that various
> functions or output signals don't affect the interrupt state of the pin.
> So far, we've relied
Hi Tony,
On Monday 20 August 2018 08:01 PM, Tony Lindgren wrote:
> * Kishon Vijay Abraham I [180808 06:35]:
>> On Tuesday 05 June 2018 07:35 PM, Rob Herring wrote:
>>> Really need 64-bit addresses and sizes? Use ranges to limit the
>>> address space if possible.
>>
>> We now have address-cells
Hi Tony,
On Monday 20 August 2018 08:01 PM, Tony Lindgren wrote:
> * Kishon Vijay Abraham I [180808 06:35]:
>> On Tuesday 05 June 2018 07:35 PM, Rob Herring wrote:
>>> Really need 64-bit addresses and sizes? Use ranges to limit the
>>> address space if possible.
>>
>> We now have address-cells
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> We rely on devices to use pinmuxing configurations in DT to select the
> GPIO function (function 0) if they're going to use the gpio in GPIO
> mode. Let's simplify things for driver authors by implementing
> gpio_request_enable() for this
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> We rely on devices to use pinmuxing configurations in DT to select the
> GPIO function (function 0) if they're going to use the gpio in GPIO
> mode. Let's simplify things for driver authors by implementing
> gpio_request_enable() for this
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> The interrupt controller hardware in this pin controller has two status
> enable bits. The first "normal" status enable bit enables or disables
> the summary interrupt line being raised when a gpio interrupt triggers
> and the "raw" status
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> The interrupt controller hardware in this pin controller has two status
> enable bits. The first "normal" status enable bit enables or disables
> the summary interrupt line being raised when a gpio interrupt triggers
> and the "raw" status
On Mon, Aug 27, 2018 at 10:13:49AM +0800, Baoquan He wrote:
>On 08/07/18 at 02:49pm, Chao Fan wrote:
>> If 'CONFIG_MEMORY_HOTREMOVE' specified, walk the acpi srat memory
>> tables, store the immovable memory regions, so that kaslr can get
>> the information abouth where can be selected or not.
>>
On Mon, Aug 27, 2018 at 10:13:49AM +0800, Baoquan He wrote:
>On 08/07/18 at 02:49pm, Chao Fan wrote:
>> If 'CONFIG_MEMORY_HOTREMOVE' specified, walk the acpi srat memory
>> tables, store the immovable memory regions, so that kaslr can get
>> the information abouth where can be selected or not.
>>
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
The workaround code in fs/reiserfs/Makefile is obsolete now.
Signed-off-by: Masahiro Yamada
---
fs/reiserfs/Makefile | 9 -
1 file changed, 9 deletions(-)
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
The workaround code in fs/reiserfs/Makefile is obsolete now.
Signed-off-by: Masahiro Yamada
---
fs/reiserfs/Makefile | 9 -
1 file changed, 9 deletions(-)
On Sun, Aug 26, 2018 at 10:00:46PM -0400, Julia Lawall wrote:
>
>
> On Sun, 26 Aug 2018, Al Viro wrote:
>
> > On Sun, Aug 26, 2018 at 03:26:54PM -0700, Joe Perches wrote:
> > > On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > > > On Sun, Aug 26, 2018 at 11:57:57AM -0700, Joe Perches wrote:
On Sun, Aug 26, 2018 at 10:00:46PM -0400, Julia Lawall wrote:
>
>
> On Sun, 26 Aug 2018, Al Viro wrote:
>
> > On Sun, Aug 26, 2018 at 03:26:54PM -0700, Joe Perches wrote:
> > > On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > > > On Sun, Aug 26, 2018 at 11:57:57AM -0700, Joe Perches wrote:
When make perf with -O, it gets error when make clean with below log:
$ make -C tools/perf O= # OK
$ make -C tools/perf O=
find: cannot delete ‘/builtin-script.o’: No such file or
directory
find: cannot delete ‘/.subcmd-config.o.cmd’: No such file or
directory
...
Makefile:38:
When make perf with -O, it gets error when make clean with below log:
$ make -C tools/perf O= # OK
$ make -C tools/perf O=
find: cannot delete ‘/builtin-script.o’: No such file or
directory
find: cannot delete ‘/.subcmd-config.o.cmd’: No such file or
directory
...
Makefile:38:
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
The version check in arch/parisc/Makefile is obsolete now.
Signed-off-by: Masahiro Yamada
---
arch/parisc/Makefile | 9 -
1 file changed, 9 deletions(-)
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
The version check in arch/parisc/Makefile is obsolete now.
Signed-off-by: Masahiro Yamada
---
arch/parisc/Makefile | 9 -
1 file changed, 9 deletions(-)
1 - 100 of 484 matches
Mail list logo
