From: Markus Elfring
Date: Tue, 27 Sep 2016 15:26:51 +0200
The script "checkpatch.pl" can point information out like the following.
WARNING: Prefer kcalloc over kzalloc with multiply
Thus fix the affected source code place.
Signed-off-by: Markus Elfring
---
drivers/md/bitmap.c | 3 +--
1
From: Markus Elfring
Date: Tue, 27 Sep 2016 15:55:01 +0200
Adjust a jump label according to the current Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/md/bitmap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/md/bitmap.c
From: Markus Elfring
Date: Tue, 27 Sep 2016 15:46:22 +0200
Adjust jump labels according to the current Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/md/bitmap.c | 18 +-
1 file changed, 9
From: Markus Elfring
Date: Tue, 27 Sep 2016 15:46:22 +0200
Adjust jump labels according to the current Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/md/bitmap.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git
From: Markus Elfring
Date: Tue, 27 Sep 2016 15:21:23 +0200
* Return directly after a call of the function "kzalloc" failed here.
* Delete two assignments for the local variable "ret" and the jump
target "err" which became unnecessary with this refactoring.
From: Markus Elfring
Date: Tue, 27 Sep 2016 15:21:23 +0200
* Return directly after a call of the function "kzalloc" failed here.
* Delete two assignments for the local variable "ret" and the jump
target "err" which became unnecessary with this refactoring.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Tue, 27 Sep 2016 13:20:23 +0200
The local variable "offset" will be set to an appropriate value a bit later.
Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Tue, 27 Sep 2016 13:20:23 +0200
The local variable "offset" will be set to an appropriate value a bit later.
Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
drivers/md/bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1
From: Markus Elfring
Date: Tue, 27 Sep 2016 14:19:00 +0200
Replace the specification of a data type 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: Tue, 27 Sep 2016 14:19:00 +0200
Replace the specification of a data type 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: Markus
From: Markus Elfring
Date: Tue, 27 Sep 2016 13:01: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
On Tue, Sep 27, 2016 at 07:50:14AM -0400, David Miller wrote:
> This still doesn't apply to the net-next tree.
> If you aren't actually building your patch against the net-next
> tree, don't bother submitting these patches any more.
Baoyou, Dave is referring to his git tree at:
From: Markus Elfring
Date: Tue, 27 Sep 2016 13:01: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
On Tue, Sep 27, 2016 at 07:50:14AM -0400, David Miller wrote:
> This still doesn't apply to the net-next tree.
> If you aren't actually building your patch against the net-next
> tree, don't bother submitting these patches any more.
Baoyou, Dave is referring to his git tree at:
From: Markus Elfring
Date: Tue, 27 Sep 2016 13:10:05 +0200
Move the assignment for the local variable "offset" behind
the source code for memory allocations by this function.
Signed-off-by: Markus Elfring
---
drivers/md/bitmap.c |
From: Markus Elfring
Date: Tue, 27 Sep 2016 13:10:05 +0200
Move the assignment for the local variable "offset" behind
the source code for memory allocations by this function.
Signed-off-by: Markus Elfring
---
drivers/md/bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Markus Elfring
Date: Tue, 27 Sep 2016 18:29:08 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (16):
Use kmalloc_array() in bitmap_storage_alloc()
Move an assignment for the variable "offset" in
From: Markus Elfring
Date: Tue, 27 Sep 2016 18:29:08 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (16):
Use kmalloc_array() in bitmap_storage_alloc()
Move an assignment for the variable "offset" in bitmap_storage_alloc()
Delete
On Tue, 2016-09-27 at 17:36 +0100, Emil Velikov wrote:
> On 27 September 2016 at 17:04, Joe Perches wrote:
> > On Tue, 2016-09-27 at 11:58 -0400, Sean Paul wrote:
> > > On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
> > > > Use a bit more consistent
On Tue, 2016-09-27 at 17:36 +0100, Emil Velikov wrote:
> On 27 September 2016 at 17:04, Joe Perches wrote:
> > On Tue, 2016-09-27 at 11:58 -0400, Sean Paul wrote:
> > > On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
> > > > Use a bit more consistent style with kernel loglevels
> > > I'm
On 2016-09-27 05:12, Vladimir Zapolskiy wrote:
> Hi Stefan,
>
> On 09/27/2016 03:26 AM, Stefan Agner wrote:
>> If a GPIO gets freed after selecting a new pinctrl configuration
>> the driver should not change pinctrl anymore. Otherwise this will
>> likely lead to a unusable pin configuration for >
On 2016-09-27 05:12, Vladimir Zapolskiy wrote:
> Hi Stefan,
>
> On 09/27/2016 03:26 AM, Stefan Agner wrote:
>> If a GPIO gets freed after selecting a new pinctrl configuration
>> the driver should not change pinctrl anymore. Otherwise this will
>> likely lead to a unusable pin configuration for >
On Sun, Sep 25, 2016 at 3:41 AM, Baoyou Xie wrote:
> We get 4 warnings when building kernel with W=1:
> drivers/gpu/drm/mediatek/mtk_hdmi.c:1089:6: warning: no previous prototype
> for 'mtk_hdmi_audio_enable' [-Wmissing-prototypes]
>
On Sun, Sep 25, 2016 at 3:41 AM, Baoyou Xie wrote:
> We get 4 warnings when building kernel with W=1:
> drivers/gpu/drm/mediatek/mtk_hdmi.c:1089:6: warning: no previous prototype
> for 'mtk_hdmi_audio_enable' [-Wmissing-prototypes]
> drivers/gpu/drm/mediatek/mtk_hdmi.c:1095:6: warning: no
The patch
ASoC: tlv320aic31xx: do not declare support for mono DAI
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: tlv320aic31xx: do not declare support for mono DAI
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
On 09/27/2016 05:38 AM, Peter Zijlstra wrote:
> On Mon, Sep 26, 2016 at 06:29:44PM -0600, Shuah Khan wrote:
>> Add support to run sched-pipe benchmark test on pipe with packet I/O mode.
I will add more detail here.
>>
>> Signed-off-by: Shuah Khan
>> ---
>>
On 27 September 2016 at 17:04, Joe Perches wrote:
> On Tue, 2016-09-27 at 11:58 -0400, Sean Paul wrote:
>> > On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
>> > Use a bit more consistent style with kernel loglevels
>> > I'm not convinced this is worth
On 09/27/2016 05:38 AM, Peter Zijlstra wrote:
> On Mon, Sep 26, 2016 at 06:29:44PM -0600, Shuah Khan wrote:
>> Add support to run sched-pipe benchmark test on pipe with packet I/O mode.
I will add more detail here.
>>
>> Signed-off-by: Shuah Khan
>> ---
>> tools/perf/bench/sched-pipe.c | 20
On 27 September 2016 at 17:04, Joe Perches wrote:
> On Tue, 2016-09-27 at 11:58 -0400, Sean Paul wrote:
>> > On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
>> > Use a bit more consistent style with kernel loglevels
>> > I'm not convinced this is worth doing if we're going to keep the
>>
On Tue, 27 Sep 2016 07:53:56 -0700
Vineet Gupta wrote:
> This doesn't seem to be used anywhere
I thought so too, until I got this response for an equivalent patch:
https://lkml.org/lkml/2016/8/31/53
Kim
On Tue, 27 Sep 2016 07:53:56 -0700
Vineet Gupta wrote:
> This doesn't seem to be used anywhere
I thought so too, until I got this response for an equivalent patch:
https://lkml.org/lkml/2016/8/31/53
Kim
On Sun, Sep 25, 2016 at 3:43 AM, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/gpu/drm/rockchip/rockchip_drm_drv.c:309:6: warning: no previous
> prototype for 'rockchip_drm_fb_suspend' [-Wmissing-prototypes]
>
On Sun, Sep 25, 2016 at 3:43 AM, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/gpu/drm/rockchip/rockchip_drm_drv.c:309:6: warning: no previous
> prototype for 'rockchip_drm_fb_suspend' [-Wmissing-prototypes]
> drivers/gpu/drm/rockchip/rockchip_drm_drv.c:318:6:
On Sun, Sep 25, 2016 at 3:57 AM, Baoyou Xie wrote:
> We get 6 warnings when building kernel with W=1:
> drivers/gpu/drm/sti/sti_mixer.c:361:6: warning: no previous prototype for
> 'sti_mixer_set_matrix' [-Wmissing-prototypes]
> drivers/gpu/drm/sti/sti_dvo.c:109:5: warning:
On Sun, Sep 25, 2016 at 3:57 AM, Baoyou Xie wrote:
> We get 6 warnings when building kernel with W=1:
> drivers/gpu/drm/sti/sti_mixer.c:361:6: warning: no previous prototype for
> 'sti_mixer_set_matrix' [-Wmissing-prototypes]
> drivers/gpu/drm/sti/sti_dvo.c:109:5: warning: no previous prototype
On Sun, Sep 25, 2016 at 3:38 AM, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c:130:5: warning: no previous
> prototype for 'rockchip_drm_fbdev_init' [-Wmissing-prototypes]
>
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote:
>
> dmesg -c
> echo 9 > /proc/sysrq-trigger
> modprobe cdc_acm
> echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
>
> [plug your device in]
>
> and provide the full output of dmesg after that.
After some
On Sun, Sep 25, 2016 at 3:38 AM, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c:130:5: warning: no previous
> prototype for 'rockchip_drm_fbdev_init' [-Wmissing-prototypes]
>
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote:
>
> dmesg -c
> echo 9 > /proc/sysrq-trigger
> modprobe cdc_acm
> echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
>
> [plug your device in]
>
> and provide the full output of dmesg after that.
After some
On 9/27/2016 10:43 AM, Sam Ravnborg wrote:
On Tue, Sep 27, 2016 at 09:51:40AM -0500, Babu Moger wrote:
On 9/27/2016 6:40 AM, Peter Zijlstra wrote:
On Tue, Sep 27, 2016 at 06:46:25AM +0200, Sam Ravnborg wrote:
Since this is only relevant for sparc, and for sparc this is "select"ed,
then
On 9/27/2016 10:43 AM, Sam Ravnborg wrote:
On Tue, Sep 27, 2016 at 09:51:40AM -0500, Babu Moger wrote:
On 9/27/2016 6:40 AM, Peter Zijlstra wrote:
On Tue, Sep 27, 2016 at 06:46:25AM +0200, Sam Ravnborg wrote:
Since this is only relevant for sparc, and for sparc this is "select"ed,
then
Joe Perches writes:
> Use the more common logging mechanism.
>
> Miscellanea:
>
> o Realign multiline statements
> o Coalesce format
>
> Signed-off-by: Joe Perches
For pxa25x_udc.h:
Acked-by: Robert Jarzmik
Cheers.
--
Robert
Joe Perches writes:
> Use the more common logging mechanism.
>
> Miscellanea:
>
> o Realign multiline statements
> o Coalesce format
>
> Signed-off-by: Joe Perches
For pxa25x_udc.h:
Acked-by: Robert Jarzmik
Cheers.
--
Robert
Greg Kroah-Hartman writes:
> On Tue, Sep 27, 2016 at 05:47:54PM +0200, Robert Jarzmik wrote:
>> If you're overburdened and feel there won't be a merge conflict in your
>> serial
>> tree, I can take it through pxa tree provided you ack it, or you can take it,
>> just
Greg Kroah-Hartman writes:
> On Tue, Sep 27, 2016 at 05:47:54PM +0200, Robert Jarzmik wrote:
>> If you're overburdened and feel there won't be a merge conflict in your
>> serial
>> tree, I can take it through pxa tree provided you ack it, or you can take it,
>> just let me know.
>
> I'll be
From: Sergey Yanovich
pxa2xx-uart was a separate uart platform driver. It was declaring
the same device names and numbers as 8250 driver. As a result,
it was impossible to use 8250 driver on PXA SoCs.
Upon closer examination pxa2xx-uart turned out to be a clone of
8250_core
From: Sergey Yanovich
pxa2xx-uart was a separate uart platform driver. It was declaring
the same device names and numbers as 8250 driver. As a result,
it was impossible to use 8250 driver on PXA SoCs.
Upon closer examination pxa2xx-uart turned out to be a clone of
8250_core driver.
Workaround
On 09/27, Waiman Long wrote:
>
> +static inline int sigequalsets(const sigset_t *set1, const sigset_t *set2)
> +{
> + switch (_NSIG_WORDS) {
> + case 4:
> + return (set1->sig[3] == set2->sig[3]) &&
> + (set1->sig[2] == set2->sig[2]) &&
> +
On 09/27, Waiman Long wrote:
>
> +static inline int sigequalsets(const sigset_t *set1, const sigset_t *set2)
> +{
> + switch (_NSIG_WORDS) {
> + case 4:
> + return (set1->sig[3] == set2->sig[3]) &&
> + (set1->sig[2] == set2->sig[2]) &&
> +
Hello Martin:
On 09/26/2016 06:26 PM, Martin K. Petersen wrote:
>> "Lee" == Lee Duncan writes:
>
> Lee,
>
> Lee> Chris Leech and I are taking over as open-iscsi maintainers.
>
> Do you want me to queue the MAINTAINER update?
Yes, that would be great. Thank you.
>
>
Hello Martin:
On 09/26/2016 06:26 PM, Martin K. Petersen wrote:
>> "Lee" == Lee Duncan writes:
>
> Lee,
>
> Lee> Chris Leech and I are taking over as open-iscsi maintainers.
>
> Do you want me to queue the MAINTAINER update?
Yes, that would be great. Thank you.
>
> Lee> * Removed git
Use the more common logging mechanism.
Miscellanea:
o Realign multiline statements
o Coalesce format
Signed-off-by: Joe Perches
---
drivers/usb/gadget/function/rndis.c | 9 -
drivers/usb/gadget/function/u_serial.c | 4 ++--
drivers/usb/gadget/udc/at91_udc.h
Use the more common logging mechanism.
Miscellanea:
o Realign multiline statements
o Coalesce format
Signed-off-by: Joe Perches
---
drivers/usb/gadget/function/rndis.c | 9 -
drivers/usb/gadget/function/u_serial.c | 4 ++--
drivers/usb/gadget/udc/at91_udc.h | 2 +-
On Tue, Sep 27, 2016 at 03:50:42PM +0200, Wolfgang Wiedmeyer wrote:
> When charging is disabled (e.g. by removing the USB cable) the charge
> current is not reset to zero. So if I expose the current by the
> CURRENT_NOW property, it incorrectly reports the current that was set
> when charging was
On Tue, Sep 27, 2016 at 03:50:42PM +0200, Wolfgang Wiedmeyer wrote:
> When charging is disabled (e.g. by removing the USB cable) the charge
> current is not reset to zero. So if I expose the current by the
> CURRENT_NOW property, it incorrectly reports the current that was set
> when charging was
On Tue, Sep 27, 2016 at 05:47:54PM +0200, Robert Jarzmik wrote:
> Robert Jarzmik writes:
>
> >>> If so, great, get the platform maintainer to sign off on this please and
> >>> then resend it.
> >
> > If you're talking about the PXA maintainer, then :
> > Acked-by: Robert
On Tue, Sep 27, 2016 at 05:47:54PM +0200, Robert Jarzmik wrote:
> Robert Jarzmik writes:
>
> >>> If so, great, get the platform maintainer to sign off on this please and
> >>> then resend it.
> >
> > If you're talking about the PXA maintainer, then :
> > Acked-by: Robert Jarzmik
> >
> > I'm
On Mon, Sep 26, 2016 at 6:21 AM, Jonathan Liu wrote:
> The panel should be enabled after the controller so that we do not have
> visual glitches on the panel while the controller is setup. Similarly,
> the panel should be disabled before the controller.
>
> Signed-off-by:
Hello,
On Tue, Sep 27, 2016 at 05:16:15AM -0500, Shaun Tancheff wrote:
> git bisect points at commit c9634dcf00c9c93b ("mm: vma_merge: fix
> vm_page_prot SMP race condition against rmap_walk")
I assume linux-next? But I can't find the commit, but I should know
what this is.
>
> Last lines to
2016-09-27 Emilio López :
> As part of the sync framework destaging, the sync_file.h header
> was moved, but an entry was not added on Kbuild to install it.
> This patch resolves this omission so that "make headers_install"
> installs this header.
>
> Fixes:
On Mon, Sep 26, 2016 at 6:21 AM, Jonathan Liu wrote:
> The panel should be enabled after the controller so that we do not have
> visual glitches on the panel while the controller is setup. Similarly,
> the panel should be disabled before the controller.
>
> Signed-off-by: Jonathan Liu
Cool,
Hello,
On Tue, Sep 27, 2016 at 05:16:15AM -0500, Shaun Tancheff wrote:
> git bisect points at commit c9634dcf00c9c93b ("mm: vma_merge: fix
> vm_page_prot SMP race condition against rmap_walk")
I assume linux-next? But I can't find the commit, but I should know
what this is.
>
> Last lines to
2016-09-27 Emilio López :
> As part of the sync framework destaging, the sync_file.h header
> was moved, but an entry was not added on Kbuild to install it.
> This patch resolves this omission so that "make headers_install"
> installs this header.
>
> Fixes: 460bfc41fd52 ("dma-buf/sync_file:
On Tue, 2016-09-27 at 11:58 -0400, Sean Paul wrote:
> > On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
> > Use a bit more consistent style with kernel loglevels
> > I'm not convinced this is worth doing if we're going to keep the
> WARN/WARNING discrepancy, and I don't
On Tue, 2016-09-27 at 11:58 -0400, Sean Paul wrote:
> > On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
> > Use a bit more consistent style with kernel loglevels
> > I'm not convinced this is worth doing if we're going to keep the
> WARN/WARNING discrepancy, and I don't think we should
On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
> Use a bit more consistent style with kernel loglevels
I'm not convinced this is worth doing if we're going to keep the
WARN/WARNING discrepancy, and I don't think we should switch DRM_WARN
to DRM_WARNING since it's so
On Sun, Sep 25, 2016 at 10:18 PM, Joe Perches wrote:
> Use a bit more consistent style with kernel loglevels
I'm not convinced this is worth doing if we're going to keep the
WARN/WARNING discrepancy, and I don't think we should switch DRM_WARN
to DRM_WARNING since it's so widely used.
Sean
>
From: Chris Roth
>From Allan Chou
From: Chris Roth
Add support for Cypress GX3 SuperSpeed to Gigabit Ethernet
Bridge Controller (Vendor=04b4 ProdID=3610).
Patch verified on x64 linux kernel 4.7.4 system with the
Kensington SD4600P
From: Chris Roth
>From Allan Chou
From: Chris Roth
Add support for Cypress GX3 SuperSpeed to Gigabit Ethernet
Bridge Controller (Vendor=04b4 ProdID=3610).
Patch verified on x64 linux kernel 4.7.4 system with the
Kensington SD4600P USB-C Universal Dock with Power, which uses the
Cypress GX3
On Mon, Sep 26, 2016 at 4:36 AM, Chris Wilson wrote:
> On Sun, Sep 25, 2016 at 07:18:34PM -0700, Joe Perches wrote:
>> Remove function name and special " *ERROR*" from argument list
>>
>> $ size drivers/gpu/drm/built-in.o* (x86-32 defconfig, most drm selected)
>>text
On Mon, Sep 26, 2016 at 4:36 AM, Chris Wilson wrote:
> On Sun, Sep 25, 2016 at 07:18:34PM -0700, Joe Perches wrote:
>> Remove function name and special " *ERROR*" from argument list
>>
>> $ size drivers/gpu/drm/built-in.o* (x86-32 defconfig, most drm selected)
>>text data bss
Currently "%o" not parsed properly and printed as '>o<'
# perf record -e ext4:ext4* touch new_file; perf script | grep "mode"
Signed-off-by: Dmitry Monakhov
---
tools/lib/traceevent/event-parse.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Currently "%o" not parsed properly and printed as '>o<'
# perf record -e ext4:ext4* touch new_file; perf script | grep "mode"
Signed-off-by: Dmitry Monakhov
---
tools/lib/traceevent/event-parse.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/lib/traceevent/event-parse.c
This will help us to catch missed format specifiers much quicker.
Signed-off-by: Dmitry Monakhov
---
tools/lib/traceevent/event-parse.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/lib/traceevent/event-parse.c
b/tools/lib/traceevent/event-parse.c
index
This will help us to catch missed format specifiers much quicker.
Signed-off-by: Dmitry Monakhov
---
tools/lib/traceevent/event-parse.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/lib/traceevent/event-parse.c
b/tools/lib/traceevent/event-parse.c
index 27dc1f8..546a0f9 100644
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Even with timeout increased to 950 ms we get WARNINGs from time to time.
> It mostly happens on A-MPDU stalls (e.g. when station goes out of
> range). It may take up to 5-10 secods for the firmware to recover and
> for that time it
Since the I2C sx150x GPIO expander driver uses platform_data to manage
the pins configurations, rewrite the driver as a pinctrl driver using
pinconf to get/set pin configurations from DT or debugfs.
The pinctrl driver is functionnally equivalent as the gpio-only driver
and can use DT for pinconf.
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Flowrings contain skbs waiting for transmission that were passed to us
> by netif. It means we checked every one of them looking for 802.1x
> Ethernet type. When deleting flowring we have to use freeing function
> that will check
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Even with timeout increased to 950 ms we get WARNINGs from time to time.
> It mostly happens on A-MPDU stalls (e.g. when station goes out of
> range). It may take up to 5-10 secods for the firmware to recover and
> for that time it doesn't process
Since the I2C sx150x GPIO expander driver uses platform_data to manage
the pins configurations, rewrite the driver as a pinctrl driver using
pinconf to get/set pin configurations from DT or debugfs.
The pinctrl driver is functionnally equivalent as the gpio-only driver
and can use DT for pinconf.
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Flowrings contain skbs waiting for transmission that were passed to us
> by netif. It means we checked every one of them looking for 802.1x
> Ethernet type. When deleting flowring we have to use freeing function
> that will check for 802.1x type as
Robert Jarzmik writes:
>>> If so, great, get the platform maintainer to sign off on this please and
>>> then resend it.
>
> If you're talking about the PXA maintainer, then :
> Acked-by: Robert Jarzmik
>
> I'm happy with the patch, all pxa board
Robert Jarzmik writes:
>>> If so, great, get the platform maintainer to sign off on this please and
>>> then resend it.
>
> If you're talking about the PXA maintainer, then :
> Acked-by: Robert Jarzmik
>
> I'm happy with the patch, all pxa board maintainers have been warned, and
> there
>
On Tue, 27 Sep 2016, Vladislav Naumov wrote:
> Yes, I still have one of those!
> 0079:0011 DragonRise Inc. Gamepad
> Left shift buttons are broken now, but axis and main buttons are still
> working.
> Axis is handled properly with 3.16.0-4-686-pae #1 SMP Debian
> 3.16.7-ckt25-2
On Tue, Sep 27, 2016 at 08:39:59AM -0700, Eric Dumazet wrote:
...
> > + }
> > + if (sk && !atomic_inc_not_zero(>sk_refcnt))
> > + sk = NULL;
>
> Minor detail, but note that raw sockets do not use rcu (yet)
>
> Since you have read_lock(>lock), no writer can suddenly change
>
On Tue, 27 Sep 2016, Vladislav Naumov wrote:
> Yes, I still have one of those!
> 0079:0011 DragonRise Inc. Gamepad
> Left shift buttons are broken now, but axis and main buttons are still
> working.
> Axis is handled properly with 3.16.0-4-686-pae #1 SMP Debian
> 3.16.7-ckt25-2 (2016-04-08) i686
On Tue, Sep 27, 2016 at 08:39:59AM -0700, Eric Dumazet wrote:
...
> > + }
> > + if (sk && !atomic_inc_not_zero(>sk_refcnt))
> > + sk = NULL;
>
> Minor detail, but note that raw sockets do not use rcu (yet)
>
> Since you have read_lock(>lock), no writer can suddenly change
>
Joe Perches wrote:
> Help along debugging by showing what switch/case variable is not
> being processed in these messages.
>
> Signed-off-by: Joe Perches
> Acked-by: Larry Finger
Patch applied to wireless-drivers-next.git, thanks.
Joe Perches wrote:
> Help along debugging by showing what switch/case variable is not
> being processed in these messages.
>
> Signed-off-by: Joe Perches
> Acked-by: Larry Finger
Patch applied to wireless-drivers-next.git, thanks.
ad5748893b27 rtlwifi: Add switch variable to 'switch case not
On Tue, Sep 27, 2016 at 09:51:40AM -0500, Babu Moger wrote:
>
> On 9/27/2016 6:40 AM, Peter Zijlstra wrote:
> >On Tue, Sep 27, 2016 at 06:46:25AM +0200, Sam Ravnborg wrote:
> >>Since this is only relevant for sparc, and for sparc this is "select"ed,
> >>then there is limited/no gain having this
On Tue, Sep 27, 2016 at 09:51:40AM -0500, Babu Moger wrote:
>
> On 9/27/2016 6:40 AM, Peter Zijlstra wrote:
> >On Tue, Sep 27, 2016 at 06:46:25AM +0200, Sam Ravnborg wrote:
> >>Since this is only relevant for sparc, and for sparc this is "select"ed,
> >>then there is limited/no gain having this
put_cpu_var takes the percpu data, not the data returned from
get_cpu_var.
This doesn't change the behavior.
Cc: Tejun Heo
Signed-off-by: Shaohua Li
---
lib/random32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/random32.c
put_cpu_var takes the percpu data, not the data returned from
get_cpu_var.
This doesn't change the behavior.
Cc: Tejun Heo
Signed-off-by: Shaohua Li
---
lib/random32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/random32.c b/lib/random32.c
index
put_cpu_var takes the percpu data, not the data returned from
get_cpu_var.
This doesn't change the behavior.
Cc: Tejun Heo
Cc: Alexei Starovoitov
Signed-off-by: Shaohua Li
---
kernel/bpf/core.c | 2 +-
1 file changed, 1 insertion(+), 1
put_cpu_var takes the percpu data, not the data returned from
get_cpu_var.
This doesn't change the behavior.
Cc: Tejun Heo
Cc: Alexei Starovoitov
Signed-off-by: Shaohua Li
---
kernel/bpf/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/bpf/core.c
On Tue, 2016-09-27 at 18:08 +0300, Cyrill Gorcunov wrote:
> +static struct sock *raw_sock_get(struct net *net, const struct
> inet_diag_req_v2 *r)
> +{
> + struct raw_hashinfo *hashinfo = raw_get_hashinfo(r);
> + struct sock *sk = NULL, *s;
> + int slot;
> +
> + if
On Tue, 2016-09-27 at 18:08 +0300, Cyrill Gorcunov wrote:
> +static struct sock *raw_sock_get(struct net *net, const struct
> inet_diag_req_v2 *r)
> +{
> + struct raw_hashinfo *hashinfo = raw_get_hashinfo(r);
> + struct sock *sk = NULL, *s;
> + int slot;
> +
> + if
On Mon, Sep 26, 2016 at 03:56:59PM -0600, Chris Roth wrote:
> I'm not sure what I'm doing wrong:
>
> I'm trying to get the from statement to read original author (Allan
> Chou) first, and then me (Chris Roth) second. I've used the following
> two commands:
>
> git format-patch -o /tmp/
On Mon, Sep 26, 2016 at 03:56:59PM -0600, Chris Roth wrote:
> I'm not sure what I'm doing wrong:
>
> I'm trying to get the from statement to read original author (Allan
> Chou) first, and then me (Chris Roth) second. I've used the following
> two commands:
>
> git format-patch -o /tmp/
501 - 600 of 1198 matches
Mail list logo