On Wed, Aug 01, 2012 at 11:20:13AM -0600, Stephen Warren wrote:
> On 08/01/2012 09:54 AM, Jiang Liu wrote:
> > From: Jiang Liu
> >
> > Use PCIe capabilities access functions to simplify PCIe ARM implementation.
> >
> > Signed-off-by: Jiang Liu
>
> This is probably fine from my perspective
On Wed, Aug 1, 2012 at 8:00 PM, Christoph Lameter wrote:
> On Wed, 1 Aug 2012, Michael Kerrisk wrote:
>
>> Is the patch below acceptable? (I've attached the complete page as well.)
>
> Yes looks good.
Thanks for checking it!
>> See you in San Diego (?),
>
> Yup. I will be there too.
See you
Hello Chanho Min,
On 2012-08-02 오전 11:50, Chanho Min wrote:
-Original Message-
From: Kyungsik Lee [mailto:kyungsik@lge.com]
Sent: Wednesday, August 01, 2012 10:06 AM
To: Chris Ball
Cc: Venkatraman S; Jaehoon Chung; raphael.andy@gmail.com; linux-
m...@vger.kernel.org;
This is a preparation for removing the acpi_get_table_with_size(), as this
function could be well covered by acpi_get_table(), and there is no need
to have both of them to exist.
v2: As reminded by Yinghai, apply the replacment to
drivers/iommu/amd_iommu_init.c
which is a new user of the
On Wed, 1 Aug 2012 16:59:39 -0400
Don Dutile wrote:
> On 08/01/2012 02:37 AM, Feng Tang wrote:
> > This is a preparation for removing the acpi_get_table_with_size(), as this
> > function could be well covered by acpi_get_table(), and there is no need
> > to have both of them to exist.
> >
> >
> -Original Message-
> From: Matthias Kaehlcke [mailto:matthias.l...@kaehlcke.net]
> Sent: Thursday, August 02, 2012 1:48 AM
> To: Venu Byravarasu
> Cc: a.zu...@towertech.it; sa...@linux.intel.com;
> broo...@opensource.wolfsonmicro.com; Laxman Dewangan;
> kyle.ma...@fuel7.com;
On Wed, Aug 01, 2012 at 03:43:37PM +0200, Oleg Nesterov wrote:
...
> However, I am not sure we can trust it. We are in kernel mode,
> DEBUGCTLMSR_BTF can be cleared by kprobes (Ananth, please correct me).
> I think we need to check TIF_BLOCKSTEP.
Kprobes resets DEBUGCTLMSR_BTF only if we have
> -Original Message-
> From: Ira W. Snyder [mailto:i...@ovro.caltech.edu]
> Sent: Thursday, August 02, 2012 1:31 AM
> To: Liu Qiang-B32616
> Cc: linux-cry...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; dan.j.willi...@gmail.com; Vinod Koul; Tabi Timur-
>
> -Original Message-
> From: Ira W. Snyder [mailto:i...@ovro.caltech.edu]
> Sent: Thursday, August 02, 2012 12:31 AM
> To: Liu Qiang-B32616
> Cc: linux-cry...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; dan.j.willi...@gmail.com; Vinod Koul;
>
> -Original Message-
> From: Ira W. Snyder [mailto:i...@ovro.caltech.edu]
> Sent: Thursday, August 02, 2012 12:36 AM
> To: Liu Qiang-B32616
> Cc: linux-cry...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; dan.j.willi...@gmail.com; Vinod Koul;
>
On 2012年08月02日 12:18, Kevin Cernekee wrote:
On Wed, Aug 1, 2012 at 8:31 PM, Fan Du wrote:
show_backtrace must have an valid task when calling unwind_stack,
so fix it by checking first.
[...]
--- a/arch/mips/kernel/traps.c
+++ b/arch/mips/kernel/traps.c
@@ -151,6 +151,10 @@ static void
On 12-07-31 04:21 PM, Randy Dunlap wrote:
> On 07/31/2012 11:58 AM, Salar Ali Mumtaz wrote:
>
>> Now the debug_info only shows y/n/m values.
>>
>
>
> or no value at all??
Yes.
y/n/m or no value at all.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Wed, Aug 1, 2012 at 8:31 PM, Fan Du wrote:
> show_backtrace must have an valid task when calling unwind_stack,
> so fix it by checking first.
[...]
> --- a/arch/mips/kernel/traps.c
> +++ b/arch/mips/kernel/traps.c
> @@ -151,6 +151,10 @@ static void show_backtrace(struct task_struct *task,
>
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches before asking Linus to pull them ...
Changes since 20120731:
Removed trees: samsung, bjdooks-i2c (unfetchable)
Linus'
Hi all,
After merging the final tree, today's linux-next build (sparc64 defconfig)
produced this warning:
mm/shmem.c: In function 'shmem_interleave':
mm/shmem.c:1343:9: warning: assignment makes integer from pointer without a
cast [enabled by default]
Introduced by commit c3cfa3129c03 ("tmpfs:
On Wed, Aug 01, 2012 at 04:21:47PM -0700, Greg KH wrote:
> On Wed, Aug 01, 2012 at 05:54:00PM +0100, Matthew Garrett wrote:
> > On Tue, Jul 31, 2012 at 03:32:40PM -0700, Greg KH wrote:
> >
> > > With this series, does the latest MacBook work properly for the Intel
> > > graphics driver? Or is
Remove the non-sense isdnloop revision transform code, so as to fix:
[ 22.016214] isdnloop-ISDN-driver Rev 1.11.6.7
[ 22.097508] isdnloop: (loop0) virtual card added
[ 22.174400] Kernel panic - not syncing: stack-protector: Kernel stack is
corrupted in: 83244972
[ 22.174400]
[
On Thu, Aug 2, 2012 at 5:04 AM, Ondrej Zary wrote:
> There are more variants of Clevo M5x0V laptops and Positivo Mobile is just
> one of them.
> Another one is UMAX VisionBook 2400WXC. Use only generic Clevo DMI strings to
> match all
> variants.
>
Thanks, applied to my for-next branch
-Bryan
On Thu, Aug 2, 2012 at 5:04 AM, Ondrej Zary wrote:
> Enable autoloading of leds-clevo-mail by using MODULE_DEVICE_TABLE.
>
Thanks, applied to my for-next branch
-Bryan
> Signed-off-by: Ondrej Zary
>
> --- a/drivers/leds/leds-clevo-mail.c
> +++ b/drivers/leds/leds-clevo-mail.c
> @@ -31,7 +31,7
show_backtrace must have an valid task when calling unwind_stack,
so fix it by checking first.
root@romashell:/root> echo l > /proc/sysrq-trigger
SysRq : Show backtrace of all active CPUs
Stack : 81bf 81ceroot@octeon:/root> 81bf
0036
On Thu, 2 Aug 2012 11:20:33 +1000
Stephen Rothwell wrote:
> Hi Len,
>
> After merging the acpi tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/iommu/amd_iommu_init.c: In function 'early_amd_iommu_init':
> drivers/iommu/amd_iommu_init.c:1535:2: error:
On Tue, Jul 31, 2012 at 03:25:55PM -0700, Greg KH wrote:
> On Sun, Jul 29, 2012 at 05:26:33PM -0700, Jon Mason wrote:
> > +struct ntb_transport_qp;
> > +
> > +struct ntb_client {
> > + char *name;
> > + int (*probe) (struct pci_dev *pdev);
> > + void (*remove) (struct pci_dev *pdev);
> > +};
On Tue, Jul 31, 2012 at 02:02:25PM -0400, chetan loke wrote:
> On Tue, Jul 31, 2012 at 1:27 PM, Jon Mason wrote:
> >
> > I don't see the benefit of having the driver in staging. Any vendors
> > who would notice the ntb driver in staging would be sitting on these
> > mailing lists and hopefully
Reviewed-by: Kenji Kaneshige
Regards,
Kenji Kaneshige
> -Original Message-
> From: Jiang Liu [mailto:liu...@gmail.com]
> Sent: Thursday, August 02, 2012 12:54 AM
> To: Bjorn Helgaas; Don Dutile
> Cc: Jiang Liu; Yinghai Lu; Izumi, Taku/泉 拓; Rafael J . Wysocki; Kaneshige,
> Kenji/金重 憲治;
Reviewed-by: Kenji Kaneshige
Regards,
Kenji Kaneshige
> -Original Message-
> From: Jiang Liu [mailto:liu...@gmail.com]
> Sent: Thursday, August 02, 2012 12:54 AM
> To: Bjorn Helgaas; Don Dutile
> Cc: Jiang Liu; Yinghai Lu; Izumi, Taku/泉 拓; Rafael J . Wysocki; Kaneshige,
> Kenji/金重 憲治;
Reviewed-by: Kenji Kaneshige
Regards,
Kenji Kaneshige
> -Original Message-
> From: Jiang Liu [mailto:liu...@gmail.com]
> Sent: Thursday, August 02, 2012 12:54 AM
> To: Bjorn Helgaas; Don Dutile
> Cc: Jiang Liu; Yinghai Lu; Izumi, Taku/泉 拓; Rafael J . Wysocki; Kaneshige,
> Kenji/金重 憲治;
Hi Len,
After merging the acpi tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/iommu/amd_iommu_init.c: In function 'early_amd_iommu_init':
drivers/iommu/amd_iommu_init.c:1535:2: error: implicit declaration of function
'acpi_get_table_with_size'
This fixes two issues that could cause incompatibility between
kernel versions:
- If a tracer uses SECCOMP_RET_TRACE to select a syscall number
higher than the largest known syscall, emulate the unknown
vsyscall by returning -ENOSYS. (This is unlikely to make a
noticeable difference on
On Sun, 13 May 2012, John David Anglin wrote:
> On 13-May-12, at 4:40 PM, John David Anglin wrote:
>
> > Yes, the revised change fixes the compilation error. I'll know in a while
> > if
> > my config boots.
>
>
> I successfully booted 3.4-rc7 with this change on rp3440 (4 cpu smp). My
>
Oleg Nesterov writes:
> [...]
> Well, not sure this will help... but if you can reproduce this,
> may be you can identify the sender of the wrong SIGHUP at least.
>
> cd /sys/kernel/debug/tracing/
> echo "sig==1" >> events/signal/signal_generate/filter
> echo 1 >>
Sorry misunderstood your offlist mail I can cook up an x32 binary easily
enough.
Meredydd Luff wrote:
>On 2 Aug 2012 00:33, "H. Peter Anvin" wrote:
>> > Sorry, you're right. The argument vector needs compatibility
>support.
>> >
>> > This means you need an x32 version of the function
>
That bar could be 64bit pref mem.
Signed-off-by: Yinghai Lu
Cc: David Airlie
Reviewed-by: Daniel Vetter
---
drivers/char/agp/intel-gtt.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
Index: linux-2.6/drivers/char/agp/intel-gtt.c
Is it still Wednesday?
As promised, here are the last bits for md. Primarily performance
improvements made possible the new plugging code. These can make a
significant difference on SDD's and a noticeable difference on spinning rust.
Thanks,
NeilBrown
The following changes since commit
On Wed, Aug 01, 2012 at 05:36:52PM -0500, Alexis R. Cortes wrote:
> This patch is intended to work around a known issue on the
> SN65LVPE502CP USB3.0 re-driver that can delay the negotiation
> between a device and the host past the usual handshake timeout,
Paragraphs, please. :)
> if that
On 01/08/12 14:54, Cruz Julian Bishop wrote:
> Previously, when calling is_between(a, b, c), the calculation was wrong.
> It counted C as between A and B if C was equal to B, but not A.
>
> Example of this are:
>
> is_between(1, 10, 10) = 1 (Expected: 0)
> is_between(1, 10, 1) = 0 (Expected: 0)
On Wed, Aug 1, 2012 at 3:08 PM, Lukas Hejtmanek wrote:
> On Wed, Aug 01, 2012 at 02:32:17PM -0700, Yinghai Lu wrote:
>> yes, i knew that.
>>
>> one patch in my for-pci-next should address that.
>>
>>
Hello Borislav,
On Wed, Aug 01, 2012 at 07:38:37PM +0200, Borislav Petkov wrote:
> Hi,
>
> I'm hitting the WARN_ON in $Subject with latest linus:
> v3.5-8833-g2d534926205d on a 4-node AMD system. As it looks from
> dmesg, it is happening on node 0, 1 and 2 but not on 3. Probably the
>
On 08/01/2012 04:30 PM, H. Peter Anvin wrote:
> On 08/01/2012 04:09 PM, Meredydd Luff wrote:
#
# x32-specific system call numbers start at 512 to avoid cache impact
>>>
>>> I think that should be common, not 64 (as should kcmp be).
>>
>> I copied the original execve, which is 64.
>>
>
On Wed, Aug 01, 2012 at 04:46:27PM -0500, Alexis R. Cortes wrote:
> Hi Sarah,
>
> Sure!! I'll update the patch's description and will send another patch in a
> few moments.
>
> As an additional comment, I ran the 'checkpatch.pl' script and verified
> there were no errors before submitting the
On 08/01/2012 04:09 PM, Meredydd Luff wrote:
>>> #
>>> # x32-specific system call numbers start at 512 to avoid cache impact
>>
>> I think that should be common, not 64 (as should kcmp be).
>
> I copied the original execve, which is 64.
>
Sorry, you're right. The argument vector needs
Alexis R. Cortes wrote:
> This patch is intended to work around a known issue on the
> SN65LVPE502CP USB3.0 re-driver that can delay the negotiation
> between a device and the host past the usual handshake timeout,
> and if that happens on the first insertion, the host controller
> port will enter
On Wed, Aug 01, 2012 at 05:54:00PM +0100, Matthew Garrett wrote:
> On Tue, Jul 31, 2012 at 03:32:40PM -0700, Greg KH wrote:
>
> > With this series, does the latest MacBook work properly for the Intel
> > graphics driver? Or is this to resolve some other hardware issue?
>
> Apple only seem to
Thomas, Ingo,
This is against tip/timers/urgent. Let me know
if you'd like to see any further changes
-john
Unexpected behavior could occur if the time is set to
a value large enough to overflow a 64bit ktime_t
(which is something larger then the year 2264).
So check timekeeping inputs
Linus,
The following changes since commit 28a33cbc24e4256c143dce96c7d93bf423229f92:
Linux 3.5 (2012-07-21 13:58:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-3.6-rc1
---
This patch set contains mostly fixes and
The solution to this would be to disallow creation of files and
folders on NTFS drives containing illegal characters.
Illegal characters with respect to Windows & the like are different
from Illegal characters with respect to the NTFS filesystem structure.
Looking at ntfs-3g(8) [yes, I'm
On Wed, Aug 1, 2012 at 11:53 PM, H. Peter Anvin wrote:
> On 08/01/2012 03:10 PM, Meredydd Luff wrote:
>> diff --git a/arch/x86/syscalls/syscall_64.tbl
>> b/arch/x86/syscalls/syscall_64.tbl
>> index 51171ae..c35df9e 100644
>> --- a/arch/x86/syscalls/syscall_64.tbl
>> +++
On Fri, 27 Jul 2012 13:56:55 -0400
Jeff Garzik wrote:
> Rest in peace Andre,
He was a nice guy, and sure did like to talk on the phone.
He was very active and popular in the local Porsche enthusiast
community and is remember for his generosity. People share memories
here:
Following the trend of releasing before going on vacation, here is the
iproute2 release to go with last weeks 3.5.0 kernel release. The changes
were mainly adding support for the new queuing disciplines (codel etc)
and cleaning up the manual pages.
Source:
On Thursday, August 02, 2012 1:21 AM Damien Cassou wrote:
>
> From: Damien Cassou
>
> The devm_clk_get function allocates memory that is released when a driver
> detaches. This patch uses this function for data that is allocated in the
> probe
> function of a platform device and is only freed
Hi Paul,
For the last few days, I have been getting this error when trying to
fetch the moduleh tree:
fatal: unable to connect to openlinux.windriver.com:
openlinux.windriver.com[0: 192.124.127.100]: errno=Connection timed out
Is this tree still in use? Or should I just remove it from
On 08/01/2012 03:10 PM, Meredydd Luff wrote:
> diff --git a/arch/x86/syscalls/syscall_64.tbl
> b/arch/x86/syscalls/syscall_64.tbl
> index 51171ae..c35df9e 100644
> --- a/arch/x86/syscalls/syscall_64.tbl
> +++ b/arch/x86/syscalls/syscall_64.tbl
> @@ -319,6 +319,7 @@
> 310 64
On Thu, Aug 02, 2012 at 12:41:56AM +0200, Sasha Levin wrote:
> How would your DEFINE_HASHTABLE look like if we got for the simple
> 'struct hash_table' approach?
I think defining a different enclosing anonymous struct which the
requested number of array entries and then aliasing the actual
Hi Ben,
Since I haven't been able to fetch these trees for quite some time and I
haven't heard from you about them, I am removing the following trees from
linux-next. If/When you have time to maintain these trees again, we can
add them back without problems.
samsung
On 08/01/2012 10:24 PM, Tejun Heo wrote:
> On Wed, Aug 01, 2012 at 09:06:50PM +0200, Sasha Levin wrote:
>> Using a struct makes the dynamic case much easier, but it complicates the
>> static case.
>>
>> Previously we could create the buckets statically.
>>
>> Consider this struct:
>>
>> struct
This patch is intended to work around a known issue on the
SN65LVPE502CP USB3.0 re-driver that can delay the negotiation
between a device and the host past the usual handshake timeout,
and if that happens on the first insertion, the host controller
port will enter in Compliance Mode as per xHCI
On Wed, Aug 01, 2012 at 11:00:04PM +0200, Marc Kleine-Budde wrote:
> On 08/01/2012 08:21 PM, Fabio Baltieri wrote:
> > This patch implements the functions to add two LED triggers, named
> > -tx and -rx, to a canbus device driver.
> >
> > Triggers are called from specific handlers by each CAN
I recently started experiencing crashes (every 1-2 days) on one of my
ScientificLinux 6.2 boxes. It appears that the machine runs out of memory,
but the memory report makes no sense.
I'm seeing it with each of the following kernels:
kernel-2.6.32-220.17.1.el6.x86_64
On 02.08.2012 00:23, Meredydd Luff wrote:
Submitting this as a separate patch per rich...@nod.at's suggestion.
Signed-off-by: Meredydd Luff
Queued for 3.7.
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Submitting this as a separate patch per rich...@nod.at's suggestion.
Signed-off-by: Meredydd Luff
---
arch/um/kernel/exec.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/um/kernel/exec.c b/arch/um/kernel/exec.c
index 6cade93..e74ec80 100644
---
Jiri Kosina writes:
> if (personality(current->personality) == PER_LINUX32
> - && personality == PER_LINUX)
> - personality = PER_LINUX32;
> + && personality(personality) == PER_LINUX)
> + personality &= ~PER_LINUX | PER_LINUX32;
That doesn't work.
[v2 for style, CREDITS file is deprecated]
HPA is already on record calling for an execveat() which also does
fexecve()'s job: https://lkml.org/lkml/2006/7/11/556.
And the current glibc hack for fexecve() is already causing problems
in the wild. Eg:
On Wed, Aug 01, 2012 at 02:32:17PM -0700, Yinghai Lu wrote:
> yes, i knew that.
>
> one patch in my for-pci-next should address that.
>
> http://git.kernel.org/?p=linux/kernel/git/yinghai/linux-yinghai.git;a=patch;h=fcce563f868e296f46a2eeaa88d6959bcee26a2d
this is probably only half-way. well
On 01.08.2012 23:44, Meredydd Luff wrote:
HPA is already on record calling for an execveat() which also does
fexecve()'s job: https://lkml.org/lkml/2006/7/11/556.
And the current glibc hack for fexecve() is already causing problems
in the wild. Eg:
On Tue, 31 Jul 2012 19:23:59 -0700
Alex Kelly wrote:
> This was done in preparation for making core dump functionality optional.
>
> The variable "suid_dumpable" and associated functions are left in fs/exec.c
> because they're used elsewhere, such as in ptrace.
This patch will need to be
On Wed, Aug 01, 2012 at 02:27:34PM -0700, Yinghai Lu wrote:
> you may try to boot with pci=nocrs
ok, pci=nocrs i got:
02:00.0 InfiniBand: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s
- IB QDR / 10GigE] (rev b0)
02:00.1 InfiniBand: Mellanox Technologies MT25400 Family [ConnectX-2
HPA is already on record calling for an execveat() which also does
fexecve()'s job: https://lkml.org/lkml/2006/7/11/556.
And the current glibc hack for fexecve() is already causing problems
in the wild. Eg: https://bugzilla.redhat.com/show_bug.cgi?id=241609,
https://lkml.org/lkml/2006/12/27/123,
On 08/01/2012 03:24 PM, Mark Hounschell wrote:
What would happen if NVIDIA used this define in their proprietary
driver? I ask because I am currently in a situation where I believe I
may be about to use a product that may be doing this very thing. We had
to sign a license agreement to get the
On Wed, 01 Aug 2012 17:24:33 -0400
Mark Hounschell wrote:
> What would happen if NVIDIA used this define in their proprietary driver? I
Ask a lawyer but I believe Nvidia has more sense than that both
politically and legally. They walk a very fine line as it is (and IMHO
the wrong side of it
On Wed, Aug 1, 2012 at 1:56 PM, Lukas Hejtmanek wrote:
> On Wed, Aug 01, 2012 at 11:29:02AM -0700, Yinghai Lu wrote:
>> iov bar is not assigned by BIOS, and kernel can not find range for it too.
>>
>> Lukas, can you post whole boot log with PCI_DEBUG enabled? That will
>> tell exact why kernel
On Wed, Aug 1, 2012 at 1:28 PM, Lukas Hejtmanek wrote:
> On Wed, Aug 01, 2012 at 11:29:02AM -0700, Yinghai Lu wrote:
>> On Wed, Aug 1, 2012 at 10:37 AM, Roland Dreier wrote:
>> > On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek
>> > wrote:
>> >> [3.558296] mlx4_core :02:00.0: not enough
What would happen if NVIDIA used this define in their proprietary driver? I
ask because I am currently in a situation where I believe I may be about to
use a product that may be doing this very thing. We had to sign a license
agreement to get the kernel driver source for this product. What we
On Wed, Aug 01, 2012 at 10:01:31PM +0200, Peter Stuge wrote:
> Hi Alexis,
>
> Did you run the patch through checkpatch.pl before submitting it?
>
> I think you will get a bunch of important and completely automatic
> feedback when you do that. Please fix everything that the script
> mentions.
>
On 8/1/2012 11:54 AM, Jiang Liu wrote:
> From: Jiang Liu
>
> Use PCIe capabilities access functions to simplify PCIe tile implementation.
>
> Signed-off-by: Jiang Liu
> ---
> arch/tile/kernel/pci.c | 25 +
> 1 file changed, 5 insertions(+), 20 deletions(-)
Acked-by:
There are more variants of Clevo M5x0V laptops and Positivo Mobile is just one
of them.
Another one is UMAX VisionBook 2400WXC. Use only generic Clevo DMI strings to
match all
variants.
Signed-off-by: Ondrej Zary
--- a/drivers/leds/leds-clevo-mail.c
+++ b/drivers/leds/leds-clevo-mail.c
@@
Enable autoloading of leds-clevo-mail by using MODULE_DEVICE_TABLE.
Signed-off-by: Ondrej Zary
--- a/drivers/leds/leds-clevo-mail.c
+++ b/drivers/leds/leds-clevo-mail.c
@@ -31,7 +31,7 @@ static int __init clevo_mail_led_dmi_callback(const struct
dmi_system_id *id)
}
/*
- * struct
Fabio Baltieri hat am 1. August 2012 um 20:21
geschrieben:
> so, v6, change trigger names for fixed size allocation capped to (IFNAMSIZ +
> 4)
> and removed kasprintf as suggested by Oliver (thanks!).
>
> This also has the side effect of reducing the error path to just one check to
>
On Mon, Jul 30, 2012 at 10:33:34AM -0700, Colin Cross wrote:
> On Mon, Jul 30, 2012 at 4:58 AM, Anton Vorontsov
> wrote:
> > This command disables NMI-entry. If NMI source was previously shared with
> > a serial console ("debug port"), this effectively releases the port from
> > KDB exclusive
On 08/01/2012 01:49 PM, Fabio Baltieri wrote:
> Add support for canbus activity led indicators on flexcan devices by
> calling appropriate can_led_* functions.
>
> These are only enabled when CONFIG_CAN_LEDS is Y, becomes no-op
> otherwise.
>
> Cc: Oliver Hartkopp
> Cc: Wolfgang Grandegger
>
On 08/01/2012 08:21 PM, Fabio Baltieri wrote:
> This patch implements the functions to add two LED triggers, named
> -tx and -rx, to a canbus device driver.
>
> Triggers are called from specific handlers by each CAN device driver and
> can be disabled altogether with a Kconfig option.
>
> The
On 08/01/2012 02:37 AM, Feng Tang wrote:
This is a preparation for removing the acpi_get_table_with_size(), as this
function could be well covered by acpi_get_table(), and there is no need
to have both of them to exist.
v2: As reminded by Yinghai, apply the replacment to
On Wed, Aug 01, 2012 at 02:37:35PM -0600, Stephen Warren wrote:
> One outstanding issue with this change is that it removes the pm_runtime
> calls from the interrupt handler thread. Equivalent code should presumably
> be added to regmap_irq_thread(). However, I haven't attempted this yet
> since
On Wed, Aug 01, 2012 at 11:29:02AM -0700, Yinghai Lu wrote:
> iov bar is not assigned by BIOS, and kernel can not find range for it too.
>
> Lukas, can you post whole boot log with PCI_DEBUG enabled? That will
> tell exact why kernel does not assign them.
>
> Recent kernel from 3.4... should
On 07/23/2012 02:19 PM, Rafael Aquini wrote:
In a glance, I believe this whole dance you're suggesting might just be too much
of an overcomplication, and the best approach would be simply teaching the
hotplug bits about the ballooned corner case just like it's being done to
On Mon, Jul 30, 2012 at 03:15:44PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jul 30, 2012 at 04:58:20AM -0700, Anton Vorontsov wrote:
> > 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 Mon, Jul 30, 2012 at 03:07:24PM +0100, Russell King - ARM Linux wrote:
[]
> Now the thing here is that even if we did preserve SPSR_svc, with the
> above exit sequence, there is _no_ way to preserve the value of SPSR_svc.
> Normally, this doesn't matter because we know that the regions we
On 07/22/2012 10:33 PM, Minchan Kim wrote:
IMHO, better approach is that after we can get complete free pageblocks
by compaction or reclaim, move balloon pages into that pageblocks and make
that blocks to unmovable. It can prevent fragmentation and it makes
current or future code don't need to
From: Gyungoh Yoo
The MAX8907 is an I2C-based power-management IC containing voltage
regulators, a reset controller, a real-time clock, and a touch-screen
controller.
The original driver was written by:
* Gyungoh Yoo
Various fixes and enhancements by:
* Jin Park
* Tom Cherry
* Prashant
On 01/08/2012 22:43, Vincent ETIENNE wrote:
> Hi
> Some further progress on bisection
>
> I'm now here
>
> git bisect start
> # bad: [2d534926205db9ffce4bbbde67cb9b2cee4b835c] Merge tag
> 'irqdomain-for-linus' of git://git.secretlab.ca/git/linux-2.6
> git bisect bad
Hi
Some further progress on bisection
I'm now here
git bisect start
# bad: [2d534926205db9ffce4bbbde67cb9b2cee4b835c] Merge tag
'irqdomain-for-linus' of git://git.secretlab.ca/git/linux-2.6
git bisect bad 2d534926205db9ffce4bbbde67cb9b2cee4b835c
# good: [c3b92c8787367a8bb53d57d9789b558f1295cc96]
From: Stephen Warren
The Arizona core contains a shared IRQ line driven by multiple blocks,
each represented as a separate regmap_irq_chip in the kernel.
The existing code avoids calling request_threaded_irq() with no handler
multiple times on this shared interrupt line (which apparently wasn't
On Thu, Jul 26, 2012 at 10:51:18AM +0800, Bryan Wu wrote:
> OK, thanks, I've merge this patch through my tree and can I add your ack to
> it?
Sure,
Acked-by: Mark Brown
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, Aug 01, 2012 at 11:29:02AM -0700, Yinghai Lu wrote:
> On Wed, Aug 1, 2012 at 10:37 AM, Roland Dreier wrote:
> > On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek
> > wrote:
> >> [3.558296] mlx4_core :02:00.0: not enough MMIO resources for
> >> SR-IOV (nres: 0, iov->nres: 1)
> >
>
hi,
El Wed, Aug 01, 2012 at 11:52:37AM +0530 Venu Byravarasu ha dit:
> TPS65910 PMIC is a MFD with RTC as one of the device.
> Adding RTC driver for supporting RTC device present
> inside TPS65910 PMIC.
>
> Only support for RTC alarm is implemented as part of this patch.
>
> Signed-off-by:
On Wed, Aug 01, 2012 at 09:06:50PM +0200, Sasha Levin wrote:
> Using a struct makes the dynamic case much easier, but it complicates the
> static case.
>
> Previously we could create the buckets statically.
>
> Consider this struct:
>
> struct hash_table {
> u32 bits;
> struct
On Wed, Aug 01, 2012 at 01:57:24PM -0600, Stephen Warren wrote:
> From: Stephen Warren
>
> The kerneldoc for irq_set_irq_wake() says:
>
> Enable/disable power management wakeup mode, which is
> disabled by default.
Applied, thanks.
--
To unsubscribe from this list: send the line
On Sun, 29 Jul 2012, Eric Dumazet wrote:
> On Sun, 2012-07-29 at 12:10 +0200, Eric Dumazet wrote:
>
> > You can probably design something needing no more than 4 bytes per cpu,
> > and this thing could use non locked operations as bonus.
> >
> > like the following ...
>
> Coming back from my
* Tino Reichardt wrote:
> * Dave Kleikamp wrote:
> > On 07/28/2012 06:08 AM, Tino Reichardt wrote:
> > > * Tino Reichardt wrote:
> > >> > This patch adds support for the two linux interfaces of the
> > >> > discard/TRIM
> > >> > command for SSD devices and sparse/thinly-provisioned LUNs.
> > >
On Sun, 29 Jul 2012, Eric Dumazet wrote:
> On Sun, 2012-07-29 at 12:10 +0200, Eric Dumazet wrote:
>
> > You can probably design something needing no more than 4 bytes per cpu,
> > and this thing could use non locked operations as bonus.
> >
> > like the following ...
>
> Coming back from my
On Tue, Jul 17, 2012 at 12:10:42AM +0800, Axel Lin wrote:
> The mask used in anatop_get_voltage_sel does not match the mask used in
> anatop_set_voltage_sel.
> We need to do left shift anatop_reg->vol_bit_shift bits for the correct mask.
Applied, thanks.
--
To unsubscribe from this list: send the
On 08/01/2012 02:29 PM, Tino Reichardt wrote:
> * Dave Kleikamp wrote:
>> On 07/28/2012 06:08 AM, Tino Reichardt wrote:
>>> + tt->nblocks = 0; /* mark the current end */
>>> + for (tt = totrim; tt->nblocks != 0; tt++) {
>>> + if (!(JFS_SBI(sb)->flag & JFS_DISCARD)) {
>>> +
1 - 100 of 902 matches
Mail list logo
