[PATCHv3 3/7] ia64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for IA64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv3 1/7] switch dereference_function_descriptor() to `unsigned long'

Convert dereference_function_descriptor() to accept and return `unsigned long'. There will be two new ARCH function for kernel and module function pointer dereference, which will work with `unsigned long', so the patch unifies interfaces. Besides, dereference_function_descriptor() mostly work

[PATCHv3 4/7] powerpc64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for powerpc64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv3 2/7] sections: split dereference_function_descriptor()

There are two format specifiers to print out a pointer in symbolic format: '%pS/%ps' and '%pF/%pf'. On most architectures, the two mean exactly the same thing, but some architectures (ia64, ppc64, parisc64) use an indirect pointer for C function pointers, where the function pointer points to a

[PATCHv3 3/7] ia64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for IA64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv3 1/7] switch dereference_function_descriptor() to `unsigned long'

Convert dereference_function_descriptor() to accept and return `unsigned long'. There will be two new ARCH function for kernel and module function pointer dereference, which will work with `unsigned long', so the patch unifies interfaces. Besides, dereference_function_descriptor() mostly work

[PATCHv3 0/7] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

Hello Petr, could you please pick up the series? == On some arches C function pointers are indirect and point to a function descriptor, which contains the actual pointer to the code. This mostly

[PATCHv3 0/7] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

Hello Petr, could you please pick up the series? == On some arches C function pointers are indirect and point to a function descriptor, which contains the actual pointer to the code. This mostly

Re: [PATCH v3 6/6] drm/tegra: Use u64_to_user_ptr helper

On 28.09.2017 15:50, Mikko Perttunen wrote: > Use the u64_to_user_ptr helper macro to cast IOCTL argument u64 values > to user pointers instead of writing out the cast manually. Also do > some other cleanup with user pointers to make them stand out more > and look cleaner. > > Signed-off-by:

Re: [PATCH v3 6/6] drm/tegra: Use u64_to_user_ptr helper

On 28.09.2017 15:50, Mikko Perttunen wrote: > Use the u64_to_user_ptr helper macro to cast IOCTL argument u64 values > to user pointers instead of writing out the cast manually. Also do > some other cleanup with user pointers to make them stand out more > and look cleaner. > > Signed-off-by:

Re: [PATCH v3 4/6] gpu: host1x: Disassemble more instructions

On 28.09.2017 15:50, Mikko Perttunen wrote: > The disassembler for debug dumps was missing some newer host1x opcodes. > Add disassembly support for these. > > Signed-off-by: Mikko Perttunen > --- Reviewed-by: Dmitry Osipenko And for older Tegra's:

Re: [PATCH v3 4/6] gpu: host1x: Disassemble more instructions

On 28.09.2017 15:50, Mikko Perttunen wrote: > The disassembler for debug dumps was missing some newer host1x opcodes. > Add disassembly support for these. > > Signed-off-by: Mikko Perttunen > --- Reviewed-by: Dmitry Osipenko And for older Tegra's: Tested-by: Dmitry Osipenko >

Re: [PATCH v3 1/6] gpu: host1x: Enable Tegra186 syncpoint protection

On 28.09.2017 15:50, Mikko Perttunen wrote: > Since Tegra186 the Host1x hardware allows syncpoints to be assigned to > specific channels, preventing any other channels from incrementing > them. > > Enable this feature where available and assign syncpoints to channels > when submitting a job.

Re: [PATCH v3 1/6] gpu: host1x: Enable Tegra186 syncpoint protection

On 28.09.2017 15:50, Mikko Perttunen wrote: > Since Tegra186 the Host1x hardware allows syncpoints to be assigned to > specific channels, preventing any other channels from incrementing > them. > > Enable this feature where available and assign syncpoints to channels > when submitting a job.

[GIT PULL] platform-drivers-x86 for 4.14-2

Hi Linus, My apologies for the typo in the patch subject... at this point it was rebase a published branch, or send you a spelling error... tough call! The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the

[GIT PULL] platform-drivers-x86 for 4.14-2

Hi Linus, My apologies for the typo in the patch subject... at this point it was rebase a published branch, or send you a spelling error... tough call! The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the

re

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your response.

re

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your response.

Re: [PATCH v3 0/8] Introduce support for Dell SMBIOS over WMI

On Wed, Sep 27, 2017 at 11:02:12PM -0500, Mario Limonciello wrote: > The existing way that the dell-smbios helper module and associated > other drivers (dell-laptop, dell-wmi) communicate with the platform > really isn't secure. It requires creating a buffer in physical > DMA32 memory space and

Re: [PATCH v3 0/8] Introduce support for Dell SMBIOS over WMI

On Wed, Sep 27, 2017 at 11:02:12PM -0500, Mario Limonciello wrote: > The existing way that the dell-smbios helper module and associated > other drivers (dell-laptop, dell-wmi) communicate with the platform > really isn't secure. It requires creating a buffer in physical > DMA32 memory space and

f34c8585ed ("rcutorture: Invoke call_rcu() from timer handler"): WARNING: kernel stack regs at bdf19a20 in trinity-c0:12909 has bad 'bp' value bdf17850

for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs 1418b85217 Add linux-next specific files for 20170929 +---++++---+ | | 96036c

f34c8585ed ("rcutorture: Invoke call_rcu() from timer handler"): WARNING: kernel stack regs at bdf19a20 in trinity-c0:12909 has bad 'bp' value bdf17850

files for 20170929 +---++++---+ | | 96036c4306 | f34c8585ed | 99637e4268 | next-20170929

Re: [PATCH v3 6/8] platform/x86: dell-wmi-smbios: Add a sysfs interface for SMBIOS tokens

On Wed, Sep 27, 2017 at 11:02:18PM -0500, Mario Limonciello wrote: > Currently userspace tools can access system tokens via the dcdbas > kernel module and a SMI call that will cause the platform to execute > SMM code. > > With a goal in mind of deprecating the dcdbas kernel module a different >

Re: [PATCH v3 6/8] platform/x86: dell-wmi-smbios: Add a sysfs interface for SMBIOS tokens

On Wed, Sep 27, 2017 at 11:02:18PM -0500, Mario Limonciello wrote: > Currently userspace tools can access system tokens via the dcdbas > kernel module and a SMI call that will cause the platform to execute > SMM code. > > With a goal in mind of deprecating the dcdbas kernel module a different >

Re: [PATCH v3 5/8] platform/x86: dell-wmi-smbios: introduce character device for userspace

On Wed, Sep 27, 2017 at 11:02:17PM -0500, Mario Limonciello wrote: > This userspace character device will be used to perform SMBIOS calls > from any applications. > > It provides an ioctl that will allow passing the 32k WMI calling > interface buffer between userspace and kernel space. > > This

Re: [PATCH v3 5/8] platform/x86: dell-wmi-smbios: introduce character device for userspace

On Wed, Sep 27, 2017 at 11:02:17PM -0500, Mario Limonciello wrote: > This userspace character device will be used to perform SMBIOS calls > from any applications. > > It provides an ioctl that will allow passing the 32k WMI calling > interface buffer between userspace and kernel space. > > This

random insta-reboots on AMD Phenom II

Hi! I'm afraid I see random instant reboots on current -rc, approximately once per day, only under CPU load. There's nothing on serial/etc -- just an immediate reboot. 4.13 works perfectly; last kernel I've tried is v4.14-rc2-165-g770b782f555d. gcc 7.2.0-7 (Debian). CPU is AMD Phenom II X6

random insta-reboots on AMD Phenom II

Hi! I'm afraid I see random instant reboots on current -rc, approximately once per day, only under CPU load. There's nothing on serial/etc -- just an immediate reboot. 4.13 works perfectly; last kernel I've tried is v4.14-rc2-165-g770b782f555d. gcc 7.2.0-7 (Debian). CPU is AMD Phenom II X6

Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote: > For WMI operations that are only Set or Query read or write sysfs > attributes created by WMI vendor drivers make sense. > > For other WMI operations that are run on Method, there needs to be a > way to guarantee to userspace

Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote: > For WMI operations that are only Set or Query read or write sysfs > attributes created by WMI vendor drivers make sense. > > For other WMI operations that are run on Method, there needs to be a > way to guarantee to userspace

[PATCH v2 7/7] drm: bridge: dw-hdmi: get phy ops by device type

Add device type to distinguish different chips.Different chips use different phy ops, get them by device type. Signed-off-by: Algea Cao --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH v2 7/7] drm: bridge: dw-hdmi: get phy ops by device type

Add device type to distinguish different chips.Different chips use different phy ops, get them by device type. Signed-off-by: Algea Cao --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH v2 4/7] drm/rockchip: dw_hdmi: add inno hdmi phy ops

Because some RK chips use inno hdmi phy, such as RK3328, we add inno hdmi phy ops. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 110 +++- 1 file changed, 107 insertions(+), 3 deletions(-) diff --git

[PATCH v2 6/7] drm/rockchip: dw_hdmi: update dw-hdmi encoder enable

Writing grf register according to device type. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 19 ++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c

[PATCH v2 3/7] drm: bridge: dw-hdmi: change hdmi phy hpd read function to export

Change dw_hdmi_phy_read_hpd from static to export. inno hdmi phy ops will call this interface to get hpd status. Signed-off-by: Algea Cao --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 5 +++-- include/drm/bridge/dw_hdmi.h | 3 ++- 2 files changed, 5

[PATCH v2 5/7] drm/rockchip: dw_hdmi: add hclk_vio

Add clk hclk_vio and enable it when hdmi bind. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 21 + 1 file changed, 21 insertions(+) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c

[PATCH v2 4/7] drm/rockchip: dw_hdmi: add inno hdmi phy ops

Because some RK chips use inno hdmi phy, such as RK3328, we add inno hdmi phy ops. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 110 +++- 1 file changed, 107 insertions(+), 3 deletions(-) diff --git

[PATCH v2 6/7] drm/rockchip: dw_hdmi: update dw-hdmi encoder enable

Writing grf register according to device type. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 19 ++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c

[PATCH v2 3/7] drm: bridge: dw-hdmi: change hdmi phy hpd read function to export

Change dw_hdmi_phy_read_hpd from static to export. inno hdmi phy ops will call this interface to get hpd status. Signed-off-by: Algea Cao --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 5 +++-- include/drm/bridge/dw_hdmi.h | 3 ++- 2 files changed, 5 insertions(+), 3 deletions(-)

[PATCH v2 5/7] drm/rockchip: dw_hdmi: add hclk_vio

Add clk hclk_vio and enable it when hdmi bind. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 21 + 1 file changed, 21 insertions(+) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c index

[PATCH v2 2/7] drm/rockchip: dw_hdmi: add device type

To determine type of SOC, we add a parameter dev_type. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 5 + include/drm/bridge/dw_hdmi.h| 10 ++ 2 files changed, 15 insertions(+) diff --git

[PATCH v2 2/7] drm/rockchip: dw_hdmi: add device type

To determine type of SOC, we add a parameter dev_type. Signed-off-by: Algea Cao --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 5 + include/drm/bridge/dw_hdmi.h| 10 ++ 2 files changed, 15 insertions(+) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c

[PATCH v2 1/7] drm/rockchip: dw_hdmi: update dw_hdmi_rockchip_dt_ids

Add rk3328-dw-hdmi to support rk3328. Signed-off-by: Algea Cao --- .../devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt | 1 + drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 6 ++ 2 files changed, 7 insertions(+) diff --git

[PATCH v2 1/7] drm/rockchip: dw_hdmi: update dw_hdmi_rockchip_dt_ids

Add rk3328-dw-hdmi to support rk3328. Signed-off-by: Algea Cao --- .../devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt | 1 + drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 6 ++ 2 files changed, 7 insertions(+) diff --git

[PATCH v2 0/7] Add support RK3328 drm hdmi

These patches add support drm hdmi in RK3328 and has been tested in RK development board. We add dev_type to distinguish different rockchip chips. Hdmi phy or some regs configuration can't be switched according to dev_type, that hdmi driver's compatibility will be better. Algea Cao (7):

[PATCH v2 0/7] Add support RK3328 drm hdmi

These patches add support drm hdmi in RK3328 and has been tested in RK development board. We add dev_type to distinguish different rockchip chips. Hdmi phy or some regs configuration can't be switched according to dev_type, that hdmi driver's compatibility will be better. Algea Cao (7):

Re: [PATCH net] RDS: IB: Limit the scope of has_fr/has_fmr variables

On 9/29/2017 6:13 PM, Avinash Repaka wrote: This patch fixes the scope of has_fr and has_fmr variables as they are needed only in rds_ib_add_one(). Signed-off-by: Avinash Repaka --- Indeed the final merge version actually didn't need those across files. Change looks

Re: [PATCH net] RDS: IB: Limit the scope of has_fr/has_fmr variables

On 9/29/2017 6:13 PM, Avinash Repaka wrote: This patch fixes the scope of has_fr and has_fmr variables as they are needed only in rds_ib_add_one(). Signed-off-by: Avinash Repaka --- Indeed the final merge version actually didn't need those across files. Change looks good to me. Thanks !!

Re: [PATCH v3 3/8] platform/x86: dell-wmi-smbios: Use Dell WMI descriptor check

On Wed, Sep 27, 2017 at 11:02:15PM -0500, Mario Limonciello wrote: > The Dell WMI descriptor check is used as an indication that WMI > calls are safe to run both when used with the notification > ASL/GUID pair as well as the SMBIOS calling ASL/GUID pair. > > As some code in dell-wmi-smbios is

Re: [PATCH v3 3/8] platform/x86: dell-wmi-smbios: Use Dell WMI descriptor check

On Wed, Sep 27, 2017 at 11:02:15PM -0500, Mario Limonciello wrote: > The Dell WMI descriptor check is used as an indication that WMI > calls are safe to run both when used with the notification > ASL/GUID pair as well as the SMBIOS calling ASL/GUID pair. > > As some code in dell-wmi-smbios is

Re: [PATCH] PCI: Fix legacy IRQ assignment execution stage

On 09/28/2017 04:37 AM, Lorenzo Pieralisi wrote: Through struct pci_host_bridge->{map/swizzle}_irq() hooks is now possible to define IRQ mapping functions on a per PCI host bridge basis. Actual IRQ allocation is carried out by the pci_assign_irq() function in pci_device_probe() - to make sure a

Re: [PATCH] PCI: Fix legacy IRQ assignment execution stage

On 09/28/2017 04:37 AM, Lorenzo Pieralisi wrote: Through struct pci_host_bridge->{map/swizzle}_irq() hooks is now possible to define IRQ mapping functions on a per PCI host bridge basis. Actual IRQ allocation is carried out by the pci_assign_irq() function in pci_device_probe() - to make sure a

[PATCH] Staging: rtl8188eu: core: Use list_entry instead of container_of

For variables of the type struct list_head* use list_entry to access the current list element instead of using container_of. Done using the following semantic patch by coccinelle. @r@ identifier e; struct list_head* l; @@ <... when != l == NULL l; ...> ( e = -container_of +list_entry (

[PATCH] Staging: rtl8188eu: core: Use list_entry instead of container_of

For variables of the type struct list_head* use list_entry to access the current list element instead of using container_of. Done using the following semantic patch by coccinelle. @r@ identifier e; struct list_head* l; @@ <... when != l == NULL l; ...> ( e = -container_of +list_entry (

[PATCH net] RDS: IB: Limit the scope of has_fr/has_fmr variables

This patch fixes the scope of has_fr and has_fmr variables as they are needed only in rds_ib_add_one(). Signed-off-by: Avinash Repaka --- net/rds/ib.c | 11 ++- net/rds/ib.h | 2 -- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/net/rds/ib.c

[PATCH net] RDS: IB: Limit the scope of has_fr/has_fmr variables

This patch fixes the scope of has_fr and has_fmr variables as they are needed only in rds_ib_add_one(). Signed-off-by: Avinash Repaka --- net/rds/ib.c | 11 ++- net/rds/ib.h | 2 -- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/net/rds/ib.c b/net/rds/ib.c index

Re: [PATCH net-next v2 1/7] net: dsa: add master helper to look up slaves

On 09/29/2017 02:19 PM, Vivien Didelot wrote: > The DSA tagging code does not need to know about the DSA architecture, > it only needs to return the slave device corresponding to the source > port index (and eventually the source device index for cascade-capable > switches) parsed from the frame

Re: [PATCH net-next v2 1/7] net: dsa: add master helper to look up slaves

On 09/29/2017 02:19 PM, Vivien Didelot wrote: > The DSA tagging code does not need to know about the DSA architecture, > it only needs to return the slave device corresponding to the source > port index (and eventually the source device index for cascade-capable > switches) parsed from the frame

[PATCH 2/9] kbuild: rpm-pkg: install vmlinux.bz2 unconditionally

This conditional was added by commit fc370ecfdb37 ("kbuild: add vmlinux to kernel rpm"). Its git-log mentioned vmlinux.bz2 was necessary for debugging, but did not explain why ppc64 was an exception. I see no problem to copy vmlinux.bz2 all the time. Signed-off-by: Masahiro Yamada

[PATCH 2/9] kbuild: rpm-pkg: install vmlinux.bz2 unconditionally

This conditional was added by commit fc370ecfdb37 ("kbuild: add vmlinux to kernel rpm"). Its git-log mentioned vmlinux.bz2 was necessary for debugging, but did not explain why ppc64 was an exception. I see no problem to copy vmlinux.bz2 all the time. Signed-off-by: Masahiro Yamada ---

[PATCH 3/9] kbuild: rpm-pkg: clean up mkspec

Clean up the mkspec without changing the behavior. - grep CONFIG_DRM=y more simply - move "EXCLUDE" out of the "%install" section because it can be computed when the spec file is generated - remove "BuildRoot:" field, which is now redundant - do not mkdir $RPM_BUILD_ROOT/lib/modules

[PATCH 3/9] kbuild: rpm-pkg: clean up mkspec

Clean up the mkspec without changing the behavior. - grep CONFIG_DRM=y more simply - move "EXCLUDE" out of the "%install" section because it can be computed when the spec file is generated - remove "BuildRoot:" field, which is now redundant - do not mkdir $RPM_BUILD_ROOT/lib/modules

[PATCH 8/9] kbuild: rpm-pkg: keep spec file until make mrproper

If build fails during (bin)rpm-pkg, the spec file is not cleaned by anyone until the next successful build of the package. We do not have to immediately delete the spec file in case somebody may want to take a look at it. Instead, make them ignored by git, and cleaned up by make mrproper.

[PATCH 6/9] kbuild: rpm-pkg: replace $RPM_BUILD_ROOT with %{buildroot}

$RPM_BUILD_ROOT must be escaped to prevent shell from expanding it when generating the spec file. %{build_root} is more readable than \$RPM_BUILD_ROOT. Signed-off-by: Masahiro Yamada --- scripts/package/mkspec | 32 1 file

[PATCH 6/9] kbuild: rpm-pkg: replace $RPM_BUILD_ROOT with %{buildroot}

$RPM_BUILD_ROOT must be escaped to prevent shell from expanding it when generating the spec file. %{build_root} is more readable than \$RPM_BUILD_ROOT. Signed-off-by: Masahiro Yamada --- scripts/package/mkspec | 32 1 file changed, 16 insertions(+), 16

[PATCH 8/9] kbuild: rpm-pkg: keep spec file until make mrproper

If build fails during (bin)rpm-pkg, the spec file is not cleaned by anyone until the next successful build of the package. We do not have to immediately delete the spec file in case somebody may want to take a look at it. Instead, make them ignored by git, and cleaned up by make mrproper.

[PATCH 4/9] kbuild: rpm-pkg: refactor mkspec with here doc

The repeat of echo is unreadable. The here-document is a well-known device for such scripts. One difficulty is we have a bunch of PREBUILT conditionals that would split the here-document. My idea is to add "$S" annotatation to lines only for the source package spec file, then post-process it by

[PATCH 2/3] staging: iio: tsl2x7x: migrate in_illuminance0_integration_time sysfs attribute to iio_chan_spec

The driver explicitly creates the in_illuminance0_integration_time sysfs attribute outside the IIO core. This attribute is available in the IIO core so this patches migrates the attribute to be created by the iio_chan_spec. Signed-off-by: Brian Masney --- Changes since v1

[PATCH 1/9] kbuild: rpm-pkg: remove ppc64 specific image handling

This conditional was added by commit 1a0f3d422bb9 ("kbuild: fix make rpm for powerpc"). Its git-log explains the default kernel image is zImage, but obviously the current arch/powerpc/Makefile does not set KBUILD_IMAGE, so the image file is actually vmlinux. Moreover, since commit 09549aa1baa9

[PATCH 9/9] kbuild: rpm-pkg: do not force -jN in submake

The spec file always passes %{?_smp_mflags}, but we have two problems here. [1] "make -jN rpm-pkg" emits the following warning message: make[2]: warning: -jN forced in submake: disabling jobserver mode. [2] We can not specify the number of jobs that run in parallel. Whether we give -jN

[PATCH 5/9] kbuild: rpm-pkg: fix build error when CONFIG_MODULES is disabled

When CONFIG_MODULES is disabled, make rpm-pkg / binrpm-pkg fails with the following message: The present kernel configuration has modules disabled. Type 'make config' and enable loadable module support. Then build a kernel with module support enabled. Do not install modules in the case.

[PATCH 4/9] kbuild: rpm-pkg: refactor mkspec with here doc

The repeat of echo is unreadable. The here-document is a well-known device for such scripts. One difficulty is we have a bunch of PREBUILT conditionals that would split the here-document. My idea is to add "$S" annotatation to lines only for the source package spec file, then post-process it by

[PATCH 2/3] staging: iio: tsl2x7x: migrate in_illuminance0_integration_time sysfs attribute to iio_chan_spec

The driver explicitly creates the in_illuminance0_integration_time sysfs attribute outside the IIO core. This attribute is available in the IIO core so this patches migrates the attribute to be created by the iio_chan_spec. Signed-off-by: Brian Masney --- Changes since v1 (Jul 9 2017): - Use

[PATCH 1/9] kbuild: rpm-pkg: remove ppc64 specific image handling

This conditional was added by commit 1a0f3d422bb9 ("kbuild: fix make rpm for powerpc"). Its git-log explains the default kernel image is zImage, but obviously the current arch/powerpc/Makefile does not set KBUILD_IMAGE, so the image file is actually vmlinux. Moreover, since commit 09549aa1baa9

[PATCH 9/9] kbuild: rpm-pkg: do not force -jN in submake

The spec file always passes %{?_smp_mflags}, but we have two problems here. [1] "make -jN rpm-pkg" emits the following warning message: make[2]: warning: -jN forced in submake: disabling jobserver mode. [2] We can not specify the number of jobs that run in parallel. Whether we give -jN

[PATCH 5/9] kbuild: rpm-pkg: fix build error when CONFIG_MODULES is disabled

When CONFIG_MODULES is disabled, make rpm-pkg / binrpm-pkg fails with the following message: The present kernel configuration has modules disabled. Type 'make config' and enable loadable module support. Then build a kernel with module support enabled. Do not install modules in the case.

[PATCH 1/3] staging: iio: tsl2x7x: rename tsl2x7x_settings variable to settings

The length of the 'tsl2x7x_settings' variable within the tsl2X7X_chip structure makes some of the line lengths greater than 80 characters for upcoming patches. This patch shortens the name of the 'tsl2x7x_settings' variable in this structure to just 'settings' to improve code readability.

[PATCH 7/9] kbuild: rpm-pkg: fix jobserver unavailable warning

If "make rpm-pkg" or "make binrpm-pkg" is run with -j[jobs] option, the following warning message is displayed. warning: jobserver unavailable: using -j1. Add '+' to parent make rule. Follow the suggestion. Signed-off-by: Masahiro Yamada ---

[PATCH 3/3] staging: iio: tsl2x7x: migrate *_thresh_period sysfs attributes to iio_event_spec

The sysfs attributes in_intensity0_thresh_period and in_proximity0_thresh_period are currently directly created by the driver. This patch migrates the creation of these sysfs attributes from the driver to using the IIO core via iio_event_spec. Signed-off-by: Brian Masney

[PATCH 0/3] staging: iio: tsl2x7x: staging cleanups

This patch set converts several sysfs attributes from directly being created by the driver to be created by iio_chan_spec and iio_event_spec. There is also a patch to shorten the length of a variable to fix an issue that I encountered with some lines that were over 80 characters with this

[PATCH 7/9] kbuild: rpm-pkg: fix jobserver unavailable warning

If "make rpm-pkg" or "make binrpm-pkg" is run with -j[jobs] option, the following warning message is displayed. warning: jobserver unavailable: using -j1. Add '+' to parent make rule. Follow the suggestion. Signed-off-by: Masahiro Yamada --- scripts/package/Makefile | 4 ++-- 1 file

[PATCH 3/3] staging: iio: tsl2x7x: migrate *_thresh_period sysfs attributes to iio_event_spec

The sysfs attributes in_intensity0_thresh_period and in_proximity0_thresh_period are currently directly created by the driver. This patch migrates the creation of these sysfs attributes from the driver to using the IIO core via iio_event_spec. Signed-off-by: Brian Masney ---

[PATCH 0/3] staging: iio: tsl2x7x: staging cleanups

This patch set converts several sysfs attributes from directly being created by the driver to be created by iio_chan_spec and iio_event_spec. There is also a patch to shorten the length of a variable to fix an issue that I encountered with some lines that were over 80 characters with this

[PATCH 1/3] staging: iio: tsl2x7x: rename tsl2x7x_settings variable to settings

The length of the 'tsl2x7x_settings' variable within the tsl2X7X_chip structure makes some of the line lengths greater than 80 characters for upcoming patches. This patch shortens the name of the 'tsl2x7x_settings' variable in this structure to just 'settings' to improve code readability.

Re: Problems compiling with KCFLAGS="-frecord-gcc-switches"

On 09/29/2017 01:46 PM, Josh Poimboeuf wrote: On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote: Hi Josh, when trying to compile an image with KCFLAGS="-frecord-gcc-switches", I get the folllowing build warning/error. make allmodconfig KCFLAGS="-frecord-gcc-switches" make

Re: Problems compiling with KCFLAGS="-frecord-gcc-switches"

On 09/29/2017 01:46 PM, Josh Poimboeuf wrote: On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote: Hi Josh, when trying to compile an image with KCFLAGS="-frecord-gcc-switches", I get the folllowing build warning/error. make allmodconfig KCFLAGS="-frecord-gcc-switches" make

[PATCH] Staging: rtl8188eu: core: Use list_entry instead of container_of

For variables that have type struct list_head* use list_entry to access current list element instead of using container_of. Done using the following semantic patch by coccinelle. @r@ identifier e; struct list_head* l; @@ <... when != l == NULL l; ...> ( e= -container_of +list_entry (

[PATCH] Staging: rtl8188eu: core: Use list_entry instead of container_of

For variables that have type struct list_head* use list_entry to access current list element instead of using container_of. Done using the following semantic patch by coccinelle. @r@ identifier e; struct list_head* l; @@ <... when != l == NULL l; ...> ( e= -container_of +list_entry (

Re: [PATCH v3 2/8] platform/x86: dell-smbios: Introduce a WMI-ACPI interface

On Wed, Sep 27, 2017 at 11:02:14PM -0500, Mario Limonciello wrote: > The driver currently uses an SMI interface which grants direct access > to physical memory to the firmware SMM methods via a pointer. > > Now add a WMI-ACPI interface that is detected by WMI probe and preferred > over the SMI

Re: [PATCH v3 2/8] platform/x86: dell-smbios: Introduce a WMI-ACPI interface

On Wed, Sep 27, 2017 at 11:02:14PM -0500, Mario Limonciello wrote: > The driver currently uses an SMI interface which grants direct access > to physical memory to the firmware SMM methods via a pointer. > > Now add a WMI-ACPI interface that is detected by WMI probe and preferred > over the SMI

Re: [PATCH] tpm: fix duplicate inline declaration specifier

Thanks! This fixes a warning I was seeing with Clang: drivers/char/tpm/tpm.h:560:15: warning: duplicate 'inline' declaration specifier [-Wduplicate-decl-specifier] On Fri, Sep 29, 2017 at 10:17 AM, Jarkko Sakkinen wrote: > On Tue, Sep 26, 2017 at 01:58:57PM

Re: [PATCH] tpm: fix duplicate inline declaration specifier

Thanks! This fixes a warning I was seeing with Clang: drivers/char/tpm/tpm.h:560:15: warning: duplicate 'inline' declaration specifier [-Wduplicate-decl-specifier] On Fri, Sep 29, 2017 at 10:17 AM, Jarkko Sakkinen wrote: > On Tue, Sep 26, 2017 at 01:58:57PM +, Ruben Roy wrote: >> This

Re: [PATCH] net: hns3: fix null pointer dereference before null check

Hi, Colin On 2017/9/30 3:51, Colin King wrote: > From: Colin Ian King > > pointer ndev is being dereferenced with the call to netif_running > before it is being null checked. Re-order the code to only dereference > ndev after it has been null checked. Thanks for

Re: [PATCH] net: hns3: fix null pointer dereference before null check

Hi, Colin On 2017/9/30 3:51, Colin King wrote: > From: Colin Ian King > > pointer ndev is being dereferenced with the call to netif_running > before it is being null checked. Re-order the code to only dereference > ndev after it has been null checked. Thanks for fixing it. > > Detected by

Re: Fail to build Linux with O= in master

2017-09-30 8:59 GMT+09:00 Julien Grall : > Hello, > > I have tried to build the latest master and got the following error: > > 42sh> make O=~/works/linux-build/aarch64-4k -C ~/works/linux > make: Entering directory '/home/julgra01/works/linux' > Makefile:135: *** failed to

Re: Fail to build Linux with O= in master

2017-09-30 8:59 GMT+09:00 Julien Grall : > Hello, > > I have tried to build the latest master and got the following error: > > 42sh> make O=~/works/linux-build/aarch64-4k -C ~/works/linux > make: Entering directory '/home/julgra01/works/linux' > Makefile:135: *** failed to create output directory

Re: [PATCH] HID: i2c-hid: Use device properties (instead of device tree)

Hi Rajat, On Fri, Sep 29, 2017 at 03:44:41PM -0700, Rajat Jain wrote: > Use the device properties (that can be provided by ACPI systems > as well as non ACPI systems) instead of device tree properties > (that are not provided ACPI systems). This required some minor > code restructuring. > >

Re: [PATCH] HID: i2c-hid: Use device properties (instead of device tree)

Hi Rajat, On Fri, Sep 29, 2017 at 03:44:41PM -0700, Rajat Jain wrote: > Use the device properties (that can be provided by ACPI systems > as well as non ACPI systems) instead of device tree properties > (that are not provided ACPI systems). This required some minor > code restructuring. > >

Re: KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove lguest support)

On Sat, Sep 30, 2017 at 12:39 AM, Paolo Bonzini wrote: > On 29/09/2017 17:47, Lai Jiangshan wrote: >> Hello, all >> >> An interesting (at least to me) thinking came up to me when I found >> that the lguest was removed. But I don't have enough knowledge >> to find out the

Re: KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove lguest support)

On Sat, Sep 30, 2017 at 12:39 AM, Paolo Bonzini wrote: > On 29/09/2017 17:47, Lai Jiangshan wrote: >> Hello, all >> >> An interesting (at least to me) thinking came up to me when I found >> that the lguest was removed. But I don't have enough knowledge >> to find out the answer nor energy to

<    1   2   3   4   5   6   7   8   9   10   >