On Sun, 2 Feb 2014 01:28:07 AM Filipe David Manana wrote:
One of the kbuild test robots reported this a few days ago too.
The following patch, sent shortly after the robot's warning, fixes it:
https://patchwork.kernel.org/patch/3554671/
I can confirm that fixes the bug for me (with a
* Arnaldo Carvalho de Melo a...@infradead.org wrote:
From: Arnaldo Carvalho de Melo a...@ghostprotocols.net
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 0d4dd797564cddc1f71ab0b239e9ea50ddd40b2a:
perf/doc: Remove mention of non-existent
Commit-ID: 29b596b57426831fce92cd0ebb01c77627616fdf
Gitweb: http://git.kernel.org/tip/29b596b57426831fce92cd0ebb01c77627616fdf
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:37 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: 950b8354716eb1f9c0b39777d379efa5f4125c04
Gitweb: http://git.kernel.org/tip/950b8354716eb1f9c0b39777d379efa5f4125c04
Author: Avi Kivity a...@cloudius-systems.com
AuthorDate: Wed, 22 Jan 2014 21:58:46 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Mon, 27
Commit-ID: c080f72753def150993144d755379941f8b14683
Gitweb: http://git.kernel.org/tip/c080f72753def150993144d755379941f8b14683
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:42 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: 15a0a8706c32bd38bff9ebf7c6ef24f32d1ea921
Gitweb: http://git.kernel.org/tip/15a0a8706c32bd38bff9ebf7c6ef24f32d1ea921
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:38 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: 5512cf24bed2de56f1ef44b6cc9a0a9b15499cea
Gitweb: http://git.kernel.org/tip/5512cf24bed2de56f1ef44b6cc9a0a9b15499cea
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:39 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: a00d28cb72d3629c6481fe21ba6c6b4f96caed49
Gitweb: http://git.kernel.org/tip/a00d28cb72d3629c6481fe21ba6c6b4f96caed49
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:41 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: 0ae617bedde062003fd70e566e9a2601e273ea0e
Gitweb: http://git.kernel.org/tip/0ae617bedde062003fd70e566e9a2601e273ea0e
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:40 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: d3b70220292c40d3b499797fd2f33f608fc35edb
Gitweb: http://git.kernel.org/tip/d3b70220292c40d3b499797fd2f33f608fc35edb
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:44 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: d9b62aba87a82939c73f451a166c7a21342350d6
Gitweb: http://git.kernel.org/tip/d9b62aba87a82939c73f451a166c7a21342350d6
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:43 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: f428ebd184c82a7914b2aa7e9f868918aaf7ea78
Gitweb: http://git.kernel.org/tip/f428ebd184c82a7914b2aa7e9f868918aaf7ea78
Author: Peter Zijlstra pet...@infradead.org
AuthorDate: Fri, 24 Jan 2014 16:40:02 +0100
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Wed, 29
Commit-ID: 9176753d1ed56951a6ee2a0f0a3f367904e35567
Gitweb: http://git.kernel.org/tip/9176753d1ed56951a6ee2a0f0a3f367904e35567
Author: Adrian Hunter adrian.hun...@intel.com
AuthorDate: Wed, 29 Jan 2014 16:14:36 +0200
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31
Commit-ID: 6a02652df511029127406cf8fa89cdf5e987f963
Gitweb: http://git.kernel.org/tip/6a02652df511029127406cf8fa89cdf5e987f963
Author: Francesco Fusco ffu...@redhat.com
AuthorDate: Mon, 27 Jan 2014 14:39:13 +0100
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Fri, 31 Jan
* Waiman Long waiman.l...@hp.com wrote:
How about making the selection of MCS or ticket queuing either user
configurable or depending on the setting of NR_CPUS, NUMA, etc?
No!
There are lots of disadvantages to adding such CONFIG_NUMA Kconfig
variants for locking primitives:
- an
On Sat, 1 Feb 2014, Linus Torvalds wrote:
We could do that with the whole task_work thing (or perhaps just
do_notify_resume(), especially after merging the don't necessarily
return with iret patch I sent out earlier), with additionally making
sure that scheduling does the right thing wrt a
Hi Linus,
Please pull the latest SLAB tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git slab/next
It contains random bug fixes that have accumulated in my inbox over
the past few months.
Pekka
--
The following changes since
Thanks, Greg to your bot for the hint,
gmail seems to screw up tabs for spaces. Good to know, learning by doing..
Lets give it another try:
finally I prepared a patch for the famous ftdi_sio usb serial driver.
Adding two Tagsys RFID readers I am using.
After having asked Bill Ryder he suggested
On Sun, Feb 02, 2014 at 10:22:16AM +0100, Ulrich Hahn wrote:
Thanks, Greg to your bot for the hint,
gmail seems to screw up tabs for spaces. Good to know, learning by doing..
Lets give it another try:
finally I prepared a patch for the famous ftdi_sio usb serial driver.
Adding two Tagsys
On Sun, Feb 2, 2014 at 3:35 PM, Ilia Mirkin imir...@alum.mit.edu wrote:
Some very trivial comments below:
On Fri, Jan 31, 2014 at 10:16 PM, Alexandre Courbot acour...@nvidia.com
wrote:
Add support for initializing the priv ring of GK20A. This is done by the
BIOS on desktop GPUs, but needs
On 31/01/14 16:08 +0100, Alexander Gordeev wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
+config MMAP_ALLOW_UNINITIALIZED
+ bool Allow mmapped anonymous memory to be uninitialized
+ depends on EXPERT !MMU
+ default n
+ help
+ Normally, and according to the Linux spec, anonymous memory obtained
+ from mmap() has it's contents cleared before it is
On 23/01/14 23:34, Stefano Stabellini wrote:
On Thu, 23 Jan 2014, Zoltan Kiss wrote:
The grant mapping API does m2p_override unnecessarily: only gntdev needs it,
for blkback and future netback patches it just cause a lock contention, as
those pages never go to userspace. Therefore this
Commit b1a1442a2 (HID: core: fix reporting of raw events) introduced a
regression that causes lockups for bluetooth trackpads.
This was already discussed in this thread in September:
http://www.kernelhub.org/?p=2msg=329823
but it seems nothing has been fixed so far, I still get the lockups
in
Signed-off-by: Ulrich Hahn uh...@eanco.de
diff -ur linux-3.13.1/drivers/usb/serial/ftdi_sio.c
linux-3.13.1+tagsys/drivers/usb/serial/ftdi_sio.c
--- linux-3.13.1/drivers/usb/serial/ftdi_sio.c 2014-01-29 14:06:37.0
+0100
+++ linux-3.13.1+tagsys/drivers/usb/serial/ftdi_sio.c 2014-02-02
* Richard Weinberger richard.weinber...@gmail.com:
On Sat, Feb 1, 2014 at 9:23 PM, Helge Deller del...@gmx.de wrote:
please pull the latest updates for the parisc architecture from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-for-3.14
The three
-#define VDSO_HIGH_BASE 0xe000U /* CONFIG_COMPAT_VDSO address
*/
+#define VDSO_HIGH_BASE 0xc000U /* CONFIG_COMPAT_VDSO address
*/
This is odd. Can you explain it?
He needs 3 pages instead of 1 after his changes.
Not every kernel hackers a male.
From: Stefani Seibold stef...@seibold.net
This patch do a little cleanup for the __vdso_gettimeofday() function.
It kick out an unneeded ret local variable and makes the code faster if
only the timezone is needed.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
From: Stefani Seibold stef...@seibold.net
This patch add the time support for 32 bit a VDSO to a 32 bit kernel.
For 32 bit programs running on a 32 bit kernel, the same mechanism is
used as for 64 bit programs running on a 64 bit kernel.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
From: Stefani Seibold stef...@seibold.net
This patch add the VDSO time support for the IA32 Emulation Layer.
Due the nature of the kernel headers and the LP64 compiler where the
size of a long and a pointer differs against a 32 bit compiler, there
is a lot of type hacking necessary.
From: Stefani Seibold stef...@seibold.net
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new vsyscall_32.c which setup the VVAR page.
Signed-off-by: Stefani
From: Stefani Seibold stef...@seibold.net
There a currently more than 30 users of the gtod macro, so replace the
last VVAR(vsyscall_gtod_data) by gtod macro.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/vdso/vclock_gettime.c | 6 +++---
1 file changed, 3 insertions(+), 3
From: Stefani Seibold stef...@seibold.net
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
From: Stefani Seibold stef...@seibold.net
This intermediate patch revamps the vclock_gettime.c by moving some functions
around. It is only for spliting purpose, to make whole the 32 bit vdso timer
patch easier to review.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
From: Stefani Seibold stef...@seibold.net
The _install_special_mapping() is the new base function for
install_special_mapping(). This function will return a pointer of the
created VMA or a error code in an ERR_PTR()
This new function will be needed by the for the vdso 32 bit support to map the
From: Stefani Seibold stef...@seibold.net
This patch is a small code cleanup for the __vdso_clock_gettime() function.
It removes the unneeded return values from do_monotonic_coarse() and
do_realtime_coarse() and add a fallback label for doing the kernel
gettimeofday() system call.
On Sat, Feb 01, 2014 at 01:03:28AM +, Russell King - ARM Linux wrote:
On Fri, Jan 31, 2014 at 03:59:30PM -0500, Trond Myklebust wrote:
On Thu, 2014-01-30 at 15:38 +, Russell King - ARM Linux wrote:
On Thu, Jan 30, 2014 at 06:32:08AM -0800, Christoph Hellwig wrote:
On Thu, Jan 30,
On Fri, Jan 31, 2014 at 11:23 +0100, Maxime Ripard wrote:
Make the existing users of devm_spi_register_master use the
devm_spi_alloc_master function to avoid leaking memory.
[ ... ]
drivers/spi/spi-mpc512x-psc.c| 19 ---
Note that the context for the MPC512x SPI driver
On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
This patch set contains various extensions to the tda998x driver:
- simplify the i2c read/write
- code cleanup and fix some small errors
- use global constants
- don't read write-only registers
- add DT support
- use IRQ
On Sun, Feb 02, 2014 at 12:10:56PM +0100, Ulrich Hahn wrote:
Please use a more descriptive subject line (which will end up as the
commit log summary), e.g.
[PATCH v3] USB: ftdi_sio: add Tagsys RFID Reader ids
Note that the patch version should go in the [PATCH vX] (which will not
show
Adding two more IDs to the ftdi_sio usb serial driver.
It now connects Tagsys RFID readers.
There might be more IDs out there for other Tagsys models.
Signed-off-by: Ulrich Hahn uh...@eanco.de
diff -urpN linux-3.13.1/drivers/usb/serial/ftdi_sio.c
On Sun, Feb 2, 2014 at 8:58 AM, Lucas Stach d...@lynxeye.de wrote:
Am Samstag, den 01.02.2014, 18:28 -0500 schrieb Ilia Mirkin:
On Sat, Feb 1, 2014 at 8:40 AM, Lucas Stach d...@lynxeye.de wrote:
Am Samstag, den 01.02.2014, 12:16 +0900 schrieb Alexandre Courbot:
Add a clumsy-but-working FB
Andy Lutomirski l...@amacapital.net writes:
On a stock Fedora installation:
$ sudo auditctl -l
No rules
I noticed the same recently on a recent opensuse. kauditd is running,
even though I uninstalled all audit related userland long before. I'm sure
the evil make syscalls slow flag is set
On Sun, Feb 02, 2014 at 02:41:34PM +0900, Namjae Jeon wrote:
The semantics of this flag are following:
1) It collapses the range lying between offset and length by removing any data
blocks which are present in this range and than updates all the logical
offsets of extents beyond offset +
On Sun, Feb 02, 2014 at 08:16:24AM -0700, Matthew Wilcox wrote:
On Sun, Feb 02, 2014 at 02:41:34PM +0900, Namjae Jeon wrote:
The semantics of this flag are following:
1) It collapses the range lying between offset and length by removing any
data
blocks which are present in this range
Sorry, I did not know/realize, and unfortunately he is the grammatical
default in English, although the singular they is fortunately making a comeback.
I stand corrected, through. Please acer my apologies.
-hpa
On February 2, 2014 3:20:25 AM PST, Stefani Seibold stef...@seibold.net wrote:
Even reading the timezone via gettimeofday is the uncommon case... never mind
only the timezome. Whatever you do please don't slow down the common case.
On February 2, 2014 3:27:13 AM PST, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
This patch do a little cleanup for
On Sun, 2014-02-02 at 07:43 -0800, H. Peter Anvin wrote:
Even reading the timezone via gettimeofday is the uncommon case... never mind
only the timezome. Whatever you do please don't slow down the common case.
On February 2, 2014 3:27:13 AM PST, stef...@seibold.net wrote:
From: Stefani
Hi Frederic,
On 01/31/2014 10:00 PM, Frederic Weisbecker wrote:
On Wed, Jan 29, 2014 at 10:57:59AM +0530, Preeti Murthy wrote:
Hi,
On Thu, Jan 23, 2014 at 11:22 AM, Viresh Kumar viresh.ku...@linaro.org
wrote:
Hi Guys,
So the first question is why cpufreq needs it and is it really
On Sun, Feb 02, 2014 at 03:41:27AM -0800, scan-ad...@coverity.com wrote:
Please find the latest report on new defect(s) introduced to Linux found
with Coverity Scan.
Defect(s) Reported-by: Coverity Scan
Showing 20 of 83 defect(s)
Ugh, this is even worse than the usual realtek
On Sat, 1 Feb 2014, Zoran Markovic wrote:
From: Shaibal Dutta shaibal.du...@broadcom.com
Allow the scheduler to select the best CPU to handle hub initalization
and LED blinking work. This extends idle residency times on idle CPUs
and conserves power.
This functionality is enabled when
On Sat, Jan 25, 2014 at 06:14:45PM +0100, Jean-Francois Moine wrote:
This patch adds more error checking inn I2C I/O functions.
In case of I/O error, this permits to avoid writing in bad controller
pages, a bad chipset detection or looping when getting the EDID.
I've just looked at this again,
On Sat, Jan 25, 2014 at 06:14:42PM +0100, Jean-Francois Moine wrote:
This patch takes care of the write-only registers of the tda998x.
The registers SOFTRESET, TBG_CNTRL_0 and TBG_CNTRL_1 have all bits
cleared after reset, so, they may be fully re-written.
The register MAT_CONTRL is set to
Suppose we are creating memcg cache A that could be merged with cache B
of the same memcg. Since any memcg cache has the same parameters as its
parent cache, parent caches PA and PB of memcg caches A and B must be
mergeable too. That means PA was merged with PB on creation or vice
versa, i.e. PA =
The cgroup name is not informative at all in case the cgroup hierarchy
is not flat. Besides, we can always find the memcg a particular cache
belongs to by its kmemcg id, which is now exported via memory.kmem.id
cgroup fs file for each memcg.
So let's remove the cgroup name part from kmem caches
Otherwise, kzalloc() called from a memcg won't clear the whole object.
Signed-off-by: Vladimir Davydov vdavy...@parallels.com
---
mm/slub.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/mm/slub.c b/mm/slub.c
index 962abfdfde06..a33d88afb61d 100644
--- a/mm/slub.c
+++
Currently, we try to arrange sysfs entries for memcg caches in the same
manner as for global caches. Apart from turning /sys/kernel/slab into a
mess when there are a lot of kmem-active memcgs created, it actually
does not work properly - we won't create more than one link to a memcg
cache in case
Memcg-awareness turned kmem_cache_create() into a dirty interweaving of
memcg-only and except-for-memcg calls. To clean this up, let's create a
separate function handling memcg caches creation. Although this will
result in the two functions having several hunks of practically the same
code, I
Per-memcg kmem caches are named as follows:
global-cache-name(cgroup-kmem-id:cgroup-name)
where cgroup-kmem-id is the unique id of the memcg the cache belongs
to, cgroup-name is the relative name of the memcg on the cgroup fs.
Cache names are exposed to userspace for debugging purposes (e.g.
Currently, memcg_unregister_cache(), which deletes the cache being
destroyed from the memcg_slab_caches list, is called after
__kmem_cache_shutdown() (see kmem_cache_destroy()), which starts to
destroy the cache. As a result, one can access a partially destroyed
cache while traversing a
Hi,
This patch set mostly cleanups memcg slab caches creation/destruction
paths fixing a couple of bugs in the meanwhile. However, it does
introduce some functional changes. First, it changes the memcg caches
naming convention (see patch 2). Second, it reworks sysfs layout for
memcg slub caches
Currently we destroy children caches at the very beginning of
kmem_cache_destroy(). This is wrong, because the root cache will not
necessarily be destroyed in the end - if it has aliases (refcount 0),
kmem_cache_destroy() will simply decrement its refcount and return. In
this case, at best we
On Sun, Feb 2, 2014 at 3:27 AM, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
This patch do a little cleanup for the __vdso_gettimeofday() function.
It kick out an unneeded ret local variable and makes the code faster if
only the timezone is needed.
Signed-off-by:
On Sun, Feb 2, 2014 at 3:27 AM, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
This patch is a small code cleanup for the __vdso_clock_gettime() function.
It removes the unneeded return values from do_monotonic_coarse() and
do_realtime_coarse() and add a fallback label
On Sun, Feb 2, 2014 at 3:27 AM, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
This intermediate patch revamps the vclock_gettime.c by moving some functions
around. It is only for spliting purpose, to make whole the 32 bit vdso timer
patch easier to review.
On Sun, Feb 2, 2014 at 3:27 AM, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
There a currently more than 30 users of the gtod macro, so replace the
last VVAR(vsyscall_gtod_data) by gtod macro.
Acked-by: Andy Lutomirski l...@amacapital.net
Signed-off-by: Stefani
On Sun, Feb 2, 2014 at 3:27 AM, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
This patch add the time support for 32 bit a VDSO to a 32 bit kernel.
[...]
Can you address the review comments from last time around? For
example, this still seems to have redundant vvar
On Sunday, February 02, 2014 01:54:02 AM Rafael J. Wysocki wrote:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
There is a slight possibility for the ACPI device object pointed to
by adev in acpi_hotplug_notify_cb() to become invalid between the
acpi_bus_get_device() that it comes from
On Sat, Feb 1, 2014 at 10:51 PM, Oleg Nesterov o...@redhat.com wrote:
On 02/01, Rakib Mullick wrote:
On Thu, Jan 30, 2014 at 1:02 PM, Rakib Mullick rakib.mull...@gmail.com
wrote:
On Thu, Jan 30, 2014 at 12:32 AM, Oleg Nesterov o...@redhat.com wrote:
On 01/29, Rakib Mullick wrote:
Are
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The ACPI-based PCI hotplug (ACPIPHP) code currently attaches its
hotplug context objects directly to ACPI namespace nodes representing
hotplug devices. However, after recent changes causing struct
acpi_device to be created for every namespace
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since acpi_bus_notify() is executed on all notifications for all
devices anyway, make it execute acpi_device_hotplug() for all
hotplug events instead of installing notify handlers pointing to
the same function for all hotplug devices.
This
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Subsequent changes will require the ACPI core to acquire the lock
protecting the ACPIPHP hotplug contexts, so move the definition of
the lock to the core and change its name to be more generic.
Signed-off-by: Rafael J. Wysocki
On Sunday, February 02, 2014 01:52:26 AM Rafael J. Wysocki wrote:
On Wednesday, January 29, 2014 12:57:06 AM Rafael J. Wysocki wrote:
On Tuesday, January 28, 2014 11:10:30 PM Rafael J. Wysocki wrote:
Hi All,
It looks like there's time for more adventurous stuff. :-)
The
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Introduce a new function, acpi_get_data_full(), working in analogy
with acpi_get_data() except that it can execute a callback provided
as its 4th argument right after acpi_ns_get_attached_data() has
returned a success.
That will allow Linux to
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
To avoid the need to install a hotplug notify handler for each ACPI
namespace node representing a device and having a matching scan
handler, move the check whether or not the ejection of the given
device is enabled through its scan handler from
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since acpi_hotplug_notify_cb() does not use its data argument any
more, the second argument of acpi_install_hotplug_notify_handler()
can be dropped, so do that and update its callers accordingly.
Signed-off-by: Rafael J. Wysocki
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
There is a slight possibility for the ACPI device object pointed to
by adev in acpi_hotplug_notify_cb() to become invalid between the
acpi_bus_get_device() that it comes from and the subsequent dereference
of that pointer under get_device().
The name `max_pass' is misleading, because this variable actually keeps
the estimate number of freeable objects, not the maximal number of
objects we can scan in this pass, which can be twice that. Rename it to
reflect its actual meaning.
Signed-off-by: Vladimir Davydov vdavy...@parallels.com
---
On Sun, 2 Feb 2014 16:20:58 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Sat, Jan 25, 2014 at 06:14:45PM +0100, Jean-Francois Moine wrote:
This patch adds more error checking inn I2C I/O functions.
In case of I/O error, this permits to avoid writing in bad controller
On Sun, 2 Feb 2014 16:23:09 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Sat, Jan 25, 2014 at 06:14:42PM +0100, Jean-Francois Moine wrote:
This patch takes care of the write-only registers of the tda998x.
The registers SOFTRESET, TBG_CNTRL_0 and TBG_CNTRL_1 have all
On Sun, Feb 02, 2014 at 06:30:00PM +0100, Jean-Francois Moine wrote:
On Sun, 2 Feb 2014 16:20:58 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Sat, Jan 25, 2014 at 06:14:45PM +0100, Jean-Francois Moine wrote:
This patch adds more error checking inn I2C I/O functions.
On Sun, Feb 02, 2014 at 06:45:12PM +0100, Jean-Francois Moine wrote:
On Sun, 2 Feb 2014 16:23:09 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Sat, Jan 25, 2014 at 06:14:42PM +0100, Jean-Francois Moine wrote:
This patch takes care of the write-only registers of the
On Sun, Feb 02, 2014 at 11:05:12AM -0500, Dave Jones wrote:
On Sun, Feb 02, 2014 at 03:41:27AM -0800, scan-ad...@coverity.com wrote:
Please find the latest report on new defect(s) introduced to Linux found
with Coverity Scan.
Defect(s) Reported-by: Coverity Scan
Showing 20 of
On Sun, Feb 02, 2014 at 12:43:58PM +, Russell King - ARM Linux wrote:
On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
This patch set contains various extensions to the tda998x driver:
- simplify the i2c read/write
- code cleanup and fix some small errors
- use
On Sun, 2 Feb 2014 12:43:58 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
This patch set contains various extensions to the tda998x driver:
- simplify the i2c read/write
- code cleanup and fix some small
On Sun, 2014-02-02 at 01:04 -0600, Rob Landley wrote:
Back before kernel.org did its epic barn door locking after the horses
escaped, I used to use them to generate HTML indexes for
kernel.org/doc/Documentation, but sometime after they took away my
ability to rsync updates to that they
As you read this letter, please don't feel bad, because I believe
everyone will die some day. My name is Mrs. Tan Ruby I have been
suffering from ovarian cancer Disease and the doctor says that I have
just few days to live on earth. I am From Singapore, but based in
Burkina Faso, Africa since for
Hi
[ CC'ing the relevant parties ]
On Sunday 02 February 2014, Dave Jones wrote:
On Sun, Feb 02, 2014 at 03:41:27AM -0800, scan-ad...@coverity.com wrote:
Please find the latest report on new defect(s) introduced to Linux found
with Coverity Scan.
Defect(s) Reported-by: Coverity
On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
On Sun, 2 Feb 2014 12:43:58 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
This patch set contains various extensions to the tda998x
On 02/02/2014 07:23 PM, Russell King - ARM Linux wrote:
On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
- on encoder_destroy(), the function drm_i2c_encoder_destroy()
unregisters the i2c client, so, with a DT, a second encoder_init()
would crash.
I think this is one
On Sun, 2 Feb 2014 18:23:49 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
On Sun, 2 Feb 2014 12:43:58 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
On Wed, Jan 29, 2014 at 10:01:22AM
On 02/02/14 11:29, Julien Grall wrote:
Hello,
This patch is breaking Linux compilation on ARM:
drivers/xen/grant-table.c: In function ‘__gnttab_map_refs’:
drivers/xen/grant-table.c:989:3: error: implicit declaration of function
‘FOREIGN_FRAME’ [-Werror=implicit-function-declaration]
if
On Sun, 2 Feb 2014 18:04:34 +
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
So, in summary, I'm pretty happy with this again - and it's all been
tested here with no apparant detrimental effects. All committed and
queued up here:
On Sat, Feb 1, 2014 at 7:03 PM, H. Peter Anvin h...@linux.intel.com wrote:
Clean it up by favoring the full-service version; the limited version
is replaced with double-underscore versions static to kernel/compat.c.
Ack. Make it so. I assume you've tested this on x32 (and hopefully
x86-32 on a
Hi Alexandre,
On Fri, Jan 31, 2014 at 10:16 PM, Alexandre Courbot acour...@nvidia.com wrote:
I guess my email address might surprise some of you, so let me anticipate some
questions you might have. :P Yes, this work is endorsed by NVIDIA. Several
other
NVIDIAns (CC'd), including core GPU
On Sun, Feb 02, 2014 at 07:54:00PM +0100, Jean-Francois Moine wrote:
I explained how to use the tda998x in a DT context in a message to Jyri
Sarha:
http://lists.freedesktop.org/archives/dri-devel/2014-January/052936.html
Okay, so there's a bunch of changes required to the DRM slave support
On Sat, Feb 1, 2014 at 11:19 PM, Suresh Siddha sbsid...@gmail.com wrote:
The real fix for Nate's problem will be coming from Linus, with a
slightly modified option-b that Linus proposed. Linus, please let me
know if you want me to spin it. I can do it sunday night.
Please do it, since clearly
On Sun, Feb 2, 2014 at 3:15 AM, Helge Deller del...@gmx.de wrote:
Anyway, the suggested untested patch below should fix the metag arch
to cope which my changes to fs/exec.c
...
-#define STACK_RND_MASK (0)
+#define STACK_RND_MASK (-1)
I don't think that works. That completely breaks
On Sun, 2014-02-02 at 18:07 +, Stefan Lippers-Hollmann wrote:
Hi
[ CC'ing the relevant parties ]
On Sunday 02 February 2014, Dave Jones wrote:
On Sun, Feb 02, 2014 at 03:41:27AM -0800, scan-ad...@coverity.com wrote:
Please find the latest report on new defect(s) introduced to
On Fri, Jan 31, 2014 at 03:09:41PM +0100, Peter Zijlstra wrote:
+struct m_spinlock {
+ struct m_spinlock *next, *prev;
+ int locked; /* 1 if lock acquired */
+};
+
+/*
+ * Using a single mcs node per CPU is safe because mutex_lock() should not be
+ * called from interrupt context
1 - 100 of 478 matches
Mail list logo
