This dongle ships with the X1 Carbon, and has an AX88772B
usb to ethernet chip in it.
Signed-off-by: Quinlan Pfiffer
---
drivers/net/usb/asix_devices.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/net/usb/asix_devices.c b/drivers/net/usb/asix_devices.c
index 32e31c5..fc20e53
On 2012-09-28 16:38, Dave Jones wrote:
> On Fri, Sep 28, 2012 at 10:41:50AM +0200, Jens Axboe wrote:
>
> > > Turns out that blkid is running simultaneously with losetup -d, and
> > > so it sees an elevated reference count and returns EBUSY. But why
> > > is blkid running? It's obvious, isn't
On 2012-09-28 17:02, Jeff Moyer wrote:
> Jens Axboe writes:
>
>> On 2012-09-28 08:09, Dave Chinner wrote:
>>> From: Dave Chinner
>>>
>>> xfstests has always had random failures of tests due to loop devices
>>> failing to be torn down and hence leaving filesytems that cannot be
>>> unmounted.
I have a situation where a single-bay NAS, the Qnap TS 119 P II in the
newest revision has 2 usb3 ports on the back. When using the 3.6-rc7
kernel (and earlier ones), these ports don't exist. There is no output
with lsusb, and the device doesn't show up with lspci or dmesg. The
directory
As suggested by James: this patch tries to short the path length of
scsi_cmd_to_driver(). As only REQ_TYPE_BLOCK_PC commands can be
submitted without a driver, so we could avoid the related NULL
checking, as long as we make sure we don't use it for REQ_TYPE_BLOCK_PC
type commands. Plus, this fixes
On 09/05/2012 05:25 PM, we...@cn.fujitsu.com wrote:
From: Wen Congyang
This patch series aims to support physical memory hot-remove.
The patches can free/remove the following things:
- acpi_memory_info : [RFC PATCH 4/19]
- /sys/firmware/memmap/X/{end, start,
After Kernel Summit and Plumbers, I wanted to consider all the various
side-discussions and try to summarize my current thoughts here along
with sending out my current implementation for review.
Also: I'm going on four weeks of paternity leave in the very near
(but non-deterministic) future. So
Rework of my first pass attempt at getting ashmem to utilize
the volatile range code, now using the fallocate interface.
In this implementation GET_PIN_STATUS is unimplemented, due to
the fact that adding a ISVOLATILE check wasn't considered
terribly useful in earlier reviews. It would be trivial
This patch provides the volatile range management code
that filesystems can utilize when implementing
FALLOC_FL_MARK_VOLATILE.
It tracks a collection of page ranges against a mapping
stored in an interval-tree. This code handles coalescing
overlapping and adjacent ranges, as well as splitting
This patch enables FALLOC_FL_MARK_VOLATILE/UNMARK_VOLATILE
functionality for tmpfs making use of the volatile range
management code.
Conceptually, FALLOC_FL_MARK_VOLATILE is like a delayed
FALLOC_FL_PUNCH_HOLE. This allows applications that have
data caches that can be re-created to tell the
On 09/28/2012 10:37 AM, Peter Hurley wrote:
>
> An interesting side note: more recent revisions of this BIOS (rev. A11)
> report one less variable MTRR (so, IA32_MTRRCAP is writable?)
>
>>> However, the right way to fix that is to use the PAT interfaces, which
>>> doesn't have this drawback --
On Thu, 2012-09-20 at 15:52 -0700, David Sharp wrote:
> diff --git a/include/asm-generic/trace_clock.h
> b/include/asm-generic/trace_clock.h
> new file mode 100644
> index 000..6726f1b
> --- /dev/null
> +++ b/include/asm-generic/trace_clock.h
> @@ -0,0 +1,16 @@
> +#ifndef
On Fri, Sep 28, 2012 at 08:26:08PM -0500, Daniel Santos wrote:
> On 09/28/2012 07:32 PM, Josh Triplett wrote:
> > On Fri, Sep 28, 2012 at 06:20:09PM -0500, Daniel Santos wrote:
> >> Negative sized arrays wont create a compile-time error in some cases
> >> starting with gcc 4.4 (e.g., inlined
On 2012-09-28 22:54, Paul Bolle wrote:
On Fri, 2012-09-28 at 11:43 +0800, Zhenzhong Duan wrote:
On 2012-09-27 19:35, Paul Bolle wrote:
I think setting pages_to_unuse to zero here is not needed. It is
initiated to zero in frontswap_shrink() and hasn't been touched since.
See my patch at
On 2012-09-29 01:37, Peter Hurley wrote:
On Sun, 2012-09-09 at 23:54 -0400, zhenzhong.duan wrote:
On 2012-09-08 02:40, H. Peter Anvin wrote:
On 09/07/2012 10:44 AM, Peter Hurley wrote:
diff --git a/arch/x86/kernel/cpu/mtrr/cleanup.c
b/arch/x86/kernel/cpu/mtrr/cleanup.c
I really don't like
On 09/29/2012 01:53 AM, Paul E. McKenney wrote:
> On Thu, Sep 20, 2012 at 08:51:01AM +0800, Michael Wang wrote:
>> This patch set optimize the RCU trace to make it perform better on the
>> platform with thousands of cpus.
>>
>> The optimization including:
>> -- the cpu info will be separated
On 09/27/2012 01:45 PM, we...@cn.fujitsu.com wrote:
From: Wen Congyang
Wen Congyang (2):
memory-hotplug: clear hwpoisoned flag when onlining pages
memory-hotplug: auto offline page_cgroup when onlining memory block
failed
Again, you should explain these two patches are the new
Even though with the change of commit commit 2b29175 "tools lib traceevent:
Carve out events format parsing routine", allowed __pevent_parse_format() to
parse an event without the need of a pevent handler, the event still needs to
assign the pevent handed to it.
There's no problem with assigning
On 09/05/2012 05:25 PM, we...@cn.fujitsu.com wrote:
From: Yasuaki Ishimatsu
The function get_page_bootmem() may be called more than one time to the same
page. There is no need to set page's type, private if the function is not
the first time called to the page.
Note: the patch is just
Hi,
Can you please pull from the following URL?
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
The following changes since commit 236367db10f1e618a3ced2538f5cd1802c31ebd8:
Yuval Mintz (1):
bnx2x: update fw to 7.8.2
are available in the git repository at:
On Fri, 28 Sep 2012, Joe Perches wrote:
> On Fri, 2012-09-28 at 15:50 -0400, Alan Stern wrote:
> > Here's what I just got from checkpatch:
> >
> > ERROR: space prohibited after that '-' (ctx:BxW)
> > #22: FILE: drivers/usb/host/ehci-sched.c:1419:
> > + start += (next -
On 09/28/2012 07:32 PM, Josh Triplett wrote:
> On Fri, Sep 28, 2012 at 06:20:09PM -0500, Daniel Santos wrote:
>> Negative sized arrays wont create a compile-time error in some cases
>> starting with gcc 4.4 (e.g., inlined functions), but gcc 4.3 introduced
>> the error function attribute that
On 09/11/2012 12:54 AM, wei_w...@realsil.com.cn wrote:
> From: Wei WANG
>
> Support for Realtek PCI-Express driver-based card readers including rts5209
> and rts5229.
>
> v2:
> 1. Using platform device to replace realtek slot bus
>
> v3:
> 1. Fix a bug that DMA out of SW-IOMMU space in Lenovo
On Fri, 2012-09-28 at 17:23 -0700, Josh Triplett wrote:
> On Fri, Sep 28, 2012 at 06:20:07PM -0500, Daniel Santos wrote:
> > Signed-off-by: Daniel Santos
> > ---
> > include/linux/bug.h |2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/include/linux/bug.h
On Fri, Sep 28, 2012 at 08:26:51PM -0400, Ramesh Nagappa wrote:
> >
> > Why is all of this in the middle of the changelog section?
> >
> > I'm guessing you didn't use 'git send-email' for this?
> >
> > And why are you copying me on the patch?
>
> I got the CC list from
The ACPI BGRT driver accesses the BIOS logo image when it initializes.
However, ACPI 5.0 (which introduces the BGRT) recommends putting the
logo image in EFI boot services memory, so that the OS can reclaim that
memory. Production systems follow this recommendation, breaking the
ACPI BGRT driver.
The EFI initialization creates virtual mappings for EFI boot services
memory, so if a driver wants to access EFI boot services memory, it
cannot call ioremap itself; doing so will trip the WARN about mapping
RAM twice. Thus, a driver accessing EFI boot services memory must do so
via the existing
The ACPI BGRT lets the OS access the BIOS logo image and its position on the
screen at boot time, allowing it to maintain that image on the screen until
ready to display something else, making boot more seamless. This series fixes
support for accessing the boot logo image via the BGRT when the
Some new ACPI 5.0 tables reference resources stored in boot services
memory, so keep that memory around until we have ACPI and can extract
data from it.
Signed-off-by: Josh Triplett
---
arch/x86/platform/efi/efi.c | 31 ++-
include/linux/efi.h |5 +
On 09/28/2012 07:32 PM, Josh Triplett wrote:
> On Fri, Sep 28, 2012 at 06:20:09PM -0500, Daniel Santos wrote:
>> Negative sized arrays wont create a compile-time error in some cases
>> starting with gcc 4.4 (e.g., inlined functions), but gcc 4.3 introduced
>> the error function attribute that
On Fri, Sep 28, 2012 at 07:38:32PM -0500, Daniel Santos wrote:
> On 09/28/2012 07:26 PM, Josh Triplett wrote:
> > On Fri, Sep 28, 2012 at 06:20:08PM -0500, Daniel Santos wrote:
> >> --- a/include/linux/compiler-gcc4.h
> >> +++ b/include/linux/compiler-gcc4.h
> >> @@ -15,7 +15,12 @@
> >>
> >>
On Fri, Sep 28, 2012 at 07:34:36PM -0500, Daniel Santos wrote:
> On 09/28/2012 07:23 PM, Josh Triplett wrote:
> > On Fri, Sep 28, 2012 at 06:20:06PM -0500, Daniel Santos wrote:
> >> __linktime_error() does the same thing as __compiletime_error() and is
> >> only used in bug.h. Since the macro
On 09/28/2012 07:26 PM, Josh Triplett wrote:
> On Fri, Sep 28, 2012 at 06:20:08PM -0500, Daniel Santos wrote:
>> --- a/include/linux/compiler-gcc4.h
>> +++ b/include/linux/compiler-gcc4.h
>> @@ -15,7 +15,12 @@
>>
>> #if GCC_VERSION >= 40102
>> # define __compiletime_object_size(obj)
On Fri, Sep 28, 2012 at 07:31:53PM -0500, Daniel Santos wrote:
> On 09/28/2012 07:20 PM, Josh Triplett wrote:
> > On Fri, Sep 28, 2012 at 06:20:05PM -0500, Daniel Santos wrote:
> >> --- a/include/linux/compiler-gcc4.h
> >> +++ b/include/linux/compiler-gcc4.h
> >> @@ -13,11 +13,11 @@
> >> #define
On 09/28/2012 07:23 PM, Josh Triplett wrote:
> On Fri, Sep 28, 2012 at 06:20:06PM -0500, Daniel Santos wrote:
>> __linktime_error() does the same thing as __compiletime_error() and is
>> only used in bug.h. Since the macro defines a function attribute that
>> will cause a failure at compile-time
On Fri, Sep 28, 2012 at 06:20:09PM -0500, Daniel Santos wrote:
> Negative sized arrays wont create a compile-time error in some cases
> starting with gcc 4.4 (e.g., inlined functions), but gcc 4.3 introduced
> the error function attribute that will. This patch modifies
> BUILD_BUG_ON to behave
On 09/28/2012 07:20 PM, Josh Triplett wrote:
> On Fri, Sep 28, 2012 at 06:20:05PM -0500, Daniel Santos wrote:
>> --- a/include/linux/compiler-gcc4.h
>> +++ b/include/linux/compiler-gcc4.h
>> @@ -13,11 +13,11 @@
>> #define __must_check__attribute__((warn_unused_result))
>> #define
>
> Why is all of this in the middle of the changelog section?
>
> I'm guessing you didn't use 'git send-email' for this?
>
> And why are you copying me on the patch?
I got the CC list from scripts/get_maintainers.pl
asglx-2-300 $ scripts/get_maintainer.pl
On Fri, Sep 28, 2012 at 06:20:08PM -0500, Daniel Santos wrote:
> --- a/include/linux/compiler-gcc4.h
> +++ b/include/linux/compiler-gcc4.h
> @@ -15,7 +15,12 @@
>
> #if GCC_VERSION >= 40102
> # define __compiletime_object_size(obj) __builtin_object_size(obj, 0)
> -#endif
> +
> +/* flatten
On Fri, Sep 28, 2012 at 06:20:07PM -0500, Daniel Santos wrote:
> Signed-off-by: Daniel Santos
> ---
> include/linux/bug.h |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/bug.h b/include/linux/bug.h
> index aaac4bb..298a916 100644
> ---
On Fri, Sep 28, 2012 at 06:20:06PM -0500, Daniel Santos wrote:
> __linktime_error() does the same thing as __compiletime_error() and is
> only used in bug.h. Since the macro defines a function attribute that
> will cause a failure at compile-time (not link-time), it makes more
> sense to keep
On Fri, Sep 28, 2012 at 06:20:05PM -0500, Daniel Santos wrote:
> --- a/include/linux/compiler-gcc4.h
> +++ b/include/linux/compiler-gcc4.h
> @@ -13,11 +13,11 @@
> #define __must_check __attribute__((warn_unused_result))
> #define __compiler_offsetof(a,b) __builtin_offsetof(a,b)
>
Sorry, Outlook managled the patch. I will try to find a way to re-submit it.
>
> You need a blank line before the first Signed-off-by: line.
> Surely one of the reviewers should have caught this basic thing?
>
> greg k-h
>
-- Ramesh--
To unsubscribe from this list: send the line
On Fri, 2012-09-28 at 13:14 -0700, Greg Kroah-Hartman wrote:
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Ian Chen
>
> commit 3550ccdb9d8d350e526b809bf3dd92b550a74fe1 upstream.
>
> For several MoviNAND eMMC parts, there are
On Wed, Sep 26, 2012 at 7:29 PM, David Rientjes wrote:
> NR_MLOCK is only accounted in single page units: there's no logic to
> handle transparent hugepages. This patch checks the appropriate number
> of pages to adjust the statistics by so that the correct amount of memory
> is reflected.
>
>
On Sat, Sep 29, 2012 at 12:51:04AM +0200, Ben Hutchings wrote:
> On Fri, 2012-09-28 at 13:34 -0700, Greg Kroah-Hartman wrote:
> > 3.0-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: NeilBrown
> >
> > commit
>From fd023edd911ef12aca38a72b40241661c202684f Mon Sep 17 00:00:00 2001
From: Ramesh Nagappa
Date: Thu, 27 Sep 2012 10:20:58 -0700
Subject: [PATCH] net: fix neigh_resolve_output can cause skb_under_panic
The retry loop in the neigh_resolve_output() and neigh_connected_output() can
add
a
On Fri, Sep 28, 2012 at 07:40:39PM -0400, Ramesh Nagappa wrote:
> >From fd023edd911ef12aca38a72b40241661c202684f Mon Sep 17 00:00:00 2001
> From: Ramesh Nagappa
> Date: Thu, 27 Sep 2012 10:20:58 -0700
> Subject: [PATCH] net: fix neigh_resolve_output can cause skb_under_panic
Why is all of this
A script that uses sqlite to load test results and generates a report
showing differences in performance per compiler used.
Signed-off-by: Daniel Santos
---
tools/testing/selftests/grbtree/user/gen_report.sh | 129
1 files changed, 129 insertions(+), 0 deletions(-)
create
Userspace test program using code from common.{c,h}. Userspace
compliation is accomplished by ovreriding a few kernel headers in the
overrides directory. This is an invasive hack (involving many internals
of kernel headers) that is expected to require fairly frequent
maintainence as kernel
A Gentoo-specific script (to be run by root) to iterate through all
installed compilers, execte runtest.sh script and collect the output
data.
Signed-off-by: Daniel Santos
---
tools/testing/selftests/grbtree/user/runtests.sh | 52 ++
1 files changed, 52 insertions(+), 0
This is a basic script is designed to automate the testing process (for
a single compiler) and generate delimited text output suitable for later
processing. All test parameters can be supplied via the environment, or
defaults will be used for them. The following variables affect the
script and if
Self-test code for both performance and correctness testing. The files
tools/testing/selftests/grbtree/common.{h,c} contain code for use in
both the user- and kernel-space test program/module and depends upon a
few functions being made available by said.
The purpose of these tests is to verify
On Fri, Sep 28, 2012 at 4:27 PM, Ben Hutchings wrote:
>
> The upstream version exchanges fget_light() for fget_raw_light(). Since
> 3.2 (and likewise 3.4) have fget() here, I cherry-picked e994def 'VFS:
> make vfs_fstat() use f[get|put]_light()' before this. Was that a
> bad/good/neutral idea?
Fix macro name in checkpatch: s/PARAM/PARM/.
Signed-off-by: Kees Cook
---
scripts/checkpatch.pl |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index ca05ba2..df5e229 100755
--- a/scripts/checkpatch.pl
+++
We shouldn't depend upon kernel.h including this for us. However, this
also fixes some issues with compiling in userland (coming later).
Signed-off-by: Daniel Santos
---
include/linux/rbtree.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/rbtree.h
Signed-off-by: Daniel Santos
---
include/linux/rbtree.h | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/include/linux/rbtree.h b/include/linux/rbtree.h
index 5f10915..c815b5e 100644
--- a/include/linux/rbtree.h
+++ b/include/linux/rbtree.h
@@ -35,6 +35,20
This introduces the following .config variables:
DEBUG_GRBTREE
DEBUG_GRBTREE_VALIDATE
DEBUG_GRBTREE will enable the use of the following new flags in struct
rb_relationship's flags member. When DEBUG_GRBTREE is not enabled in the
config, these flags will evaluate to zero.
RB_VERIFY_USAGE -
Signed-off-by: Daniel Santos
---
Documentation/DocBook/kernel-api.tmpl |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/DocBook/kernel-api.tmpl
b/Documentation/DocBook/kernel-api.tmpl
index 00687ee..d270f1e 100644
---
Add generic red-black tree code to rbtree.h.
Signed-off-by: Daniel Santos
---
include/linux/rbtree.h | 1125 +++-
1 files changed, 1123 insertions(+), 2 deletions(-)
diff --git a/include/linux/rbtree.h b/include/linux/rbtree.h
index 0022c1b..210ebeb
This patch set depends upon the following:
* Cleanup & new features for compiler*.h and bug.h
* kernel-doc bug fixes (for generating docs)
Summary
===
This patch set improves on Andrea Arcangeli's original Red-Black Tree
implementation by adding generic search and insert functions with
On Fri, Sep 28, 2012 at 03:58:26PM -0500, Thad Phetteplace wrote:
> I am debugging an issue with copy_to_user performance on recent linux
> kernels. I've noticed a 4X slowdown in copy speed when I move from
> kernel 2.6.18 to more recent kernels on the same hardware. I've
> tested so far on
On Fri, Sep 28, 2012 at 6:24 AM, Joerg Roedel wrote:
> Finally enable interrupt remapping for AMD systems.
>
> Signed-off-by: Joerg Roedel
> ---
> drivers/iommu/irq_remapping.c |5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/iommu/irq_remapping.c
On Fri, 2012-09-28 at 13:14 -0700, Greg Kroah-Hartman wrote:
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Russell King
>
> commit 8404663f81d212918ff85f493649a7991209fa04 upstream.
>
> The {get,put}_user macros don't perform
From: "Kirill A. Shutemov"
Special PMD is similar to special PTE: it requires special handling.
Currently, it's needed to mark PMD with all PTEs set to zero page.
If an arch wants to provide support of special PMD it need to select
HAVE_PMD_SPECIAL config option and implement pmd_special() and
From: "Kirill A. Shutemov"
Here's alternative implementation of huge zero page: virtual huge zero
page.
Virtual huge zero page is a PMD table with all entries set to zero page.
H. Peter Anvin asked to evaluate this implementation option.
Pros:
- cache friendly (not yet benchmarked);
- less
From: "Kirill A. Shutemov"
We can use the same bit as for special PTE.
There's no conflict with _PAGE_SPLITTING since it's only defined for PSE
pmd, but special PMD is only valid for non-PSE.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/Kconfig |1 +
From: "Kirill A. Shutemov"
Virtual huge zero page is a PMD table with all entries set to zero page.
When we get write-protect page fault to zero page in such PMD we drop
the whole page table and allow THP (if enabled) to allocate a real
memory instead.
The implementation requires
A section with the name "Example" (case-insensitive) has a special
meaning to kernel-doc. These sections are output using mono-type fonts.
However, leading whitespace is stripped, thus robbing a lot of meaning
from this, as indented code examples will be mangled.
This patch preserves the leading
If you have a section named "Example" that contains an empty line,
attempting to generate htmldocs give you the error:
/path/Documentation/DocBook/kernel-api.xml:3455: parser error : Opening and
ending tag mismatch: programlisting line 3449 and para
^
Prior to this patch the following code breaks:
/**
* multiline_example - this breaks kernel-doc
*/
#define multiline_example( \
myparam)
Producing this error:
Error(somefile.h:983): cannot understand prototype: 'multiline_example( \ '
This patch fixes the issue by appending all lines ending
Fixes breakages exposed by doc-comments used in the generic red-black
tree patch set.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
Hi Haojian:
On Fri, Sep 21, 2012 at 06:06:51PM +0800, Haojian Zhuang wrote:
> @@ -593,13 +610,9 @@ static int __devinit device_irq_init(struct pm860x_chip
> *chip,
> : chip->companion;
> unsigned char status_buf[INT_STATUS_NUM];
> unsigned long flags =
On Fri, 2012-09-28 at 13:14 -0700, Greg Kroah-Hartman wrote:
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Linus Torvalds
>
> commit 55815f70147dcfa3ead5738fd56d3574e2e3c1c2 upstream.
>
> We already use them for openat() and
Throughout compiler*.h, many version checks are made. These can be
simplified by using the macro that gcc's documentation recommends.
However, my primary reason for adding this is that I need bug-check
macros that are enabled at certain gcc versions and it's cleaner to use
this macro than the
BUILD_BUG_ON42(arg)
BUILD_BUG_ON_CONST42(arg)
Prior to gcc 4.2, the optimizer was unable to determine that many
constant values stored in structs were indeed compile-time constants and
optimize them out. Sometimes, it will find an intergral value to be a
compile-time constant, but fail to
A very common use of __builtin_constant_p is to make sure that a certain
value is a compile time constant and generate a build-time error if it
is not. However, __builtin_constant_p is broken in a variety of ways in
various situations (on various versions of gcc) and never returns one in
an
Negative sized arrays wont create a compile-time error in some cases
starting with gcc 4.4 (e.g., inlined functions), but gcc 4.3 introduced
the error function attribute that will. This patch modifies
BUILD_BUG_ON to behave like BUILD_BUG already does, using the error
function attribute so that
For gcc 4.1 & later, expands to __attribute__((flatten)) which forces
the compiler to inline everything it can into the function. This is
useful in combination with noinline when you want to control the depth
of inlining, or create a single function where inline expansions will
occur. (see
__linktime_error() does the same thing as __compiletime_error() and is
only used in bug.h. Since the macro defines a function attribute that
will cause a failure at compile-time (not link-time), it makes more
sense to keep __compiletime_error(), which is also neatly mated with
Using GCC_VERSION reduces complexity, is easier to read and is GCC's
recommended mechanism for doing version checks. (Just don't ask me why
they didn't define it in the first place.) This also makes it easy to
merge compiler-gcc{3,4}.h should somebody want to.
Signed-off-by: Daniel Santos
---
This helps to keep the file from getting confusing, removes one
duplicate version check and should encourage future editors to put new
macros where they belong.
Signed-off-by: Daniel Santos
---
include/linux/compiler-gcc4.h | 20 +++-
1 files changed, 11 insertions(+), 9
Some of args were missed in free_args(), as well as subargs.
That is args like FILTER_ARG_NUM have left and right pointers to
other args that also need to be freed.
Signed-off-by: Steven Rostedt
---
tools/lib/traceevent/parse-filter.c | 11 +++
1 files changed, 11 insertions(+), 0
Signed-off-by: Daniel Santos
---
include/linux/bug.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/bug.h b/include/linux/bug.h
index aaac4bb..298a916 100644
--- a/include/linux/bug.h
+++ b/include/linux/bug.h
@@ -73,7 +73,7 @@ extern int
NOTE: this is has already been comitted to -mm
__attribute__((error(msg))) was introduced in gcc 4.3 (not 4.4) and as I
was unable to find any gcc bugs pertaining to it, I'm presuming that it
has functioned as advertised since 4.3.0.
Signed-off-by: Daniel Santos
Cc: Michal Marek
Signed-off-by:
Hi Jangam,
On Fri, Sep 14, 2012 at 06:54:50PM +0530, Ashish Jangam wrote:
> This is the DA9055 MFD core driver that instantiate all the dependent
> component
> drivers and provides them the device access via I2C.
>
> This patch is functionally tested on Samsung SMDK6410.
>
> Signed-off-by:
This patch set is a dependency of the generic red-black tree patch set, which
I have now split up into three smaller sets.
The major aim of this patch set is to cleanup compiler-gcc*.h and improve the
manageability of of compiler features at various versions (when they are
broken, etc.), and to
Joerg,
On Fri, Sep 28, 2012 at 6:24 AM, Joerg Roedel wrote:
> Add the six routines required to setup interrupt remapping
> with the AMD IOMMU. Also put it all together into the AMD
> specific irq_remap_ops.
>
> Signed-off-by: Joerg Roedel
> ---
> drivers/iommu/amd_iommu.c | 16
On Fri, 28 Sep 2012, Christoph Lameter wrote:
> > The first prototype, SLAM XP1, will be posted in October. I'd simply like
> > to avoid reverting this patch down the road and having all of us
> > reconsider the topic again when clear alternatives exist that, in my
> > opinion, make the code
On Fri, Sep 28, 2012 at 6:23 AM, Joerg Roedel wrote:
> To easily map device ids to interrupt remapping table
> entries a new lookup table is necessary.
>
> Signed-off-by: Joerg Roedel
> ---
> drivers/iommu/amd_iommu_init.c | 16
> drivers/iommu/amd_iommu_types.h |9
On Fri, 2012-09-28 at 13:34 -0700, Greg Kroah-Hartman wrote:
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: NeilBrown
>
> commit 6dafab6b1383e912cd252fa809570b484eb6e0dc upstream.
[...]
> This is suitable for -stable as
Hi Haojian,
On Fri, Sep 21, 2012 at 06:06:50PM +0800, Haojian Zhuang wrote:
> Changelog:
> v2:
> 1. Resolve merge conflict since other patches also update 88pm860x-core.c
> 2. Add document of DT support
All 4 patches applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
Hi Venu,
On Fri, Sep 21, 2012 at 04:25:36PM +0530, Venu Byravarasu wrote:
> Add RTC alarm interrupt details to TPS65910 MFD device list, to support
> RTC alarm events.
>
> Signed-off-by: Venu Byravarasu
> ---
> drivers/mfd/tps65910.c | 10 ++
> 1 files changed, 10 insertions(+), 0
> It is not correct. The kobject_put() is prepared against find_memory_block()
> in remove_memory_block() since kobject->kref is incremented in it.
> So release_memory_block() is called by device_unregister() correctly as
> follows:
Ok. Looks good then.
Please rewrite the description more kindly
On Fri, Sep 28, 2012 at 07:19:27PM -0300, Gustavo Padovan wrote:
> * Ben Hutchings [2012-09-29 00:13:03 +0200]:
>
> > On Fri, 2012-09-28 at 13:33 -0700, Greg Kroah-Hartman wrote:
> > > 3.0-stable review patch. If anyone has any objections, please let me
> > > know.
> > >
> > >
On Fri, Sep 28, 2012 at 3:19 AM, Lai Jiangshan wrote:
> HI, Christoph, KOSAKI
>
> SLAB always allocates kmem_list3 for all nodes(N_HIGH_MEMORY), also node
> bug/bad things happens.
> SLUB always requires kmem_cache_node on the correct node, so these fix is
> needed.
>
> SLAB uses
On Thu, Sep 27, 2012 at 11:50 PM, Yasuaki Ishimatsu
wrote:
> Hi Chen,
>
>
> 2012/09/28 11:22, Ni zhan Chen wrote:
>>
>> On 09/05/2012 05:25 PM, we...@cn.fujitsu.com wrote:
>>>
>>> From: Yasuaki Ishimatsu
>>>
>>> remove_memory() only try to offline pages. It is called in two cases:
>>> 1. hot
Hey Dan,
Thanks for the response.
>> Linux cyber-ubuntu 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC
>> 2012 x86_64 x86_64 x86_64 GNU/Linux
> That kernel is too old. Can you test with a 3.5.x kernel (or even
> better would be a 3.6-rc kernel). Those are the only ones we look
> at
>>> I don't understand it. How can we get rid of the warning?
>>
>> See cpu_device_release() for example.
>
> If we implement a function like cpu_device_release(), the warning
> disappears. But the comment says in the function "Never copy this way...".
> So I think it is illegal way.
What does
* Ben Hutchings [2012-09-29 00:13:03 +0200]:
> On Fri, 2012-09-28 at 13:33 -0700, Greg Kroah-Hartman wrote:
> > 3.0-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Vinicius Costa Gomes
> >
> > commit
1 - 100 of 2396 matches
Mail list logo
