On Thu, May 23, 2013 at 09:12:17PM +0200, Thierry Reding wrote:
> On Thu, May 23, 2013 at 10:39:34AM +0900, Simon Horman wrote:
> > On Mon, May 20, 2013 at 03:46:59PM +0200, Laurent Pinchart wrote:
> > > Hi Axel,
> > >
> > > Thank you for the patch.
> > >
> > > On Monday 20 May 2013 21:45:41
On Fri, May 24, 2013 at 09:35:02PM -0700, James Bottomley wrote:
> I'll go along with this. I'm also wondering what the problem would be
> if we just allowed all commands on either CAP_SYS_RAWIO or opening the
> device for write, so we just defer to the filesystem permissions and
> restricted
On 5/24/13 3:03 AM, Dave Chinner wrote:
> Right, patch below should fix the problem.
>
> What a frustrating bug. Now, where's my bottle of scotch?
In your pantry, Dave. Next to the others! ;)
-Eric
> Cheers,
>
> Dave.
>
--
To unsubscribe from this list: send the line "unsubscribe
I found a lot of mistakes using struct platform_driver without owner
so I make a macro instead of the function platform_driver_register.
It can set owner in it, then guys don`t care about module owner again.
Signed-off-by: Libo Chen
---
drivers/base/platform.c |8 +---
On OMAP4 platforms, EHCI HCD needs the physical layer signalling
activated, along with the NOP USB Transceiver driver. Otherwise, the
kernel boots without registering any USB device.
This patch applies to Linux 3.10-rc2.
Signed-off-by: Adrien Vergé
---
diff --git a/drivers/usb/host/Kconfig
On Fri, 2013-05-24 at 17:02 +0900, Tejun Heo wrote:
> On Fri, May 24, 2013 at 4:13 PM, Paolo Bonzini wrote:
> >> The same filtering table being applied to different classes of
> >> hardware is a software bug, but my point is that the practive
> >> essentially entrusts non-insignificant part of
Commit 8d57470d introduced a kernel panic while setting mem=2G at
boot time, and commit c9b3234a6 turns the the kernel panic to hang.
While, the reason is the same: the are accessing a BAD address; I mean
the mapping is broken.
Here is a mem mapping range dumped at boot time:
[mem
On Fri, 2013-05-24 at 10:32 +0200, Paolo Bonzini wrote:
> Il 24/05/2013 10:03, James Bottomley ha scritto:
> > > >>> Does anyone in the real world actually care about this bug?
> > >>
> > >> Yes, or I would move on and not waste so much time on this.
> >>> > >
> >>> > > Fine, so
Martin K. Petersen, on 05/22/2013 09:32 AM wrote:
> Paolo> First of all, I'll note that SG_IO and block-device-specific
> Paolo> ioctls both have their place. My usecase for SG_IO is
> Paolo> virtualization, where I need to pass information from the LUN to
> Paolo> the virtual machine with as
From: Zhang Yanfei
The only user of saved_max_pfn in s390 is read_oldmem interface but we
have removed that interface, so saved_max_pfn is now unneeded in s390,
and we needn't set it anymore.
Signed-off-by: Zhang Yanfei
Cc: Martin Schwidefsky
Cc: Heiko Carstens
Cc: Michael Holzheu
---
From: Zhang Yanfei
The only user of saved_max_pfn in ia64 is read_oldmem interface but we
have removed that interface, so saved_max_pfn is now unneeded in ia64,
and we needn't set it anymore.
Signed-off-by: Zhang Yanfei
Cc: Matt Fleming
Cc: Tony Luck
Cc: Fenghua Yu
---
From: Zhang Yanfei
saved_max_pfn is used to know the amount of memory that the previous
kernel used. And for powerpc, we set saved_max_pfn by passing the
kernel commandline parameter "savemaxmem=".
The only user of saved_max_pfn in powerpc is read_oldmem interface.
Since we have removed
From: Zhang Yanfei
saved_max_pfn is used to know the amount of memory that the previous
kernel used. And for powerpc, we set saved_max_pfn by passing the
kernel commandline parameter "savemaxmem=".
The only user of saved_max_pfn in mips is read_oldmem interface.
Since we have removed
From: Zhang Yanfei
Signed-off-by: Zhang Yanfei
Cc: Vivek Goyal
---
Documentation/kdump/kdump.txt | 31 ++-
1 files changed, 6 insertions(+), 25 deletions(-)
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index 9c7fd98..bec123e 100644
From: Zhang Yanfei
Signed-off-by: Zhang Yanfei
Cc: Dave Jones
---
Documentation/devices.txt |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/Documentation/devices.txt b/Documentation/devices.txt
index 08f01e7..4f85739 100644
--- a/Documentation/devices.txt
+++
From: Zhang Yanfei
/dev/oldmem provides the interface for us to access the "old memory" in
the dump-capture kernel. Unfortunately, no one actually uses this interface.
And this interface could actually cause some real problems if used on ia64
where the cached/uncached accesses are mixed. See
/dev/oldmem provides the interface for us to access the "old memory" in
the dump-capture kernel. Unfortunately, no one actually uses this interface.
And this interface could actually cause some real problems if used on ia64
where the cached/uncached accesses are mixed. See the discussion from
the
On Tue, May 21, 2013 at 3:22 PM, Linus Torvalds
wrote:
>
> Untested patch attached. It compiles cleanly, looks sane, and most of
> it is just making the function prototypes look much nicer. I think it
> works.
Ok, here's another patch in the "let's make the VFS go faster series".
This one,
Zhang Yanfei writes:
> Hello Eric,
>
>> The function copy_oldmem_page also concerns me. I don't have a clue why
>> we duplicate that function on every architecutre in a slightly different
>> form. There should be enough abstractions in the kernel to make that
>> unnecessary. I would be glad
On Wed, May 22, 2013 at 04:06:57PM -0500, Scott Wood wrote:
> On 05/20/2013 10:06:46 PM, Alexey Kardashevskiy wrote:
> >diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c
> >index 8465c2a..da6bf61 100644
> >--- a/arch/powerpc/kvm/powerpc.c
> >@@ -396,6 +396,7 @@ int
On 2013/5/24 17:30, Tang Chen wrote:
> In memory hot-remove procedure, we free pagetable pages to buddy system.
> But for local pagetable pages, do not free them to buddy system because
> they were skipped in offline procedure. The memory block they reside in
> could have been offlined, and we
I was testing a config for one bug and triggered a livelock lockup. A
NMI watchdog dump showed what was happening:
[ 65.972000] NMI backtrace for cpu 2
[ 65.972000] CPU: 2 PID: 48 Comm: kworker/2:1 Not tainted 3.10.0-rc2-test+
#151
[ 65.972000] Hardware name: To Be Filled By O.E.M. To Be
On 2013/5/24 17:30, Tang Chen wrote:
> In memory offline procedure, skip pages marked as LOCAL_NODE_DATA.
> For now, this kind of pages are used to store local node pagetables.
>
> The minimum unit of memory online/offline is a memory block. In a
> block, the movable pages will be offlined as
The XHCI stack usually uses wait_for_completion_interruptible_timeout()
to wait for the completion of an XHCI command, and treats both timeouts
and interruptions as errors. This is a bad idea, since these commands
are often essential for the correct operation of the USB stack, and
their failure
The current XHCI code treats a command completion event with the
COMP_CMD_STOP code as a slightly different version of COMP_CMD_ABORT. In
particular, it puts the pointed-to command TRB through the normal
command completion handlers. This is not how this event works.
As XHCI spec 4.6.1.1
Hello Eric,
于 2013年05月25日 06:44, Eric W. Biederman 写道:
> Vivek Goyal writes:
>
>> On Fri, May 24, 2013 at 05:06:26PM +0200, Michael Holzheu wrote:
>>> Hello Vivek,
>>>
>>> On Fri, 24 May 2013 10:36:44 -0400
>>> Vivek Goyal wrote:
>>>
>>> [snip]
>>>
Sorry, I don't understand the problem.
Hello,
Please advise if you can help me with bellow problem. I receive the
following messages on boot:
May 25 01:52:37 Leny kernel: ata1.00: failed to enable AA (error_mask=0x1)
May 25 01:52:37 Leny kernel: ata1.00: ATA-8: ST500LM012 HN-M500MBB,
2AR10001, max UDMA/100
May 25 01:52:37 Leny
Add the (*probe) function to the platform_driver and use the
module_platform_driver() macro to initialize the module.
Remove the unnecessary __init and __exit tags.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
This is a simple wrapper around writel(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
On Fri, May 24, 2013 at 10:25 AM, Bjorn Helgaas wrote:
>
> The problem we're trying to solve is that when allocation for type X
> fails, we retry allocation for type Y.
>
> This patch handles IO specially. I think it basically says, "if we
> only have IO allocation failures, don't retry MEM
On 2013-05-23 14:31:43, Paul Taysom wrote:
> When msync is called on a memory mapped file, that
> data is not flushed to the disk.
>
> In Linux, msync calls fsync for the file. For ecryptfs,
> fsync just calls the lower level file system's fsync.
> Changed the ecryptfs fsync code to call
BenH reported that there is some assign unassigned resource problem
in powerpc.
It turns out after
| commit 0c5be0cb0edfe3b5c4b62eac68aa2aa15ec681af
| Date: Thu Feb 23 19:23:29 2012 -0800
|
|PCI: Retry on IORESOURCE_IO type allocations
even the root bus does not have io port range, it will
strict_strtol is deprecated in favor of kstrtol.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/misc/ep93xx_pwm.c
This is a simple wrapper around readl(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git
This is a simple wrapper around readl(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git
This is a simple wrapper around readl(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git
This is a simple wrapper around writel(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
This is a simple wrapper around writel(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git
This is a simple wrapper around writel(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
This is a simple wrapper around writel(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git
This is a simple wrapper around writel(), remove it.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git
These are simple wrappers around writel() and readl(). Remove them.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 30 +-
1 file changed, 9 insertions(+), 21
The mmio_base is an ioremap'ed memory resource. The normal memory
io functions should be used not the __raw_* versions.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 4 ++--
1 file changed, 2
Use managed device resources to clean up the probe/remove.
Signed-off-by: H Hartley Sweeten
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ryan Mallon
Cc: Matthieu Crapet
---
drivers/misc/ep93xx_pwm.c | 73 +--
1 file changed, 20 insertions(+), 53
This driver needs to be converted to the new PWM framework.
Before converting it clean up all the cruft,
H Hartley Sweeten (14):
misc/ep93xx_pwm: use managed device resources
misc/ep93xx_pwm: use {read,write}* instead of __raw_* versions for io
misc/ep93xx_pwm: remove
Hi Linus,
The following changes since commit c7788792a5e7b0d5d7f96d0766b4cb6112d47d75:
Linux 3.10-rc2 (2013-05-20 14:37:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
for you to fetch changes up to
Vivek Goyal writes:
> On Fri, May 24, 2013 at 05:06:26PM +0200, Michael Holzheu wrote:
>> Hello Vivek,
>>
>> On Fri, 24 May 2013 10:36:44 -0400
>> Vivek Goyal wrote:
>>
>> [snip]
>>
>> > Sorry, I don't understand the problem. If we swapped low memory and
>> > crash reserved memory, that
On Fri, May 24, 2013 at 03:23:40PM -0400, Steven Rostedt wrote:
> On Fri, 2013-05-24 at 10:23 -0400, Dave Jones wrote:
>
> > .config: http://paste.fedoraproject.org/14281/94052971/raw/
> >
> > trace shows the problem process was 'cc1', so I was likely building a
> > kernel
> > at the
On Fri, 2013-05-24 at 20:25 +0200, Bjørn Mork wrote:
> Richard Weinberger writes:
> > Am 24.05.2013 15:18, schrieb Bjørn Mork:
> >> Richard Weinberger writes:
> >>
> >>> The Option GTM681W uses a qualcomm chip and can be
> >>> served by the qcserial device driver.
> >>
> >> Should it also be
On Fri, 24 May 2013 15:21:36 -0700 Davidlohr Bueso
wrote:
> >
> > Where should readers go to understand the overall locking scheme? A
> > description of the overall object hierarchy and the role which the
> > various locks play?
>
> That can be done, how about something like
>
On Fri, 2013-05-24 at 13:16 -0700, Andrew Morton wrote:
> On Wed, 15 May 2013 18:08:03 -0700 Davidlohr Bueso
> wrote:
>
> > This function currently acquires both the rw_mutex and the rcu lock on
> > successful lookups, leaving the callers to explicitly unlock them, creating
> > another two
On Fri, May 24, 2013 at 11:45:33AM +0200, Paolo Bonzini wrote:
> > It's not just unimplemented commands. Exposing any new command exposes
> > its borderline problems together with it.
>
> For commands that are used by Linux already, the right way to fix the
> problems is not obscuring the
Fixes:
arch/arm/mach-at91/built-in.o: In function `ksz9021rn_phy_fixup':
:(.text+0x1174): undefined reference to `mdiobus_write'
:(.text+0x1188): undefined reference to `mdiobus_write'
:(.text+0x119c): undefined reference to `mdiobus_write'
:(.text+0x11b0): undefined reference to `mdiobus_write'
Hi all,
On Thu, May 23, 2013 at 9:02 PM, Jaehoon Chung wrote:
> On 05/23/2013 04:25 PM, Guennadi Liakhovetski wrote:
>> On Wed, 22 May 2013, Felipe Ferreri Tonello wrote:
>>
>>> Hi Guennadi,
>>>
>>> On Wednesday, May 22, 2013 10:30:40 PM Guennadi Liakhovetski wrote:
On Wed, 22 May 2013,
The latest feature release Git v1.8.3 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
bfb88c182daeed5601ba860d785ac813433f55f1 git-1.8.3.tar.gz
92cc8ae5f4c1db2e7751ad0dc9c3227ca31080aa
Hi Mark,
On Tue, May 21, 2013 at 01:12:30PM -0500, Mark Brown wrote:
> The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
>
> Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
>
> are available in the git repository at:
>
>
On 05/24, Russell King - ARM Linux wrote:
> On Thu, May 23, 2013 at 10:54:26AM -0700, Stephen Boyd wrote:
> > On 05/15/13 12:38, Stephen Boyd wrote:
> > > On 05/08/13 14:47, Stephen Boyd wrote:
> > >> From: Brian Swetland
> > >>
> > >> Currently v7 CPUs with an MIDR that has no bits set in the
On 05/14/13 10:19, Jingoo Han wrote:
PM_GENERIC_DOMAINS needs PM dependency.
Fixed build warning as below:
warning: (PLAT_S3C64XX&& CPU_EXYNOS4210) selects PM_GENERIC_DOMAINS which has
unmet direct dependencies (PM)
If so, PLAT_S3C64XX should be fixed together.
diff --git
Hi Andy
On Thu, 23 May 2013, Andy Shevchenko wrote:
> When user interrupts ongoing transfers the dmatest may end up with console
> lockup, oops, or data mismatch. This patch prevents user to abort any ongoing
> test.
Personally I would be against such a change. What about interrupting the
test
On 05/18/13 19:19, Oliver Schinagl wrote:
+
+
+/* We read the entire key, using a look up table. Returned is only the
+ * requested byte. This is of course slower then it could be and uses 4 times
+ * more reads as needed but keeps code a little simpler.
+ */
+u8 sunxi_sid_read_byte(const int
Il 24/05/2013 10:32, Paolo Bonzini ha scritto:
> Il 24/05/2013 10:03, James Bottomley ha scritto:
>> Does anyone in the real world actually care about this bug?
Yes, or I would move on and not waste so much time on this.
>>
>> Fine, so produce a simple fix for
> On Thur, 23 May 2013 Andrew Morton wrote:
> > On Wed, 15 May 2013 07:46:36 -0500 Cliff Wickman wrote:
> > Certain tests in walk_page_range() (specifically split_huge_page_pmd())
> > assume that all the mapped PFN's are backed with page structures. And this
> > is
> > not usually true for
On Fri, May 24, 2013 at 7:22 PM, Takashi Iwai wrote:
>
> Well, I assumed that the EAPD off triggers the pin widget off by the
> hardware, too. But it seems wrong. By some reason, the hardware
> clears the pin automatically. Hmm.
>
> Could you try to trace the verbs while plugging the
On Fri, May 24, 2013 at 12:02:15PM -0500, Russ Anderson wrote:
> On Fri, May 24, 2013 at 11:11:11AM -0500, Robin Holt wrote:
> > Russ,
> >
> > Can we open a bug for the BIOS folks and see if we can get this addressed?
>
> I already talked with them. It is not in an area that we
>
On Fri, May 24, 2013 at 11:12:57AM -0700, Shawn Nematbakhsh wrote:
> If a USB controller with XHCI_RESET_ON_RESUME goes to runtime suspend,
> a reset will be performed upon runtime resume. Any previously suspended
> devices attached to the controller will be re-enumerated at this time.
> This will
Vahram,
This is your first patch modified to be a little more robust. If there is
no objection, I'll push it to linux-next along with Gu's nointegrity
patch.
From: Vahram Martirosyan
Date: Fri, 24 May 2013 13:57:12 +0500
The mentioned functions do not pay attention to the error codes returned
On Fri, May 24, 2013 at 08:11:01PM +, Matthew Garrett wrote:
> On Fri, 2013-05-24 at 15:05 -0500, Russ Anderson wrote:
>
> > One other data point is if the query_variable_info call is hacked to
> > remove one of the EFI flags (ie comment out EFI_VARIABLE_BOOTSERVICE_ACCESS)
> > the
On Thu, May 23, 2013 at 03:55:53AM +0800, Xiao Guangrong wrote:
> Zap at lease 10 pages before releasing mmu-lock to reduce the overload
> caused by requiring lock
>
> After the patch, kvm_zap_obsolete_pages can forward progress anyway,
> so update the comments
>
> [ It improves kernel building
On 05/24/2013 04:25 AM, Gu Zheng wrote:
> Hi Vahram,
>I saw the same issue in the bugzilla:
> https://bugzilla.kernel.org/show_bug.cgi?id=53331,
> and I sent out a patch this issue, but I've get any feedback.
Sorry I missed that bug. I just realized that bugzilla.kernel.org has
been sending
On Wed, 2013-05-22 at 13:59 +0200, Stanislaw Gruszka wrote:
> > AFICT, we wake queues only if beacon arrives or mac80211 call drv_config
> > with BSS_CHANGED_IDLE. I'm not sure if the latter prevent stuck.
>
> It should prevent stuck. When we fail to auth, drv_config() with
> BSS_CHANGED_IDLE
On Thu, 16 May 2013 05:28:26 + (GMT) Jingoo Han wrote:
> These functions allow the driver core to automatically clean up any
> allocation made by backlight drivers. Thus it simplifies the error
> paths.
>
> ...
>
> --- a/drivers/video/backlight/backlight.c
> +++
Hi Xiao,
On Thu, May 23, 2013 at 03:55:52AM +0800, Xiao Guangrong wrote:
> The current kvm_mmu_zap_all is really slow - it is holding mmu-lock to
> walk and zap all shadow pages one by one, also it need to zap all guest
> page's rmap and all shadow page's parent spte list. Particularly, things
>
On Wed, 15 May 2013 18:08:03 -0700 Davidlohr Bueso
wrote:
> This function currently acquires both the rw_mutex and the rcu lock on
> successful lookups, leaving the callers to explicitly unlock them, creating
> another two level locking situation.
>
> Make the callers (including those that
On Fri, May 24, 2013 at 06:03:00PM +1000, Dave Chinner wrote:
> xfstest generic/193 is *supposed* to test behaviour of suid/sgid bits
> and clearing them is various situations.
>
> You know what I'm about to say, don't you? The test doesn't test
> what it thinks it is testing. it puts the
On Fri, 2013-05-24 at 15:05 -0500, Russ Anderson wrote:
> One other data point is if the query_variable_info call is hacked to
> remove one of the EFI flags (ie comment out EFI_VARIABLE_BOOTSERVICE_ACCESS)
> the efi_call_phys4() call fails with EFI_INVALID_PARAMETER and
> the system boots. Of
Hi Emilio,
On Fri, May 24, 2013 at 09:53:07AM -0300, Emilio López wrote:
> Hi,
>
> El 24/05/13 06:23, Maxime Ripard escribió:
> > From: Stefan Roese
> >
> > Signed-off-by: Stefan Roese
> > ---
> > arch/arm/boot/dts/sun4i-a10-cubieboard.dts | 15 +++
> > 1 file changed, 15
Hi Emilio,
On Fri, May 24, 2013 at 09:46:32AM -0300, Emilio López wrote:
> El 24/05/13 06:23, Maxime Ripard escribió:
> > From: Stefan Roese
> >
> > The Allwinner A10 has an ethernet controller that seem to be developped
> > internally by them.
> >
> > The exact feature set of this controller
On Fri, May 24, 2013 at 08:43:31AM +0100, Matt Fleming wrote:
> On Thu, 23 May, at 03:32:34PM, Russ Anderson wrote:
> >efi: mem127: type=4, attr=0xf,
> > range=[0x6bb22000-0x7ca9c000) (271MB)
>
> EFI_BOOT_SERVICES_CODE
>
> >efi: mem133: type=5, attr=0x800f,
From: Fabio Estevam
Fix the following sparse warning:
drivers/dma/mxs-dma.c:696:17: warning: symbol 'mxs_dma_xlate' was not declared.
Should it be static?
Signed-off-by: Fabio Estevam
---
drivers/dma/mxs-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, 15 May 2013 22:12:32 +0200 Oleg Nesterov wrote:
> Imho, "atomic_t call_count" is ugly and should die. It buys
> nothing and in fact it can grow more than necessary, expand
> doesn't check if it was already incremented by another task.
>
> Kill it, and introduce "static int
On Fri, May 24, 2013 at 03:33:38PM +, Yu, Fenghua wrote:
> > From: Jacob Shin [mailto:jacob.s...@amd.com]
> > Add support for early microcode patch loading on AMD.
> >
> > Signed-off-by: Jacob Shin
> > ---
> > arch/x86/Kconfig | 16 +-
> >
On 10:15 Fri 24 May , boris brezillon wrote:
> On 23/05/2013 21:35, Thierry Reding wrote:
> >On Thu, May 23, 2013 at 06:38:52PM +0200, Boris BREZILLON wrote:
> >>Hello,
> >>
> >>I sent a patch 1 month ago to add pinctrl support to pwm-atmel-tcb
> >>driver and didn't get any review.
> >>
>
On Thu, May 9, 2013 at 1:51 PM, Lance Ortiz wrote:
> The following warning was seen on 3.9 when a corrected PCIe error was being
> handled by the AER subsystem.
>
> WARNING: at .../drivers/pci/search.c:214 pci_get_dev_by_id+0x8a/0x90()
>
> This occurred because a call to
From: Stephen M. Cameron
If a new logical drive is added and the CCISS_REGNEWD ioctl is invoked
(as is normal with the Array Configuration Utility) the process
will hang as below. It attempts to acquire the same mutex twice, once
in do_ioctl() and once in cciss_unlocked_open(). The BKL was
On Fri, 2013-05-24 at 10:23 -0400, Dave Jones wrote:
> .config: http://paste.fedoraproject.org/14281/94052971/raw/
>
> trace shows the problem process was 'cc1', so I was likely building a kernel
> at the time. There was also a trinity run going on in the background.
>
> cmdline: nothing
Richard Weinberger writes:
> Am 24.05.2013 15:18, schrieb Bjørn Mork:
>> Richard Weinberger writes:
>>
>>> The Option GTM681W uses a qualcomm chip and can be
>>> served by the qcserial device driver.
>>
>> Should it also be added to the qmi_wwan driver?
>
> Don't know. But I can happily test it.
diff --git a/Makefile b/Makefile
index 01003d4..bfbfaf9 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 9
-SUBLEVEL = 3
+SUBLEVEL = 4
EXTRAVERSION =
NAME = Unicycling Gorilla
diff --git a/arch/arm64/kernel/debug-monitors.c
b/arch/arm64/kernel/debug-monitors.c
I'm announcing the release of the 3.9.4 kernel.
All users of the 3.9 kernel series must upgrade.
The updated 3.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.9.y
and can be browsed at the normal kernel.org git web browser:
On 05/17/2013 11:17 AM, Dan Murphy wrote:
> On 05/17/2013 11:15 AM, Nishanth Menon wrote:
>> On 11:02-20130517, Dan Murphy wrote:
>>> The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
>>> are different.
>>>
>>> A1-A3 = gpio_wk7
>>> ES = gpio_110
>>>
>>> There is no change to
On Friday 24 May 2013, Olof Johansson wrote:
> [+akpm]
[+florian]
> On Fri, May 24, 2013 at 8:38 AM, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > Hi Florian,
> >
> > As you seems very busy I'd like to propose the help you to handle
> > the
> > fbdev subsystem to easier the
On Fri, May 24 2013, OS Engineering wrote:
> Hi Jens and Kernel Gurus,
[snip]
Thanks for writing all of this up, but I'm afraid it misses the point
somewhat. As stated previously, we have (now) two existing competing
implementations in the kernel. I'm looking for justification on why YOUR
MSM_TLMM_BASE is currently not mapped by 8x60. Remove it.
Signed-off-by: Rohit Vaswani
---
arch/arm/mach-msm/include/mach/msm_iomap-8x60.h |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-msm/include/mach/msm_iomap-8x60.h
This cleans up the gpio-msm-v2 driver of all the global define usage.
The number of gpios are now defined in the device tree. This enables
adding irqdomain support as well.
Signed-off-by: Rohit Vaswani
---
.../devicetree/bindings/gpio/gpio-msm.txt | 26 +++
Remove gpiomux-v2 as it's not being used and make way for future improvements.
Signed-off-by: Rohit Vaswani
---
arch/arm/mach-msm/Kconfig| 13 +++-
arch/arm/mach-msm/Makefile |6 +--
arch/arm/mach-msm/gpiomux-8x60.c | 19
arch/arm/mach-msm/gpiomux-v2.c |
Hi Linus,
Could this series go through David's tree or is there a better way to do this?
It would be great if I can have you ack for the gpio patch.
Thanks,
Rohit
Rohit Vaswani (3):
ARM: msm: Remove gpiomux-v2 and re-organize MSM_GPIOMUX configs
ARM: msm: Remove unused and unmapped
Hi Linus,
Could this series go through David's tree or is there a better way to do this?
It would be great if I can have you ack for the gpio patch.
Thanks,
Rohit
Rohit Vaswani (3):
ARM: msm: Remove gpiomux-v2 and re-organize MSM_GPIOMUX configs
ARM: msm: Remove unused and unmapped
diff --git a/Makefile b/Makefile
index 3d88eb8..a85d4eb 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 46
+SUBLEVEL = 47
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/drivers/gpu/drm/radeon/evergreen.c
I'm announcing the release of the 3.4.47 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:
diff --git a/Makefile b/Makefile
index f8ade05..dad194f 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 0
-SUBLEVEL = 79
+SUBLEVEL = 80
EXTRAVERSION =
NAME = Sneaky Weasel
diff --git a/drivers/hwmon/abituguru.c b/drivers/hwmon/abituguru.c
index 65a35cf..61ab615
I'm announcing the release of the 3.0.80 kernel.
All users of the 3.0 kernel series must upgrade.
The updated 3.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.0.y
and can be browsed at the normal kernel.org git web browser:
1 - 100 of 872 matches
Mail list logo
