On Sun, 29 Dec 2013 23:47:20 +0100
Julia Lawall wrote:
> diff --git a/drivers/infiniband/hw/mlx4/sysfs.c
> b/drivers/infiniband/hw/mlx4/sysfs.c index 97516eb..db2ea31 100644
> --- a/drivers/infiniband/hw/mlx4/sysfs.c
> +++ b/drivers/infiniband/hw/mlx4/sysfs.c
> @@ -582,8 +582,10 @@ static int
Hi
I confirm that this patch works. Tested it overnight with Zedboard (Cortex A9).
Thanks again!
BR,
Jouko--
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
Viimeinen ilmoitus
Sähköpostiosoitteesi ID on voittanut (450,000.00 euroa) Espanjan "El Gordo"
Kansainvälinen E-mail arpajaisvoittoluettelot oli onnekas numeroita
9/11/13/24/43 ja
Ref: ES/9420X2/68.
Suunnittelua ja hallintaa Yhteystiedot:
STALLION MEGA KORVAUSVAATIMUKSEN AGENCY
Juan Carlos
>-Original Message-
>From: Jim Davis [mailto:jim.ep...@gmail.com]
>Sent: Tuesday, December 31, 2013 1:02 AM
>To: linux-kernel@vger.kernel.org; Greg Kroah-Hartman;
>andreas.dil...@intel.com; Peng, Tao; sachin.ka...@linaro.org;
>de...@driverdev.osuosl.org
>Subject: randconfig build error
Joe Perches wrote:
> I get:
>
> $ grep-2.5.4 -rP --include=*.[ch] -oh \
>
> "\b(?:printk|[a-z_]+_(?:printk|emerg|alert|crit|err|warn|notice|info|debug|dbg))[^;]*\bcurrent->[\w_]+"
> * | \
> grep -P -oh "\bcurrent->[\w_]+"| sort | uniq -c | sort -rn
> 380 current->pid
> 267
> > > > I'm just thinking of a programmer, e.g. changing a struct like this:
> > > >
> > > > struct foo {
> > > >u8 addr[ETH_ALEN];
> > > > - u16 dummy;
> > > > };
>
> I don't know of a way to catch that.
> Anyone else?
Well, one could have a semantic patch that checks for that. But the
On Tue, Dec 31, 2013 at 1:13 AM, Johannes Berg
wrote:
>
> On Mon, 2013-12-30 at 19:57 -0200, Henrique de Moraes Holschuh wrote:
> > On Mon, 30 Dec 2013, Johannes Berg wrote:
> > > On Mon, 2013-12-30 at 20:58 +0100, Julia Lawall wrote:
> > > > > Is there any way we could catch (sparse, or some
Hi,
One comment as following.
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Friday, December 27, 2013 12:00 PM
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH
On Tue, Dec 24, 2013 at 03:39:50PM +0100, Geert Uytterhoeven wrote:
> On Fri, Nov 22, 2013 at 4:47 PM, Geert Uytterhoeven
> wrote:
> > When booting a multi-platform m68k kernel on a non-Mac with "console=ttyS0"
> > on the kernel command line, it crashes with:
>
> Can we please get this in
On 12/30, Rob Clark wrote:
> On Mon, Dec 30, 2013 at 8:12 PM, Rob Clark wrote:
> > On Mon, Dec 30, 2013 at 4:15 PM, Stephen Boyd wrote:
> >> This file doesn't use the clk_reset() API that is exposed in
> >> mach-msm's mach/clk.h file. Remove the include so that this
> >> driver can be compiled
> What about something like this?
>
> Not shcheduling timer when nothing changed should save a bit of power/cpu...
>
> if (pattern_data->pattern[pattern_data->count] == '/') {
> return;
> }
>
> this = pattern_data->pattern[pattern_data->count]
> if (this == '#')
> new_brigtness =
On 12/30/2013 08:53 PM, Tim Jester-Pfadt wrote:
Fixed required and prohibited spaces to make rtw_io.h checkpatch.pl clean
Signed-off-by: Tim Jester-Pfadt
---
drivers/staging/rtl8188eu/include/rtw_io.h | 36 +++---
1 file changed, 18 insertions(+), 18 deletions(-)
Reserving a tag (request) for flush to avoid dead lock is a overkill. tag is
valuable resource. We can track flush request number and disallow too many
pending flush requests allocated. With this patch,
blk_mq_alloc_request_pinned() could do a busy nop (but not a dead loop) if too
pending
steal_tags only happens when free tags is more than half of the total tags.
This is too restrict and can cause live lock. I found one cpu has free tags,
but other cpu can't steal (thread is bound to specific cpus), threads which
wants to allocate tags are always sleeping. I found this when I run
Hi Mark,
> Subject: Re: [PATCH] ASoC: fsl_sai: Fix one bug for hardware limitation.
>
> On Thu, Dec 26, 2013 at 10:57:22AM +0800, Xiubo Li wrote:
> > This is maybe one bug or a limitation of the hardware that the {T,R}CR2's
> > Synchronous Mode bits must be set as late as possible, or the SAI
> Subject: Re: [PATCH] ASoC: simple-card: cleanup asoc_simple_card_parse_of()
> code
>
> On Fri, Dec 27, 2013 at 11:14:38AM +0800, Xiubo Li wrote:
> > Since there is only one common format via "simple-audio-card,format"
> > for simple card driver(CPU & CODEC DAI), there is no need to do the
> >
On 12/30/2013 05:48 PM, Kirill A. Shutemov wrote:
On Mon, Dec 30, 2013 at 11:33:47AM -0500, Sasha Levin wrote:
On 12/30/2013 06:43 AM, Kirill A. Shutemov wrote:
On Sat, Dec 28, 2013 at 08:45:03PM -0500, Sasha Levin wrote:
We've recently stumbled on several issues with the page lock which
On 12/30/13, Prarit Bhargava wrote:
>
>
> On 12/30/2013 07:56 AM, rui wang wrote:
>
>> An irq can be mapped to only one vector number, but can have multiple
>> destination CPUs. i.e. the same irq/vector can appear on multiple
>> CPUs' vector_irq[]. So checking data->affinity is necessary I think.
Fixed required and prohibited spaces to make rtw_io.h checkpatch.pl clean
Signed-off-by: Tim Jester-Pfadt
---
drivers/staging/rtl8188eu/include/rtw_io.h | 36 +++---
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git
These days comedi drivers are looking really nice. :) You will need to
resend because it's missing a change log and a Signed-off-by line. Wait
for Ian or Hartley to comment before resending. I had a few minor style
nits mentioned inline below. Run the patch through
`scripts/checkpatch.pl
From: "Felipe F. Tonello"
Make sure user-space will receive the touch end event even if the device
driver suspends while touchscreen is still active (with fingers touching it).
Signed-off-by: Felipe F. Tonello
---
drivers/input/touchscreen/egalax_ts.c | 5 +
1 file changed, 5
From: "Felipe F. Tonello"
Adds a helper function to send end touch events for active tracking ids.
And also implements it in egalax driver.
Felipe F. Tonello (2):
input: mt: Add helper function to send end events
input: egalax: report end state in suspend callback
drivers/input/input-mt.c
From: "Felipe F. Tonello"
This is useful to report for users of devices that don't know anything
about the suspension of the device. So users will receive a touch end event
when the device is about to suspend, making it more user friendly.
One example of users is the X Server with the evdev
>
> From: Stefan Beller
>To: PINTU KUMAR ; "linux...@kvack.org"
>; "linux-kernel@vger.kernel.org"
>; "mgor...@suse.de"
>Sent: Monday, 30 December 2013 1:55 AM
>Subject: Re: Help about calculating total memory consumption during booting
>
>
>On 29.12.2013
On Monday, December 30, 2013 03:58:43 PM Kashyap Chamarthy wrote:
> On 12/29/2013 04:04 PM, Rafael J. Wysocki wrote:
> > On Sunday, December 29, 2013 01:12:18 PM Kashyap Chamarthy wrote:
> >> [. . .]
> >>
> Here's host dmesg: https://bugzilla.kernel.org/attachment.cgi?id=119751
>
>
Hi Mark,
> -
> ..
>
> /* get CPU/CODEC common format via simple-audio-card,format */
> info->daifmt = snd_soc_of_parse_daifmt(node, "simple-audio-card,") &
> (SND_SOC_DAIFMT_FORMAT_MASK | SND_SOC_DAIFMT_INV_MASK);
>
> ..
>
>
This patch adds Comedi driver for Humusoft MF634 (PCIe) and MF624 (PCI)
data acquisition cards. The legacy card Humusoft MF614 is not supported.
More info about the cards may be found at http://humusoft.cz/produkty/datacq/
The driver was tested with both cards. Everything seems to work properly.
create mode 100644 drivers/staging/comedi/drivers/mf6x4.c
diff --git a/drivers/staging/comedi/Kconfig b/drivers/staging/comedi/Kconfig
index bfa27e7..89e25b4 100644
--- a/drivers/staging/comedi/Kconfig
+++ b/drivers/staging/comedi/Kconfig
@@ -884,6 +884,12 @@ config COMEDI_GSC_HPDI
To
Hi Mark and all,
Merry Christmas.
> Subject: Re: [PATCH] ASoC: simple-card: cleanup asoc_simple_card_parse_of()
> code
>
> On Fri, Dec 27, 2013 at 11:14:38AM +0800, Xiubo Li wrote:
> > Since there is only one common format via "simple-audio-card,format"
> > for simple card driver(CPU & CODEC
v2 changlog:
1./ Rebased on the latest code of for-next branch.
As Mark pointed out, the driver should register all regulators
regardless of how many are used in the system in order to aid diagnostics.
But in the previous patch, only register the regulators that are used.
Signed-off-by: Wenyou
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Monday, December 30, 2013 8:03 PM
> To: Yang, Wenyou
> Cc: lgirdw...@gmail.com; plagn...@jcrosoft.com; Ferre, Nicolas; linux-
> ker...@vger.kernel.org; linux-arm-ker...@lists.infradead.org
> Subject: Re: [PATCH]
In his regular article entitled Build regressions/improvements in v3.13-rc6"
(http://lkml.indiana.edu/hypermail/linux/kernel/1312.3/01550.html), Geert
Uytterhoeven reports the following warning regression:
+ /scratch/kisskb/src/drivers/net/wireless/b43/phy_n.c: warning: 'val_addr' may
be used
On Mon, Dec 30, 2013 at 8:12 PM, Rob Clark wrote:
> On Mon, Dec 30, 2013 at 4:15 PM, Stephen Boyd wrote:
>> This file doesn't use the clk_reset() API that is exposed in
>> mach-msm's mach/clk.h file. Remove the include so that this
>> driver can be compiled as part of the multi-platform kernel.
On Mon, Dec 30, 2013 at 4:15 PM, Stephen Boyd wrote:
> This file doesn't use the clk_reset() API that is exposed in
> mach-msm's mach/clk.h file. Remove the include so that this
> driver can be compiled as part of the multi-platform kernel.
Thanks!
Signed-off-by: Rob Clark
> Cc: Rob Clark
>
On Mon, Dec 30, 2013 at 1:37 PM, David Rientjes wrote:
> 8779657d29c0 ("stackprotector: Introduce CONFIG_CC_STACKPROTECTOR_STRONG")
> causes the build to break when the compiler doesn't support
> -fstack-protector-strong:
>
> cc1: error: unrecognized command line option
>
On Mon, 30 Dec 2013 18:24:51 -0500
Joe Xue wrote:
> >> +#define MAX_PATTEN_LEN 255
> >
> > Arbitary limits that are not needed if it was in userspace, and not it
> > seems a sensible one - why not use 256 ?
>
> The maximum memory is 256, we keep one for '\0'
Why - you have pattern_len already
Dear Friend,
I need someone in your Country I want to invest 30MillionEuros. For more info
send me your telephone number for conversation to enable us have a concrete
discussion and meeting.
Best Regards
Mr.Norbert Koffi
--
To unsubscribe from this list: send the line "unsubscribe
On Mon, Dec 30, 2013 at 08:40:45PM -0200, Henrique de Moraes Holschuh wrote:
> On Mon, 30 Dec 2013, Henrique de Moraes Holschuh wrote:
> > On Mon, 30 Dec 2013, Julian Andres Klode wrote:
> > > On Mon, Nov 11, 2013 at 02:56:30PM +0100, Julian Andres Klode wrote:
> > > > Add support for battery
Hi again,
On Mon, Dec 30, 2013 at 03:52:51PM +0100, Sebastian Reichel wrote:
> On Mon, Dec 30, 2013 at 03:31:25PM +0100, Pali Rohár wrote:
> > [...] I think that correct commit message is not needed now.
> Wolfram Sang gave a talk about that at 30C3 yesterday. Official
> recordings of his talk
>> +#define MAX_PATTEN_LEN 255
>
> Arbitary limits that are not needed if it was in userspace, and not it
> seems a sensible one - why not use 256 ?
The maximum memory is 256, we keep one for '\0'
>> +static ssize_t pattern_delay_unit_store(struct device *dev,
>> + struct device_attribute *attr,
The associative array code creates unnecessary and potentially problematic
global variable 'status'. Remove it since never used.
Signed-off-by: Stephen Hemminger
--- a/lib/assoc_array.c 2013-12-20 07:59:47.468147094 -0800
+++ b/lib/assoc_array.c 2013-12-30 15:14:38.034880698 -0800
@@ -157,7
On Tue, 2013-12-31 at 00:13 +0100, Johannes Berg wrote:
> On Mon, 2013-12-30 at 19:57 -0200, Henrique de Moraes Holschuh wrote:
> > On Mon, 30 Dec 2013, Johannes Berg wrote:
> > > On Mon, 2013-12-30 at 20:58 +0100, Julia Lawall wrote:
> > > > > Is there any way we could catch (sparse, or some
On Mon, 2013-12-30 at 19:57 -0200, Henrique de Moraes Holschuh wrote:
> On Mon, 30 Dec 2013, Johannes Berg wrote:
> > On Mon, 2013-12-30 at 20:58 +0100, Julia Lawall wrote:
> > > > Is there any way we could catch (sparse, or some other script?) that
> > > > struct reorganising won't break the
Hi!
> > +#define NBT_DBG(fmt, arg...) \
> > + pr_debug("%s: " fmt "" , __func__ , ## arg)
> > +
> > +#define NBT_DBG_FW(fmt, arg...) \
> > + pr_debug("%s: " fmt "" , __func__ , ## arg)
> > +
> > +#define NBT_DBG_POWER(fmt, arg...) \
> > + pr_debug("%s: " fmt "" ,
On Mon, Dec 30, 2013 at 11:33:47AM -0500, Sasha Levin wrote:
> On 12/30/2013 06:43 AM, Kirill A. Shutemov wrote:
> >On Sat, Dec 28, 2013 at 08:45:03PM -0500, Sasha Levin wrote:
> >>We've recently stumbled on several issues with the page lock which
> >>triggered BUG_ON()s.
> >>
> >>While working on
On Mon, 30 Dec 2013, Henrique de Moraes Holschuh wrote:
> On Mon, 30 Dec 2013, Julian Andres Klode wrote:
> > On Mon, Nov 11, 2013 at 02:56:30PM +0100, Julian Andres Klode wrote:
> > > Add support for battery charge thresholds in new Sandy Bridge and Ivy
> > > Bridge
> > > ThinkPads. Based on the
Hi!
> > +++ b/drivers/bluetooth/hci_h4p/core.c
> > @@ -0,0 +1,1357 @@
> > +/*
> > + * This file is part of hci_h4p bluetooth driver
> > + *
> > + * Copyright (C) 2005-2008 Nokia Corporation.
> > + *
> > + * Contact: Ville Tervo
>
> I think you can just remove the contact names since I think
Mention module name in Kconfig.
Signed-off-by: Pavel Machek
diff --git a/drivers/bluetooth/Kconfig b/drivers/bluetooth/Kconfig
index 9d46f23..a53e8c7 100644
--- a/drivers/bluetooth/Kconfig
+++ b/drivers/bluetooth/Kconfig
@@ -241,7 +241,7 @@ config BT_WILINK
core driver to
Hi!
> > +config BT_HCIH4P
> > + tristate "HCI driver with H4 Nokia extensions"
> > + depends on BT && ARCH_OMAP
>
> Since then we moved away from doing hci_* prefix of drivers since that is
> misleading. See btusb.ko, btmrvl_sdio.ko etc.
>
> So this might be better named BT_NOK_H4P or
Hi Grant, Rob,
On Tue, 10 Dec 2013, Paul Walmsley wrote:
> On Sun, 24 Nov 2013, Grant Likely wrote:
>
> > On Fri, 22 Nov 2013 17:50:35 -0800, Tony Lindgren wrote:
> > > * Tony Lindgren [131122 17:16]:
> > > > * Tony Lindgren [131122 17:09]:
> > > > > * Russell King - ARM Linux [131122
Linus,
Please pull a couple of DT fixes for 3.13.
Rob
The following changes since commit 413541dd66d51f791a0b169d9b9014e4f56be13c:
Linux 3.13-rc5 (2013-12-22 13:08:32 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
On Mon, 30 Dec 2013, Julian Andres Klode wrote:
> On Mon, Nov 11, 2013 at 02:56:30PM +0100, Julian Andres Klode wrote:
> > Add support for battery charge thresholds in new Sandy Bridge and Ivy Bridge
> > ThinkPads. Based on the unofficial documentation in tpacpi-bat.
> >
> > The threshold files
On Mon, 30 Dec 2013, Johannes Berg wrote:
> On Mon, 2013-12-30 at 20:58 +0100, Julia Lawall wrote:
> > > Is there any way we could catch (sparse, or some other script?) that
> > > struct reorganising won't break the condition needed ("within a
> > > structure that contains at least two more
8779657d29c0 ("stackprotector: Introduce CONFIG_CC_STACKPROTECTOR_STRONG")
causes the build to break when the compiler doesn't support
-fstack-protector-strong:
cc1: error: unrecognized command line option ‘-fstack-protector-strong’
cc1: error: unrecognized command line option
On 12/30/2013 11:40 AM, Andreas Dilger wrote:
> On Dec 30, 2013, at 12:18, Dave Hansen wrote:
>> Why is this necessary to do in the kernel? Why not leave it to
>> userspace to walk the filesystem(s)?
>
> I would suspect that trying to do it in userspace would be quite bad. It
> would require
On Mon, 2013-12-30 at 20:58 +0100, Julia Lawall wrote:
> > Is there any way we could catch (sparse, or some other script?) that
> > struct reorganising won't break the condition needed ("within a
> > structure that contains at least two more bytes")?
>
> What kind of reorganizing could happen?
On 12/30/13 13:15, Stephen Boyd wrote:
> This file doesn't use the clk_reset() API that is exposed in
> mach-msm's mach/clk.h file. Remove the include so that this
> driver can be compiled as part of the multi-platform kernel.
>
> Cc: Rob Clark
> Cc: Dave Airlie
Signed-off-by: Stephen Boyd
>
This file doesn't use the clk_reset() API that is exposed in
mach-msm's mach/clk.h file. Remove the include so that this
driver can be compiled as part of the multi-platform kernel.
Cc: Rob Clark
Cc: Dave Airlie
---
drivers/gpu/drm/msm/mdp4/mdp4_dtv_encoder.c | 2 --
1 file changed, 2
On 12/30/13 13:15, Stephen Boyd wrote:
> These patches allow the DT based MSM platforms to be built as part of the
> multi-platform kernel. I need acks from Chris Ball on the mmc patch and
> Rob/Dave on the drm patch. I dropped Arnd's ack on patch 6 because I've
> rebased that patch on top of the
From: "Ivan T. Ivanov"
This patch fix compilation error when driver is compiled
in multi-platform builds.
drivers/built-in.o: In function `msm_otg_link_clk_reset':
./drivers/usb/phy/phy-msm-usb.c:314: undefined reference to `clk_reset'
./drivers/usb/phy/phy-msm-usb.c:318: undefined reference to
The MSM timer is only used on MSM devices that don't have the
architected timers. Introduce a hidden Kconfig option for this
driver so that we don't build it on the platforms that don't need
it.
Signed-off-by: Stephen Boyd
---
arch/arm/mach-msm/Kconfig | 9 +
arch/arm/mach-msm/Makefile
These patches allow the DT based MSM platforms to be built as part of the
multi-platform kernel. I need acks from Chris Ball on the mmc patch and
Rob/Dave on the drm patch. I dropped Arnd's ack on patch 6 because I've
rebased that patch on top of the patchset David sent out (which this is in
reply
The DT based MSM platforms can join the multi-platform builds, so
introduce a DT based ARCH_MSM option. This option allows DT based
MSM platforms to be built into the multi-platform kernel. Also
introduce a hidden ARCH_MSM config that both the DT and non-DT
platform support code select to avoid
The functionality provided by clock.c in mach-msm is only needed
on proc_comm based platforms. Only build the file if proc_comm is
enabled. This prevents compile failures for platforms that are
part of the multi-platform kernel.
Signed-off-by: Stephen Boyd
---
arch/arm/mach-msm/Makefile | 2 +-
The msm_serial_hs driver uses mach specific dma APIs. This is not
compatible with the multi-platform ARM effort. Let's only compile
this driver on MSM devices that are prepared to support it;
allowing the DT based MSM devices to enter the multi-platform ARM
build.
Acked-by: Greg Kroah-Hartman
The msm_sdcc driver uses mach specific dma APIs. This is not
compatible with the multi-platform ARM effort. Let's only compile
this driver on MSM devices that are prepared to support it,
allowing the DT based MSM devices to enter the multi-platform ARM
build.
Cc: Chris Ball
Signed-off-by:
On 12/30/2013 12:15 PM, Julia Lawall wrote:
From: Julia Lawall
Ether_addr_equal_64bits is more efficient than ether_addr_equal, and can be
used when each argument is an array within a structure that contains at
least two bytes of data beyond the array.
The structures involved are:
CC davem, sparclinux
On Sun, Nov 24, 2013 at 12:54 AM, Kirill Tkhai wrote:
> 23.11.2013, 22:40, "Guenter Roeck" :
>> ===
>> Building sparc64:allmodconfig ... failed
>> --
>> Error log:
>> arch/sparc/kernel/kgdb_64.c: In function 'kgdb_trap':
>>
On Wed, Dec 18, 2013 at 06:17:33AM +, Zheng, Lv wrote:
> Currently we didn't do much on automatically optimized out ACPI_FUTURE_USAGE
> functions as long as they do not affect the generation of vmlinux binary.
They do affect the size of vmlinux, though, if they're left compiled in
but not
"perf list" listing of hardware events doesn't work on older ARM devices.
The change enabling event detection:
commit b41f1cec91c37eeea6fdb15effbfa24ea0a5536b
Author: Namhyung Kim
Date: Tue Aug 27 11:41:53 2013 +0900
perf list: Skip unsupported events
uses the following code in
On Sat, Dec 21, 2013 at 10:14:09AM -0800, Randy Dunlap wrote:
> On 12/21/13 08:21, Masanari Iida wrote:
> > Correct spelling typo in Documentations/virtual/kvm
> >
> > Signed-off-by: Masanari Iida
>
> Acked-by: Randy Dunlap
>
> Thanks.
Applied, thanks.
--
To unsubscribe from this list: send
Hi,
I am Ms.Riojas,US citizen in Afghanistan ,it's my great pleasure to come across
your contact today.If you wouldn't mind, can we chat? On face book/ Skype or
yahoo messenger for an important discussion that will project good image to our
future. As we are ready to go home in few months
We only setup a workqueue for edac devices that use the polling
method. We still try to cancel the workqueue if an edac_device
uses the irq method though. This causes a warning from debug
objects when we remove an edac device:
WARNING: CPU: 0 PID: 56 at lib/debugobjects.c:260
The Krait L1/L2 error reporting device is made up of two
interrupts, one per-CPU interrupt for the L1 caches and one
interrupt for the L2 cache.
Cc: Lorenzo Pieralisi
Cc: Mark Rutland
Cc: Kumar Gala
Cc:
Signed-off-by: Stephen Boyd
---
Documentation/devicetree/bindings/arm/cpus.txt | 72
In the near future we're going to use these percpu irq functions
in the Krait CPU EDAC driver. Export them so that the EDAC driver
can be compiled as a module.
Acked-by: Thomas Gleixner
Signed-off-by: Stephen Boyd
---
kernel/irq/manage.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
This allows us to probe the krait-edac driver.
Cc: David Brown
Signed-off-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 41 +
1 file changed, 41 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
Add support for the Krait CPU cache error detection. This is a
simplified version of the code originally written by Stepan
Moskovchenko[1] ported to the EDAC device framework.
[1]
https://www.codeaurora.org/cgit/quic/la/kernel/msm/tree/arch/arm/mach-msm/cache_erp.c?h=msm-3.4
Cc: Stepan
Krait CPUs have a handful of L2 cache controller registers that
live behind a cp15 based indirection register. First you program
the indirection register (l2cpselr) to point the L2 'window'
register (l2cpdr) at what you want to read/write. Then you
read/write the 'window' register to do what you
This patchset adds support for the Krait L1/L2 cache error detection
hardware. The first patch fixes a generic framework bug. The next
two patches lay the groundwork for this driver to be added by
exporting percpu irq functions as well as adding the Krait l2 indirection
register code. The next
On Mon, 30 Dec 2013, Julian Andres Klode wrote:
> I think that a more generic approach is a good idea, but
> I don't think creating a new power supply device would be the right
...
> We could extend the existing battery devices and then get paths like
>
From: Fabio Estevam
There is no need to jump to the 'err' label.
Returnn the error directly instead.
Signed-off-by: Fabio Estevam
---
drivers/regulator/wm831x-dcdc.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/regulator/wm831x-dcdc.c
> Seems to be missing an "iwlwifi:" or so prefix, but I guess we can add
> it when we take the patch ...
Sorry. Not sure why that happened. I'll look into it.
> Is there any way we could catch (sparse, or some other script?) that
> struct reorganising won't break the condition needed ("within
On Dec 30, 2013, at 12:18, Dave Hansen wrote:
>
> Why is this necessary to do in the kernel? Why not leave it to
> userspace to walk the filesystem(s)?
I would suspect that trying to do it in userspace would be quite bad. It would
require traversing the whole directory tree to issue cache
On Mon, 2013-12-30 at 14:55 +0800, Chen Baozi wrote:
> xen_remap used to be defined as ioremap_cached on arm64. In commit
> c04e8e2fe, a new ioremap_cache was implemented, and ioremap_cached
> was deleted, while xen_remap stays the same. This would lead to
> the failure when building with
On 12/30/2013 05:45 AM, Li Wang wrote:
> This patch extends 'fadvise' to support directory level page cache
> cleaning. The call to posix_fadvise(fd, 0, 0, POSIX_FADV_DONTNEED)
> with 'fd' referring to a directory will recursively reclaim page cache
> entries of files inside 'fd'. For secruity
On Mon, 2013-12-30 at 19:15 +0100, Julia Lawall wrote:
> From: Julia Lawall
>
> Ether_addr_equal_64bits is more efficient than ether_addr_equal, and can be
> used when each argument is an array within a structure that contains at
> least two bytes of data beyond the array.
>
> The structures
Hi Martin,
On Sun, Dec 15, 2013 at 12:33 PM, Martin Mares wrote:
> I see that a mechanism for fast lookup of hardware identification data
> is needed. However, why should such a mechanism depend on udev, systemd,
> or Linux in general?
>
> What I would really like to have is a universal library
This lets you select hwdb support at compile time.
hwdb is an efficient hardware database shipped with recent versions of udev. It
contains
among other sources pci.ids so querying hwdb rather than reading pci.ids
directly should give
the same result.
Ideally Linux distros using udev could stop
The x86 "Processor type and features" menu has really been
letting itself go over the years. It needs to be put on a
diet as a new-year's resolution.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
From: Dave Hansen
This takes the relatively obscure (NUMA-Q anyone?) platforms
(both 32 and 64-bit) and sticks them in their own menu.
Virtually nobody needs to set these, and those that do know how
to find them the hard way.
Signed-off-by: Dave Hansen
---
From: Dave Hansen
This consolidates a bunch of VM, memory and NUMA options down to
be under a single Kconfig menu. Most of this stuff is pretty
obscure, like HIGHPTE or ZONE_DMA support. It doesn't really
deserve to be in the top-level menu.
For what it's worth "Processor type and features"
From: Dave Hansen
This tries to consolidate the actual processor options that
someone might want to configure. It's a bit arbitrary how you
might separate these, but I at least took a stab at it.
The real goal here was to hide stuff that folks will rarely look
at, and to make them easier to
These options fit in much better in the "Virtualization" than in
the processor features menu. Move them.
Signed-off-by: Dave Hansen
Cc: Borislav Petkov
Cc: Dmitry Torokhov
Cc: K. Y. Srinivasan
Cc: Haiyang Zhang
Cc: Alexander Graf
Cc: Gleb Natapov
Cc: Paolo Bonzini
---
From: Dave Hansen
This just continues to move things under the Memory and NUMA
Options menu, breaking it up a bit to make the patches easier to
audit.
Signed-off-by: Dave Hansen
---
linux.git-davehans/arch/x86/Kconfig | 248 ++--
1 file changed, 124
From: Dave Hansen
This removes another 4 lines from the default x86 menu. Note
that I slightly changed the MTRR prompt text since PAT is
hidden under here. This makes PAT easier to find since it
"depends on MTRR" anyway.
Signed-off-by: Dave Hansen
---
linux.git-davehans/arch/x86/Kconfig |
From: Dave Hansen
These are a few architecture-specific options that affect the
scheduler. Group them together.
Signed-off-by: Dave Hansen
---
linux.git-davehans/arch/x86/Kconfig | 28
1 file changed, 16 insertions(+), 12 deletions(-)
diff -puN
From: Dave Hansen
This is a fairly small one, but it still saves 3 lines in the
top-level menu.
Signed-off-by: Dave Hansen
---
linux.git-davehans/arch/x86/Kconfig | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff -puN arch/x86/Kconfig~x86-mce-menu arch/x86/Kconfig
---
From: Dave Hansen
While I respect the fact that the owners of Dell Inspiron 8000s
have kept I8K compiling and "working" all these years, the URL
referenced contains a helpful README:
> This package is no longer maintained by me. I don't use it
> anymore and I'm not interested in maintaing it.
From: Dave Hansen
Move the "Memtest" option over to the "Memory Debugging" menu.
The code is not x86 specific at all, but it still resides in
arch/x86, so keep the x86 dependency.
Signed-off-by: Dave Hansen
---
linux.git-davehans/arch/x86/Kconfig | 11 ---
From: Fabio Estevam
We should use 'platform' in the MODULE_ALIAS for the regulator.
Signed-off-by: Fabio Estevam
---
drivers/regulator/pfuze100-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/pfuze100-regulator.c
1 - 100 of 578 matches
Mail list logo
