On Mon, Nov 24, 2014 at 06:12:33PM +0100, Alban Bedel wrote:
> Using this driver the DTS for the add-on board can further constrain
> this supply to get the voltage it need, for example 3.3V. I understand
> I saw 3 ways to solve this problem:
> 1) This, use a "filter" regulator
> 2) Extend each
On 11/20/2014 01:58 PM, Shuah Khan wrote:
> On 11/19/2014 05:13 PM, Tim Bird wrote:
>>
>> This test shows the amount of memory used by the system.
>> Note that this is dependent on the user-space that is loaded
>> when this program runs. Optimally, this program would be
>> run as the init program
virt_to_obj takes kmem_cache address, address of slab page,
address x pointing somewhere inside slab object,
and returns address of the begging of object.
Signed-off-by: Andrey Ryabinin
---
include/linux/slub_def.h | 5 +
1 file changed, 5 insertions(+)
diff --git
Hi,
On 24/11/14 10:10, Eric Auger wrote:
> On 11/24/2014 10:47 AM, Christoffer Dall wrote:
>> On Sun, Nov 23, 2014 at 06:56:57PM +0100, Eric Auger wrote:
>>> This patch series enables irqfd on arm and arm64.
>>>
>>> Irqfd framework enables to inject a virtual IRQ into a guest upon an
>>> eventfd
This patch adds arch specific code for kernel address sanitizer.
16TB of virtual addressed used for shadow memory.
It's located in range [0xd900 - 0xe900]
which belongs to vmalloc area.
At early stage we map whole shadow region with zero page.
Latter, after pages mapped
This is a test module doing various nasty things like
out of bounds accesses, use after free. It is useful for testing
kernel debugging features like kernel address sanitizer.
It mostly concentrates on testing of slab allocator, but we
might want to add more different stuff here in future (like
Add kernel address sanitizer hooks to mark allocated page's addresses
as accessible in corresponding shadow region.
Mark freed pages as inaccessible.
Signed-off-by: Andrey Ryabinin
---
include/linux/kasan.h | 6 ++
mm/compaction.c | 2 ++
mm/kasan/kasan.c | 14 ++
kmalloc internally round up allocation size, and kmemleak
uses rounded up size as object's size. This makes kasan
to complain while kmemleak scans memory or calculates of object's
checksum. The simplest solution here is to disable kasan.
Signed-off-by: Andrey Ryabinin
---
mm/kmemleak.c | 6
Kernel Address sanitizer (KASan) is a dynamic memory error detector. It provides
fast and comprehensive solution for finding use-after-free and out-of-bounds
bugs.
KASAN uses compile-time instrumentation for checking every memory access,
therefore GCC >= v4.9.2 required.
This patch only adds
Recently instrumentation of builtin functions calls was removed from GCC 5.0.
To check the memory accessed by such functions, userspace asan always uses
interceptors for them.
So now we should do this as well. This patch declares memset/memmove/memcpy
as weak symbols. In mm/kasan/kasan.c we have
With this patch kasan will be able to catch bugs in memory allocated
by slub.
Initially all objects in newly allocated slab page, marked as free.
Later, when allocation of slub object happens, requested by caller
number of bytes marked as accessible, and the rest of the object
(including slub's
Remove static and add function declarations to mm/slab.h so they
could be used by kernel address sanitizer.
Signed-off-by: Andrey Ryabinin
---
include/linux/slub_def.h | 5 +
mm/slub.c| 4 ++--
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git
Hello Lukasz,
On Mon, Nov 24, 2014 at 11:38:54AM +0100, Lukasz Majewski wrote:
> Hi Eduardo,
>
> >
> > Lukasz,
> >
> > On Tue, Nov 18, 2014 at 11:16:30AM +0100, Lukasz Majewski wrote:
> > > The return code from ->get_max_state() callback was not checked
> > > during binding cooling device to
Wrap access to object's metadata in external functions with
metadata_access_enable()/metadata_access_disable() function calls.
This hooks separates payload accesses from metadata accesses
which might be useful for different checkers (e.g. KASan).
Signed-off-by: Andrey Ryabinin
---
mm/slub.c |
We need to manually unpoison rounded up allocation size for dname
to avoid kasan's reports in dentry_string_cmp().
When CONFIG_DCACHE_WORD_ACCESS=y dentry_string_cmp may access
few bytes beyound requested in kmalloc() size.
dentry_string_cmp() relates on that fact that dentry allocated
using
On Mon, Nov 24, 2014 at 5:30 AM, David Howells wrote:
> Christian Borntraeger wrote:
>
>> +#define get_scalar_volatile_pointer(x) ({ \
>> + typeof(x) *__p = &(x); \
>> + volatile typeof(x) *__vp = __p; \
>> + (void)(long)*__p; __vp; })
>> +#define ACCESS_ONCE(x)
KASan is a runtime memory debugger designed to find use-after-free
and out-of-bounds bugs.
Currently KASAN supported only for x86_64 architecture and requires kernel
to be build with SLUB allocator.
KASAN uses compile-time instrumentation for checking every memory access,
therefore you
will need
On Mon, Nov 24, 2014 at 12:39 PM, David Sterba wrote:
Hi Chris,
I thought the fix for the scrub/replace deadlock would be included in
this pull, I can reproduce it on each run of xfstests with 3.18-rc.
btrfs: fix dead lock while running replace and defrag concurrently
On Mon, Nov 24, 2014 at 06:32:04PM +0100, Alban Bedel wrote:
> Honestly my primary aim wasn't the sequencing, but rather to increase
> the usefulness of generic drivers. Generic driver generally only
> manipulate a single supply, however many hardware might have more,
> and won't need any
On Sat, Nov 22, 2014 at 8:55 AM, Borislav Petkov wrote:
> On Fri, Nov 21, 2014 at 01:26:07PM -0800, Andy Lutomirski wrote:
>> x86 call do_notify_resume on paranoid returns if TIF_UPROBE is set
>> but not on non-paranoid returns. I suspect that this is a mistake
>> and that the code only works
On 24/11/2014 16:28, Nadav Amit wrote:
>
> Since kvm_load_guest_fpu is called before the guest_fpu is ever stored, there
> are 2 more problems that currently cause #GP:
> 1. XCOMP_BV[63] = 0
> 2. XSTATE_BV sets a bit (including bit 63) that is not set in XCOMP_BV
> (XCOMP_BV is initialised to
On Thu, 20 Nov 2014 06:56:53 -0700
Shuah Khan wrote:
> Thanks for doing this. Looks good to me. I think you missed
> Documentation maintainer. Adding linux-doc and Jon Corbet to
> the thread with my ack to take this through Documentation tree.
Thanks for the heads-up. I've applied it to the
On 11/18/2014 10:17 PM, Felipe Balbi wrote:
> I think the driver is mis-detecting Babble. A babble only occurs when
> the device side tries to move data without the host asking for anything.
It also occurs if the device moves more than packet_size bytes. Not
really helping, I know…
Sebastian
--
On 11/18/2014 10:17 PM, Felipe Balbi wrote:
> while this helps the situation it doesn't solve the problem I'm having
> with testusb on BBB when host port is connected to peripheral port on
> the same BBB.
Exactly. On the same device. I see the same problem if I connect host
to peripheral port on
On Tue, 25 Nov 2014 01:39:19 +0900
SeongJae Park wrote:
> 6) Attach that task to the new cgroup by writing its PID to the
> -/sys/fs/cgroup/cpuset/tasks file for that cgroup.
> +/sys/fs/cgroup/cpuset tasks file for that cgroup.
That one looks like it was correct before the change...?
Hi Linus,
Please pull hwmon fixes for Linux 3.18-rc7 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v3.18-rc7
Thanks,
Guenter
--
The following changes since commit fc14f9c1272f62c3e8d01300f52467c0d9af50f9:
Linux 3.18-rc5
2014-11-24 20:17 GMT+03:00 Christoph Lameter :
> On Mon, 24 Nov 2014, Min-Hua Chen wrote:
>
>> In check_slab, s->name is passed incorrectly to the error
>> messages. It will cause confusing error messages if the object
>> check fails. This patch fix this bug by removing s->name.
>
> I have seen a
Hi Chris,
I thought the fix for the scrub/replace deadlock would be included in
this pull, I can reproduce it on each run of xfstests with 3.18-rc.
btrfs: fix dead lock while running replace and defrag concurrently
https://patchwork.kernel.org/patch/5264531/
I've retested it again including
On Sat, Nov 15, 2014 at 09:10:44PM -0200, Henrique de Moraes Holschuh wrote:
> And since I have learned my lesson, I took your comment to mean "look
> deeper". I took the time to both try to understand somewhat the mm/ code
> AND write a kernel module to do empiric testing before I wrote this
Hi Eric,
Thanks for your reply
You are right, it seems a bug in the NIOS2 architecture port.
I will check how local_irq_disable()/local_irq_enable() is implemented
on this kind of architecture.
Regards,
Angelo
Il 24/11/2014 16:33, Eric Dumazet ha scritto:
On Mon, 2014-11-24 at 14:29 +0100,
On Mon, Nov 24, 2014 at 02:04:15PM +, Vincent Guittot wrote:
> On 21 November 2014 at 13:34, Morten Rasmussen
> wrote:
> > Should the subject mention that the patch adds utilization tracking?
> > Maybe: 'sched: Add utilization tracking' ?
> >
> >
> > On Mon, Nov 03, 2014 at 04:54:38PM +,
On Mon, 2014-11-24 at 16:58 +, David Howells wrote:
> Mimi Zohar wrote:
>
> Mimi Zohar wrote:
>
> > +if (id) {
> > + lookup = id->data;
> > + len = id->len;
> > + }
> > if (!lookup) {
>
> The last line here can then just be replaced by an else-clause.
I
On Mon, 24 Nov 2014 15:24:33 +
Mark Brown wrote:
> On Mon, Nov 24, 2014 at 02:02:02PM +0100, Alban Bedel wrote:
>
> > +This binding allow creating a group of regulators for use with simple
> > +drivers that only expect a single power supply. Additionally it is
> > +possible to enforce the
From: Markus Elfring
Date: Mon, 24 Nov 2014 17:25:30 +0100
An identifier was corrected in a change log entry because it contained a typo.
Signed-off-by: Markus Elfring
---
Documentation/scsi/ChangeLog.lpfc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, Nov 24, 2014 at 5:30 AM, David Howells wrote:
> Christian Borntraeger wrote:
>
>> +#define get_scalar_volatile_pointer(x) ({ \
>> + typeof(x) *__p = &(x); \
>> + volatile typeof(x) *__vp = __p; \
>> + (void)(long)*__p; __vp; })
>> +#define ACCESS_ONCE(x)
On Mon, Nov 24, 2014 at 02:45:45PM +, Vincent Guittot wrote:
> On 21 November 2014 at 13:37, Morten Rasmussen
> wrote:
> > On Mon, Nov 03, 2014 at 04:54:47PM +, Vincent Guittot wrote:
>
> >>
> >> + /*
> >> + * The dst_cpu is idle and the src_cpu CPU has only 1 CFS task.
> >> +
Hello Krzysztof,
On 11/24/2014 04:18 PM, Krzysztof Kozlowski wrote:
> Hi,
>
>
> This is initial idea to solve dependency between AudioSS clocks
> and main clock controller on Exynos platform.
>
> This solves boot failure of Peach Pi/Pit and Arndale Octa [1].
>
I tested this series on an
From: Markus Elfring
Date: Mon, 24 Nov 2014 15:55:23 +0100
A word was corrected in the description for a parameter of
the mmp_unregister_path() function.
Signed-off-by: Markus Elfring
---
drivers/video/fbdev/mmp/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
usb: phy: Handle per-PHY event for connnect and disconnect events
When usb is connected and enumerated in device mode or when usb is
disconnected,call usb_phy_set_event from phy drivers to handle per-PHY event.
Cc: Felipe Balbi
Cc: Greg Kroah-Hartman
Cc: linux-kernel@vger.kernel.org
Cc:
usb: phy: hold wakeupsource when USB is enumerated in peripheral mode
Some systems require a mechanism to prevent system to enter into suspend
state when USB is connected and enumerated in peripheral mode.
This patch provides an interface to hold a wakeupsource to prevent suspend.
PHY drivers
PHY drivers require a generic interface to handle per-PHY events.
usb_phy_set_event interface sets event to phy event.
PHY drivers call this interface for each phy event.
Cc: Felipe Balbi
Cc: Greg Kroah-Hartman
Cc: linux-kernel@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: Android Kernel
On Mon, 2014-11-24 at 18:08 +0100, Takashi Iwai wrote:
> At Sun, 23 Nov 2014 13:40:51 +0530, Sudip Mukherjee wrote:
[]
> > replaced all references of the debug messages via printk
> > with dev_* macro (mostly dev_dbg).
> > one reference was changed to pr_err as there the card might have been
> >
From: Markus Elfring
Date: Mon, 24 Nov 2014 15:52:00 +0100
Two jump labels were adjusted in the implementation of the
create_node_manager_caches() function because these identifiers
contained typos.
Signed-off-by: Markus Elfring
---
fs/f2fs/node.c | 8
1 file changed, 4
From: Markus Elfring
Date: Mon, 24 Nov 2014 15:50:15 +0100
Two mistyped words were corrected in the description for
the mmp_unregister_path() function.
Signed-off-by: Markus Elfring
---
drivers/video/fbdev/mmp/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Mon, Nov 24, 2014 at 12:34 AM, Jassi Brar wrote:
> On 18 November 2014 at 04:11, Andrew Bresticker wrote:
>
>> +
>> +static int tegra_xusb_mbox_send_data(struct mbox_chan *chan, void *data)
>> +{
>> + struct tegra_xusb_mbox *mbox = to_tegra_mbox(chan->mbox);
>> + struct
Hi,
I'm trying to make some sense of this patch, so questions below:
On Wed, Nov 19, 2014 at 02:21:55PM +, zhichang.y...@linaro.org wrote:
> From: "zhichang.yuan"
>
> This patch make the processing of map_mem more common and support more
> discrete memory layout cases.
>
> In current
Mimi Zohar wrote:
Mimi Zohar wrote:
> +if (id) {
> + lookup = id->data;
> + len = id->len;
> + }
> if (!lookup) {
The last line here can then just be replaced by an else-clause.
David
--
To unsubscribe from this list: send the line "unsubscribe
On Mon, 24 Nov 2014, Min-Hua Chen wrote:
> In check_slab, s->name is passed incorrectly to the error
> messages. It will cause confusing error messages if the object
> check fails. This patch fix this bug by removing s->name.
I have seen a patch like thios before.
Acked-by: Christoph Lameter
From: Markus Elfring
Date: Mon, 24 Nov 2014 15:40:41 +0100
Identifiers were corrected in descriptions for the functions
fc_fcp_pkt_destroy() and fc_fcp_destroy().
Signed-off-by: Markus Elfring
---
drivers/scsi/libfc/fc_fcp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
On Mon, Nov 24, 2014 at 02:41:28PM +, Vincent Guittot wrote:
> On 21 November 2014 at 13:37, Morten Rasmussen
> wrote:
> > On Mon, Nov 03, 2014 at 04:54:45PM +, Vincent Guittot wrote:
>
> [snip]
>
> >> */
> >> if (prefer_sibling && sds->local &&
> >> -
On Mon, 2014-11-24 at 16:13 +, David Howells wrote:
> David Howells wrote:
>
> > > Actually after cleaning the tree and re-signing the modules, I get
> > > following
> > >
> > > Unrecognized character \x7F; marked by <-- HERE after <-- HERE near
> > > column 1 at ./scripts/sign-file line
On Mon, 2014-11-24 at 16:55 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > Don't assume that the issuer & serialNumber are specified.
>
> Bah... I didn't assume, I just did it wrong.
>
> > +#define DEBUG 1
>
> Shouldn't be in the patch.
>
> > +if (id) {
>
> Tab, not spaces.
On Mon, 24 Nov 2014 15:15:27 +
Mark Brown wrote:
> On Mon, Nov 24, 2014 at 02:02:00PM +0100, Alban Bedel wrote:
>
> > +Constrained Supply Regulator
> > +
> > +This binding allow creating a virtual regulator that constrain its
> > +supply to provides the requested voltage. This is to allow
From: Markus Elfring
Date: Mon, 24 Nov 2014 15:35:48 +0100
A word was corrected in the description for
the sci_remote_device_destruct() function.
Signed-off-by: Markus Elfring
---
drivers/scsi/isci/remote_device.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 14/11/14 12:35, Daniel Thompson wrote:
> Hi Thomas, Hi Jason,
>
> [Today I was *planning* to ask if patches 1 & 2 are OK for the irqchip
> tree. However just to be on the safe side I ran some build tests and
> they picked up something I overlooked last time. So instead of a poke
> I've
At Sun, 23 Nov 2014 13:40:51 +0530,
Sudip Mukherjee wrote:
>
> From: Sudip Mukherjee
>
> replaced all references of the debug messages via printk
> with dev_* macro (mostly dev_dbg).
> one reference was changed to pr_err as there the card might have been
> uninitialized.
>
> this patch will
On Mon, Nov 24, 2014 at 11:53:56AM +, David Drysdale wrote:
> Hook up x86-64, i386 and x32 ABIs.
>
> Signed-off-by: David Drysdale
This one has been breaking my linux-next build for the past week. I'm
not sure what's going on. I build with a script:
make allmodconfig
cat << EOF >>
From: Dinh Nguyen
Since we have assigned clk=NULL, which is a valid clk, we should not
be returning when a clock node is not provide. Instead, we should return
only when we cannot enable the clock.
Signed-off-by: Dinh Nguyen
---
drivers/usb/dwc2/gadget.c | 10 +++---
1 file changed, 7
On 24/11/2014 15:26, Eric Auger wrote:
>> > +#ifdef __KVM_HAVE_IOAPIC
>> > +void kvm_vcpu_request_scan_ioapic(struct kvm *kvm);
>> > +#else
>> > +static inline void kvm_vcpu_request-scan_ioapic(struct kvm *kvm)
> Hi Paolo,
>
> you have a typo above: "-" instead of "_".
Indeed, thanks. The
On Mon, Nov 24, 2014 at 02:24:00PM +, Vincent Guittot wrote:
> On 21 November 2014 at 13:35, Morten Rasmussen
> wrote:
> > On Mon, Nov 03, 2014 at 04:54:42PM +, Vincent Guittot wrote:
>
> [snip]
>
> >> The average running time of RT tasks is used to estimate the remaining
> >> compute
From: Markus Elfring
Date: Mon, 24 Nov 2014 17:34:23 +0100
Subject: [PATCH 0/6] Fix a few typos around the word "destroy"
The word "destroy" was mistyped in some files.
Markus Elfring (6):
isci: Fix a typo for the word "destroy"
SCSI-libfc: Fix typos for the word "destroy"
video:
On Fri, Nov 21, 2014 at 8:43 AM, Mahendran Ganesh
wrote:
> In zs_create_pool(), prev_class is assigned (ZS_SIZE_CLASSES - 1)
> times. And the prev_class only references to the previous size_class.
> So we do not need unnecessary assignement.
>
> This patch assigns *prev_class* when a new
Mimi Zohar wrote:
> Don't assume that the issuer & serialNumber are specified.
Bah... I didn't assume, I just did it wrong.
> +#define DEBUG 1
Shouldn't be in the patch.
> +if (id) {
Tab, not spaces.
I'll fix these up and merge your patch into mine to avoid the issues coming
out
On Mon, Nov 24, 2014 at 11:33:18AM +0530, Balavasu kuppusammyprathaban wrote:
> This patch fixes the checkpatch.pl issue
> Error: do not initialise statics to 0 or NULL
>
> Signed-off-by: Balavasu kuppusammyprathaban
> ---
> drivers/staging/lustre/lnet/lnet/router.c | 10 +-
> 1 file
GFP_USER, GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE are escalatedly
confined defined, also implied by their names:
GFP_USER = GFP_USER
GFP_USER + __GFP_HIGHMEM = GFP_HIGHUSER
GFP_USER + __GFP_HIGHMEM + __GFP_MOVABLE = GFP_HIGHUSER_MOVABLE
So just
Userspace is expecting non-compacted format for KVM_GET_XSAVE, but
struct xsave_struct might be using the compacted format. Convert
in order to preserve userspace ABI.
Likewise, userspace is passing non-compacted format for KVM_SET_XSAVE
but the kernel will pass it to XRSTORS, and we need to
The first patch ensures that XSAVES is not exposed in the guest until
we emulate MSR_IA32_XSS. The second exports XSAVE data in the correct
format.
I tested these on a non-XSAVES system so they should not be completely
broken, but I need some help. I am not even sure which XSAVE states
are
This feature is not supported inside KVM guests yet, because we do not emulate
MSR_IA32_XSS. Mask it out.
Cc: Nadav Amit
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/cpuid.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/cpuid.c
Few paths used as example to describe cgroupfs usage have been wrong
from f6e07d38078e ("Documentation: update cgroupfs mount point") by
mistake. This patch fix those trivial wrong paths.
Signed-off-by: SeongJae Park
---
Documentation/cgroups/cgroups.txt | 4 ++--
1 file changed, 2
> On 23 November 2014 at 21:27 Joe Perches wrote:
>
>
> On Sat, 2014-11-22 at 21:56 +0100, Fabian Frederick wrote:
> > This script generates a graph based on errors/warnings/checks detected
> > by checkpatch -f recursively on each files of a directory.
> > Results are grouped by subfolders and
From: Arnaldo Carvalho de Melo
New function to compare the build_ids between different DSOs
Signed-off-by: Arnaldo Carvalho de Melo
Signed-off-by: Kan Liang
---
tools/perf/util/dso.c | 33 +
tools/perf/util/dso.h | 3 +++
2 files changed, 36 insertions(+)
From: Kan Liang
symoff can support both same binaries and different binaries. However,
the offset may be changed for different binaries. This patch checks the
buildid of perf.data. If they are from different binaries, print a
warning to notify the user.
Signed-off-by: Kan Liang
---
Hi,
On Mon, Nov 24, 2014 at 09:45:35PM +0530, Sumit Semwal wrote:
> On 24 November 2014 at 21:24, Felipe Balbi wrote:
> > On Mon, Nov 24, 2014 at 09:19:09PM +0530, Sumit Semwal wrote:
> >> Hi Felipe,
> >>
> >> On 24 November 2014 at 20:08, Felipe Balbi wrote:
> >> > Hi,
> >> >
> >> > On Fri,
On 11/24/2014 07:11 AM, Masami Hiramatsu wrote:
> (CC'ed Shuah, since this is related to kselftest)
>
>
> So, if your server directory is mounted with noexec, it's an environmental
> problem. I guess you can not build any kernel drivers on that testbox, can
> you?
>
> Anyway, this gives us a
From: Kan Liang
Sometime, especially debugging scaling issue, the function level diff
may be high granularity. The user may want to do deeper diff analysis
for some cache or lock issue. The "symoff" key can let the user sort
differential profile by ips.
Here is an example.
The source code for
Hi Thierry,
On Mon, Nov 24, 2014 at 10:32:38AM +0100, Thierry Reding wrote:
> This conflict is uglier than I had anticipated. Perhaps it would make
> sense to pull in a stable IOMMU branch into Tegra so that I can resolve
> the conflict on top of that?
>
> Joerg, do you have a stable branch
On 24 November 2014 at 21:24, Felipe Balbi wrote:
> On Mon, Nov 24, 2014 at 09:19:09PM +0530, Sumit Semwal wrote:
>> Hi Felipe,
>>
>> On 24 November 2014 at 20:08, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Fri, Nov 21, 2014 at 09:13:00PM +0530, Kiran Raparthy wrote:
>> >> On 21 November 2014
Add support for bluetooth MCI WB335 (AR9565) Wi-Fi+bt module.
This bluetooth module requires loading patch and sysconfig by ath3k driver.
CC: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index d85ced2..086240c 100644
David Howells wrote:
> > Actually after cleaning the tree and re-signing the modules, I get following
> >
> > Unrecognized character \x7F; marked by <-- HERE after <-- HERE near
> > column 1 at ./scripts/sign-file line 1.
> > make[1]: *** [arch/x86/crypto/aes-x86_64.ko] Error 255
>
>
On Wed, Nov 19, 2014 at 11:46 AM, Antonio Borneo
wrote:
> From: Jean-Baptiste Maneyrol
>
> Current driver uses a common buffer for reading reports either
> synchronously in i2c_hid_get_raw_report() and asynchronously in
> the interrupt handler.
> There is race condition if an interrupt arrives
On Mon, Nov 24, 2014 at 10:49:31AM +0100, Pieter Smith wrote:
> On Sun, Nov 23, 2014 at 03:23:02PM -0800, Josh Triplett wrote:
> > On Sun, Nov 23, 2014 at 11:29:08PM +0100, Richard Weinberger wrote:
> > > On Sun, Nov 23, 2014 at 3:20 PM, Pieter Smith wrote:
> > > > To implement splice support,
This two patches implement blk-mq support for the UBI block driver.
As the scatter gather part is rather generic I've moved it directl
into UBI such that it can be reused later.
So far only reading data into a scatter gather list is possible.
After implementing ubi_eba_read_leb_sg() we could
Adds a new set of functions to deal with scatter gather.
ubi_eba_read_leb_sg() will read from a LEB into a scatter gather list.
The new data structure struct ubi_sgl will be used within UBI to
hold the scatter gather list itself and metadata to have a cursor
within the list.
Signed-off-by:
Convert the driver to blk-mq.
Beside of moving to the modern block interface this change boosts
also the performance of the driver.
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron NAND 256MiB 3,3V 8-bit
nand: 256MiB, SLC, page size: 2048, OOB size: 64
root@debian-armhf:~#
MCP7940x is same RTC as MCP7941x. The difference is that MCP7941x chips
contain additional EEPROM on a different i2c address.
DS1307 driver already supports MCP7941x, so just add a new i2c device id
and rename functions and defines accordingly.
Signed-off-by: Tomas Novotny
---
On 2014-11-21 22:58, Andrey Utkin wrote:
(I was asked to research this topic to help students. So please ignore
this topic if all you want to say is that it is OK to code in editor
without autocompletion and any other integration, and that there's LXR
website. We all know that.)
Dear kernel
This series is tested with MCP79401 and it is based on 3.18-rc6.
Tomas Novotny (4):
rtc: ds1307: add support for mcp7940x chips
of: add vendor prefix for Pericom Technology
rtc: ds1307: add device tree bindings documentation
rtc: ds1307: add device tree support
Signed-off-by: Tomas Novotny
---
.../devicetree/bindings/rtc/maxim,ds1307.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/maxim,ds1307.txt
diff --git a/Documentation/devicetree/bindings/rtc/maxim,ds1307.txt
Signed-off-by: Tomas Novotny
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index a344ec2..8ebd82f 100644
---
Note that alarm interrupt and trickle charger are not handled (I have no
hardware with these features).
Signed-off-by: Tomas Novotny
---
Only the "common" compatible string for that driver (maxim,ds1307) is
documented, so checkpatch complains for the rest. If it is better to document
every
On Mon, Nov 24, 2014 at 7:38 AM, Yuanhan Liu
wrote:
> FYI, we noticed the below changes on
>
> commit 4ed2d765dfaccff5ebdac68e2064b59125033a3b ("net-timestamp: TCP
> timestamping")
> e7fd2885385157d4 4ed2d765dfaccff5ebdac68e20
> --
>:10
On Fri, Nov 21, 2014 at 01:26:09PM -0800, Andy Lutomirski wrote:
> This causes all non-NMI, non-double-fault kernel entries from
> userspace to run on the normal kernel stack. Double-fault is
> exempt to minimize confusion if we double-fault directly from
> userspace due to a bad kernel stack.
>
On Fri, Nov 21, 2014 at 01:26:11PM -0800, Andy Lutomirski wrote:
> In some IST handlers, if the interrupt came from user mode,
> we can safely enable preemption. Add helpers to do it safely.
>
> This is intended to be used my the memory failure code in
> do_machine_check.
>
> Signed-off-by:
On 11/23/2014 8:41 PM, ethan zhao wrote:
> Linda,
>
> On 2014/11/21 12:44, Linda Knippers wrote:
>>
>> On 11/20/2014 07:37 PM, ethan zhao wrote:
>>> Dirk,
>>>
>>> On 2014/11/21 0:50, Dirk Brandewie wrote:
On 11/19/2014 12:22 PM, Linda Knippers wrote:
> On 11/18/2014 3:37 AM, Ethan Zhao
On 24/11/2014 16:28, Nadav Amit wrote:
> Since kvm_load_guest_fpu is called before the guest_fpu is ever stored, there
> are 2 more problems that currently cause #GP:
> 1. XCOMP_BV[63] = 0
> 2. XSTATE_BV sets a bit (including bit 63) that is not set in XCOMP_BV
> (XCOMP_BV is initialised to
On Mon, Nov 24, 2014 at 09:19:09PM +0530, Sumit Semwal wrote:
> Hi Felipe,
>
> On 24 November 2014 at 20:08, Felipe Balbi wrote:
> > Hi,
> >
> > On Fri, Nov 21, 2014 at 09:13:00PM +0530, Kiran Raparthy wrote:
> >> On 21 November 2014 20:41, Felipe Balbi wrote:
> >> > On Fri, Nov 21, 2014 at
On Thu, Nov 20, 2014 at 3:11 PM, Antonios Motakis
wrote:
> On Wed, Nov 12, 2014 at 11:58 AM, Eric Auger wrote:
>> On 10/27/2014 07:07 PM, Antonios Motakis wrote:
>>> This patch enables the IOCTLs VFIO_DEVICE_GET_REGION_INFO ioctl call,
>>> which allows the user to learn about the available MMIO
Hi Felipe,
On 24 November 2014 at 20:08, Felipe Balbi wrote:
> Hi,
>
> On Fri, Nov 21, 2014 at 09:13:00PM +0530, Kiran Raparthy wrote:
>> On 21 November 2014 20:41, Felipe Balbi wrote:
>> > On Fri, Nov 21, 2014 at 11:31:21AM +0530, Kiran Raparthy wrote:
>> >> usb: phy: Handle per-PHY event for
Em Mon, Nov 24, 2014 at 12:32:04PM -0300, Arnaldo Carvalho de Melo escreveu:
> >^
> > In file included from util/srcline.c:11:0:
> > util/symbol.h:35:21: note: previous definition of ‘bfd_demangle’ was
> > here
> > static inline char *bfd_demangle(void __maybe_unused *v,
> >
On Mon, Nov 24, 2014 at 12:02 PM, Eric Auger wrote:
> On 11/24/2014 11:00 AM, Christoffer Dall wrote:
>> On Sun, Nov 23, 2014 at 06:56:59PM +0100, Eric Auger wrote:
>>> This patch enables irqfd on arm.
>>>
>>> Both irqfd and resamplefd are supported. Injection is implemented
>>> in vgic.c without
501 - 600 of 2022 matches
Mail list logo
