On 07/24/2012 04:24 PM, Philipp Reisner wrote:
> Hi Jens,
>
> Please consider to pull these changes for the 3.6 merge window.
> I did not found a for-3.6/drivers branch, so I based the patches
> on the 3.5 release.
>
> Best,
> Phil
>
>
> The following changes since commit 28a33cbc24e4256c143dc
>>> On 27.07.12 at 19:54, Konrad Rzeszutek Wilk wrote:
> On Fri, Jul 27, 2012 at 08:27:39AM +0100, Jan Beulich wrote:
>> >>> On 26.07.12 at 22:43, Konrad Rzeszutek Wilk
>> >>> wrote:
>> > + /* Check if the user supplied the e820_hole parameter
>> > + * which would create a machine looking E82
>>> On 27.07.12 at 19:34, Konrad Rzeszutek Wilk wrote:
> On Fri, Jul 27, 2012 at 12:47:47PM +0100, Jan Beulich wrote:
>> >>> On 27.07.12 at 13:18, Stefano Stabellini
>> >>>
> wrote:
>> > On Thu, 26 Jul 2012, Konrad Rzeszutek Wilk wrote:
>> >> 1) All P2M lookups instead of using the __ka addres
On 2012.07.30 at 07:50 +0100, Al Viro wrote:
> On Sat, Jul 28, 2012 at 12:43:16PM +0200, Markus Trippelsdorf wrote:
> > Printing with CUPS is broken on the current git tree. Whenever I print a
> > page
> > the job just sits in the CUPS queue showing "processing". But it never
> > reaches
> > the
Il 30/07/2012 01:50, Rusty Russell ha scritto:
>> Also, being the first user of chained scatterlist doesn't exactly give
>> me warm fuzzies.
>
> We're far from the first user: they've been in the kernel for well over
> 7 years. They were introduced for the block layer, but they tended to
> ignore
Il 30/07/2012 06:43, Asias He ha scritto:
>>
>
> Yes. Something like this:
>
> qemu -drive file=foo.img,cache=writeback/unsafe
>
> is not safe against power losses also?
cache=writeback and cache=none are safe, cache=unsafe isn't.
> I think we can add REQ_FLUSH & REQ_FUA support to bio path
On 29/07/12 21:50, Mark Brown wrote:
On Fri, Jul 27, 2012 at 01:45:57PM +0100, Lee Jones wrote:
Nothing special here. We're only providing a compatible string
to ensure the driver is probed using a Device Tree boot.
+ pcm: ux500-pcm {
+ compatible = "steric
On 29/07/12 21:52, Mark Brown wrote:
On Fri, Jul 27, 2012 at 01:46:01PM +0100, Lee Jones wrote:
arch/arm/boot/dts/db8500.dtsi |8
This is a generic DT include file but...
+ sound {
+ compatible = "stericsson,snd-soc-mop500";
+
+
This patch adds logic to parse lis3 properties from a device tree node
and store them in a freshly allocated lis3lv02d_platform_data.
Note that the actual match tables are left out here. This part should
happen in the drivers that bind to the individual busses (SPI/I2C/PCI).
Also adds some DT bin
If probed from a device tree, this driver now passes the node
information to the generic part, so the runtime information can be
derived.
Successfully tested on a PXA3xx board.
Signed-off-by: Daniel Mack
---
No changes from v1 and v2
drivers/misc/lis3lv02d/lis3lv02d_spi.c | 14 ++
On 29/07/12 21:31, Mark Brown wrote:
On Fri, Jul 27, 2012 at 01:45:45PM +0100, Lee Jones wrote:
+++ b/Documentation/devicetree/bindings/sound/ux500.txt
@@ -0,0 +1,62 @@
+* ux500 Audio Driver and ab8500 Audio CODEC
+
+Required properties:
+ - compatible:
+ - Machine Driver : "stericsson,snd-so
Hello,
On Thursday, July 26, 2012 1:13 PM Hideki EIRAKU wrote:
> Previously the vb2_dma_contig_mmap() function was using a dma_addr_t as a
> physical address. The two addressses are not necessarily the same.
> For example, when using the IOMMU funtion on certain platforms, dma_addr_t
> addresses
HI,
Le 30/07/2012 08:30, Joel Becker a écrit :
> On Sat, Jul 28, 2012 at 12:18:30AM +0200, Vincent ETIENNE wrote:
>> Hello
>>
>> Get this on first write made ( by deliver sending mail to inform of the
>> restart of services )
>> Home partition (the one receiving the mail) is based on ocfs2 creat
Il 30/07/2012 08:25, Wang Sen ha scritto:
> When using the commands below to write some data to a virtio-scsi LUN of the
> QEMU guest(32-bit) with 1G physical memory(qemu -m 1024), the qemu will crash.
>
> # sudo mkfs.ext4 /dev/sdb (/dev/sdb is the virtio-scsi LUN.)
> # sudo mount
On Sun, Jul 29, 2012 at 07:13:57PM +0200, Linus Walleij wrote:
> On Mon, Jul 23, 2012 at 1:59 PM, Thierry Reding
> wrote:
>
> > This commit adds a driver for the Avionic Design N-bit GPIO expander.
> > The expander provides a variable number of GPIO pins with interrupt
> > support.
> (...)
> > di
On Mon, Jul 09, 2012 at 09:40:22PM +, Randy Dunlap wrote:
> On 07/09/2012 10:54 AM, Jussi Kivilinna wrote:
>
> > Quoting Randy Dunlap :
> >
> >> On 07/02/2012 12:23 AM, Stephen Rothwell wrote:
> >>
> >>> Hi all,
> >>>
> >>> Changes since 20120629:
> >>>
> >>
> >>
> >> on i386:
> >>
> >>
> >>
On Mon, Jul 30, 2012 at 09:45:14AM +0200, Vincent ETIENNE wrote:
>
> HI,
>
> Le 30/07/2012 08:30, Joel Becker a écrit :
> > On Sat, Jul 28, 2012 at 12:18:30AM +0200, Vincent ETIENNE wrote:
> >> Hello
> >>
> >> Get this on first write made ( by deliver sending mail to inform of the
> >> restart of
On Wed, Jul 11, 2012 at 07:36:46PM +0200, Johannes Goetzfried wrote:
> This patchset adds x86_64/avx assembler implementations of the Cast5 and the
> Cast6 cipher.
>
> Johannes Goetzfried (6):
> crypto: cast5 - prepare generic module for optimized implementations
> crypto: testmgr - add larger
On Mon, Jul 30, 2012 at 09:10:23AM +0200, Markus Trippelsdorf wrote:
>
> Looks like you're right. The first warning happens during startup. The last
> one
> when I print a test page (which now succeeds).
> Thanks Al.
> WTF: open("/dev/input/mice", 34946)
> WTF: open("/dev/usblp0", 32898)
> WTF
On Thu, Jul 19, 2012 at 09:42:37AM -0500, Seth Jennings wrote:
> This is a continuation of support for the Power7+ in-Nest
> hardware accelerator.
>
> https://lkml.org/lkml/2012/4/12/223
>
> This patchset adds the hardware driver and the cryptographic
> driver for hardware accelerated compression
On Fri, 2012-07-20 at 09:01 -0500, Seth Jennings wrote:
> On 07/20/2012 12:33 AM, Michael Ellerman wrote:
> > On Thu, 2012-07-19 at 09:42 -0500, Seth Jennings wrote:
> >> This patch adds the driver for interacting with the 842
> >> compression accelerator on IBM Power7+ systems.
> >
> > ...
> >
>
Enables use of GPT partition labels, APM partition labels, and MBR
disk signatures to specify block devices during early boot.
Traditional device names and GPT partition UUIDs are still supported.
This is useful on systems with nondeterministic device ordering.
Signed-off-by: Andy Getzendanner
-
> -Original Message-
> From: diand...@google.com [mailto:diand...@google.com] On Behalf Of Doug
> Anderson
> Sent: Saturday, July 21, 2012 6:07 AM
> To: Sean Paul
> Cc: grant.lik...@secretlab.ca; linus.wall...@stericsson.com;
> linux-kernel@vger.kernel.org;
> ol...@chromium.org; Sangsu
On 2012.07.30 at 08:56 +0100, Al Viro wrote:
> On Mon, Jul 30, 2012 at 09:10:23AM +0200, Markus Trippelsdorf wrote:
> >
> > Looks like you're right. The first warning happens during startup. The last
> > one
> > when I print a test page (which now succeeds).
> > Thanks Al.
>
> > WTF: open("/de
If range.start argument was between ULLONG_MAX - BBSIZE and ULLONG_MAX,
BTOBB macro resulted in overflow which caused start to be set to 0.
Now, invalid argument error is returned instead.
Signed-off-by: Tomas Racek
---
fs/xfs/xfs_discard.c |4
1 files changed, 4 insertions(+), 0 deleti
We recently changed the locking in this function, but this return was
missed. It needs an unlock and the IRQs need to be restored.
Signed-off-by: Dan Carpenter
---
Applies to linux-next.
diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
index 07b14ba..7a5ccb2c 100644
--- a/drivers/scsi/ipr.c
"rc" is always zero here, so there is no need to check.
Signed-off-by: Dan Carpenter
diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
index 7a5ccb2c..fc49f17 100644
--- a/drivers/scsi/ipr.c
+++ b/drivers/scsi/ipr.c
@@ -5847,7 +5847,7 @@ static int ipr_queuecommand(struct Scsi_Host *shost,
At Sun, 29 Jul 2012 16:23:08 +0200,
Daniel Mack wrote:
>
> On 29.07.2012 13:39, Fengguang Wu wrote:
> >>> err = snd_es1688_init(chip, 1);
> >>> if (err < 0)
> >>> - return err;
> >>> + goto exit_release_dma;
> >>>
> >>> /* Register device */
> >>> return snd_device_new(ca
On Mon, Jul 30, 2012 at 10:05:36AM +0200, Markus Trippelsdorf wrote:
> On 2012.07.30 at 08:56 +0100, Al Viro wrote:
> > On Mon, Jul 30, 2012 at 09:10:23AM +0200, Markus Trippelsdorf wrote:
> > >
> > > Looks like you're right. The first warning happens during startup. The
> > > last one
> > > when
On Sun, Jul 29, 2012 at 09:31:53PM +0200, Witold Szczeponik wrote:
> the aim is to select a PNP ACPI option where resources can be disabled
> (or are not needed). E.g., the parallel port of the 600E can be used
> with and without IRQ lines. The means to allow for this is to use the
> sysfs interf
Hello!
This is yet another quick update on the patchset which replaces custom
consistent dma regions usage in dma-mapping framework in favour of
generic vmalloc areas created on demand for each allocation. The main
purpose for this patchset is to remove 2MiB limit of dma
coherent/writecombine all
'const void *' is a safer type for caller function type. This patch
updates all references to caller function type.
Signed-off-by: Marek Szyprowski
Reviewed-by: Kyungmin Park
Reviewed-by: Minchan Kim
---
include/linux/vmalloc.h |8
mm/vmalloc.c| 18 +-
This patch changes dma-mapping subsystem to use generic vmalloc areas
for all consistent dma allocations. This increases the total size limit
of the consistent allocations and removes platform hacks and a lot of
duplicated code.
Atomic allocations are served from special pool preallocated on boot,
On Sun, Jul 22, 2012 at 01:16:21PM -0700, Bret Towe wrote:
> just booted a fresh 3.5 kernel and got the following on login via gdm
> on the client computer
> didn't see any crashes yet on any other computer but didn't give it
> long to try after seeing this
> let me know if you need more info
> thi
On 30 July 2012 13:34, 박상수 wrote:
>
>
>> -Original Message-
>> From: diand...@google.com [mailto:diand...@google.com] On Behalf Of Doug
>> Anderson
>> Sent: Saturday, July 21, 2012 6:07 AM
>> To: Sean Paul
>> Cc: grant.lik...@secretlab.ca; linus.wall...@stericsson.com;
>> linux-kernel@vg
There are different types of chargers avalibale like AC, Solar, USB, etc..
Even in USB we have different types SDP/DCP/CDP/ACA and all these
chargers have different o/p ratings. For example SDP supports only 500mA of
charge current whereas AC charger can support upto 8A or more.
Similarly batterie
Hi All,
I tried using gpio as an interrupt line for my driver
(drivers/staging/iio/light/tsl2x7x_core.c) for omap5.
The interrupt line number was directly passed to the driver using
device tree. But what I observed
is the following crash..
[1.599273] mousedev: PS/2 mouse device common for al
Hi All,
[seems the email from my intel email address didn't hit the list,
resend with gmail, sorry for the noise]
When I debugged a suspend/resume bug, I found that tick_broadcast_mask is not
restored for a CPU after it is offline/onlined since kernel 3.4, while it's
fine for 3.3.
Further check
Hey,
Op 29-07-12 22:15, Marcin Slusarz schreef:
> On Thu, Jul 26, 2012 at 02:56:22PM +0200, Ortwin Glück wrote:
>> On 25.07.2012 20:42, Marcin Slusarz wrote:
>>> Good, below patch should fix this panic.
>>>
>>> Note that you can hit an oops in drm_handle_vblank because patch from
>>> http://lists.
On 28 July 2012 01:10, Sarah Sharp wrote:
> On Fri, Jul 27, 2012 at 02:40:56PM +0800, Daniel J Blueman wrote:
>> On 27 July 2012 14:14, Sarah Sharp wrote:
>> > On Fri, Jul 27, 2012 at 12:03:44PM +0800, Daniel J Blueman wrote:
>> >> When various USB3 devices with Etron XHCI controllers, we see a b
On 07/30/2012 10:12 AM, Paolo Bonzini wrote:
> Il 30/07/2012 01:50, Rusty Russell ha scritto:
>>> Also, being the first user of chained scatterlist doesn't exactly give
>>> me warm fuzzies.
>>
>> We're far from the first user: they've been in the kernel for well over
>> 7 years. They were introdu
On Sun, Jul 29, 2012 at 09:29:30PM +0100, Ben Hutchings wrote:
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -251,17 +251,29 @@ unsigned long shrink_slab(struct shrink_
> > unsigned long total_scan;
> [...]
> > + total_scan += delta;
> > + if (total_scan < 0) {
All the unnessary functions in omap-phy-internal is removed.
These functionality are now handled by omap-usb2 phy driver.
Cc: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Tony Lindgren
---
arch/arm/mach-omap2/omap_phy_internal.c | 138 ---
arch/arm/
This patch series adds device tree support for MUSB and device
tree support for all the related modules to get MUSB working in
OMAP platform.
A new omap-usb2 phy driver has been added (with only dt suppport)
to perform phy configurations. Previously this configuration was
performed by twl6030, usi
Add twl6030-usb data node in twl6030 device tree file
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4-panda.dts |4
arch/arm/boot/dts/omap4-sdp.dts |4
arch/arm/boot/dts/twl6030.dtsi|5 +
3 files changed, 13 insertions(+)
diff --git a/arch/arm/b
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes to
> -Original Message-
> From: Linuxppc-dev [mailto:linuxppc-dev-
> bounces+poonam.aggrwal=freescale@lists.ozlabs.org] On Behalf Of Greg
> KH
> Sent: Friday, July 27, 2012 11:30 PM
> To: Singh Sandeep-B37400
> Cc: de...@driverdev.osuosl.org; linuxppc-...@lists.ozlabs.org; linux-arm-
> k
Add omap-usb2 data node in omap4 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 29c6243..15f1890 100644
--- a/arch/arm/boot/dts/
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 +++-
drivers/usb/musb/omap2430.c| 54 +
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver and
the documentation with device tree binding information is
Add twl4030-usb data node in twl4030 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index 22f4d13..761a5a5 1006
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3-evm.dts|6 ++
arch/arm/boot/dts/omap3.dtsi
Add device tree support for twl4030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 19 ++
drivers/usb/otg/twl4030-usb.c | 26 +++
> -Original Message-
> From: Linuxppc-dev [mailto:linuxppc-dev-
> bounces+poonam.aggrwal=freescale@lists.ozlabs.org] On Behalf Of Greg
> KH
> Sent: Friday, July 27, 2012 11:42 PM
> To: Singh Sandeep-B37400
> Cc: de...@driverdev.osuosl.org; linuxppc-...@lists.ozlabs.org; linux-arm-
> k
On 07/30/2012 07:36 AM, Avi Kivity wrote:
> On 07/30/2012 12:05 AM, Sasha Levin wrote:
>> On 07/29/2012 02:48 PM, Avi Kivity wrote:
>>> On 07/27/2012 02:27 PM, Sasha Levin wrote:
On 07/26/2012 01:42 PM, Avi Kivity wrote:
> On 07/24/2012 08:10 PM, Sasha Levin wrote:
>> [ 215.026612] NM
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 21 +++
drivers/usb/otg/twl6030-usb.c | 39 +-
On 7/25/2012 11:35 PM, Venu Byravarasu wrote:
> +
> +static struct rtc_class_ops tps65910_rtc_ops = {
const?
> + .read_time = tps65910_rtc_read_time,
> + .set_time = tps65910_rtc_set_time,
> + .read_alarm = tps65910_rtc_read_alarm,
> + .set_alarm = tps65910_rtc
-Original Message-
From: John Stoffel [mailto:j...@stoffel.org]
Sent: 27 July 2012 19:42
To: Singh Sandeep-B37400
Cc: linuxppc-...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org;
ga...@kernel.crashing.org; linux-kernel@vger.kernel.org;
de...@driverdev.osuosl.org
Subject: Re: [2/3
On 07/30/2012 12:13 PM, Sasha Levin wrote:
>
> Yup, looks like it. kvm_stats is something like this:
>
> kvm_entry142104033 939393
> kvm_exit 142104004 939390
> kvm_apic 847
Sourav,
On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav wrote:
> Hi All,
>
> I tried using gpio as an interrupt line for my driver
> (drivers/staging/iio/light/tsl2x7x_core.c) for omap5.
> The interrupt line number was directly passed to the driver using
> device tree. But what I observed
> is th
On Monday 30 July 2012 02:39 PM, Kishon Vijay Abraham I wrote:
> + writel(~PHY_PD, phy->control_dev);
> + /* XXX: add proper documentation for this delay */
> + mdelay(200);
Do you need this to be busy?
--
To unsubscribe from this list: se
On 28/07/12 01:23, Linus Walleij wrote:
> On Tue, Jul 24, 2012 at 8:50 AM, John Crispin wrote:
>
>> Implement support for pinctrl on lantiq/falcon socs. The FALCON has 5 banks
>> of up to 32 pins.
>>
>> Signed-off-by: John Crispin
>> Signed-off-by: Thomas Langer
>> Cc: Linus Walleij
>> Cc: devi
On Mon, Jul 30, 2012 at 12:28:35AM +0200, Sasha Levin wrote:
> Hi all,
>
> I was poking around /dev/kmem related code, and noticed the following in
> mmap_kmem():
>
> /* Turn a kernel-virtual address into a physical page frame */
> pfn = __pa((u64)vma->vm_pgoff << PAGE_SHIFT) >>
Hi,
On Mon, Jul 30, 2012 at 3:07 PM, Shubhrajyoti wrote:
> On Monday 30 July 2012 02:39 PM, Kishon Vijay Abraham I wrote:
>> + writel(~PHY_PD, phy->control_dev);
>> + /* XXX: add proper documentation for this delay */
>> + mdelay(200);
>
Hi Linus,
the main kbuild branch ended up with a single commit this time, a fix to
send errors to stderr. Please pull from the below repository.
Thanks,
Michal
The following changes since commit f8f5701bdaf9134b1f90e5044a82c66324d2073f:
Linux 3.5-rc1 (2012-06-02 18:29:26 -0700)
are available
Thanks for your comments. Please find replies inline.
Regards,
Sandeep
-Original Message-
From: Francois Romieu [mailto:rom...@fr.zoreil.com]
Sent: 27 July 2012 20:56
To: Singh Sandeep-B37400
Cc: linuxppc-...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org;
ga...@kernel.crashing.
Hi Linus,
Please pull following kconfig changes for v3.6-rc1:
* kconfig Makefile portability fixes
* menuconfig/nconfig help pager usability fix
* .gitignore cleanup
* quoting fix in scripts/config
* Makefile prints errors to stderr
* support for arbitrarily log lines in .config
* fix oldnoconfig
28.07.2012 01:54, J. Bruce Fields пишет:
On Wed, Jul 25, 2012 at 04:55:45PM +0400, Stanislav Kinsbursky wrote:
Bruce, I feel this patch set is ready for inclusion.
v2:
1) Rebase on Bruce's "for-3.6" branch.
This patch set makes grace period and hosts reclaiming network namespace
aware.
On a
On Monday 30 July 2012 03:16 PM, ABRAHAM, KISHON VIJAY wrote:
> Hi,
>
> On Mon, Jul 30, 2012 at 3:07 PM, Shubhrajyoti wrote:
>> On Monday 30 July 2012 02:39 PM, Kishon Vijay Abraham I wrote:
>>> + writel(~PHY_PD, phy->control_dev);
>>> + /* XXX: add proper d
Thanks Stephen for your comments.
Plz see my comments inline.
> -Original Message-
> From: Stephen Boyd [mailto:sb...@codeaurora.org]
> Sent: Monday, July 30, 2012 2:47 PM
> To: Venu Byravarasu
> Cc: a.zu...@towertech.it; sa...@linux.intel.com;
> broo...@opensource.wolfsonmicro.com; Laxma
On Sat, Jul 14, 2012 at 2:12 AM, Shuah Khan wrote:
> The label oops is used in CONFIG_DEBUG_VM ifdef block and is defined
> outside ifdef CONFIG_DEBUG_VM block. This results in the following
> build warning when built with CONFIG_DEBUG_VM disabled. Fix to move
> label oops definition to inside a C
On Fri, Jul 27, 2012 at 06:32:15PM +0800, Wen Congyang wrote:
> We don't call __add_pages() directly in the function add_memory()
> because some other architecture related things need to be done
> before or after calling __add_pages(). So we should introduce
> a new function arch_remove_memory() to
if usb power supply registration fails,
we wont unregister the ac power supply
if battery power supply registration fails,
we wont unregister the usb, and ac supply,
take care of those things and also no need of goto -err_mem: at the fail case of
kzalloc simply can have return -ENO
At 07/30/2012 06:23 PM, Heiko Carstens Wrote:
> On Fri, Jul 27, 2012 at 06:32:15PM +0800, Wen Congyang wrote:
>> We don't call __add_pages() directly in the function add_memory()
>> because some other architecture related things need to be done
>> before or after calling __add_pages(). So we should
Hi Linus,
this is the non-critical part of kbuild for v3.6-rc1:
* Two new coccinelle semantic patches
* New scripts/tags.sh regexp
* scripts/config improvements that I mistakenly applied here instead of
in the kconfig branch (but there are no conflicts)
* Debian packaging fixes
Thanks,
Michal
On Mon, Jul 23, 2012 at 10:53 AM, Pavel Emelyanov wrote:
> This project is an attempt to implement the checkpoint-restore functionality
> for processes and containers without driving too much code into the kernel
> tree,
> but putting there "various oddball helper code" instead.
Is CRIU able to
module_platform_driver can be used to replace the
platform_driver register and unregister functions,
with the calls to module_init and module_exit,
i.e. all the code that is doing like the below
static int __init mymod_init(void)
{
return platform_driver_register(&drv_operations);
}
stat
with devm_kzalloc there is no need of freeing at the errorpath
and also at unregister it.
Signed-off-by: Devendra Naga
---
drivers/power/ds2781_battery.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/power/ds2781_battery.c b/drivers/power/ds2781_batt
Hi Linus,
Paul Bolle did a cleanup of headers in various architectures.
Because the patch touch several architectures at once, it was easiest
for me to apply them to the kbuild tree.
Thanks,
Michal
The following changes since commit f8f5701bdaf9134b1f90e5044a82c66324d2073f:
Linux 3.5-rc1 (2
On Mon, 2012-06-25 at 09:12 -0400, Peter Jones wrote:
> This adds support for appending to all UEFI variables, and also for
> deleting authentication variables.
>
> Signed-off-by: Peter Jones
> ---
> drivers/firmware/efivars.c | 99
> +---
> 1 file chan
> On Sun, Jul 29, 2012 at 09:31:53PM +0200, Witold Szczeponik wrote:
> > the aim is to select a PNP ACPI option where resources can be disabled
> > (or are not needed). E.g., the parallel port of the 600E can be used
> > with and without IRQ lines. The means to allow for this is to use the
> > sy
Hi,
On Fri, Jul 27, 2012 at 1:05 PM, Alexandre Courbot wrote:
> Some device drivers (panel backlights especially) need to follow precise
> sequences for powering on and off, involving gpios, regulators, PWMs
> with a precise powering order and delays to respect between each steps.
> These sequenc
Ping?
On Fri, Jun 29, 2012 at 10:48 AM, Sasha Levin wrote:
> Hi all,
>
> I've stumbled on the following while fuzzing with trinity in a KVM tools
> guest using latest linux-next:
>
> [ 3299.675163] [ cut here ]
> [ 3299.676027] kernel BUG at arch/x86/mm/pat.c:279!
> [ 329
On Thu, Jul 26, 2012 at 05:20:43PM +0200, Sebastian Andrzej Siewior wrote:
> If someone is using single stepping over uprobe brackpoint then after
> we pass the uprobe single step, single stepping is disabled and the user
> who enebaled them in the first place does not know anything about this.
>
On Mon, Jul 30, 2012 at 3:04 PM, DebBarma, Tarun Kanti
wrote:
> Sourav,
>
> On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav wrote:
>> Hi All,
>>
>> I tried using gpio as an interrupt line for my driver
>> (drivers/staging/iio/light/tsl2x7x_core.c) for omap5.
>> The interrupt line number was direc
On 29.07.2012 22:15, Marcin Slusarz wrote:
No, the real problem is: with "noaccel" we don't register "software engine",
but vblank ISR relies on its existance and happily derefences NULL pointer.
Now, this patch should fix it for real...
Unfortunately I am still seeing the crash. Without "noac
Hi,
On 27 July 2012 13:37, Fabio Estevam wrote:
> On Fri, Jul 27, 2012 at 12:17 AM, Vinod Koul
> wrote:
>
>>> Reported-by: Javier Martin
>>> Signed-off-by: Fabio Estevam
>> Applied thanks (to fixes-for 3.7)
>
> You mentioned that you would also copy stable. Would it be applied
> into stable s
On Sun, 29 Jul 2012, Namjae Jeon wrote:
> Date: Sun, 29 Jul 2012 07:31:54 -0400
> From: Namjae Jeon
> To: ty...@mit.edu, sand...@redhat.com, lczer...@redhat.com,
> linux-e...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org, Namjae Jeon ,
> Amit Sahrawat
> Subject: [PATCH] ext4: add er
On Fri, Jul 27, 2012 at 09:05:48PM +0900, Alexandre Courbot wrote:
> Some device drivers (panel backlights especially) need to follow precise
> sequences for powering on and off, involving gpios, regulators, PWMs
> with a precise powering order and delays to respect between each steps.
> These sequ
Hi all,
I do realize that we're in the middle of the merge window. But maybe
some of you will be bored enough to look into this; and no problem if
you don't feel like it -- I promise to send a brand new shiny v4 after
the merge window, so you won't miss a bit of this new cool stuff. :-)
In v3:
-
On Sun, 2012-07-29 at 06:50 -0400, Namjae Jeon wrote:
> update two mount option(discard, nfs) in vfat.txt.
>
> Signed-off-by: Namjae Jeon
> ---
Thanks. I knew there must be somewhere to document mount options but I
thought it would be in the userspace tools (util-linux).
Reviewed-by: Steven J.
The new arch callback should manage NMIs that usually cause KGDB to
enter. That is, not all NMIs should be enabled/disabled, but only
those that issue kgdb_handle_exception().
We must mask it as serial-line interrupt can be used as an NMI, so
if the original KGDB-entry cause was say a breakpoint,
This patch implements a new callback: clear_irqs. It is used for the
cases when KDB-entry (e.g. NMI) and KDB IO (e.g. serial port) shares
the same interrupt. To get the idea, let's take some real example (ARM
machine): we have a serial port which interrupt is routed to an NMI,
and the interrupt is
Just move the macros into header file as we would want to use them for
KGDB FIQ entry code.
The following macros were moved:
- svc_entry
- usr_entry
- kuser_cmpxchg_check
- vector_stub
To make kuser_cmpxchg_check actually work across different files, we
also have to make kuser_cmpxchg64_fixu
Just a couple of calls to manage VIC FIQ routing. We'll use them for
KGDB FIQ support on ARM Versatile machines.
Signed-off-by: Anton Vorontsov
---
arch/arm/common/vic.c | 28
arch/arm/include/asm/hardware/vic.h |2 ++
2 files changed, 30 insertio
This makes the code more izolated.
The downside of this is that we now have an additional branch and the
code itself is 8 bytes longer. But on the bright side, this new layout
can be more cache friendly since cr_alignment address might be already
in the cache line (not that I measured anything, it
As Colin Cross noticed, serial ports could be noisy, so occasional
characters once in a while are possible. So, considering the noise
possibility, entering the debugger on any received byte is unacceptable
for production devices.
This changes KGDB FIQ behaviour in a such way so that we have to typ
If enabled, kernel will able to enter KGDB upon serial line activity on
UART ports.
Note that even with this patch and CONFIG_KGDB_FIQ is enabled, you still
need to pass kgdb_fiq.enable=1 kernel command line option, otherwise UART
will behave in a normal way.
By default UART0 is used, but this ca
Currently kernel never set KGDB_REASON_NMI. We do now, when we enter
KGDB/KDB from an NMI.
This is not to be confused with kgdb_nmicallback(), NMI callback is
an entry for the slave CPUs during CPUs roundup, but REASON_NMI is the
entry for the master CPU.
Signed-off-by: Anton Vorontsov
---
kern
1 - 100 of 594 matches
Mail list logo
