From: Markus Elfring
Date: Mon, 17 Apr 2017 13:03:49 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 7 +++
1 file changed, 3
From: Markus Elfring
Date: Mon, 17 Apr 2017 13:03:49 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git
On Tue, 11 Apr 2017 18:04:50 +0300
Amir Goldstein wrote:
> On Tue, Apr 11, 2017 at 1:50 PM, Richard Weinberger
> wrote:
> > Hi!
> >
> > Am 11.04.2017 um 12:20 schrieb Amir Goldstein:
> >> On Thu, Apr 6, 2017 at 3:26 PM, Richard Weinberger
> >>
On Tue, 11 Apr 2017 18:04:50 +0300
Amir Goldstein wrote:
> On Tue, Apr 11, 2017 at 1:50 PM, Richard Weinberger
> wrote:
> > Hi!
> >
> > Am 11.04.2017 um 12:20 schrieb Amir Goldstein:
> >> On Thu, Apr 6, 2017 at 3:26 PM, Richard Weinberger
> >> wrote:
> >>> Am 06.04.2017 um 14:09 schrieb
From: Markus Elfring
Date: Mon, 17 Apr 2017 12:58:33 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 5 ++---
1 file changed, 2
From: Markus Elfring
Date: Mon, 17 Apr 2017 12:58:33 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
From: Markus Elfring
Date: Mon, 17 Apr 2017 11:36:34 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 5 ++---
1 file changed, 2
From: Markus Elfring
Date: Mon, 17 Apr 2017 11:36:34 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
From: Markus Elfring
Date: Mon, 17 Apr 2017 11:20:41 +0200
Use the word "failed" in the string for three function calls.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 6 +++---
1 file changed, 3
From: Markus Elfring
Date: Mon, 17 Apr 2017 11:20:41 +0200
Use the word "failed" in the string for three function calls.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
From: Markus Elfring
Date: Mon, 17 Apr 2017 11:10:47 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 16 +++-
1 file
From: Markus Elfring
Date: Mon, 17 Apr 2017 11:10:47 +0200
Adjust jump labels according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/net/ethernet/marvell/mvpp2.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git
From: Markus Elfring
Date: Mon, 17 Apr 2017 10:52:02 +0200
The script "checkpatch.pl" pointed out that labels should not be indented.
Thus delete two horizontal tabs before the jump label "err_drop_frame"
in the function "mvpp2_rx".
Signed-off-by: Markus Elfring
From: Markus Elfring
Date: Mon, 17 Apr 2017 10:52:02 +0200
The script "checkpatch.pl" pointed out that labels should not be indented.
Thus delete two horizontal tabs before the jump label "err_drop_frame"
in the function "mvpp2_rx".
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Mon, 17 Apr 2017 10:40:32 +0200
Replace the specification of two data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding
From: Markus Elfring
Date: Mon, 17 Apr 2017 10:40:32 +0200
Replace the specification of two data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
On Tue, 11 Apr 2017, Michal Hocko wrote:
> On Tue 11-04-17 13:59:44, Cristopher Lameter wrote:
> > On Tue, 11 Apr 2017, Michal Hocko wrote:
> >
> > > I didn't say anything like that. Hence the proposed patch which still
> > > needs some more thinking and evaluation.
> >
> > This patch does not
On Tue, 11 Apr 2017, Michal Hocko wrote:
> On Tue 11-04-17 13:59:44, Cristopher Lameter wrote:
> > On Tue, 11 Apr 2017, Michal Hocko wrote:
> >
> > > I didn't say anything like that. Hence the proposed patch which still
> > > needs some more thinking and evaluation.
> >
> > This patch does not
From: Markus Elfring
Date: Mon, 17 Apr 2017 10:30:29 +0200
Replace the specification of data structures by references to
a local variable as the parameter for the operator "sizeof"
to make the corresponding size determination a bit safer.
Signed-off-by: Markus
From: Markus Elfring
Date: Mon, 17 Apr 2017 10:30:29 +0200
Replace the specification of data structures by references to
a local variable as the parameter for the operator "sizeof"
to make the corresponding size determination a bit safer.
Signed-off-by: Markus Elfring
---
On Tue, Mar 21, 2017 at 04:32:45PM -0700, Stephen Hemminger wrote:
> On Tue, 21 Mar 2017 23:28:45 +0100
> Linus Lüssing wrote:
>
> > However, the IP code drops it in the beginning of ip_input.c/ip_rcv()
> > as the dnat target did not update the skb->pkt_type. If after
>
On Tue, Mar 21, 2017 at 04:32:45PM -0700, Stephen Hemminger wrote:
> On Tue, 21 Mar 2017 23:28:45 +0100
> Linus Lüssing wrote:
>
> > However, the IP code drops it in the beginning of ip_input.c/ip_rcv()
> > as the dnat target did not update the skb->pkt_type. If after
> > dnat'ing the packet is
From: Markus Elfring
Date: Mon, 17 Apr 2017 09:12:34 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
On Mon, 17 Apr 2017, Sergey Senozhatsky wrote:
> Minchan reported that doing copy_page() on a kmalloc(PAGE_SIZE) page
> with DEBUG_SLAB enabled can cause a memory corruption (See below or
> lkml.kernel.org/r/1492042622-12074-2-git-send-email-minc...@kernel.org )
Yes the alignment guarantees do
From: Markus Elfring
Date: Mon, 17 Apr 2017 09:12:34 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
On Mon, 17 Apr 2017, Sergey Senozhatsky wrote:
> Minchan reported that doing copy_page() on a kmalloc(PAGE_SIZE) page
> with DEBUG_SLAB enabled can cause a memory corruption (See below or
> lkml.kernel.org/r/1492042622-12074-2-git-send-email-minc...@kernel.org )
Yes the alignment guarantees do
From: Markus Elfring
Date: Mon, 17 Apr 2017 09:06:33 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Mon, 17 Apr 2017 09:06:33 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:55:42 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:55:42 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
On Thu, 2017-04-13 at 08:14 +1000, NeilBrown wrote:
> On Wed, Apr 12 2017, Jeff Layton wrote:
>
> > Now that we have a better way to store and report errors that occur
> > during writeback, we need to convert the existing codebase to use it. We
> > could just adapt all of the filesystem code and
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:48:23 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
On Thu, 2017-04-13 at 08:14 +1000, NeilBrown wrote:
> On Wed, Apr 12 2017, Jeff Layton wrote:
>
> > Now that we have a better way to store and report errors that occur
> > during writeback, we need to convert the existing codebase to use it. We
> > could just adapt all of the filesystem code and
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:48:23 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:38:32 +0200
Replace the specification of two data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:38:32 +0200
Replace the specification of two data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:09:07 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was
From: Markus Elfring
Date: Mon, 17 Apr 2017 08:09:07 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle
From: Markus Elfring
Date: Sun, 16 Apr 2017 22:45:33 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The script “checkpatch.pl” pointed information out like the following.
Comparison to NULL could be written …
Thus
From: Markus Elfring
Date: Sun, 16 Apr 2017 22:45:33 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The script “checkpatch.pl” pointed information out like the following.
Comparison to NULL could be written …
Thus fix the affected source code
From: Markus Elfring
Date: Sun, 16 Apr 2017 22:11:22 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected
From: Markus Elfring
Date: Sun, 16 Apr 2017 22:11:22 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle
From: Markus Elfring
Date: Sun, 16 Apr 2017 21:45:38 +0200
Replace the specification of two data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding
From: Markus Elfring
Date: Sun, 16 Apr 2017 21:45:38 +0200
Replace the specification of two data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
From: Markus Elfring
Date: Sun, 16 Apr 2017 21:23:19 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "devm_kmalloc_array".
This issue
From: Markus Elfring
Date: Sun, 16 Apr 2017 21:23:19 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "devm_kmalloc_array".
This issue was detected by using the
struct master is not necessary in the header file, it is a private
struct only used in component.c
Signed-off-by: Helen Koike
---
include/linux/component.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/component.h b/include/linux/component.h
index
Add kernel-doc style documentation in component.h to facilitate
understanding the component system without reading the entire code.
Signed-off-by: Helen Koike
---
include/linux/component.h | 137 ++
1 file changed, 127
Add kernel-doc style documentation in component.h to facilitate
understanding the component system without reading the entire code.
Signed-off-by: Helen Koike
---
include/linux/component.h | 137 ++
1 file changed, 127 insertions(+), 10 deletions(-)
struct master is not necessary in the header file, it is a private
struct only used in component.c
Signed-off-by: Helen Koike
---
include/linux/component.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/component.h b/include/linux/component.h
index a559eeb..a15c094 100644
From: Haiyang Zhang
Date: Wed, 12 Apr 2017 11:35:05 -0700
> From: Haiyang Zhang
>
> If the outgoing skb has a RX queue mapping available, we use the queue
> number directly, other than put it through Send Indirection Table.
>
>
From: Haiyang Zhang
Date: Wed, 12 Apr 2017 11:35:05 -0700
> From: Haiyang Zhang
>
> If the outgoing skb has a RX queue mapping available, we use the queue
> number directly, other than put it through Send Indirection Table.
>
> Signed-off-by: Haiyang Zhang
> Reviewed-by: Stephen Hemminger
From: Haiyang Zhang
Date: Wed, 12 Apr 2017 11:35:06 -0700
> From: Haiyang Zhang
>
> Azure hosts are not supporting non-TCP port numbers in vRSS hashing for
> now. For example, UDP packet loss rate will be high if port numbers are
> also
From: Haiyang Zhang
Date: Wed, 12 Apr 2017 11:35:06 -0700
> From: Haiyang Zhang
>
> Azure hosts are not supporting non-TCP port numbers in vRSS hashing for
> now. For example, UDP packet loss rate will be high if port numbers are
> also included in vRSS hash.
>
> So, we created this patch to
On Mon, 17 Apr 2017 09:04:03 +0200, Greg KH wrote:
> On Mon, Apr 17, 2017 at 02:47:34AM +0200, Karim Eshapa wrote:
>>
>> Macros more related to BLK operations.
>
> That doesn't make any sense to me, can you be more explicit?.
skein_block.h contains all fn's related to processing on
different
On Mon, 17 Apr 2017 09:04:03 +0200, Greg KH wrote:
> On Mon, Apr 17, 2017 at 02:47:34AM +0200, Karim Eshapa wrote:
>>
>> Macros more related to BLK operations.
>
> That doesn't make any sense to me, can you be more explicit?.
skein_block.h contains all fn's related to processing on
different
From: Markus Elfring
Date: Mon, 17 Apr 2017 16:44:32 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (25):
Use devm_kmalloc_array() in mvneta_init()
Improve two size determinations in mvneta_init()
From: Markus Elfring
Date: Mon, 17 Apr 2017 16:44:32 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (25):
Use devm_kmalloc_array() in mvneta_init()
Improve two size determinations in mvneta_init()
Use kmalloc_array() in
From: Vivien Didelot
Date: Wed, 12 Apr 2017 12:45:03 -0400
> This patch moves as is the legacy DSA code from dsa.c to legacy.c,
> except the few shared symbols which remain in dsa.c.
>
> Signed-off-by: Vivien Didelot
>
From: Vivien Didelot
Date: Wed, 12 Apr 2017 12:45:03 -0400
> This patch moves as is the legacy DSA code from dsa.c to legacy.c,
> except the few shared symbols which remain in dsa.c.
>
> Signed-off-by: Vivien Didelot
> ---
> Changes in v2:
> - drop CONFIG_NET_DSA_LEGACY so that legacy code
From: Wolfgang Bumiller
Date: Wed, 12 Apr 2017 16:21:38 +0200
> Commit 1045ba77a ("net sched actions: Add support for user cookies")
> added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
> nlattr array unconditionally, while it was otherwise used as well
From: Wolfgang Bumiller
Date: Wed, 12 Apr 2017 16:21:38 +0200
> Commit 1045ba77a ("net sched actions: Add support for user cookies")
> added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
> nlattr array unconditionally, while it was otherwise used as well as
> initialized only
Marek, Andrea,
Before we even start discussing minor improvements (like coding style),
I'd like to discuss the sharp FTL and partition table format, and
decide whether we want to have such an old FTL included in the kernel.
Actually, that's the very reason I asked Andrea to post his series as
Marek, Andrea,
Before we even start discussing minor improvements (like coding style),
I'd like to discuss the sharp FTL and partition table format, and
decide whether we want to have such an old FTL included in the kernel.
Actually, that's the very reason I asked Andrea to post his series as
On 04/14/2017 01:58 PM, Peter Zijlstra wrote:
> On Fri, Apr 14, 2017 at 01:38:13PM +0200, Peter Zijlstra wrote:
>> On Thu, Apr 13, 2017 at 10:56:08AM -0300, Lauro Ramos Venancio wrote:
>>> This patch constructs the sched groups from each CPU perspective. So, on
>>> a 4 nodes machine with ring
On 04/14/2017 01:58 PM, Peter Zijlstra wrote:
> On Fri, Apr 14, 2017 at 01:38:13PM +0200, Peter Zijlstra wrote:
>> On Thu, Apr 13, 2017 at 10:56:08AM -0300, Lauro Ramos Venancio wrote:
>>> This patch constructs the sched groups from each CPU perspective. So, on
>>> a 4 nodes machine with ring
On Mon, 17 Apr 2017 14:47:54 +0800
Peter Xu wrote:
> On Sun, Apr 16, 2017 at 07:42:27PM -0600, Alex Williamson wrote:
>
> [...]
>
> > -static void vfio_lock_acct(struct task_struct *task, long npage)
> > +static int vfio_lock_acct(struct task_struct *task, long npage, bool
On Mon, 17 Apr 2017 14:47:54 +0800
Peter Xu wrote:
> On Sun, Apr 16, 2017 at 07:42:27PM -0600, Alex Williamson wrote:
>
> [...]
>
> > -static void vfio_lock_acct(struct task_struct *task, long npage)
> > +static int vfio_lock_acct(struct task_struct *task, long npage, bool
> > lock_cap)
> >
On Mon, Apr 17, 2017 at 8:53 AM, Greg KH wrote:
> On Mon, Apr 17, 2017 at 02:07:05AM -0400, Matt Brown wrote:
>> this patch depends on patch 1 and 2
>>
>> enforces restrictions on unprivileged users injecting commands
>> into other processes in the same tty session
On Mon, Apr 17, 2017 at 8:53 AM, Greg KH wrote:
> On Mon, Apr 17, 2017 at 02:07:05AM -0400, Matt Brown wrote:
>> this patch depends on patch 1 and 2
>>
>> enforces restrictions on unprivileged users injecting commands
>> into other processes in the same tty session using the TIOCSTI ioctl
>>
>>
On 04/17/2017 02:48 AM, Zheng, Lv wrote:
Hi,
From: Devel [mailto:devel-boun...@acpica.org] On Behalf Of Zheng, Lv
Sent: Monday, April 17, 2017 5:40 PM
To: Guenter Roeck ; Moore, Robert
Cc: linux-a...@vger.kernel.org; de...@acpica.org; Wysocki,
On 04/17/2017 02:48 AM, Zheng, Lv wrote:
Hi,
From: Devel [mailto:devel-boun...@acpica.org] On Behalf Of Zheng, Lv
Sent: Monday, April 17, 2017 5:40 PM
To: Guenter Roeck ; Moore, Robert
Cc: linux-a...@vger.kernel.org; de...@acpica.org; Wysocki, Rafael J
;
linux-kernel@vger.kernel.org
Subject:
With frame pointers disabled, on some older versions of GCC (like
4.8.3), it's possible for the stack pointer to get aligned at a
half-word boundary:
04d0 :
4d0: 41 57 push %r15
4d2: 41 56 push %r14
4d4:
With frame pointers disabled, on some older versions of GCC (like
4.8.3), it's possible for the stack pointer to get aligned at a
half-word boundary:
04d0 :
4d0: 41 57 push %r15
4d2: 41 56 push %r14
4d4:
Option mem= will limit the max address system can use. Any memory
region above the limit will be removed. And memmap=nn[KMG] which
has no offset specified has the same behaviour as mem=. KASLR need
consider this when choose the random position for decompressing
kernel. Do it in this patch.
Option mem= will limit the max address system can use. Any memory
region above the limit will be removed. And memmap=nn[KMG] which
has no offset specified has the same behaviour as mem=. KASLR need
consider this when choose the random position for decompressing
kernel. Do it in this patch.
In commit 9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time")
memmap was changed to adopt multiple values with comma delimited in
one entry, so update the related description.
And if only specify size value without offset, like memmap=nn[KMG],
memmap behaves equal to mem=nn[KMG],
In commit 9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time")
memmap was changed to adopt multiple values with comma delimited in
one entry, so update the related description.
And if only specify size value without offset, like memmap=nn[KMG],
memmap behaves equal to mem=nn[KMG],
In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"),
memmap= option is parsed so that kaslr can avoid those reserved
regions. It uses cmdline_find_option to get the value if memmap=
is specified, however the problem is cmdline_find_option can only
find the last entry if multiple
In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"),
memmap= option is parsed so that kaslr can avoid those reserved
regions. It uses cmdline_find_option to get the value if memmap=
is specified, however the problem is cmdline_find_option can only
find the last entry if multiple
next_arg will be used to parse cmdline in x86/boot/compressed code,
so move it to lib/cmdline.c for better code reuse.
No change in functionality.
Signed-off-by: Baoquan He
Cc: Andrew Morton
Cc: Jessica Yu
Cc: Petr Mladek
next_arg will be used to parse cmdline in x86/boot/compressed code,
so move it to lib/cmdline.c for better code reuse.
No change in functionality.
Signed-off-by: Baoquan He
Cc: Andrew Morton
Cc: Jessica Yu
Cc: Petr Mladek
Cc: Jens Axboe
Cc: Josh Triplett
Cc: zijun_hu
Cc: Larry Finger
Cc:
People reported kernel panic occurs during system boots up with mem boot option.
After checking code, several problems are found about memmap= and mem= in boot
stage
kaslr.
*) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only
one memmap
entry is considered and only
People reported kernel panic occurs during system boots up with mem boot option.
After checking code, several problems are found about memmap= and mem= in boot
stage
kaslr.
*) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only
one memmap
entry is considered and only
On Sun, Apr 16, 2017 at 09:20:50AM +0800, kbuild test robot wrote:
> Hi Josh,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: d5ff0814fda50f0306e102f39640cf5bb76af08e
> commit:
On Sun, Apr 16, 2017 at 09:20:50AM +0800, kbuild test robot wrote:
> Hi Josh,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: d5ff0814fda50f0306e102f39640cf5bb76af08e
> commit:
Hi,
sorry for the late reply.
On 04/03/2017 07:29 PM, Cong Wang wrote:
> (Cc'ing netdev and maintainers)
>
> On Mon, Mar 27, 2017 at 2:16 AM, David Palma wrote:
>>
>> Hi,
>>
>> Sending a simple UDP packet (39 bytes long), over a 6lowpan interface
>> (using fakelb),
Hi,
sorry for the late reply.
On 04/03/2017 07:29 PM, Cong Wang wrote:
> (Cc'ing netdev and maintainers)
>
> On Mon, Mar 27, 2017 at 2:16 AM, David Palma wrote:
>>
>> Hi,
>>
>> Sending a simple UDP packet (39 bytes long), over a 6lowpan interface
>> (using fakelb), creates a kernel panic
Hi Masami,
On Mon, Apr 17, 2017 at 8:52 PM, Masami Hiramatsu wrote:
> On Mon, 17 Apr 2017 11:44:27 +0900
> Namhyung Kim wrote:
>
>> When function tracer has a pid filter, it adds a probe to sched_switch
>> to track if current task can be ignored. The
Hi Masami,
On Mon, Apr 17, 2017 at 8:52 PM, Masami Hiramatsu wrote:
> On Mon, 17 Apr 2017 11:44:27 +0900
> Namhyung Kim wrote:
>
>> When function tracer has a pid filter, it adds a probe to sched_switch
>> to track if current task can be ignored. The probe checks the
>> ftrace_ignore_pid from
Hi Daniel,
On Monday 17 Apr 2017 18:57:57 Daniel Axtens wrote:
> Hi,
>
> >> > I hate to pester, but wondered if you had found anything obvious.
> >> > I really do appreciate you taking the time to look.
> >>
> >> Sorry, I haven't had the chance and now will not be able to until
> >> January
Hi Daniel,
On Monday 17 Apr 2017 18:57:57 Daniel Axtens wrote:
> Hi,
>
> >> > I hate to pester, but wondered if you had found anything obvious.
> >> > I really do appreciate you taking the time to look.
> >>
> >> Sorry, I haven't had the chance and now will not be able to until
> >> January
On Sun, Apr 16, 2017 at 10:26 AM, Sebastian Reichel wrote:
> Hi Michael,
>
> On Sat, Apr 15, 2017 at 07:00:29PM -0700, Michael Scott wrote:
>> On Apr 15, 2017 3:18 PM, "Sebastian Reichel" wrote:
>>> Droid 4 has wl1835 connected to the OMAP's UART4 port, which is
On Sun, Apr 16, 2017 at 10:26 AM, Sebastian Reichel wrote:
> Hi Michael,
>
> On Sat, Apr 15, 2017 at 07:00:29PM -0700, Michael Scott wrote:
>> On Apr 15, 2017 3:18 PM, "Sebastian Reichel" wrote:
>>> Droid 4 has wl1835 connected to the OMAP's UART4 port, which is
>>
>> Technically, I believe the
Hi Daniel,
Thank you for the patch.
On Monday 17 Apr 2017 18:52:40 Daniel Axtens wrote:
> When an in-use webcam is disconnected, I noticed the following
> messages:
>
> uvcvideo: Failed to resubmit video URB (-19).
>
> -19 is -ENODEV, which does make sense given that the device has
>
Hi Daniel,
Thank you for the patch.
On Monday 17 Apr 2017 18:52:40 Daniel Axtens wrote:
> When an in-use webcam is disconnected, I noticed the following
> messages:
>
> uvcvideo: Failed to resubmit video URB (-19).
>
> -19 is -ENODEV, which does make sense given that the device has
>
This patch series address a few issues at the documentation, after
applying this patch series:
https://lkml.org/lkml/2017/4/16/2
The first patch solves a limitation with Sphinx and literal blocks
inside a footnote.
The next two patches fix issues with xpad.rst documentation, with
mentions
Move the kAPI kernel-doc produced documentation to
Documentation/input and add uAPI documentation there too.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/iio/intro.rst | 4 ++--
Documentation/driver-api/index.rst
This patch series address a few issues at the documentation, after
applying this patch series:
https://lkml.org/lkml/2017/4/16/2
The first patch solves a limitation with Sphinx and literal blocks
inside a footnote.
The next two patches fix issues with xpad.rst documentation, with
mentions
Move the kAPI kernel-doc produced documentation to
Documentation/input and add uAPI documentation there too.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/iio/intro.rst | 4 ++--
Documentation/driver-api/index.rst
701 - 800 of 1040 matches
Mail list logo