, this select can be dropped as PMIC_DA9055 doesn't
exist.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Tested with git grep only.
1) Note that the DA9052 and DA9055 drivers all have code for module
support, but their Kconfig entries only allow them to be builtin. Can't
these entries be made
The Kconfig entry for the Openmoko GTA02 / Freerunner phone selects
MACH_NEO1973. But there is no Kconfig symbol MACH_NEO1973. The select
statement for that symbol is a nop. It can safely be dropped.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Tested with git grep.
1) There appear
? Drop that select or add an (equally
useless) config entry for MACH_NOKIA_RM696? Or should I try to ignore it
for the time being?
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested! This specifically needs testing on (some) 64 bit platforms,
because this means HAVE_ALIGNED_STRUCT_PAGE will not be selected anymore
on those platforms.
drivers/staging/zcache/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion
This could have been either ARCH_S5P64X0 or CPU_S5P6450. Looking at
commit 2555e663b367b8d555e76023f4de3f6338c28d6c (ARM: S5P64X0: Add UART
serial support for S5P6450) - which added this typo - makes clear this
should be CPU_S5P6450.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Bravely
entered mainline in v3.9-rc2 (still as commit
51acbcec6c42b24482bac18e42befc822524535d). It missed one instance of
CONFIG_MULTICORE_RAID456, so this additional patch is needed (which also
cleans that macro from two defconfig files). Compile tested, by the way.
Paul Bolle
From
.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested, actually.
drivers/acpi/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
index 92ed969..b46f5e3 100644
--- a/drivers/acpi/Kconfig
+++ b/drivers/acpi/Kconfig
@@ -334,7
, these references serve no purpose and
can be removed.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested: I don't have the hardware. Neither do I have the compiler for
this architecture at hand.
arch/sh/drivers/dma/Kconfig| 2 +-
arch/sh/include/cpu-sh4/cpu/dma-register.h | 1
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Tested by grepping the tree.
1) Typo was added in commit f8c95fe6d9adad72fc7bce90f4ab68d119f50c5b
(ARM: imx: support DEBUG_LL uart port selection for all i.MX SoCs).
Looking at that patch and at the tree makes clear that DEBUG_IMX53_UART
On Mon, 2013-03-11 at 17:34 +0400, Sergei Shtylyov wrote:
On 11-03-2013 17:16, Paul Bolle wrote:
1) Typo was added in commit f8c95fe6d9adad72fc7bce90f4ab68d119f50c5b
(ARM: imx: support DEBUG_LL uart port selection for all i.MX SoCs).
Looking at that patch and at the tree makes clear
On Mon, 2013-03-11 at 21:37 +0800, Shawn Guo wrote:
On Mon, Mar 11, 2013 at 02:16:00PM +0100, Paul Bolle wrote:
1) Typo was added in commit f8c95fe6d9adad72fc7bce90f4ab68d119f50c5b
(ARM: imx: support DEBUG_LL uart port selection for all i.MX SoCs).
Looking at that patch and at the tree
Signed-off-by: Shawn Guo shawn@linaro.org
,it does remove the MX50 reference, so this patch is not needed.
That's not correct:
$ git grep -n DEBUG_IMX50_IMX53_UART v3.9-rc2
v3.9-rc2:arch/arm/Kconfig.debug:495:
DEBUG_IMX50_IMX53_UART || \
Paul
SoCs).
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
The Kconfig entry for TS2020 based tuners defaults to modular if
DVB_FE_CUSTOMISE is set. But that Kconfig symbol was replaced with
MEDIA_SUBDRV_AUTOSELECT as of v3.7. So use the new symbol. And negate
the logic, so we are in line with all the similar entries in this file.
Signed-off-by: Paul
The Kconfig option MACH_OMAP_H4_OTG was already considered dead as of
v2.6.36, as can be seen in commit
267ecec95f7d215d2da38252640b06198515acc3 (Removing dead
MACH_OMAP_H4_OTG). Remove its last trace now.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Tested with make ARCH=arm menuconfig
Fix three typos (originally) introduced by commit
a9a84c37d1ee50db8f3752b117caf2b48dcd4f8a (atmel_lcdfb: backlight
control).
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Tested by grepping the tree.
1) So two of these typos were introduced in v2.6.25. (The third was
introduced in commit
setting of bus width from board code).
These two commits removed all gpio related code from these two drivers.
But they skipped removing their two selects of GPIO_PCA953X. Remove
these now as they are outdated. Their dependencies can never evaluate to
true anyhow.
Signed-off-by: Paul Bolle pebo
let's use
that.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Tested with make ARCH=powerpc oldconfig (on some powerpc
defconfig).
1) By the way: why does the XZ related code use both the macro
CONFIG_XZ_DEC_POWERPC and the macro XZ_DEC_POWERPC? (Ditto for other
architectures.) That looks odd
The Kconfig symbol POWER4_ONLY got removed in commit
694caf0255dcab506d1e174c96a65ab65d96e108 (powerpc: Remove
CONFIG_POWER4_ONLY). Remove its last traces.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested.
arch/powerpc/platforms/Kconfig.cputype | 6 ++
1 file changed, 2 insertions
The Kconfig symbol PCI_PERMEDIA got removed in v2.6.24, through commit
e6b6e3ffb9ee8926f9f2f7dc9147df73e27d5828 ([POWERPC] Remove APUS support
from arch/ppc). Remove its last occurrence.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Tested with make ARCH=powerpc menuconfig using ps3_defconfig
instead.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) The net effect of this is that the number of uarts of the S3C2412 CPU
drops from 4 to 3. So this needs testing (by people with access to that
hardware).
1) Related note: a few lines down there's the line
default 4
The Kconfig symbol SND_SOC_OF_SIMPLE got removed in commit
f0fba2ad1b6b53d5360125c41953b7afcd6deff0 (ASoC: multi-component - ASoC
Multi-Component Support). But that commit missed one instance. Remove
it now, together with the prompt it has effectively hidden ever since.
Signed-off-by: Paul Bolle
Commit 2d78d4beb64eb07d50665432867971c481192ebf ([PATCH] bitops:
sparc64: use generic bitops) made the default of GENERIC_HWEIGHT depend
on !ULTRA_HAS_POPULATION_COUNT. But since there's no Kconfig symbol with
that name, this always evaluates to true. Delete this dependency.
Signed-off-by: Paul
The Kconfig entry for QE_USB contains
default y if USB_GADGET_FSL_QE
But USB_GADGET_FSL_QE got removed in commit
193ab2a6070039e7ee2b9b9bebea754a7c52fd1b (usb: gadget: allow multiple
gadgets to be built). This default will therefor never be set and can
be removed.
Signed-off-by: Paul
The (rudimentary) support for the Openmoko Neo1973 GTA01 got removed in
commit 1ae5cbc52e7c6619a3f44b87809fd25370df31bb (ASoC: neo1973_wm8753:
remove references to the neo1973-gta01 machine). Remove its last traces
in the Kconfig file too.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested
all the dead code at the time) did not get
applied.
3) What is the current status of the (out of tree) code that adds
RALINK_RT288X and RALINK_RT305X?
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
On Wed, 2013-03-13 at 10:51 +0100, Jonas Gorski wrote:
On 13 March 2013 09:59, Paul Bolle pebo...@tiscali.nl wrote:
3) What is the current status of the (out of tree) code that adds
RALINK_RT288X and RALINK_RT305X?
They are now present in 3.9-rc1, see a0b0197c (more specifically
85639910
On Wed, 2013-03-13 at 13:30 +0200, Lasse Collin wrote:
On 2013-03-12 Paul Bolle wrote:
1) By the way: why does the XZ related code use both the macro
CONFIG_XZ_DEC_POWERPC and the macro XZ_DEC_POWERPC? (Ditto for other
architectures.) That looks odd.
In a preboot environment the options
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested. Perhaps the first test that people with access to the relevant
hardware might do, is to test _before applying this patch_ with FB_OMAP2
set. Perhaps this negative dependency isn't needed at all. Or is it
obvious?
drivers/gpu/drm/omapdrm
code were that can't happen anymore?
(Both functions being static they probably are inlined.)
2) And even if inlining does generate code where this can't happen,
isn't it enough that preq.dev can be used uninitialized if no code were
inlined?
Paul Bolle
--
To unsubscribe from this list: send
Team li...@simtec.co.uk
Cc: Paul Bolle pebo...@tiscali.nl
Signed-off-by: Cesar Eduardo Barros ces...@cesarb.net
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5cb888a..b73c00d 100644
--- a/MAINTAINERS
+++ b
On Sat, 2013-03-02 at 23:10 +, Ben Hutchings wrote:
On Sat, 2013-03-02 at 23:35 +0100, Paul Bolle wrote:
1) So if xen_vbd_translate() fails, it can return before setting
preq.dev. That makes the call of pr_debug() use an uninitialized value,
doesn't it?
Oh yes, so it's a completely
to generate the list of files to check against. Using the
files and directories currently in one's kernel tree is liable to
generating false positives or false negatives.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
On Mon, 2013-03-04 at 07:55 +, Jan Beulich wrote:
On 03.03.13 at 11:20, Paul Bolle pebo...@tiscali.nl wrote:
For one, a fix for the (indeed valid) compiler warning has been in
Konrad's tree for several days
(http://git.kernel.org/cgit/linux/kernel/git/konrad/xen.git/commit/drivers/block
commented out? There's no comment nor is there
anything in the commit explanation on this change.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
of that warning is, in short, that rcu_lockdep_assert()
compiles away if CONFIG_PROVE_RCU is not set. Silence this warning by
open coding nfnl_get_lock() in the sole place it was called, which
allows to remove that function.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Compile tested only
we can change the
while()-do{} loop into a do{}-while() loop. And that suffices to make
GCC see that 'ret' will not be used uninitialized.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Compile tested only!
drivers/media/usb/dvb-usb/m920x.c | 4 ++--
1 file changed, 2 insertions(+), 2
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
The kconfig parsing code doesn't care about this typo, but it's a typo
nevertheless.
drivers/hid/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
index 5f07d85..49e2939 100644
Do what commit f12a500e4adcc0961803e54b5ed1e74275d399f1
(ARM: SPEAr13xx: Enable CONFIG_ARCH_HAS_CPUFREQ) wanted to do.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested.
arch/arm/plat-spear/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/plat-spear
we can assume that this entry needs to select
COMMON_CLK instead.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested.
arch/arm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 5b71469..31acce7 100644
--- a/arch/arm
Commit f7ade3c168e4f437c11f57be012992bbb0e3075c (MIPS: Get rid of
CONFIG_CPU_HAS_LLSC) did what it promised to do. But since then that
macro and its Kconfig symbol popped up again. Get rid of those again.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Untested.
1) The related commits
Commit f7ade3c168e4f437c11f57be012992bbb0e3075c (MIPS: Get rid of
CONFIG_CPU_HAS_LLSC) did what it promised to do. But since then that
macro and its Kconfig symbol popped up again. Get rid of those again.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) This version fixes an embarrassing
On Tue, 2013-03-05 at 13:55 +0100, Jonas Gorski wrote:
On 5 March 2013 13:20, Paul Bolle pebo...@tiscali.nl wrote:
diff --git a/arch/mips/include/asm/mach-sead3/cpu-feature-overrides.h
b/arch/mips/include/asm/mach-sead3/cpu-feature-overrides.h
index d9c8284..b40f37f 100644
--- a/arch
the ahash functionality this driver uses.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Untested!
1) Apparently, one can indirectly select a Kconfig symbol. That actually
surprised me. But if the kconfig parser does not work this way this
patch (and it's explanation) is bogus.
drivers/crypto
. Change that one too.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) This patch was first send over a year ago. Now I have reapplied it on
top of v3.9-rc1, which only added an offset of two lines.
1) Still tested with make ARCH=ia64 menuconfig only (which makes it
rather lightly tested).
2
, there is no Kconfig symbol named EMAC_INC.
The select statement for that symbol is a nop. Drop it.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested, but it's hard to see what can got wrong here.
arch/m68k/Kconfig.machine | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/m68k/Kconfig.machine
(because they prefer an explicit, though
superfluous, select of COMMON_CLK) I'll redo my patch.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Commit 25e9d28d927d2e1731df53f60cde53d75bcb7c36 (ARM: EXYNOS: remove
system mmu initialization from exynos tree) removed the Kconfig symbol
EXYNOS_DEV_SYSMMU. Remove its last traces too.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Untested.
1) Please note that this patch changes
Fix obvious typo introduced in commit
e121aefa7d9f10eee5cf26ed47129237a05d940b (remoteproc: fix missing
CONFIG_FW_LOADER configurations).
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Untested.
1) The REMOTEPROC Kconfig entry has been using the useless FW_CONFIG
select statement for a few
that never hit mainline. Drop it.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) v2: Sebastian suggested to drop this select entirely.
1) Still untested.
arch/arm/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 5b71469..0c990b7 100644
--- a/arch
infrastructure).
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Untested.
1) Commit explanation inspired by commit
2c7d1644406748d7c5da7b9db3c5080296af55bf (sparc: Do not select
GENERIC_HARDIRQS_NO_DEPRECATED).
arch/arm64/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/Kconfig
was to select HDMI (which this
entry already did through depending on DRM) and to include linux/hdmi.h
(which this commit also did).
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested.
drivers/gpu/drm/tegra/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/tegra
for stable, be itself submitted with
CC:stable?
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, 2013-03-06 at 08:46 +0800, Greg KH wrote:
On Tue, Mar 05, 2013 at 11:22:49PM +0100, Paul Bolle wrote:
1) But actually thinking about this: that upstream commit did end up in
the (longterm) v3.4.y series. And my patch is also relevant for the
v3.8.y series.
As that patch
.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) This patch was first sent over a year ago. Now I have reapplied it on
top of v3.9-rc1, which required a trivial adaption to context changes.
1) Still git grep tested only.
2) Please note that ARCH_SCORE7, MACH_SPCT6600, and SCORE_SIM still
aren't
The Kconfig symbol GENERIC_TIME was removed from the kernel in v2.6.36,
with commit 592913ecb87a9e06f98ddb55b298f1a66bf94c6b (time: Kill off
CONFIG_GENERIC_TIME). Somehow this select statement still popped up
recently. It's a nop so we can drop it.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
on
INPUT_KEYBOARD this entry should select KEYBOARD_SAMSUNG instead.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Tested with git grep only.
1) Perhaps the fact that the symbol KEYBOARD_SAMSUNG enables a driver
called samsung-keypad caused confusion here. Anyhow, my choice for
KEYBOARD_SAMSUNG
The Kconfig symbol HAVE_SCHED_CLOCK got removed in v3.4, with commit
6905a65879b51d326396e63dfea40861a30bc17f (ARM: Make the sched_clock
framework mandatory). Drop the last two select statements for that
symbol too. They're useless now.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Tested
On Wed, 2013-03-06 at 14:32 +0200, Ohad Ben-Cohen wrote:
Robert Tivy (cc'ed) already submitted a patch to this (it's part of a
bigger series Robert is now polishing).
Great.
Rob, it might indeed be a good idea to add CC:
sta...@vger.kernel.org to the commit log.
Thanks,
Paul Bolle
The unused Kconfig symbol MACH_N35 was removed in commit
85fd6d63bf2927b9da7ab1b0d46723bfdb13808c (ARM: S3C2410: move
mach-s3c2410/* into mach-s3c24xx/). But there is still one (pointless)
select statement for that symbol. Drop it.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
arch/arm/mach
to touch it.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
of EXYNOS_DEV_SYSMMU around
(say) v3.10-rc1? If so, that's fine with me.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
is quite nice).
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
There is no Kconfig symbol PPC_WSP_COPRO. The select statement for it is
a nop. Drop it.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
A short treatise on the uneventful life of PPC_WSP_COPRO in the mainline
kernel tree
Release v3.0 included commit 76b4eda866c4936af8d696f040abea56bf688e16
count = width of
type [enabled by default]
Silence these warnings by casting the 'address' variable (of type
dma_addr_t) to u64 on those two lines.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Compile tested only.
1) Changing '0L' to 'OUL' might be a bit of cargo cult programming. I
doubt
looks a bit odd too.
And why is 'cookie' __u64? Is struct cpl_fw6_msg_ofld_connection_wr_rpl
used in userspace code? Can't 'cookie' be of type struct sk_buff *? Is
there a requirement for it to be 64 bits wide on both 32 bit and 64 bit?
Paul Bolle
--
To unsubscribe from this list: send the line
:
‘saa7164_s_register’ defined but not used [-Wunused-function]
Silence these warnings by wrapping these two functions in an #ifdef
CONFIG_VIDEO_ADV_DEBUG and #endif pair.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Compile tested only.
1) These warnings are apparently a side effect of commit
On Tue, 2013-02-05 at 09:46 -0600, Steve Wise wrote:
On 2/5/2013 4:15 AM, Paul Bolle wrote:
And why is 'cookie' __u64? Is struct cpl_fw6_msg_ofld_connection_wr_rpl
used in userspace code? Can't 'cookie' be of type struct sk_buff *? Is
there a requirement for it to be 64 bits wide on both 32
/infiniband/hw/cxgb4/cm.c:2941:16: warning: cast from pointer to
integer of different size [-Wpointer-to-int-cast]
[...]
But byte swapping isn't needed as the firmware doesn't actually touch
the cookie. Dropping byte swapping makes the warnings go away too.
Signed-off-by: Paul Bolle pebo
posted to silence two GCC warnings while
building v3.6-rc7. Basically identical warnings can still be seen while
building v3.8-rc5. What's the status of this patch?
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
On Mon, 2012-10-29 at 13:45 +0100, Paul Bolle wrote:
On Mon, 2012-10-29 at 12:17 +, James Bottomley wrote:
mvsas has a maintainer: poke them harder
According to MAINTAINERS that's you. Is Xiangliang Yu perhaps the actual
maintainer?
Building the mvsas driver triggers identical warnings
On Mon, 2012-11-05 at 11:58 +0100, Paul Bolle wrote:
Building advansys.o triggers this warning:
drivers/scsi/advansys.c:71:2: warning: #warning this driver is still not
properly converted to the DMA API [-Wcpp]
This warning can be traced back to a patch called advansys: add warning
On Wed, 2013-01-30 at 08:07 +, Saurav Kashyap wrote:
I am submitting some correction patches today and this patch will be part
of the scsi-misc submission after that set.
Thanks.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Wed, 2012-09-26 at 12:09 +0200, Paul Bolle wrote:
When fast calibration of the TSC fails an error is printed:
tsc: Fast TSC calibration failed
This message was printed at default level (ie, as a warning) before
commit c767a54ba0657e52e6edaa97cbe0b0a8bf1c1655 (x86/debug: Add
ENTRY
Drop these messages, that were probably used to debug the suspend and
resume code, but now serve no purpose.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) v1 was called PCI: pciehp: hide ENTRY messages behind ctrl_dbg().
But Bjorn and Rafael prefer to drop these messages completely.
1
/2012/11/24/96 .
Nothing has changed. I suggest to remove this entry entirely.
I guess the CATS entry might also be removed. But that doesn't have an
F: pattern, so I'm not sure what code that entry covers.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
look GCC is right here. But I'm totally new to the code in
question, so I'll just ask whether this can really go in stable as is.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
happen. So rework
the code to use the previous logic, but also make sure 'obj' will not be
dereferenced while NULL.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Compile tested only!
drivers/platform/x86/acer-wmi.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
]
The cause of that warning is that lockdep_assert_held() compiles away if
CONFIG_LOCKDEP is not set. Silence this warning by using the argument to
lockdep_assert_held() as a nop if CONFIG_LOCKDEP is not set.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Compile tested only.
1) This patch
? This doesn't seem to be related to
two older lpc_ich threads I was involved in (in November 2012). Not that
I mind testing stuff, that's not the problem...
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
On Fri, 2013-01-25 at 12:06 +0100, Linus Walleij wrote:
Basically I do git log and when I see this I think:
commit 0c418844dce21fa7000b51190f393c7d6a7ee12d
Author: Paul Bolle pebo...@tiscali.nl
Date: Mon Nov 19 21:04:11 2012 +0100
mfd: lpc_ich: One uninitialized cell is no error
On Fri, 2013-01-25 at 13:43 +0100, Linus Walleij wrote:
On Fri, Jan 25, 2013 at 1:00 PM, Paul Bolle pebo...@tiscali.nl wrote:
Would testing on 3.7.5 be helpful?
Sure it's as good an indicator of the quality of the patch as any.
If it works on that kernel, it makes probablility lower
On Fri, 2013-01-25 at 14:25 +0100, Paul Bolle wrote:
0) insmod-ing an updated lpc_ich.ko generated quite a bit of noise in
dmesg:
6[19913.247530] iTCO_wdt: Found a ICH8M-E TCO device (Version=2,
TCOBASE=0x1060)
6[19913.249310] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0
ENTRY
Messages like these are probably only useful while debugging pciehp, so
let's hide them behind the ctrl_dbg() macro.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Compile tested only!
1) Perhaps a better solution is to drop these messages entirely.
drivers/pci/hotplug/pciehp_core.c | 5
On Fri, 2013-01-25 at 14:25 +0100, Paul Bolle wrote:
1) Should I try booting with the updated module too?
Booting turned out to be a non-issue. I use lpc_ich as a module (Fedora
17 default) and lpc_ich isn't included by default in Fedora 17's
initramfs. So booting v3.7.5 with an updated module
module didn't lead to any obvious issues.
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 2013-01-24 at 01:07 +0900, Kouichi ONO wrote:
At target_fabric_port_link(), struct se_device *dev is used before set?
It seems the (stable specific) patch in
http://article.gmane.org/gmane.linux.kernel.stable/40880 should fix
that.
Paul Bolle
--
To unsubscribe from this list: send
Zhang's patch hits mainline
(presumably in one of the v3.9 release candidates)?
Paul Bolle
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
On Wed, 2013-02-20 at 10:40 +, James Bottomley wrote:
On Sat, 2013-02-09 at 21:09 +0100, Paul Bolle wrote:
--- a/drivers/scsi/aacraid/src.c
+++ b/drivers/scsi/aacraid/src.c
@@ -407,7 +407,7 @@ static int aac_src_deliver_message(struct fib *fib)
fib-hw_fib_va
.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Jack wanted to use uninitialized_var() after I posted the first
version of this trivial patch. I suggested to see what happened with
Ingo's idea to remove uninitialized_var() entirely. Nothing seems to
have happened, so I decided to try a different
count = width of
type [enabled by default]
These warnings are caused by a right shift of 32. Use upper_32_bits() to
suppress them.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Instead of a cast to u64, this version uses upper_32_bits() as James
suggested. I also stopped changing 0L to 0UL
and AHC_VL are only ever set for AHC_AIC7770 this fix
should not lead to any functional change.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) I noticed these warnings while building v3.6-rc6 on current Fedora
17, using Fedora's default config.
1) Compile tested only.
2) This patch
it by substituting ieee-dev for (its
equivalent) dev.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) I noticed this warning while building v3.6-rc6 on current Fedora 17,
using Fedora's default config.
1) Compile tested only (by just compiling libipw_wx.o).
drivers/net/wireless/ipw2x00
() will
always return 0. Suppress this warning in the way a few other drivers do
that too.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) I noticed this warning while building v3.6-rc6 on current Fedora 17,
using Fedora's default config.
1) Compile tested only.
drivers/isdn/hardware/mISDN/hfcpci.c
(and the commented out references to them) to
silence these warnings. Anyone wanting to fix the alarm irq
functionality can easily find the removed code in the git log of this
file or through some web searches.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) I noticed this warning while building
sas_dev_type' [-Wenum-compare]
Silence these warnings by using the named constants from enum
sas_device_type with the same value as the currently used named
constants.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) I noticed these warnings while building v3.6-rc6 on current Fedora
17, using
The named constant RAMDISK is unused. It used to set the (obsolete)
kernel boot header field ram_size, but its usage for that purpose got
dropped in commit 5e47c478b0b69bc9bc3ba544e4b1ca3268f98fef (x86: remove
zImage support). Now remove this constant too.
Signed-off-by: Paul Bolle pebo
DRAGEN2 should obviously be CONFIG_DRAGEN2, but the screen.h entry it
triggers only references files that are nowhere to be found in the
current tree. Besides, nothing uses screen.h. So just drop all that.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Entirely untested. It's hard to see
kernel to load
+ microcode to CPU's as early as possible. No functional change if no
+ microcode data is glued to the initrd, therefore it's safe to say Y.
+
config X86_MSR
tristate /dev/cpu/*/msr - Model-specific register support
---help---
Paul Bolle
The ramdisk kernel parameter was finally removed in commit
1adbee50fd6fce5af4feb34d2db93cfe4d2066a4 (ramdisk: remove
long-deprecated ramdisk= boot-time parameter). It had been marked as
deprecated since v1.3.96! Remove this note from its Kconfig entry.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
201 - 300 of 4150 matches
Mail list logo
