On 05/17/2017 06:01 PM, Krzysztof Kozlowski wrote:
On Wed, May 17, 2017 at 12:58:38PM +0200, Richard Leitner wrote:
...
1. Currently usb251xb uses i2c_smbus_*, usb3503 uses regmap_* and
usb4604 uses i2c_master_* functions for the hub configuration. What
would be the preferred solution?
On 05/17/2017 06:01 PM, Krzysztof Kozlowski wrote:
On Wed, May 17, 2017 at 12:58:38PM +0200, Richard Leitner wrote:
...
1. Currently usb251xb uses i2c_smbus_*, usb3503 uses regmap_* and
usb4604 uses i2c_master_* functions for the hub configuration. What
would be the preferred solution?
On Wed, 2017-05-17 at 15:48 -0500, Gustavo A. R. Silva wrote:
> While looking into Coverity ID 1408956 I ran into the following
> piece
> of code at drivers/net/ethernet/intel/i40e/i40e_main.c:8807:
>
> 8807 if (pf->hw.mac.type == I40E_MAC_X722) {
> 8808 pf->flags |=
On Wed, 2017-05-17 at 15:48 -0500, Gustavo A. R. Silva wrote:
> While looking into Coverity ID 1408956 I ran into the following
> piece
> of code at drivers/net/ethernet/intel/i40e/i40e_main.c:8807:
>
> 8807 if (pf->hw.mac.type == I40E_MAC_X722) {
> 8808 pf->flags |=
This patch fixes the "please, no space before tabs" warnings emitted by
checkpatch.pl script.
Signed-off-by: Dhiru Kholia
---
drivers/staging/ccree/cc_crypto_ctx.h | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git
This patch fixes the "please, no space before tabs" warnings emitted by
checkpatch.pl script.
Signed-off-by: Dhiru Kholia
---
drivers/staging/ccree/cc_crypto_ctx.h | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/ccree/cc_crypto_ctx.h
On 05/18/17 at 11:03am, Bharat Bhushan wrote:
> This patch have minor updates in Documentation for arm64i as
> relocatable kernel.
> Also this patch updates documentation for using uncompressed
> image "Image" which is used for ARM64.
>
> Signed-off-by: Bharat Bhushan
>
On 05/18/17 at 11:03am, Bharat Bhushan wrote:
> This patch have minor updates in Documentation for arm64i as
> relocatable kernel.
> Also this patch updates documentation for using uncompressed
> image "Image" which is used for ARM64.
>
> Signed-off-by: Bharat Bhushan
> ---
>
Hi Rick,
Minor comment below.
On 18 May 2017 at 03:59, Rick Altherr wrote:
> When a hw_random device's quality is non-zero, it will automatically be
> used to fill the kernel's entropy pool. Since timeriomem_rng is used by
> many different devices, the quality needs to be
Hi Rick,
Minor comment below.
On 18 May 2017 at 03:59, Rick Altherr wrote:
> When a hw_random device's quality is non-zero, it will automatically be
> used to fill the kernel's entropy pool. Since timeriomem_rng is used by
> many different devices, the quality needs to be provided by platform
On Mon, Apr 24, 2017 at 01:50:18PM +0900, Masahiro Yamada wrote:
> Many Makefiles needed to add -Iinclude/drm as an include path,
> but the right thing to do is to include headers in the form
> #include
>
> This series fixes the source files, then rip off -Iinclude/drm flags.
>
>
> Masahiro
On Mon, Apr 24, 2017 at 01:50:18PM +0900, Masahiro Yamada wrote:
> Many Makefiles needed to add -Iinclude/drm as an include path,
> but the right thing to do is to include headers in the form
> #include
>
> This series fixes the source files, then rip off -Iinclude/drm flags.
>
>
> Masahiro
Borislav Petkov writes:
> Top-posting so that the PPC list can see the whole patch below.
>
> Since I don't know PPC, let me add PPC ML to CC for a confirmation this
> change is correct.
>
> Which brings me to the tangential: this driver is from 2006-ish and
> is for some
Borislav Petkov writes:
> Top-posting so that the PPC list can see the whole patch below.
>
> Since I don't know PPC, let me add PPC ML to CC for a confirmation this
> change is correct.
>
> Which brings me to the tangential: this driver is from 2006-ish and
> is for some "Marvell MV64x60 Memory
This patch have minor updates in Documentation for arm64i as
relocatable kernel.
Also this patch updates documentation for using uncompressed
image "Image" which is used for ARM64.
Signed-off-by: Bharat Bhushan
---
Documentation/kdump/kdump.txt | 10 --
1 file
This patch have minor updates in Documentation for arm64i as
relocatable kernel.
Also this patch updates documentation for using uncompressed
image "Image" which is used for ARM64.
Signed-off-by: Bharat Bhushan
---
Documentation/kdump/kdump.txt | 10 --
1 file changed, 8 insertions(+),
On Fri, Apr 28, 2017 at 06:11:55PM +0200, Sabrina Dubroca wrote:
> The current aesni AES-GCM implementation only offers support for
> rfc4106(gcm(aes)). This makes some things a little bit simpler
> (handling of associated data and authentication tag), but it means
> that non-IPsec users of
On Fri, Apr 28, 2017 at 06:11:55PM +0200, Sabrina Dubroca wrote:
> The current aesni AES-GCM implementation only offers support for
> rfc4106(gcm(aes)). This makes some things a little bit simpler
> (handling of associated data and authentication tag), but it means
> that non-IPsec users of
Hi everybody,
tonight my dmesg was flooded with mesages like
vmscan: shrink_slab: ext4_es_scan+0x0/0x150 negative objects to delete
nr=-2147483624
Is that an integer overflow happening in ext4?
It's the first time I see this message. Any help on how to debug/reprocude this
are appreciated.
Hi everybody,
tonight my dmesg was flooded with mesages like
vmscan: shrink_slab: ext4_es_scan+0x0/0x150 negative objects to delete
nr=-2147483624
Is that an integer overflow happening in ext4?
It's the first time I see this message. Any help on how to debug/reprocude this
are appreciated.
Hi Bjorn,
On 05/18/2017 05:08 AM, Bjorn Helgaas wrote:
On Wed, Apr 05, 2017 at 10:28:22AM +0800, Jeffy Chen wrote:
Currently we only free the allocated resource struct when error.
This would cause memory leak after pci_free_resource_list.
I think I see the problem here. The release path is
Hi Bjorn,
On 05/18/2017 05:08 AM, Bjorn Helgaas wrote:
On Wed, Apr 05, 2017 at 10:28:22AM +0800, Jeffy Chen wrote:
Currently we only free the allocated resource struct when error.
This would cause memory leak after pci_free_resource_list.
I think I see the problem here. The release path is
On 05/18/2017 09:59 AM, Masahiro Yamada wrote:
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Acked-by: Archit Taneja
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
On 05/18/2017 09:59 AM, Masahiro Yamada wrote:
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Acked-by: Archit Taneja
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/i2c/Makefile | 2 --
1 file changed, 2 deletions(-)
diff
On Tue, Apr 25, 2017 at 11:25:40AM +0300, Gilad Ben-Yossef wrote:
> The tcrypt AEAD cycles speed tests disables irqs during the test, which is
> broken at the very least since commit
> '1425d2d17f7309c6 ("crypto: tcrypt - Fix AEAD speed tests")'
> adds a wait for completion as part of the test and
On Tue, Apr 25, 2017 at 11:25:40AM +0300, Gilad Ben-Yossef wrote:
> The tcrypt AEAD cycles speed tests disables irqs during the test, which is
> broken at the very least since commit
> '1425d2d17f7309c6 ("crypto: tcrypt - Fix AEAD speed tests")'
> adds a wait for completion as part of the test and
Hi Robin,
On Wed, May 17, 2017 at 11:29 PM, Robin Murphy wrote:
> Hi Magnus,
>
> On 17/05/17 11:07, Magnus Damm wrote:
>> From: Magnus Damm
>>
>> Convert from archdata to iommu_priv via iommu_fwspec on ARM64 but
>> let 32-bit ARM keep on using
Hi Robin,
On Wed, May 17, 2017 at 11:29 PM, Robin Murphy wrote:
> Hi Magnus,
>
> On 17/05/17 11:07, Magnus Damm wrote:
>> From: Magnus Damm
>>
>> Convert from archdata to iommu_priv via iommu_fwspec on ARM64 but
>> let 32-bit ARM keep on using archdata for now.
>>
>> Once the 32-bit ARM code
"Aneesh Kumar K.V" writes:
> POWER9 supports hugepages of size 2M and 1G in radix MMU mode. This patch
> enables the usage of 1G page size for hugetlbfs. This also update the helper
> such we can do 1G page allocation at runtime.
>
> We still don't enable 1G page
"Aneesh Kumar K.V" writes:
> POWER9 supports hugepages of size 2M and 1G in radix MMU mode. This patch
> enables the usage of 1G page size for hugetlbfs. This also update the helper
> such we can do 1G page allocation at runtime.
>
> We still don't enable 1G page size on DD1 version. This is to
FYI, we noticed the following commit:
commit: 66de5f1b197e175840a132f7ee8927bfc3ff92b3 ("scsi: Move
scsi_device.cmd_list manipulation code")
https://github.com/bvanassche/linux for-next
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu kvm64,+ssse3 -smp 2 -m 8G
caused
FYI, we noticed the following commit:
commit: 66de5f1b197e175840a132f7ee8927bfc3ff92b3 ("scsi: Move
scsi_device.cmd_list manipulation code")
https://github.com/bvanassche/linux for-next
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu kvm64,+ssse3 -smp 2 -m 8G
caused
On 2017-05-13 15:36, Andy Shevchenko wrote:
> On Sat, May 13, 2017 at 10:29 AM, Jan Kiszka wrote:
>> First, the logic for translating a register bit to the return code of
>> exar_get_direction and exar_get_value were wrong. And second, there was
>> a flip regarding the
On 2017-05-13 15:36, Andy Shevchenko wrote:
> On Sat, May 13, 2017 at 10:29 AM, Jan Kiszka wrote:
>> First, the logic for translating a register bit to the return code of
>> exar_get_direction and exar_get_value were wrong. And second, there was
>> a flip regarding the register bank in
> The difficulty in pipe mode is that information needs to be written
> sequentially to the pipe. Meta data headers are usually generated
> (and also expected) at the beginning of the file (or piped output).
> To solve this problem, we introduce new synthetic record types,
> one for each meta-data
> The difficulty in pipe mode is that information needs to be written
> sequentially to the pipe. Meta data headers are usually generated
> (and also expected) at the beginning of the file (or piped output).
> To solve this problem, we introduce new synthetic record types,
> one for each meta-data
On Thu, May 11, 2017 at 02:53:43PM +0300, Gilad Ben-Yossef wrote:
> drbg_kcapi_sym_ctr() was using wait_for_completion_interruptible() to
> wait for completion of async crypto op but if a signal occurs it
> may return before DMA ops of HW crypto provider finish, thus
> corrupting the output
On Thu, May 11, 2017 at 02:53:43PM +0300, Gilad Ben-Yossef wrote:
> drbg_kcapi_sym_ctr() was using wait_for_completion_interruptible() to
> wait for completion of async crypto op but if a signal occurs it
> may return before DMA ops of HW crypto provider finish, thus
> corrupting the output
On 2017-05-13 15:54, Andy Shevchenko wrote:
> On Sat, May 13, 2017 at 10:29 AM, Jan Kiszka wrote:
>> This implements the setup of RS232 and the switch-over to RS485 or RS422
>> for the Siemens IOT2040. That uses an EXAR XR17V352 with external logic
>> to switch between the
On 2017-05-13 15:54, Andy Shevchenko wrote:
> On Sat, May 13, 2017 at 10:29 AM, Jan Kiszka wrote:
>> This implements the setup of RS232 and the switch-over to RS485 or RS422
>> for the Siemens IOT2040. That uses an EXAR XR17V352 with external logic
>> to switch between the different modes. The
On Wed 17 May 06:14 PDT 2017, Johannes Berg wrote:
> On Thu, 2017-05-04 at 13:13 +, Kalle Valo wrote:
> >
> > > > This code intentionally checked if TX status was requested, and
> > > > if not then it doesn't go to the effort of building it.
> > > >
> > >
> > > What I'm finding puzzling is
On Wed 17 May 06:14 PDT 2017, Johannes Berg wrote:
> On Thu, 2017-05-04 at 13:13 +, Kalle Valo wrote:
> >
> > > > This code intentionally checked if TX status was requested, and
> > > > if not then it doesn't go to the effort of building it.
> > > >
> > >
> > > What I'm finding puzzling is
On Tue, May 16, 2017 at 7:38 AM, Peter Zijlstra wrote:
> On Thu, May 04, 2017 at 10:31:43AM +0800, Zefan Li wrote:
>> It is assumed that the head of cache_groups always has valid RMID,
>> which isn't true.
>>
>> When we deallocate RMID from conflicting events currently we
On Tue, May 16, 2017 at 7:38 AM, Peter Zijlstra wrote:
> On Thu, May 04, 2017 at 10:31:43AM +0800, Zefan Li wrote:
>> It is assumed that the head of cache_groups always has valid RMID,
>> which isn't true.
>>
>> When we deallocate RMID from conflicting events currently we don't
>> move them to
On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote:
> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar
> wrote:
> > Is there a better way to run the timekeeping code in an userspace
> > application? I suspect it would need something like the Linux Kernel
> >
On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote:
> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar
> wrote:
> > Is there a better way to run the timekeeping code in an userspace
> > application? I suspect it would need something like the Linux Kernel
> > Library project.
>
> I
Hi Sergey,
On Wed, May 17, 2017 at 06:14:23PM +0900, Sergey Senozhatsky wrote:
> Hello Minchan,
>
> On (05/17/17 17:32), Minchan Kim wrote:
> [..]
> > > what we can return now is a `partially updated' data, with some new
> > > and some stale pages. this is quite unlikely to end up anywhere good.
Hi Sergey,
On Wed, May 17, 2017 at 06:14:23PM +0900, Sergey Senozhatsky wrote:
> Hello Minchan,
>
> On (05/17/17 17:32), Minchan Kim wrote:
> [..]
> > > what we can return now is a `partially updated' data, with some new
> > > and some stale pages. this is quite unlikely to end up anywhere good.
Add COMPILE_TEST for the compilation test coverage.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/stm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/stm/Kconfig b/drivers/gpu/drm/stm/Kconfig
index 2c4817f..722ad11
Add COMPILE_TEST for the compilation test coverage.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/stm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/stm/Kconfig b/drivers/gpu/drm/stm/Kconfig
index 2c4817f..722ad11 100644
---
Use <...> notation to include headers located in include/linux.
While we are here, tweak the includes order a bit to sort them
alphabetically.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c| 4 ++--
Use <...> notation to include headers located in include/linux.
While we are here, tweak the includes order a bit to sort them
alphabetically.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c| 4 ++--
drivers/gpu/drm/amd/powerplay/hwmgr/pp_acpi.c | 2
Hi Archit,
On 17 May 2017 at 13:45, Archit Taneja wrote:
> The recent ION clean ups introduced some leftover code that can be
> removed, and a bug that comes up if the call to dma_buf_map_attachment()
> from an importer fails. Fix these.
>
> Archit Taneja (3):
>
Hi Archit,
On 17 May 2017 at 13:45, Archit Taneja wrote:
> The recent ION clean ups introduced some leftover code that can be
> removed, and a bug that comes up if the call to dma_buf_map_attachment()
> from an importer fails. Fix these.
>
> Archit Taneja (3):
> staging: android: ion: Remove
On Wed, 2017-05-17 at 19:30 -0500, Gustavo A. R. Silva wrote:
> Remove this assignment once the value stored in variable _k_ is
> overwritten after a few lines.
>
> Addresses-Coverity-ID: 1226927
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/scsi/qlogicfas408.c |
On Wed, 2017-05-17 at 19:30 -0500, Gustavo A. R. Silva wrote:
> Remove this assignment once the value stored in variable _k_ is
> overwritten after a few lines.
>
> Addresses-Coverity-ID: 1226927
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/scsi/qlogicfas408.c | 1 -
> 1 file changed, 1
On 17/05/17 17:39, Chris Packham wrote:
> The mchp23lcv1024 is software compatible with the mchp23k256, the
> only difference (from a software point of view) is the size. There
> is no way to detect the size so we must be told via a Device Tree.
I've just noticed that another difference between
On 17/05/17 17:39, Chris Packham wrote:
> The mchp23lcv1024 is software compatible with the mchp23k256, the
> only difference (from a software point of view) is the size. There
> is no way to detect the size so we must be told via a Device Tree.
I've just noticed that another difference between
Hi Daniel,
2017-05-17 21:40 GMT+09:00 Daniel Vetter :
> On Mon, Apr 24, 2017 at 01:50:33PM +0900, Masahiro Yamada wrote:
>> Include instead of relative path from include/drm, then
>> remove the -Iinclude/drm compiler flag.
>>
>> While we are here, use <...> instead of "..." for
Hi Daniel,
2017-05-17 21:40 GMT+09:00 Daniel Vetter :
> On Mon, Apr 24, 2017 at 01:50:33PM +0900, Masahiro Yamada wrote:
>> Include instead of relative path from include/drm, then
>> remove the -Iinclude/drm compiler flag.
>>
>> While we are here, use <...> instead of "..." for
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/stm/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/stm/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/mga/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/mga/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/i810/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/i810/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/stm/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/stm/Makefile b/drivers/gpu/drm/stm/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/mga/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/mga/Makefile b/drivers/gpu/drm/mga/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/i810/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/i810/Makefile b/drivers/gpu/drm/i810/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/omapdrm/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/omapdrm/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/via/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/via/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/omapdrm/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/omapdrm/Makefile b/drivers/gpu/drm/omapdrm/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/via/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/via/Makefile b/drivers/gpu/drm/via/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/r128/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/r128/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/virtio/Makefile | 2 --
drivers/gpu/drm/virtio/virtgpu_debugfs.c | 2 +-
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/r128/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/r128/Makefile b/drivers/gpu/drm/r128/Makefile
index
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/virtio/Makefile | 2 --
drivers/gpu/drm/virtio/virtgpu_debugfs.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_drv.c
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/udl/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/udl/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/i2c/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/i2c/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/gma500/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/udl/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/udl/Makefile b/drivers/gpu/drm/udl/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/i2c/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/i2c/Makefile b/drivers/gpu/drm/i2c/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/gma500/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/Makefile b/drivers/gpu/drm/gma500/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/vgem/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/vgem/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/vgem/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/vgem/Makefile b/drivers/gpu/drm/vgem/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/savage/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/savage/Makefile
Many Makefiles needed to add -Iinclude/drm as an include path,
but the right thing to do is to include headers in the form
#include
This series fixes the source files, then rip off -Iinclude/drm flags.
V3: rebased on commit bb2af9bda33 (drm-misc-next)
Masahiro Yamada (16):
drm/vc4: fix
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/savage/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/savage/Makefile b/drivers/gpu/drm/savage/Makefile
Many Makefiles needed to add -Iinclude/drm as an include path,
but the right thing to do is to include headers in the form
#include
This series fixes the source files, then rip off -Iinclude/drm flags.
V3: rebased on commit bb2af9bda33 (drm-misc-next)
Masahiro Yamada (16):
drm/vc4: fix
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
While we are here, use <...> instead of "..." for include/linux/*.h
and include/sound/*.h headers too.
Signed-off-by: Masahiro Yamada
---
Changes in v3:
- Rebase
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/tdfx/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/tdfx/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
While we are here, use <...> instead of "..." for include/linux/*.h
and include/sound/*.h headers too.
Signed-off-by: Masahiro Yamada
---
Changes in v3:
- Rebase
drivers/gpu/drm/vc4/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/tdfx/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/tdfx/Makefile b/drivers/gpu/drm/tdfx/Makefile
index
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/sis/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/sis/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/vmwgfx/Makefile | 3 ---
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 3 ++-
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/sis/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/sis/Makefile b/drivers/gpu/drm/sis/Makefile
index
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
drivers/gpu/drm/vmwgfx/Makefile | 3 ---
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 3 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 3
(This is a rebased and updated version of Stephane Eranian's version
in https://patchwork.kernel.org/patch/1499081/)
Up until now, meta-data was only available when perf record
was used in "regular" mode, i.e., generating a perf.data file.
For users depending on pipe mode, neither host or
(This is a rebased and updated version of Stephane Eranian's version
in https://patchwork.kernel.org/patch/1499081/)
Up until now, meta-data was only available when perf record
was used in "regular" mode, i.e., generating a perf.data file.
For users depending on pipe mode, neither host or
As preparation for using header records in pipe mode, replace
int fd with struct feat_fd fd in write functions for all header
record types.
Record types that are not used in pipe-mode (such as auxtrace) will
never be called with fd->buf set and fail if so.
Signed-off-by: David Carrillo-Cisneros
Make buf in helper function "writen" constant to simplify
the life of its callers.
This requires to hack a cast of buf prior to passing it to "ion"
which is simpler than the alternative of reworking the "ion"
function to provide a read and a write paths, the latter with
constant buf argument.
As preparation for using header records in pipe mode, replace
int fd with struct feat_fd fd in write functions for all header
record types.
Record types that are not used in pipe-mode (such as auxtrace) will
never be called with fd->buf set and fail if so.
Signed-off-by: David Carrillo-Cisneros
Make buf in helper function "writen" constant to simplify
the life of its callers.
This requires to hack a cast of buf prior to passing it to "ion"
which is simpler than the alternative of reworking the "ion"
function to provide a read and a write paths, the latter with
constant buf argument.
1 - 100 of 1766 matches
Mail list logo