Re: [PATCH 6/6] x86: Allow disabling HW_BREAKPOINTS and PERF_EVENTS

* Andi Kleen wrote: > From: Andi Kleen > > As suggested by Ingo. No, you haven't read my suggestion carefully enough so NAK. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo i

Re: [dm-devel] dm-writeboost testing

Mikulas, > nvidia binary driver, but it may happen in other parts of the kernel too. > The fact that it works in your setup doesn't mean that it is correct. You are right. I am convinced. As far as I looked around the kernel code, it seems to be choosing kthread when one needs looping in backgro

Re: [PATCH] kernel/exit.c: call read_unlock() when failure occurs after already called read_lock() in do_wait().

On 10/05/2013 02:34 PM, Al Viro wrote: > On Sat, Oct 05, 2013 at 01:53:26PM +0800, Chen Gang wrote: >> If failure occurs after called read_lock(), need call read_unlock() too. >> >> It can fail in multiple position, so add new tag 'fail_lock' for it >> (also can let 'if' only content one jump state

Re: [dm-devel] Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]

Dave, > That's where arbitrary delays in the storage stack below XFS cause > problems - if the first FUA log write is delayed, the next log > buffer will get filled, issued and delayed, and when we run out of > log buffers (there are 8 maximum) the entire log subsystem will > stall, stopping *all*

Re: [PATCH v4] i2c: enable runtime PM for I2C adapter devices enumerated from ACPI

On Tue, Oct 01, 2013 at 04:09:42PM +0300, Mika Westerberg wrote: > The ACPI specification requires the parent device to be powered on before > any of its children. It can be only powered off when all the children are > already off. > > Currently whenever there is no I2C traffic going on, the I2C c

Re: [PATCH 00/16] sched/wait: Collapse __wait_event macros -v5

* Peter Zijlstra wrote: > On Fri, Oct 04, 2013 at 10:44:05PM +0200, Peter Zijlstra wrote: > > > > slightly related; do we want to do something like the following two > > patches? > > and Yeah, both look good to me - but I'd move them into kernel/sched/completion.c and kernel/sched/wait.c if

[PATCH] IIO AD7923 iio_consumer support

This patch adds support for iio_consumer to Analog Devices AD7923 ADC driver. Signed-off-by: Christophe Leroy Verified-by: Patrick Vasseur diff -urN a/drivers/iio/adc/ad7923.c b/drivers/iio/adc/ad7923.c --- a/drivers/iio/adc/ad7923.c 1970-01-01 01:00:00.0 +0100 +++ b/drivers/iio/adc/ad

Re: [PATCH] IIO AD7923 iio_consumer support

On 10/05/2013 10:21 AM, Christophe Leroy wrote: > This patch adds support for iio_consumer to Analog Devices AD7923 ADC driver. > > Signed-off-by: Christophe Leroy > Verified-by: Patrick Vasseur > > diff -urN a/drivers/iio/adc/ad7923.c b/drivers/iio/adc/ad7923.c > --- a/drivers/iio/adc/ad7923.c

Re: [PATCH] IIO AD7923 iio_consumer support

Le 05/10/2013 10:41, Lars-Peter Clausen a écrit : On 10/05/2013 10:21 AM, Christophe Leroy wrote: + .consumer_channel = "channel_0", + .adc_channel_label = "0", + }, + { + .consumer_dev_name = AD7923_NAME, + .consumer_channel =

Re: [PATCH] IIO AD7923 iio_consumer support

On 10/05/2013 11:18 AM, leroy christophe wrote: > > Le 05/10/2013 10:41, Lars-Peter Clausen a écrit : >> On 10/05/2013 10:21 AM, Christophe Leroy wrote: >>> +.consumer_channel = "channel_0", >>> +.adc_channel_label = "0", >>> +}, >>> +{ >>> +.consumer_dev_name = AD7

Re: [PATCH] IIO AD7923 iio_consumer support

Le 05/10/2013 11:35, Lars-Peter Clausen a écrit : On 10/05/2013 11:18 AM, leroy christophe wrote: Le 05/10/2013 10:41, Lars-Peter Clausen a écrit : On 10/05/2013 10:21 AM, Christophe Leroy wrote: +.consumer_channel = "channel_0", +.adc_channel_label = "0", +}, +{ +

Re: [PATCH] IIO AD7923 iio_consumer support

On 10/05/2013 11:39 AM, leroy christophe wrote: > > Le 05/10/2013 11:35, Lars-Peter Clausen a écrit : >> On 10/05/2013 11:18 AM, leroy christophe wrote: >>> Le 05/10/2013 10:41, Lars-Peter Clausen a écrit : On 10/05/2013 10:21 AM, Christophe Leroy wrote: > +.consumer_channel = "ch

Re: [PATCH V2] tick: Make sleep length calculation more accurate

On Wed, Oct 02, 2013 at 08:03:39PM +0200, Daniel Lezcano wrote: > On 10/02/2013 06:42 PM, Frederic Weisbecker wrote: > >On Wed, Oct 02, 2013 at 06:22:29PM +0200, Daniel Lezcano wrote: > >>On 10/02/2013 05:57 PM, Frederic Weisbecker wrote: > >>>2013/10/2 Daniel Lezcano : > The sleep_length is co

Tutorial Arcgis 10.1 Ita Download

Tutorial Arcgis 10.1 Ita Download > * Tutorial Arcgis 10.1 Ita Download* Young Jeezy-Trap Or Di

Re: [PATCH v4] i2c: enable runtime PM for I2C adapter devices enumerated from ACPI

On Sat, Oct 05, 2013 at 11:09:01AM +0300, Mika Westerberg wrote: > It looks like Windows actually powers the I2C controller off independently > of the I2C client power state. We should probably do the same in Linux even > though it is not following what the ACPI spec says (but makes sense with > s

Re: [PATCH 2/5] [PATCH 2/5] revert: "blk-mq: blk-mq should free bios in pass through case"

On Fri, Oct 04, 2013 at 12:39:33PM -0500, Mike Christie wrote: > Sorry, messed up function name. I meant blk_end_request*. > > For blk_execute_rq_nowait/blk_execute_rq and normal request use, the > lower levels free the bios as they are completed by one of the > blk_finish_request* calls. The call

Re: Commit 07f9b61 breaks systems that don't implement a _CBA method

On Sat, Oct 5, 2013 at 7:55 AM, Yinghai Lu wrote: > On Fri, Oct 4, 2013 at 3:11 PM, Bjorn Helgaas wrote: >> On Thu, Oct 3, 2013 at 7:18 PM, Hedi Berriche wrote: > >> It's regrettable that the code is so subtle. The obvious thing to do >> would be to check for _CBA, and if it doesn't exist, look

[PATCH v3 0/4] mmc: omap_hsmmc: SDIO irq

Changes: - split the subject patch into normal handling and workaround for am335x - rebase Andreas Fenkart (3): mmc: omap_hsmmc: Enable SDIO IRQ. mmc: omap_hsmmc: Remux pins to support SDIO interrupt on AM335x mmc: omap_hsmmc: debugfs for SDIO IRQ and GPIO remux Tony Lindgren (1): mmc:

[PATCH v3 1/4] mmc: omap_hsmmc: Fix context save and restore for DT

From: Tony Lindgren We want to get rid of the omap specific platform init code callbacks as they don't play nice with device tree. Let's convert the context loss check to be based on a register state detection instead. Cc: Andreas Fenkart Cc: Balaji T K Signed-off-by: Tony Lindgren diff --g

[PATCH v3 2/4] mmc: omap_hsmmc: Enable SDIO IRQ.

For now, only support SDIO interrupt if we are booted with DT. This is because some platforms need special quirks. And we don't want to add new legacy mux platform init code callbacks any longer as we are moving to DT based booting anyways. Broken hardware, missing the swakueup line, should fallba

[PATCH v3 3/4] mmc: omap_hsmmc: Remux pins to support SDIO interrupt on AM335x

The am335x can't detect pending cirq in PM runtime suspend. This patch reconfigures dat1 as a GPIO before going to suspend. SDIO interrupts are detected with the GPIO, while in runtime suspend, standard detection of the module block otherwise. Signed-off-by: Andreas Fenkart diff --git a/Document

[PATCH v3 4/4] mmc: omap_hsmmc: debugfs entries for SDIO IRQ detection and GPIO remuxing.

Update the debugfs related code for the SDIO IRQ support. Note that PSTATE shows current state of data lines, incl. SDIO IRQ pending Signed-off-by: Andreas Fenkart diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c index a8894ee..f7fe06f 100644 --- a/drivers/mmc/host/omap

Re: [PATCH 1/1] Fix SD card detection and use correct transfer interval.

Marcus Overhagen gmail.com> writes: > > Increasing the timeout when polling for card status to 100ms > as used at other places in this driver fixes SD card detection. > > Also use correct interval when doing the interrupt transfer, > this fixes the "xhci_queue_intr_tx: 74 callbacks suppressed"

Re: [PATCH 19/26] ivtv: Convert driver to use get_user_pages_unlocked()

Hi Jan: This patch alone does not have suffcient information for me to evaluate it. get_user_pages_unlocked() is added in another patch which I did not receive, and which I cannot find in any list archives. I wasted quite a bit of time looking for this additional patch: https://git.kernel.org/

Re: [PATCH v2 2/9] procfs: add proc_allow_access() to check if file's opener may access task

On Fri, Oct 04, 2013 at 03:17:08PM -0700, Andy Lutomirski wrote: > On Fri, Oct 4, 2013 at 12:41 PM, Djalal Harouni wrote: > > On Fri, Oct 04, 2013 at 12:32:09PM -0700, Andy Lutomirski wrote: > >> On Fri, Oct 4, 2013 at 12:27 PM, Djalal Harouni wrote: > >> > On Fri, Oct 04, 2013 at 12:16:26PM -070

Re: [PATCH] Fix the upper MTU limit in ipv6 GRE tunnel

On Fri, Oct 04, 2013 at 10:52:13AM +0100, Oussama Ghorbel wrote: > Unlike ipv4, the struct member hlen holds the length of the GRE and ipv6 > headers. This length is also counted in dev->hard_header_len. > Perhaps, it's more clean to modify the hlen to count only the GRE header > without ipv6 heade

Re: [PATCH RFC 00/77] Re-design MSI/MSI-X interrupts enablement pattern

On Fri, Oct 04, 2013 at 10:29:16PM +0100, Ben Hutchings wrote: > On Fri, 2013-10-04 at 10:29 +0200, Alexander Gordeev wrote: > All I can see there is that Tejun didn't think that the global limits > and positive return values were implemented by any architecture. I would say more than just that :)

[PATCH] wdt: sunxi: Fix section mismatch

This driver has a section mismatch, for probe and remove functions, leading to the following warning during the compilation. WARNING: drivers/watchdog/built-in.o(.data+0x24): Section mismatch in reference from the variable sunxi_wdt_driver to the function .init.text:sunxi_wdt_probe() The variable

Re: lustre: why does cfs_get_random_bytes() exist?

On Sat, Oct 05, 2013 at 06:10:54AM +, Dilger, Andreas wrote: > >With modern kernels, the /dev/random driver has the > >add_device_randomness() interface which is used to mix in > >personalization information, which includes the network MAC address. > >So that particular concern should be covere

[PATCH] ARM: sunxi: dts: preliminary cubietruck support

From: Oliver Schinagl A new cubieboard has been introduced, the cubietruck. I did try to also add emac support, but that didn't work well with the included RTL8211E Gbit PHY so I ommited that for now (it doesn't work with u-boot either). I tested the uart0 port and the LEDS which all seemed to

[PATCH] ARM: sunxi: dts: Add support for the cubieboard3, the CubieTruck

From: Oliver Schinagl Cubieboard3, CT Signed-off-by: Oliver Schinagl --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/sun7i-a20-cubietruck.dts | 60 ++ 2 files changed, 61 insertions(+) create mode 100644 arch/arm/boot/dts/sun7i-a20-cubietru

[PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

Theoretically, the maximize size of "%d" or "%u" is 11 (10 + '\0'), so need set MAX_NAMELEN 11 instead of 10. In real world, it may not cause issue, but still recommend to fix this 'theoretical' bug (especially original definition already considered about 'theoretical' using). Signed-off-by: Chen

Re: [PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

Hello Al Viro: Is this patch correct? ;-) Thanks. On 10/05/2013 11:19 PM, Chen Gang wrote: > Theoretically, the maximize size of "%d" or "%u" is 11 (10 + '\0'), so > need set MAX_NAMELEN 11 instead of 10. > > In real world, it may not cause issue, but still recommend to fix this > 'theoretical

Hello

I AM MR SALIU ALI, THE MANAGER FOREIGN REMITTANCE DEPARTMENT (BOA) BANK OF AFRICAN IN BURKINA FASO. I WILL LIKE YOU TO INDICATE YOUR INTEREST TO RECEIVE THE TRANSFER OF US$7.5 MILLION. 6O% FOR ME AND 40% FOR YOU, YOU WILL STAND AS NEXT OF KING TO MY LATE CUSTOMER WHO DIED IN PLAN CRASH ON THE (

Re: [PATCH] wdt: sunxi: Fix section mismatch

On 10/05/2013 07:20 AM, Maxime Ripard wrote: This driver has a section mismatch, for probe and remove functions, leading to the following warning during the compilation. WARNING: drivers/watchdog/built-in.o(.data+0x24): Section mismatch in reference from the variable sunxi_wdt_driver to the func

Re: [PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

On Sat, 2013-10-05 at 23:19 +0800, Chen Gang wrote: > Theoretically, the maximize size of "%d" or "%u" is 11 (10 + '\0'), so > need set MAX_NAMELEN 11 instead of 10. %d can be negative. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord.

[PATCH v3] ARM: bcm: Add DEBUG_LL console support

This patch adds low level debug uart support to Broadcom mobile based SOCs. Signed-off-by: Christian Daudt Changes from V2: - Changed to follow hex ordering on entries - Dropped defconfig changes Changes from V1: - Switched to use the common 8250 debug introduced in 3.12-rc1 diff --git a/a

[ANNOUNCE] 3.10.14-rt9

Dear RT folks! I'm pleased to announce the v3.10.14-rt9 patch set. Changes since v3.10.14-rt8 - the threshold module option of hwlat is no longer ignored. Path sent by Mike Galbraith - two patches from Kirill Tkhai to get basic RT compiled on Sparc. - the ppc patch for the 5200 has been altere

Re: [PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

On 10/05/2013 11:41 PM, Joe Perches wrote: > On Sat, 2013-10-05 at 23:19 +0800, Chen Gang wrote: >> Theoretically, the maximize size of "%d" or "%u" is 11 (10 + '\0'), so >> need set MAX_NAMELEN 11 instead of 10. > > %d can be negative. > > > > Oh, really, it is incorrect. Al Viro succeeds on

Re: [PATCH] kernel/exit.c: call read_unlock() when failure occurs after already called read_lock() in do_wait().

On Sat, Oct 05, 2013 at 03:33:40PM +0800, Chen Gang wrote: > Oh, it is my fault, this is incorrect patch. Hmm... I realize a mistake > of me: I have said "when finding issues, I need consider about LTP in q4 > 2013, need let it can be tested by LTP". Not really. The mistake was different. > And

Linux 3.4.65

I'm announcing the release of the 3.4.65 kernel. All users of the 3.4 kernel series must upgrade. The updated 3.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.4.y and can be browsed at the normal kernel.org git web browser:

Linux 3.11.4

I'm announcing the release of the 3.11.4 kernel. All users of the 3.11 kernel series must upgrade. The updated 3.11.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.11.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 3.4.65

diff --git a/Makefile b/Makefile index 580b364..3a8897f 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 4 -SUBLEVEL = 64 +SUBLEVEL = 65 EXTRAVERSION = NAME = Saber-toothed Squirrel diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c index df1b604..bd

Re: Linux 3.10.15

diff --git a/Makefile b/Makefile index 129c49f..9a77179 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 10 -SUBLEVEL = 14 +SUBLEVEL = 15 EXTRAVERSION = NAME = TOSSUG Baby Fish diff --git a/arch/arm/crypto/aes-armv4.S b/arch/arm/crypto/aes-armv4.S index 19d6cd6..3

Linux 3.10.15

I'm announcing the release of the 3.10.15 kernel. All users of the 3.10 kernel series must upgrade. The updated 3.10.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.10.y and can be browsed at the normal kernel.org git web browser:

Linux 3.0.99

-- NOTE! The 3.0.x kernel series will be moving to End-Of-Life soon, within a few weeks. Please move anything that is relying on this kernel version to the other longterm kernel releases (3.4.x or 3.10.x) as soon as possible. If anyone has any questions about this, pl

Re: Linux 3.0.99

diff --git a/Makefile b/Makefile index 8c8330e..0d6881a 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 0 -SUBLEVEL = 98 +SUBLEVEL = 99 EXTRAVERSION = NAME = Sneaky Weasel diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c index 89d6877..282c98f 100

Re: [RFC][PATCH 4/3] vfs: Allow rmdir to remove mounts in all but the current mount namespace

Quoting Eric W. Biederman (ebied...@xmission.com): > > Programs have been known to test for empty directories by attempting > to remove them. To keep from violating the principle of least > surprise don't let directories the caller can see with someting > mounted on them be deleted. > > With a l

Re: lustre: why does cfs_get_random_bytes() exist?

On Sat, Oct 05, 2013 at 10:21:21AM -0400, Theodore Ts'o wrote: > add_device_randomness() is called from __dev_open() and > dev_set_mac_address() in net/core/dev.c. This is above the ethernet > and infiniband level. So as long as it looks like a Linux network > device, and they are setting the har

Re: tty^Wrcu/perf lockdep trace.

On Fri, Oct 04, 2013 at 02:25:06PM -0700, Paul E. McKenney wrote: > > Why > > do we still have a per-cpu kthread in nocb mode? The idea is that we do > > not disturb the cpu, right? So I suppose these kthreads get to run on > > ano

Re: [PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

On Sat, Oct 5, 2013 at 5:46 PM, Chen Gang wrote: > On 10/05/2013 11:41 PM, Joe Perches wrote: >> On Sat, 2013-10-05 at 23:19 +0800, Chen Gang wrote: >>> Theoretically, the maximize size of "%d" or "%u" is 11 (10 + '\0'), so >>> need set MAX_NAMELEN 11 instead of 10. >> >> %d can be negative. >> >>

[PATCH 1/5] drivers: usb: core: hcd: moved asterix to variable

instead of type Signed-off-by: Matthias Beyer --- drivers/usb/core/hcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c index d6a8d23..9036794 100644 --- a/drivers/usb/core/hcd.c +++ b/drivers/usb/core/hcd.c @@ -2818,7 +2818,7

[PATCH 2/5] drivers: usb: core: hcd: Whitespace fixes

including - spaces to tabs - removing spaces before array indexing (foo [] to foo[]) - adding spaces around unary operator (foo? 1 : 0 to foo ? 1 : 0) - removed trailing whitespace Signed-off-by: Matthias Beyer --- drivers/usb/core/hcd.c | 56 +- 1

[PATCH 5/5] drivers: usb: core: hcd: if-else-braces fixed

Put else keyword on same line as closing brace from if statement, added { } braces as the styleguide says. Signed-off-by: Matthias Beyer --- drivers/usb/core/hcd.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c index 5d13d6

[PATCH 3/5] drivers: usb: core: hcd: replaced C99 // comments

Signed-off-by: Matthias Beyer --- drivers/usb/core/hcd.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c index 0f3e5a0..3a2667c 100644 --- a/drivers/usb/core/hcd.c +++ b/drivers/usb/core/hcd.c @@ -428,7 +428,7 @@ rh_st

[PATCH 4/5] drivers: usb: core: hcd: removed braces for return statements

Signed-off-by: Matthias Beyer --- drivers/usb/core/hcd.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c index 3a2667c..5d13d6c 100644 --- a/drivers/usb/core/hcd.c +++ b/drivers/usb/core/hcd.c @@ -1120,18 +1120,18 @@ long

[PATCH 0/5] Cleanup in drivers/usb/core/hcd.c

Hi! I did some cleanup in drivers/usb/core/hcd.c of ERROR messages from "scripts/checkpatch.pl --file". Not all ERRORs are fixed, there are some remaining with "assignment in if statement". It's based on 7dee8df, which is Linus current master. I compiled it without errors. Checkpatch scrip

Re: tty^Wrcu/perf lockdep trace.

On Sat, Oct 05, 2013 at 06:05:11PM +0200, Peter Zijlstra wrote: > On Fri, Oct 04, 2013 at 02:25:06PM -0700, Paul E. McKenney wrote: > > > Why > > > do we still have a per-cpu kthread in nocb mode? The idea is that we do > > > not d

Re: [PATCH 2/2] mm/sparsemem: Fix a bug in free_map_bootmem when CONFIG_SPARSEMEM_VMEMMAP

Hello andrew, On 10/04/2013 04:42 AM, Andrew Morton wrote: > On Thu, 03 Oct 2013 11:32:02 +0800 Zhang Yanfei > wrote: > >> We pass the number of pages which hold page structs of a memory >> section to function free_map_bootmem. This is right when >> !CONFIG_SPARSEMEM_VMEMMAP but wrong when CONF

Re: [PATCH] kernel/exit.c: call read_unlock() when failure occurs after already called read_lock() in do_wait().

Firstly, thank you for your so much reply (especially spending your much expensive time resources). But it seems I am too hurry: I have sent 2 patches to you (I start finding them after supper). My details reply is at the bottom of this mail, please check, thanks. On 10/05/2013 11:48 PM, Al Vi

Re: [PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

On 10/06/2013 12:08 AM, Richard Weinberger wrote: > On Sat, Oct 5, 2013 at 5:46 PM, Chen Gang wrote: >> On 10/05/2013 11:41 PM, Joe Perches wrote: >>> On Sat, 2013-10-05 at 23:19 +0800, Chen Gang wrote: Theoretically, the maximize size of "%d" or "%u" is 11 (10 + '\0'), so need set MAX_N

[PATCH v2] mm/sparsemem: Fix a bug in free_map_bootmem when CONFIG_SPARSEMEM_VMEMMAP

From: Zhang Yanfei We pass the number of pages which hold page structs of a memory section to function free_map_bootmem. This is right when !CONFIG_SPARSEMEM_VMEMMAP but wrong when CONFIG_SPARSEMEM_VMEMMAP. When CONFIG_SPARSEMEM_VMEMMAP, we should pass the number of pages of a memory section to f

I want to Invest.

Hi, Can you assist me to invest in your Country? if yes, then get back to me,so I can give you details and areas you can participate and assist me. Mr. Paul -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More maj

Re: [PATCH 6/6] x86: Allow disabling HW_BREAKPOINTS and PERF_EVENTS

On Sat, Oct 05, 2013 at 09:08:06AM +0200, Ingo Molnar wrote: > > * Andi Kleen wrote: > > > From: Andi Kleen > > > > As suggested by Ingo. > > No, you haven't read my suggestion carefully enough so NAK. Ok I trust you will do a better solution then to save the 700+k text. Ball is in your cour

Re: [PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

On 10/06/2013 12:50 AM, Chen Gang wrote: > On 10/06/2013 12:08 AM, Richard Weinberger wrote: >> On Sat, Oct 5, 2013 at 5:46 PM, Chen Gang wrote: >>> On 10/05/2013 11:41 PM, Joe Perches wrote: On Sat, 2013-10-05 at 23:19 +0800, Chen Gang wrote: > Theoretically, the maximize size of "%d" or

You've won a Prize

You've won a Prize MICROSOFT IBERICA SL" YOU 'VE WON. ATTN:MICROSOFT IBERICA SL Your email has won (EUR244,000,00) (TWO HUNDRED AND FOURTY FOUR THOUSAND EURO) Batch number:XL73276498AM Ref number:QR352899526KC This is a millennium scientific computer game in which email addresses were used.It is a

Re: Use of drivers/platform and matching include?

On Fri, Oct 04, 2013 at 09:48:41AM -0700, Olof Johansson wrote: > On Fri, Oct 4, 2013 at 6:22 AM, Greg Kroah-Hartman > wrote: > > On Fri, Oct 04, 2013 at 12:41:28PM +0100, Russell King - ARM Linux wrote: > >> > >> So, no, there will be no new drivers under arch/arm. They must be in the > >> drive

Re: [PATCH 1/5] rcusync: introduce struct rcu_sync_ops

On 10/04, Linus Torvalds wrote: > > On Fri, Oct 4, 2013 at 12:30 PM, Steven Rostedt wrote: > > > > As all the rcu_synchronization() methods (on non UP) are quite > > expensive, I doubt that this optimization is worth anything. > > Maybe. It just annoys me, because afaik, the function that gets cal

Re: [PATCH 1/5] rcusync: introduce struct rcu_sync_ops

On 10/04, Peter Zijlstra wrote: > > On Fri, Oct 04, 2013 at 12:38:37PM -0700, Linus Torvalds wrote: > > On Fri, Oct 4, 2013 at 12:30 PM, Steven Rostedt wrote: > > > > > > As all the rcu_synchronization() methods (on non UP) are quite > > > expensive, I doubt that this optimization is worth anythin

Re: [PATCH 0/5] rcusync: validations + dtor + exclusive

On 10/04, Peter Zijlstra wrote: > > shall I pick them up and stuff them through tip > with the rest of the lot? This would be great, thanks. > > 4-5 should be ignored without the explicit ack. Peter seems to > > dislike the exclusive mode. I disagree but I am not going to argue. > > (well, at lea

[PATCH 1/2] mm/page_alloc.c: Implement an empty get_pfn_range_for_nid

From: Zhang Yanfei Implement an empty get_pfn_range_for_nid for !CONFIG_HAVE_MEMBLOCK_NODE_MAP, so that we could remove the #ifdef in free_area_init_node. Signed-off-by: Zhang Yanfei --- mm/page_alloc.c |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/mm/page_allo

[PATCH 2/2] mm/page_alloc.c: Get rid of unused marco LONG_ALIGN

From: Zhang Yanfei The macro is nowhere used, so remove it. Signed-off-by: Zhang Yanfei --- mm/page_alloc.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 1fb13b6..9d8508d 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -

[GIT PATCH] Staging driver fixes for 3.12-rc4

The following changes since commit 15c03dd4859ab16f9212238f29dd315654aa94f6: Linux 3.12-rc3 (2013-09-29 15:02:38 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-3.12-rc4 for you to fetch changes up to 677a3156569

[GIT PATCH] TTY/Serial fixes for 3.12-rc4

The following changes since commit 15c03dd4859ab16f9212238f29dd315654aa94f6: Linux 3.12-rc3 (2013-09-29 15:02:38 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-3.12-rc4 for you to fetch changes up to a9fbf4d591da6cd1d3e

Re: [RFC PATCH v2 0/1] FPGA subsystem core

On Fri, Oct 04, 2013 at 10:34:10PM -0700, H. Peter Anvin wrote: > I do it all the time. > > JAM/STAPL seems to me to be more used for exotic connections to > serial flash for persistent programming. The FPGA tools write two kinds of SVF/JAM/STAPL files, one is ment to be replayed the to FPGA itse

[GIT PATCH] USB fixes for 3.12-rc4

The following changes since commit 15c03dd4859ab16f9212238f29dd315654aa94f6: Linux 3.12-rc3 (2013-09-29 15:02:38 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-3.12-rc4 for you to fetch changes up to a214339d764a07b99dc

[PATCH] DMA: extend documentation to provide more API details

This patch extends dmaengine documentation to provide more details on descriptor prepare stage, transaction completion requirements and DMA error processing. Signed-off-by: Guennadi Liakhovetski --- These extensions reflect my understanding of some aspects of the dmaengine API. If it is wrong,

[GIT PULL] Btrfs

Hi Linus, Please pull my for-linus branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus I've merged my for-linus up to 3.12-rc3 because the top commit is only meant for 3.12. The rest of the fixes are also available in my master branch on top of my last 3.11 bas

Re: [PATCH 2/3] rcu: Create rcu_sync infrastructure

On 10/04, Peter Zijlstra wrote: > > On Fri, Oct 04, 2013 at 09:06:53PM +0200, Oleg Nesterov wrote: > > However, yes-yes-yes, I do think that we need the non-exclusive mode > > too, at least for percpu_down_write_nonexclusive() which I think we > > need as well. > > I just need to disagree with the

Re: [PATCH] kernel/irq/proc.c: set MAX_NAMELEN 11 instead of 10 which express the maximize size of "%d" or "%u".

Am 05.10.2013 19:06, schrieb Chen Gang: > On 10/06/2013 12:50 AM, Chen Gang wrote: >> On 10/06/2013 12:08 AM, Richard Weinberger wrote: >>> On Sat, Oct 5, 2013 at 5:46 PM, Chen Gang wrote: On 10/05/2013 11:41 PM, Joe Perches wrote: > On Sat, 2013-10-05 at 23:19 +0800, Chen Gang wrote: >>>

Re: [PATCH|RFC] of: let of_match_device() always return best match

Hi Marc, On Thu, Oct 3, 2013 at 3:51 PM, Marc Kleine-Budde wrote: > For example: > > The imx28.dtsi gives this compatible string for its CAN core: > >> compatible = "fsl,imx28-flexcan", "fsl,p1010-flexcan"; > > The flexcan driver defines: > >> static const struct of_device_id flexcan_of_ma

Re: [PATCH v2 5/5] kconfig: fix bug in search results string: use strlen(gstr->s), not gstr->len

On Thu, Oct 03, 2013 at 07:25:53PM +0200, Martin Walch wrote: > From: Martin Walch > Date: Thu, 3 Oct 2013 18:35:16 +0200 > Subject: [PATCH v2 5/5] kconfig: fix bug in search results string: use > strlen(gstr->s), not gstr->len > > The struct gstr has a capacity that may differ from the actual s

[PATCH]kconfig:mconf: avoid unneeded memcpy

In function update_text we assign jump key label per page (1)-(9) cycled, and use three space char as the header after k exceed JUMP_NB. We don't need to call memcpy with header of three space char, because it changes nothing, it just copy what was there. I don't think we need to clear old jump k

[PATCH] perf: remove duplicate block from Makefile

This looks like a merge error, the code is duplicated with the first copy doing something else as well. Just remove the second block. Signed-off-by: Ulrich Drepper Makefile |8 1 file changed, 8 deletions(-) Index: perf/config/Makefile ===

Re: [PATCH 2/5] drivers: usb: core: hcd: Whitespace fixes

On Sat, 2013-10-05 at 18:02 +0200, Matthias Beyer wrote: > - removing spaces before array indexing (foo [] to foo[]) [] > diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c [] > @@ -93,7 +93,7 @@ EXPORT_SYMBOL_GPL (usb_bus_list); > /* used when allocating bus numbers */ > #define USB_MA

Re: [PATCH 2/5] drivers: usb: core: hcd: Whitespace fixes

On Sat, 2013-10-05 at 11:04 -0700, Joe Perches wrote: > On Sat, 2013-10-05 at 18:02 +0200, Matthias Beyer wrote: > > - removing spaces before array indexing (foo [] to foo[]) > [] > > diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c > [] > > @@ -93,7 +93,7 @@ EXPORT_SYMBOL_GPL (usb_bus_

Re: [PATCH v2 3/9] ARM: dts: Add SHAM data and documentation for AM33XX

On 10/04/2013 09:26 AM, Mark Rutland wrote: > On Mon, Sep 30, 2013 at 04:13:00PM +0100, Joel Fernandes wrote: >> From: "Mark A. Greer" >> >> Add the generic AM33XX SHAM module's device tree data and >> enable it for the am335x-evm, am335x-evmsk, and am335x-bone >> platforms. Also add Documentatio

Re: [PATCH v2 4/9] ARM: dts: Add AES data and documentation for AM33XX

These patches were not authored by me but I'll go ahead and fix them up anyway. On 10/04/2013 09:33 AM, Mark Rutland wrote: > On Mon, Sep 30, 2013 at 04:13:01PM +0100, Joel Fernandes wrote: >> From: "Mark A. Greer" >> >> Add the generic AM33XX AES module's device tree data and >> enable it for th

[GIT PULL] GPIO fixes for v3.12

Hi Linus, here are two GPIO fixes for v3.12, both dealing with setting up IRQs properly on the OMAP for the device tree boot path. The subject as such is pretty tricky and we're still discussing how we want to handle this long-term, but this fix is widely ACKed and tested. In the absence of linux

Re: [PATCH|RFC] of: let of_match_device() always return best match

On 10/05/2013 07:46 PM, Fabio Estevam wrote: > Hi Marc, > > On Thu, Oct 3, 2013 at 3:51 PM, Marc Kleine-Budde wrote: > >> For example: >> >> The imx28.dtsi gives this compatible string for its CAN core: >> >>> compatible = "fsl,imx28-flexcan", "fsl,p1010-flexcan"; >> >> The flexcan driver

[PATCH] checkpatch.pl: Check for the FSF mailing address

Kernel maintainers reject new instances of the GPL boilerplate paragraph directing people to write to the FSF for a copy of the GPL, since the FSF has moved in the past and may do so again. Signed-off-by: Josh Triplett --- Inspired by Greg's standard response to omit the paragraph "unless you wa

Re: [PATCH] checkpatch.pl: Check for the FSF mailing address

On Sat, 2013-10-05 at 11:43 -0700, Josh Triplett wrote: > Kernel maintainers reject new instances of the GPL boilerplate paragraph > directing people to write to the FSF for a copy of the GPL, since the > FSF has moved in the past and may do so again. [] > diff --git a/scripts/checkpatch.pl b/scrip

Re: [GIT PATCH] TTY/Serial fixes for 3.12-rc4

On Sat, Oct 5, 2013 at 10:34 AM, Greg KH wrote: > > One fixes the reported regression in the n_tty code that a number of > people found recently That one looks broken. Well, it looks like it might "work", but do so by hiding the issue for one case, while leaving it in the more general case. Why

Re: [PATCH] DMA: extend documentation to provide more API details

On Sat, Oct 05, 2013 at 07:36:20PM +0200, Guennadi Liakhovetski wrote: > This patch extends dmaengine documentation to provide more details > on descriptor prepare stage, transaction completion requirements > and DMA error processing. > > Signed-off-by: Guennadi Liakhovetski > --- > > These exte

Re: [PATCH] checkpatch.pl: Check for the FSF mailing address

On Sat, Oct 05, 2013 at 11:51:48AM -0700, Joe Perches wrote: > On Sat, 2013-10-05 at 11:43 -0700, Josh Triplett wrote: > > Kernel maintainers reject new instances of the GPL boilerplate paragraph > > directing people to write to the FSF for a copy of the GPL, since the > > FSF has moved in the past

[PATCH v3 3/3] ARM: dts: AM33XX: Fix AES interrupt number

AES interrupts were previously not used, but after recent changes to omap-aes driver, its being used. We correct the interrupt number to have working PIO mode. Signed-off-by: Joel Fernandes --- arch/arm/boot/dts/am33xx.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch

[PATCH v3 2/3] ARM: dts: AM33XX: Add AES data and documentation

From: "Mark A. Greer" Add the generic AM33XX AES module's device tree data and enable it for the am335x-evm, am335x-evmsk, and am335x-bone platforms. Also add Documentation file describing the data for the AES module. [jo...@ti.com: Dropped interrupt-parent propert, documentation fixups] CC: P

[PATCH v3 1/3] ARM: dts: AM33XX: Add SHAM data and documentation

From: "Mark A. Greer" Add the generic AM33XX SHAM module's device tree data and enable it for the am335x-evm, am335x-evmsk, and am335x-bone platforms. Also add Documentation file describing the data for the SHAM module. [jo...@ti.com: Dropped interrupt-parrent property, documentation fixups] CC

[PATCH v3 0/3] AM33XX crypto DTS patches

These patches are some minor fixups and changes to commit messages to the AM33XX crypto (aes, sham) patches with reference to the comments at: http://comments.gmane.org/gmane.linux.drivers.devicetree/45961 Joel Fernandes (1): ARM: dts: AM33XX: Fix AES interrupt number Mark A. Greer (2): ARM:

Conflict in merge of the the random tree

While merging the random tree into -next there was a trivial conflict in drivers/char/random.c between 0244ad004a54e3 (Remove GENERIC_HARDIRQ config option) and 557360455b (random: push extra entropy to the output pools). I've fixed this up as below: diff --cc drivers/char/random.c index 7737b5b,

  1   2   >