Introduce a quirk to use CMB-like memory on older devices that have
an exposed BAR but do not advertise support for using CMBLOC and
CMBSIZE.
We'd like to use some of these older cards to test P2P memory.
Signed-off-by: Logan Gunthorpe
---
drivers/nvme/host/nvme.h | 7
Register the CMB buffer as p2pmem and use the appropriate allocation
functions to create and destroy the IO SQ.
If the CMB supports WDS and RDS, publish it for use as p2p memory
by other devices.
Signed-off-by: Logan Gunthorpe
---
drivers/nvme/host/pci.c | 75
Introduce a quirk to use CMB-like memory on older devices that have
an exposed BAR but do not advertise support for using CMBLOC and
CMBSIZE.
We'd like to use some of these older cards to test P2P memory.
Signed-off-by: Logan Gunthorpe
---
drivers/nvme/host/nvme.h | 7 +++
Register the CMB buffer as p2pmem and use the appropriate allocation
functions to create and destroy the IO SQ.
If the CMB supports WDS and RDS, publish it for use as p2p memory
by other devices.
Signed-off-by: Logan Gunthorpe
---
drivers/nvme/host/pci.c | 75
For P2P requests we must use the pci_p2pmem_[un]map_sg() functions
instead of the dma_map_sg functions.
With that, we can then indicate PCI_P2P support in the request queue.
For this, we create an NVME_F_PCI_P2P flag which tells the core to
set QUEUE_FLAG_PCI_P2P in the request queue.
For P2P requests we must use the pci_p2pmem_[un]map_sg() functions
instead of the dma_map_sg functions.
With that, we can then indicate PCI_P2P support in the request queue.
For this, we create an NVME_F_PCI_P2P flag which tells the core to
set QUEUE_FLAG_PCI_P2P in the request queue.
On 02/28/2018 01:39 PM, Eric Anholt wrote:
> Hi Florian,
>
> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-defconfig-next-2018-02-28
>
> for you to fetch changes up to
On 02/28/2018 01:39 PM, Eric Anholt wrote:
> Hi Florian,
>
> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-defconfig-next-2018-02-28
>
> for you to fetch changes up to
On 02/28/2018 01:39 PM, Eric Anholt wrote:
> Hi Florian,
>
> The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
>
> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux
On 02/28/2018 01:39 PM, Eric Anholt wrote:
> Hi Florian,
>
> The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
>
> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
head: ea5dfef5a890c9e6e47bdddfc23c4a4ba0c1bea1
commit: 2066f4d67e7d9cbe44e451d782cdcc0a0d12e5d3 [1/2] x86/apic: Move pending
intr check code into it's own function
config: i386-randconfig-x007-201808 (attached as
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
head: ea5dfef5a890c9e6e47bdddfc23c4a4ba0c1bea1
commit: 2066f4d67e7d9cbe44e451d782cdcc0a0d12e5d3 [1/2] x86/apic: Move pending
intr check code into it's own function
config: i386-randconfig-x007-201808 (attached as
This series updates building dtc with flex and bison rather than using
the _shipped files and updates dtc to the current upstream version. The
new dtc adds some new warnings, so turn off the noisiest ones. While
here adjusting the warnings, we can also now re-enable some that have
gotten
Commit eea199b445f6 ("kbuild: remove unnecessary LEX_PREFIX and
YACC_PREFIX") removed YACC_PREFIX definition, but left one use of it. There
was not any build error since there is no user of "cmd_bison_h" currently.
Remove the last remaining occurrence of YACC_PREFIX.
Fixes: eea199b445f6 ("kbuild:
This series updates building dtc with flex and bison rather than using
the _shipped files and updates dtc to the current upstream version. The
new dtc adds some new warnings, so turn off the noisiest ones. While
here adjusting the warnings, we can also now re-enable some that have
gotten
Commit eea199b445f6 ("kbuild: remove unnecessary LEX_PREFIX and
YACC_PREFIX") removed YACC_PREFIX definition, but left one use of it. There
was not any build error since there is no user of "cmd_bison_h" currently.
Remove the last remaining occurrence of YACC_PREFIX.
Fixes: eea199b445f6 ("kbuild:
If dtc is rebuilt, we should rebuild .dtb files with the new dtc.
Cc: Masahiro Yamada
Signed-off-by: Rob Herring
---
scripts/Makefile.lib | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/Makefile.lib
If dtc is rebuilt, we should rebuild .dtb files with the new dtc.
Cc: Masahiro Yamada
Signed-off-by: Rob Herring
---
scripts/Makefile.lib | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
index 1bc2f90cb8c0..6aeb91524c76 100644
---
The latest dtc update adds some new noisy warnings, so turn them off by
default. Disable 'avoid_unnecessary_addr_size' and 'alias_paths'. They
can be re-enabled by building with 'W=1'.
Signed-off-by: Rob Herring
---
scripts/Makefile.lib | 2 ++
1 file changed, 2 insertions(+)
The latest dtc update adds some new noisy warnings, so turn them off by
default. Disable 'avoid_unnecessary_addr_size' and 'alias_paths'. They
can be re-enabled by building with 'W=1'.
Signed-off-by: Rob Herring
---
scripts/Makefile.lib | 2 ++
1 file changed, 2 insertions(+)
diff --git
This adds the following commits from upstream:
aadd0b65c987 checks: centralize printing of property names in failure messages
88960e398907 checks: centralize printing of node path in check_msg
f1879e1a50eb Add limited read-only support for older (V2 and V3) device tree to
libfdt.
37dea76e9700
This adds the following commits from upstream:
aadd0b65c987 checks: centralize printing of property names in failure messages
88960e398907 checks: centralize printing of node path in check_msg
f1879e1a50eb Add limited read-only support for older (V2 and V3) device tree to
libfdt.
37dea76e9700
Now that the kernel build supports flex and bison, remove the _shipped
files and generate them during the build instead.
Based on Masahiro's original patch.
Cc: Masahiro Yamada
Signed-off-by: Rob Herring
---
scripts/dtc/Makefile
Now that the kernel build supports flex and bison, remove the _shipped
files and generate them during the build instead.
Based on Masahiro's original patch.
Cc: Masahiro Yamada
Signed-off-by: Rob Herring
---
scripts/dtc/Makefile |6 +-
scripts/dtc/dtc-lexer.lex.c_shipped
We can re-enable some dtc warnings that have been completely or mostly
fixed. There are a few remaining ones in arm64 dts files which crept in
recently.
Signed-off-by: Rob Herring
---
scripts/Makefile.lib | 3 ---
1 file changed, 3 deletions(-)
diff --git
We can re-enable some dtc warnings that have been completely or mostly
fixed. There are a few remaining ones in arm64 dts files which crept in
recently.
Signed-off-by: Rob Herring
---
scripts/Makefile.lib | 3 ---
1 file changed, 3 deletions(-)
diff --git a/scripts/Makefile.lib
Dou,
can you please look into that? I zapped the commits from x86/apic for now.
Thanks,
tglx
On Thu, 1 Mar 2018, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
> head: ea5dfef5a890c9e6e47bdddfc23c4a4ba0c1bea1
> commit:
Dou,
can you please look into that? I zapped the commits from x86/apic for now.
Thanks,
tglx
On Thu, 1 Mar 2018, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
> head: ea5dfef5a890c9e6e47bdddfc23c4a4ba0c1bea1
> commit:
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/core/devlink.c: In function 'devlink_resource_validate_size':
net/core/devlink.c:2349:34: error: invalid type argument of '->' (have 'struct
devlink_resource_size_params')
if (size >
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/core/devlink.c: In function 'devlink_resource_validate_size':
net/core/devlink.c:2349:34: error: invalid type argument of '->' (have 'struct
devlink_resource_size_params')
if (size >
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
head: ea5dfef5a890c9e6e47bdddfc23c4a4ba0c1bea1
commit: 2066f4d67e7d9cbe44e451d782cdcc0a0d12e5d3 [1/2] x86/apic: Move pending
intr check code into it's own function
config: i386-randconfig-x004-201808 (attached as
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
head: ea5dfef5a890c9e6e47bdddfc23c4a4ba0c1bea1
commit: 2066f4d67e7d9cbe44e451d782cdcc0a0d12e5d3 [1/2] x86/apic: Move pending
intr check code into it's own function
config: i386-randconfig-x004-201808 (attached as
On Wed, Feb 28, 2018 at 05:32:52PM +0200, Michael S. Tsirkin wrote:
> On Wed, Feb 28, 2018 at 12:49:35PM +0100, Marc-André Lureau wrote:
> > Hi
> >
> > On Tue, Feb 27, 2018 at 1:20 AM, Michael S. Tsirkin wrote:
> > > On Thu, Feb 15, 2018 at 10:33:09PM +0100, Marc-André Lureau
On Wed, Feb 28, 2018 at 05:32:52PM +0200, Michael S. Tsirkin wrote:
> On Wed, Feb 28, 2018 at 12:49:35PM +0100, Marc-André Lureau wrote:
> > Hi
> >
> > On Tue, Feb 27, 2018 at 1:20 AM, Michael S. Tsirkin wrote:
> > > On Thu, Feb 15, 2018 at 10:33:09PM +0100, Marc-André Lureau wrote:
> > >>
Ever since "random: kill dead extract_state struct" [1], the
dont_count_entropy member of struct timer_rand_state has been
effectively unused. Since it hasn't found a new use in 12 years, it's
probably safe to finally kill it.
[1] Pre-git,
Ever since "random: kill dead extract_state struct" [1], the
dont_count_entropy member of struct timer_rand_state has been
effectively unused. Since it hasn't found a new use in 12 years, it's
probably safe to finally kill it.
[1] Pre-git,
On 02/28/2018 02:31 PM, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> I want to use the _mapcount field to record what a page is in use as.
> This can help with debugging and we can also expose that information to
> userspace through /proc/kpageflags to help diagnose
On 02/28/2018 02:31 PM, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> I want to use the _mapcount field to record what a page is in use as.
> This can help with debugging and we can also expose that information to
> userspace through /proc/kpageflags to help diagnose memory usage (not
>
> On Feb 28, 2018, at 2:12 AM, Pavel Emelyanov wrote:
>
> On 02/27/2018 05:18 AM, Dmitry V. Levin wrote:
>> On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote:
>>> On 02/21/2018 03:44 AM, Andrew Morton wrote:
On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport
> On Feb 28, 2018, at 2:12 AM, Pavel Emelyanov wrote:
>
> On 02/27/2018 05:18 AM, Dmitry V. Levin wrote:
>> On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote:
>>> On 02/21/2018 03:44 AM, Andrew Morton wrote:
On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport
wrote:
The PM runtime operations are unused when CONFIG_PM is disabled,
leading to a harmless warning:
drivers/media/platform/renesas-ceu.c:1003:12: error: 'ceu_runtime_suspend'
defined but not used [-Werror=unused-function]
static int ceu_runtime_suspend(struct device *dev)
The PM runtime operations are unused when CONFIG_PM is disabled,
leading to a harmless warning:
drivers/media/platform/renesas-ceu.c:1003:12: error: 'ceu_runtime_suspend'
defined but not used [-Werror=unused-function]
static int ceu_runtime_suspend(struct device *dev)
Dearest One.
I know this mail will come to you as a surprise since we have not meet
or had a previous correspondence,please bear with me.I really like to
have a good relationship with you.I have a special reason why I decided
to contact you.
please can you contact me through my email adress so
Dearest One.
I know this mail will come to you as a surprise since we have not meet
or had a previous correspondence,please bear with me.I really like to
have a good relationship with you.I have a special reason why I decided
to contact you.
please can you contact me through my email adress so
Dearest One.
I know this mail will come to you as a surprise since we have not meet
or had a previous correspondence,please bear with me.I really like to
have a good relationship with you.I have a special reason why I decided
to contact you.
please can you contact me through my email adress so
I noticed that offsetof(struct filename, iname) is actually 28 on 64
bit platforms, so we always pass an unaligned pointer to
strncpy_from_user. This is mostly a problem for those 64 bit platforms
without HAVE_EFFICIENT_UNALIGNED_ACCESS, but even on x86_64, unaligned
accesses carry a penalty.
A
Dearest One.
I know this mail will come to you as a surprise since we have not meet
or had a previous correspondence,please bear with me.I really like to
have a good relationship with you.I have a special reason why I decided
to contact you.
please can you contact me through my email adress so
I noticed that offsetof(struct filename, iname) is actually 28 on 64
bit platforms, so we always pass an unaligned pointer to
strncpy_from_user. This is mostly a problem for those 64 bit platforms
without HAVE_EFFICIENT_UNALIGNED_ACCESS, but even on x86_64, unaligned
accesses carry a penalty.
A
The new ixgbevf_set_rx_buffer_len() function causes a harmless warnings
in configurations with large page size:
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c: In function
'ixgbevf_set_rx_buffer_len':
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c:1758:15: error: unused
variable
The new ixgbevf_set_rx_buffer_len() function causes a harmless warnings
in configurations with large page size:
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c: In function
'ixgbevf_set_rx_buffer_len':
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c:1758:15: error: unused
variable
Anson Huang
Best Regards!
> -Original Message-
> From: Leonard Crestez [mailto:leonard.cres...@nxp.com]
> Sent: Thursday, March 1, 2018 1:26 AM
> To: Anson Huang ; rui.zh...@intel.com;
> edubez...@gmail.com; shawn...@kernel.org
> Cc: dl-linux-imx
Anson Huang
Best Regards!
> -Original Message-
> From: Leonard Crestez [mailto:leonard.cres...@nxp.com]
> Sent: Thursday, March 1, 2018 1:26 AM
> To: Anson Huang ; rui.zh...@intel.com;
> edubez...@gmail.com; shawn...@kernel.org
> Cc: dl-linux-imx ; linux...@vger.kernel.org;
>
On Tue, 27 Feb 2018 07:36:46 -0800
"Paul E. McKenney" wrote:
> > > --- a/include/linux/sched.h
> > > +++ b/include/linux/sched.h
> > > @@ -1589,6 +1589,12 @@ static inline int test_tsk_need_resched(struct
> > > task_struct *tsk)
> > > */
> > > #ifndef
On Tue, 27 Feb 2018 07:36:46 -0800
"Paul E. McKenney" wrote:
> > > --- a/include/linux/sched.h
> > > +++ b/include/linux/sched.h
> > > @@ -1589,6 +1589,12 @@ static inline int test_tsk_need_resched(struct
> > > task_struct *tsk)
> > > */
> > > #ifndef CONFIG_PREEMPT
> > > extern int
On Wed, Feb 28, 2018 at 10:17:50PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 28, 2018 at 8:43 PM, Rodrigo Rivas Costa
> wrote:
> > This device has a feature report to send and receive commands.
> > Use it to get the serial number and set the device's uniq value.
>
On Wed, Feb 28, 2018 at 10:17:50PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 28, 2018 at 8:43 PM, Rodrigo Rivas Costa
> wrote:
> > This device has a feature report to send and receive commands.
> > Use it to get the serial number and set the device's uniq value.
>
> > #include
> > #include
Hi Bjorn,
On Wed, Feb 28, 2018 at 3:07 PM, Bjorn Helgaas wrote:
> On Mon, Feb 19, 2018 at 01:02:33PM +, David Woodhouse wrote:
>> Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
>> ARM64") added this generic function with the intent of using it
>>
Hi Bjorn,
On Wed, Feb 28, 2018 at 3:07 PM, Bjorn Helgaas wrote:
> On Mon, Feb 19, 2018 at 01:02:33PM +, David Woodhouse wrote:
>> Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
>> ARM64") added this generic function with the intent of using it
>> everywhere and
On Mon, Feb 19, 2018 at 10:30:25AM -0500, David Miller wrote:
> From: David Woodhouse
> Date: Mon, 19 Feb 2018 15:24:18 +
>
> >> For one, the sparc specific code allows mmap'ing any address range
> >> within a PCI bus device. The generic code does not allow that.
> >
>
On Mon, Feb 19, 2018 at 01:02:33PM +, David Woodhouse wrote:
> Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
> ARM64") added this generic function with the intent of using it
> everywhere and ultimately killing the old arch-specific implementations.
>
> Let's get on
On Mon, Feb 19, 2018 at 01:02:33PM +, David Woodhouse wrote:
> Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
> ARM64") added this generic function with the intent of using it
> everywhere and ultimately killing the old arch-specific implementations.
>
> Let's get on
On Mon, Feb 19, 2018 at 10:30:25AM -0500, David Miller wrote:
> From: David Woodhouse
> Date: Mon, 19 Feb 2018 15:24:18 +
>
> >> For one, the sparc specific code allows mmap'ing any address range
> >> within a PCI bus device. The generic code does not allow that.
> >
> >
> > You mean any
On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
Hi Hao,
> This patch adds compat_id support when driver creates the platform
> device for dfl-fme-region. It allows dfl-fme-region platform driver
> to create fpga-region with correct compat_id.
>
> Signed-off-by: Wu Hao
On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
Hi Hao,
> This patch adds compat_id support when driver creates the platform
> device for dfl-fme-region. It allows dfl-fme-region platform driver
> to create fpga-region with correct compat_id.
>
> Signed-off-by: Wu Hao
> ---
>
The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:
Linux 4.16-rc2 (2018-02-18 17:29:42 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes
for you to fetch changes up to
The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:
Linux 4.16-rc2 (2018-02-18 17:29:42 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes
for you to fetch changes up to
On Mon, Feb 19, 2018 at 12:59:51PM +, David Woodhouse wrote:
> Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
> ARM64") added this generic function with the intent of using it
> everywhere and ultimately killing the old arch-specific implementations.
>
> Let's get on
On Mon, Feb 19, 2018 at 12:59:51PM +, David Woodhouse wrote:
> Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
> ARM64") added this generic function with the intent of using it
> everywhere and ultimately killing the old arch-specific implementations.
>
> Let's get on
Thanks, applied.
- Ted
On Wed, Feb 28, 2018 at 01:43:28PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> add_interrupt_randomess always wakes up
> code blocking on /dev/random. This wake up is done
> unconditionally. Unfortunately
Thanks, applied.
- Ted
On Wed, Feb 28, 2018 at 01:43:28PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> add_interrupt_randomess always wakes up
> code blocking on /dev/random. This wake up is done
> unconditionally. Unfortunately this means all
On Wed, 28 Feb 2018 09:49:21 -0800
Alexander Duyck wrote:
> On Tue, Feb 27, 2018 at 2:25 PM, Alexander Duyck
> wrote:
> > On Tue, Feb 27, 2018 at 1:40 PM, Alex Williamson
> > wrote:
> >> On Tue, 27 Feb 2018
On Wed, 28 Feb 2018 09:49:21 -0800
Alexander Duyck wrote:
> On Tue, Feb 27, 2018 at 2:25 PM, Alexander Duyck
> wrote:
> > On Tue, Feb 27, 2018 at 1:40 PM, Alex Williamson
> > wrote:
> >> On Tue, 27 Feb 2018 11:06:54 -0800
> >> Alexander Duyck wrote:
> >>
> >>> From: Alexander Duyck
> >>>
On Sun, Feb 04, 2018 at 11:07:46PM +0100, Jason A. Donenfeld wrote:
> In the unfortunate event that a developer fails to check the return
> value of get_random_bytes_wait, or simply wants to make a "best effort"
> attempt, for whatever that's worth, it's much better to still fill the
> buffer with
On Sun, Feb 04, 2018 at 11:07:46PM +0100, Jason A. Donenfeld wrote:
> In the unfortunate event that a developer fails to check the return
> value of get_random_bytes_wait, or simply wants to make a "best effort"
> attempt, for whatever that's worth, it's much better to still fill the
> buffer with
On Tue, Feb 27, 2018 at 7:17 PM, Bart Van Assche wrote:
> On Tue, 2018-02-27 at 19:07 -0300, Hernán Gonzalez wrote:
>> Note: This is compile only tested as I have no access to the hw.
>
> Hello Hernán,
>
> Are you aware that the only hardware that is needed to test this
On Tue, Feb 27, 2018 at 7:17 PM, Bart Van Assche wrote:
> On Tue, 2018-02-27 at 19:07 -0300, Hernán Gonzalez wrote:
>> Note: This is compile only tested as I have no access to the hw.
>
> Hello Hernán,
>
> Are you aware that the only hardware that is needed to test this driver is
> an Ethernet
On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
Hi Hao,
> This patch introduces a compat_id member and sysfs interface for each
> fpga-region, e.g userspace applications could read the compat_id
> from the sysfs interface for compatibility checking before PR.
>
> Signed-off-by:
On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
Hi Hao,
> This patch introduces a compat_id member and sysfs interface for each
> fpga-region, e.g userspace applications could read the compat_id
> from the sysfs interface for compatibility checking before PR.
>
> Signed-off-by: Wu Hao
> ---
>
On Wed, Feb 28, 2018 at 12:03:58PM -0500, David Miller wrote:
> Applied, thank you.
No problem, cheers.
--
Joey Pabalinas
signature.asc
Description: PGP signature
On Wed, Feb 28, 2018 at 12:03:58PM -0500, David Miller wrote:
> Applied, thank you.
No problem, cheers.
--
Joey Pabalinas
signature.asc
Description: PGP signature
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlxsw/spectrum.c
between commit:
77d270967c5f ("mlxsw: spectrum: Fix handling of resource_size_param")
from the net tree and commit:
4f4bbf7c4e3d ("devlink: Perform cleanup of
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlxsw/spectrum.c
between commit:
77d270967c5f ("mlxsw: spectrum: Fix handling of resource_size_param")
from the net tree and commit:
4f4bbf7c4e3d ("devlink: Perform cleanup of
Hi Philipp,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc3 next-20180228]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Philipp,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc3 next-20180228]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
The following changes since commit 4a3928c6f8a53fa1aed28ccba227742486e8ddcb:
Linux 4.16-rc3 (2018-02-25 18:50:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git
tags/riscv-for-linus-4.16-rc4_smp_mb
for you to fetch
The following changes since commit 4a3928c6f8a53fa1aed28ccba227742486e8ddcb:
Linux 4.16-rc3 (2018-02-25 18:50:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git
tags/riscv-for-linus-4.16-rc4_smp_mb
for you to fetch
On Wed, Feb 28, 2018 at 09:21:15PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 28, 2018 at 8:43 PM, Rodrigo Rivas Costa
> wrote:
> > There are two ways to connect the Steam Controller: directly to the USB
> > or with the USB wireless adapter. Both methods are
On Wed, Feb 28, 2018 at 09:21:15PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 28, 2018 at 8:43 PM, Rodrigo Rivas Costa
> wrote:
> > There are two ways to connect the Steam Controller: directly to the USB
> > or with the USB wireless adapter. Both methods are similar, but the
> > wireless
On 2/28/2018 9:49 AM, Alexander Duyck wrote:
On Tue, Feb 27, 2018 at 2:25 PM, Alexander Duyck
wrote:
On Tue, Feb 27, 2018 at 1:40 PM, Alex Williamson
wrote:
On Tue, 27 Feb 2018 11:06:54 -0800
Alexander Duyck
On 2/28/2018 9:49 AM, Alexander Duyck wrote:
On Tue, Feb 27, 2018 at 2:25 PM, Alexander Duyck
wrote:
On Tue, Feb 27, 2018 at 1:40 PM, Alex Williamson
wrote:
On Tue, 27 Feb 2018 11:06:54 -0800
Alexander Duyck wrote:
From: Alexander Duyck
This patch is meant to add support for SR-IOV on
'linux,stdout-path' has been deprecated for some time in favor of
'stdout-path'. Now dtc will warn on occurrences of 'linux,stdout-path'.
Search and replace all the of occurrences with 'stdout-path'.
Signed-off-by: Rob Herring
Cc: Mark Rutland
Cc: Benjamin
'linux,stdout-path' has been deprecated for some time in favor of
'stdout-path'. Now dtc will warn on occurrences of 'linux,stdout-path'.
Search and replace all the of occurrences with 'stdout-path'.
Signed-off-by: Rob Herring
Cc: Mark Rutland
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc:
With earlycon support now enabled, the arch specific early_printk support
can be removed.
Signed-off-by: Rob Herring
Cc: Michal Simek
---
arch/microblaze/Kconfig.debug | 8 --
arch/microblaze/include/asm/prom.h| 27 -
This started with removing 'linux,stdout-path' which dtc now warns
about, but I noticed the early_printk support only supports that. The
early_printk support is redundant with earlycon support since the 2
Xilinx UARTs support earlycon now.
This is compile tested only. If earlycon support has
This started with removing 'linux,stdout-path' which dtc now warns
about, but I noticed the early_printk support only supports that. The
early_printk support is redundant with earlycon support since the 2
Xilinx UARTs support earlycon now.
This is compile tested only. If earlycon support has
With earlycon support now enabled, the arch specific early_printk support
can be removed.
Signed-off-by: Rob Herring
Cc: Michal Simek
---
arch/microblaze/Kconfig.debug | 8 --
arch/microblaze/include/asm/prom.h| 27 -
arch/microblaze/kernel/Makefile | 1 -
In preparation to remove prom.h, remove unnecessary prom.h includes.
Signed-off-by: Rob Herring
Cc: Michal Simek
---
arch/microblaze/include/asm/cpuinfo.h | 2 +-
arch/microblaze/include/asm/pci.h | 1 -
arch/microblaze/kernel/platform.c | 1 -
In preparation to remove prom.h, remove unnecessary prom.h includes.
Signed-off-by: Rob Herring
Cc: Michal Simek
---
arch/microblaze/include/asm/cpuinfo.h | 2 +-
arch/microblaze/include/asm/pci.h | 1 -
arch/microblaze/kernel/platform.c | 1 -
arch/microblaze/pci/indirect_pci.c| 1
Commit-ID: c52232a49e203a65a6e1a670cd5262f59e9364a0
Gitweb: https://git.kernel.org/tip/c52232a49e203a65a6e1a670cd5262f59e9364a0
Author: Lingutla Chandrasekhar
AuthorDate: Thu, 18 Jan 2018 17:20:22 +0530
Committer: Thomas Gleixner
'linux,stdout-path' has been deprecated for some time in favor of
'stdout-path'. Now dtc will warn on occurrences of 'linux,stdout-path'.
Search and replace the one occurrence with 'stdout-path'.
Signed-off-by: Rob Herring
Cc: Mark Rutland
Cc: Michal Simek
401 - 500 of 2974 matches
Mail list logo