Hi Ben!
On Mon, Nov 06, 2017 at 11:03:02PM +, Ben Hutchings wrote:
> 3.16.50-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Linus Lüssing
>
> commit 54e22f265e872ae140755b3318521d400a094605 upstream.
[...]
>
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Timur Tabi
commit acf2c60a60b3d6d7080854b9483f37d99ded9b23 upstream.
do_div() requires that the first parameter is a 64-bit integer,
which but clkrate was defined as an
Hi Ben!
On Mon, Nov 06, 2017 at 11:03:02PM +, Ben Hutchings wrote:
> 3.16.50-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Linus Lüssing
>
> commit 54e22f265e872ae140755b3318521d400a094605 upstream.
[...]
> [bwh: Backported to 3.16:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Timur Tabi
commit acf2c60a60b3d6d7080854b9483f37d99ded9b23 upstream.
do_div() requires that the first parameter is a 64-bit integer,
which but clkrate was defined as an unsigned long. This
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 946e87981942552e526aca9cb6204f02a6c847cb upstream.
The verbose module parameter can be set to 2 for extremely verbose
messages so the type
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 946e87981942552e526aca9cb6204f02a6c847cb upstream.
The verbose module parameter can be set to 2 for extremely verbose
messages so the type should be int instead of bool.
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 67f08d690aa90e47a0e793fc63e2ecbe95d29839 upstream.
On 64 bit systems integers are generally still 32 bit but long values and
pointers are usually 64 bit.
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 67f08d690aa90e47a0e793fc63e2ecbe95d29839 upstream.
On 64 bit systems integers are generally still 32 bit but long values and
pointers are usually 64 bit. GCC warns when
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 6fc8ae787c589245ee3395630d2c428a1afab26c upstream.
When printing size_t values we should use the %zd or %zx format specifier
in order to ensure the value
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 6fc8ae787c589245ee3395630d2c428a1afab26c upstream.
When printing size_t values we should use the %zd or %zx format specifier
in order to ensure the value is displayed
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jin Yao
commit 80f62589fa52f530cffc50e78c0b5a2ae572d61e upstream.
When the jump instruction is displayed at the row 0 in annotate view,
the arrow is broken. An
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jin Yao
commit 80f62589fa52f530cffc50e78c0b5a2ae572d61e upstream.
When the jump instruction is displayed at the row 0 in annotate view,
the arrow is broken. An example:
16.86 │ ┌──je
On Mon, Nov 06, 2017 at 11:00:09AM -0800, Bjorn Andersson wrote:
> On Thu, Nov 2, 2017 at 7:12 AM, Kirill A. Shutemov
> wrote:
> [..]
> > Could you try the patch below instead?
> >
> > From 4a9d843f9d939d958612b0079ebe5743f265e1e0 Mon Sep 17 00:00:00 2001
> >
On 2017年11月07日 07:35, Shuah Khan wrote:
On 11/05/2017 03:08 AM, Lei Yang wrote:
I got below error message when building sync test:
make[1]: Entering directory `tools/testing/selftests/sync'
gcc -c sync.c -o tools/testing/selftests/sync/sync.o
sync.c:42:29: fatal error: linux/sync_file.h: No
On 2017年11月07日 07:35, Shuah Khan wrote:
On 11/05/2017 03:08 AM, Lei Yang wrote:
I got below error message when building sync test:
make[1]: Entering directory `tools/testing/selftests/sync'
gcc -c sync.c -o tools/testing/selftests/sync/sync.o
sync.c:42:29: fatal error: linux/sync_file.h: No
On Mon, Nov 06, 2017 at 11:00:09AM -0800, Bjorn Andersson wrote:
> On Thu, Nov 2, 2017 at 7:12 AM, Kirill A. Shutemov
> wrote:
> [..]
> > Could you try the patch below instead?
> >
> > From 4a9d843f9d939d958612b0079ebe5743f265e1e0 Mon Sep 17 00:00:00 2001
> > From: "Kirill A. Shutemov"
> > Date:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Stefan-Gabriel Mirea
commit d466d3c1217406b14b834335b5b4b33c0d45bd09 upstream.
In order to select the alternate voltage reference pair (VALTH/VALTL), the
right
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Stefan-Gabriel Mirea
commit d466d3c1217406b14b834335b5b4b33c0d45bd09 upstream.
In order to select the alternate voltage reference pair (VALTH/VALTL), the
right value for the REFSEL field in
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 906b268477bc03daaa04f739844c120fe4dbc991 upstream.
kernelci.org reports a warning for this driver, as it copies a local
variable into a 'const char *'
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 906b268477bc03daaa04f739844c120fe4dbc991 upstream.
kernelci.org reports a warning for this driver, as it copies a local
variable into a 'const char *' string:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit b629be5c8399d7c423b92135eb43a86c924d1cbc upstream.
There is a potential case where we might be failing to refill a
control block, leaving it with
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit eb03aa008561004257900983193d024e57abdd96 upstream.
For every pfn aligned to minimum_order, dissolve_free_huge_pages() will
call
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit b629be5c8399d7c423b92135eb43a86c924d1cbc upstream.
There is a potential case where we might be failing to refill a
control block, leaving it with both a NULL skb
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit eb03aa008561004257900983193d024e57abdd96 upstream.
For every pfn aligned to minimum_order, dissolve_free_huge_pages() will
call dissolve_free_huge_page() which takes
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Nikolay Aleksandrov
commit 31a4562d7408493c6377933ff2f7d7302dbdea80 upstream.
With 802.1ad support the vlan_ingress code started checking for vlan
protocol
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Nikolay Aleksandrov
commit 31a4562d7408493c6377933ff2f7d7302dbdea80 upstream.
With 802.1ad support the vlan_ingress code started checking for vlan
protocol mismatch which causes the current
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andrew Morton
commit 0f989f749b51ec1fd94bb5a42f8ad10c8b9f73cb upstream.
The patch "module: fix types of device tables aliases" newly requires that
invocations of
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andrew Morton
commit 0f989f749b51ec1fd94bb5a42f8ad10c8b9f73cb upstream.
The patch "module: fix types of device tables aliases" newly requires that
invocations of
MODULE_DEVICE_TABLE(type,
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit 824ba603573d910e32df75fe6a5e7d7ec2a0a6a7 upstream.
Add frag_size = skb_frag_size(frag) and use it when needed.
Signed-off-by: Petri Gynther
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Iván Briano
commit ccd4eb49f3392ebf989d58bd013a7bf44cdca4d6 upstream.
When PACKET_QDISC_BYPASS is not used, Tx queue selection will be done
before the packet is
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit 824ba603573d910e32df75fe6a5e7d7ec2a0a6a7 upstream.
Add frag_size = skb_frag_size(frag) and use it when needed.
Signed-off-by: Petri Gynther
Acked-by: Florian Fainelli
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Iván Briano
commit ccd4eb49f3392ebf989d58bd013a7bf44cdca4d6 upstream.
When PACKET_QDISC_BYPASS is not used, Tx queue selection will be done
before the packet is enqueued, taking into account
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit 55868120a3e5420bf5aa26a816c07d691579c9e6 upstream.
1. Add bytes_compl local variable to __bcmgenet_tx_reclaim() to collect
transmitted bytes.
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit 55868120a3e5420bf5aa26a816c07d691579c9e6 upstream.
1. Add bytes_compl local variable to __bcmgenet_tx_reclaim() to collect
transmitted bytes. dev->stats updates can
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
commit 876dbadd53a7102e2a84afc84ea2bd3ee6dc5636 upstream.
In case we fail to map a single fragment, we would be leaving the
transmit ring populated with stale
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
commit 876dbadd53a7102e2a84afc84ea2bd3ee6dc5636 upstream.
In case we fail to map a single fragment, we would be leaving the
transmit ring populated with stale entries.
This
On 2017年11月07日 07:46, Shuah Khan wrote:
On 11/05/2017 03:56 AM, Lei Yang wrote:
Replace '%d' by '%zu' to fix the following compilation warning.
memfd_test.c:517:3: warning: format ‘%d’ expects argument of
type ‘int’,but argument 2 has type ‘size_t’ [-Wformat=]
printf("malloc(%d) failed:
On 2017年11月07日 07:46, Shuah Khan wrote:
On 11/05/2017 03:56 AM, Lei Yang wrote:
Replace '%d' by '%zu' to fix the following compilation warning.
memfd_test.c:517:3: warning: format ‘%d’ expects argument of
type ‘int’,but argument 2 has type ‘size_t’ [-Wformat=]
printf("malloc(%d) failed:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 065bd8c28ba37d04c9a5b732173c1508954b1f58 upstream.
The mlx5 driver passes a string pointer in through a 'u64' variable,
which on 32-bit machines causes a
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 065bd8c28ba37d04c9a5b732173c1508954b1f58 upstream.
The mlx5 driver passes a string pointer in through a 'u64' variable,
which on 32-bit machines causes a build warning:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit 66d06757d9eb74a29775737b8c770e3b57e536d9 upstream.
1. Use c_index and ring->c_index to determine how many TxCBs/TxBDs are
ready for cleanup
-
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Luis de Bethencourt
commit 7789cd39274c51bf475411fe22a8ee7255082809 upstream.
Fix a smatch warning:
drivers/scsi/mvsas/mv_sas.c:740 mvs_task_prep() warn: curly braces
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit 66d06757d9eb74a29775737b8c770e3b57e536d9 upstream.
1. Use c_index and ring->c_index to determine how many TxCBs/TxBDs are
ready for cleanup
- c_index = the current
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Luis de Bethencourt
commit 7789cd39274c51bf475411fe22a8ee7255082809 upstream.
Fix a smatch warning:
drivers/scsi/mvsas/mv_sas.c:740 mvs_task_prep() warn: curly braces intended?
The code is
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit ae67bf0188cbb9d1786bdfcca9e1976cb36ee327 upstream.
There is no need to have both bcmgenet_xmit_single() and
bcmgenet_xmit_frag() perform a
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit ae67bf0188cbb9d1786bdfcca9e1976cb36ee327 upstream.
There is no need to have both bcmgenet_xmit_single() and
bcmgenet_xmit_frag() perform a free_bds decrement and a
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 3e7a8716e20b759eec0ad88145255bb33174f0c8 upstream.
Not all architectures are able to call __builtin_return_address().
On ARM, the mISDN code produces this
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 3e7a8716e20b759eec0ad88145255bb33174f0c8 upstream.
Not all architectures are able to call __builtin_return_address().
On ARM, the mISDN code produces this warning:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
commit e6c97234d1b18d4751671df15d52e29daa8a7ba8 upstream.
Reduce stack use by using kmemdup and not using a very
large struct on stack.
In function
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Paul Gortmaker
commit 09c20c032b0f753969ae778d9783d946f054d7fe upstream.
Currently the match() function supports a leading * to match any
prefix and a trailing *
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
commit e6c97234d1b18d4751671df15d52e29daa8a7ba8 upstream.
Reduce stack use by using kmemdup and not using a very
large struct on stack.
In function ‘i40e_dbg_dump_desc’:
warning:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Paul Gortmaker
commit 09c20c032b0f753969ae778d9783d946f054d7fe upstream.
Currently the match() function supports a leading * to match any
prefix and a trailing * to match any suffix. However
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit d6707bec598649450ee0887bf11896e525777874 upstream.
Currently, bcmgenet_desc_rx() calls bcmgenet_rx_refill() at the end of
Rx packet processing loop,
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Petri Gynther
commit d6707bec598649450ee0887bf11896e525777874 upstream.
Currently, bcmgenet_desc_rx() calls bcmgenet_rx_refill() at the end of
Rx packet processing loop, after the current Rx
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
commit f48bed16a756f5bc0244acd581f61968f7d7c2a4 upstream.
Since the skb is attached to the first control block of a fragmented
skb it is possible that the skb
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
commit f48bed16a756f5bc0244acd581f61968f7d7c2a4 upstream.
Since the skb is attached to the first control block of a fragmented
skb it is possible that the skb could be freed when
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 8e0cc8c326d99e41468c96fea9785ab78883a281 upstream.
gcc points out code that is not indented the way it is
interpreted:
net/caif/cfpkt_skbuff.c: In
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hannes Reinecke
commit 36dd5acd196574d41de3e81d8264df475bbb7123 upstream.
If no user settings are found it's pointless trying to
read them from flash. So skip that step.
This
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 8e0cc8c326d99e41468c96fea9785ab78883a281 upstream.
gcc points out code that is not indented the way it is
interpreted:
net/caif/cfpkt_skbuff.c: In function
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hannes Reinecke
commit 36dd5acd196574d41de3e81d8264df475bbb7123 upstream.
If no user settings are found it's pointless trying to
read them from flash. So skip that step.
This also fixes a
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Paul Gortmaker
commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream.
Currently an allyesconfig build [gcc-4.9.1] can generate the following:
WARNING:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Paul Gortmaker
commit 4a3893d069b788f3570c19c12d9e986e8e15870f upstream.
Currently an allyesconfig build [gcc-4.9.1] can generate the following:
WARNING: vmlinux.o(.text.unlikely+0x3864):
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit d43e6fb4ac4abfe4ef7c102833ed02330ad701e0 upstream.
The #warning was present 10 years ago when the driver first got merged.
As the platform is rather
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Manuel Schölling
commit 9f8b93cb32e088d3377c86fabb666b884bac0f12 upstream.
The time comparsion functions require arguments of type unsigned long
instead of (signed)
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit d43e6fb4ac4abfe4ef7c102833ed02330ad701e0 upstream.
The #warning was present 10 years ago when the driver first got merged.
As the platform is rather obsolete by now, it
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Manuel Schölling
commit 9f8b93cb32e088d3377c86fabb666b884bac0f12 upstream.
The time comparsion functions require arguments of type unsigned long
instead of (signed) long.
Signed-off-by:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jeff Kirsher
commit 5f5316fcd08ef74b282adf6774956431fac62663 upstream.
Resolves compile warning about use of a deprecated function call:
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jeff Kirsher
commit 5f5316fcd08ef74b282adf6774956431fac62663 upstream.
Resolves compile warning about use of a deprecated function call:
drivers/net/ethernet/amd/nmclan_cs.c: In function
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Atsushi Nemoto
commit e4c4c9c15ebe8ec03b7f5bf36e079052cc88217c upstream.
Signed-off-by: Atsushi Nemoto
Signed-off-by: Brian Norris
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Atsushi Nemoto
commit e4c4c9c15ebe8ec03b7f5bf36e079052cc88217c upstream.
Signed-off-by: Atsushi Nemoto
Signed-off-by: Brian Norris
Signed-off-by: Arnd Bergmann
Signed-off-by: Ben Hutchings
On Monday, November 6, 2017 2:46:48 PM CET Geert Uytterhoeven wrote:
> Hi Rafael,
>
> On Fri, Nov 3, 2017 at 12:42 PM, Rafael J. Wysocki wrote:
> > On Thursday, November 2, 2017 12:00:27 AM CET Rafael J. Wysocki wrote:
> >> This series is a replacement for commit 0cc2b4e5a020
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
In 3.16-stable, we get this warning:
drivers/scsi/scsi_tgt_if.c:289:36: warning: passing argument 1 of
'virt_to_phys' makes pointer from integer without a cast
On Monday, November 6, 2017 2:46:48 PM CET Geert Uytterhoeven wrote:
> Hi Rafael,
>
> On Fri, Nov 3, 2017 at 12:42 PM, Rafael J. Wysocki wrote:
> > On Thursday, November 2, 2017 12:00:27 AM CET Rafael J. Wysocki wrote:
> >> This series is a replacement for commit 0cc2b4e5a020 (PM / QoS: Fix
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
In 3.16-stable, we get this warning:
drivers/scsi/scsi_tgt_if.c:289:36: warning: passing argument 1 of
'virt_to_phys' makes pointer from integer without a cast
On Monday, November 6, 2017 6:47:35 PM CET Reinette Chatre wrote:
> Hi Rafael,
>
> On 11/4/2017 5:34 AM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > The special value of 0 for device resume latency PM QoS means
> > "no restriction", but there are two
On Monday, November 6, 2017 6:47:35 PM CET Reinette Chatre wrote:
> Hi Rafael,
>
> On 11/4/2017 5:34 AM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > The special value of 0 for device resume latency PM QoS means
> > "no restriction", but there are two problems with that.
> >
>
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit e03c2da6574223081b786960e39c1e5ecf5d492d upstream.
non-x86 builds want the #warning in the IPS code about compiling on the wrong
architecture
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit e03c2da6574223081b786960e39c1e5ecf5d492d upstream.
non-x86 builds want the #warning in the IPS code about compiling on the wrong
architecture removed because it keeps
Hi Gustavo,
On Thu, Oct 19, 2017 at 09:06:16AM -0500, Gustavo A. R. Silva wrote:
> diff --git a/net/netfilter/ipset/ip_set_core.c
> b/net/netfilter/ipset/ip_set_core.c
> index cf84f7b..72f654a 100644
> --- a/net/netfilter/ipset/ip_set_core.c
> +++ b/net/netfilter/ipset/ip_set_core.c
> @@ -1386,7
Hi Gustavo,
On Thu, Oct 19, 2017 at 09:06:16AM -0500, Gustavo A. R. Silva wrote:
> diff --git a/net/netfilter/ipset/ip_set_core.c
> b/net/netfilter/ipset/ip_set_core.c
> index cf84f7b..72f654a 100644
> --- a/net/netfilter/ipset/ip_set_core.c
> +++ b/net/netfilter/ipset/ip_set_core.c
> @@ -1386,7
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
The driver uses a 32-bit variable to store a pointer, causing a couple of
warnings:
../drivers/staging/bcm/CmHost.c: In function 'StoreCmControlResponseMessage':
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Luis de Bethencourt
commit 8c182ae20791d638c07ff499709c4a1d4697bd7c upstream.
For loop is outside of the else branch of the above conditional statement.
Fixing
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 53bd4a004ee5ff0f71a858de78faac98924b4a87 upstream.
>From the indenting, it looks like curly braces were intended here.
Signed-off-by: Dan
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
The driver uses a 32-bit variable to store a pointer, causing a couple of
warnings:
../drivers/staging/bcm/CmHost.c: In function 'StoreCmControlResponseMessage':
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Luis de Bethencourt
commit 8c182ae20791d638c07ff499709c4a1d4697bd7c upstream.
For loop is outside of the else branch of the above conditional statement.
Fixing misleading indentation.
Fix a
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 53bd4a004ee5ff0f71a858de78faac98924b4a87 upstream.
>From the indenting, it looks like curly braces were intended here.
Signed-off-by: Dan Carpenter
Signed-off-by: Greg
Andrew,
Here is a new get_user_pages api for cases where a driver intends to
keep an elevated page count indefinitely. This is distinct from usages
like iov_iter_get_pages where the elevated page counts are transient.
The iov_iter_get_pages cases immediately turn around and submit the
pages to a
Until there is a solution to the dma-to-dax vs truncate problem it is
not safe to allow long standing memory registrations against
filesytem-dax vmas. Device-dax vmas do not have this problem and are
explicitly allowed.
This is temporary until a "memory registration with layout-lease"
mechanism
Andrew,
Here is a new get_user_pages api for cases where a driver intends to
keep an elevated page count indefinitely. This is distinct from usages
like iov_iter_get_pages where the elevated page counts are transient.
The iov_iter_get_pages cases immediately turn around and submit the
pages to a
Until there is a solution to the dma-to-dax vs truncate problem it is
not safe to allow long standing memory registrations against
filesytem-dax vmas. Device-dax vmas do not have this problem and are
explicitly allowed.
This is temporary until a "memory registration with layout-lease"
mechanism
Until there is a solution to the dma-to-dax vs truncate problem it is
not safe to allow RDMA to create long standing memory registrations
against filesytem-dax vmas.
Cc: Sean Hefty
Cc: Doug Ledford
Cc: Hal Rosenstock
Cc: Jeff
V4L2 memory registrations are incompatible with filesystem-dax that
needs the ability to revoke dma access to a mapping at will, or
otherwise allow the kernel to wait for completion of DMA. The
filesystem-dax implementation breaks the traditional solution of
truncate of active file backed mappings
Until there is a solution to the dma-to-dax vs truncate problem it is
not safe to allow RDMA to create long standing memory registrations
against filesytem-dax vmas.
Cc: Sean Hefty
Cc: Doug Ledford
Cc: Hal Rosenstock
Cc: Jeff Moyer
Cc: Ross Zwisler
Cc: Jason Gunthorpe
Cc:
Cc:
Reported-by:
V4L2 memory registrations are incompatible with filesystem-dax that
needs the ability to revoke dma access to a mapping at will, or
otherwise allow the kernel to wait for completion of DMA. The
filesystem-dax implementation breaks the traditional solution of
truncate of active file backed mappings
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 96a30175f927facfb421655ef08b7a0fe546fbed upstream.
A recent patch tried to work around a valid warning for the use of a
deprecated interface by blindly
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 96a30175f927facfb421655ef08b7a0fe546fbed upstream.
A recent patch tried to work around a valid warning for the use of a
deprecated interface by blindly changing from the
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Anil Gurumurthy
commit b7f4d6343820af5c2dc3979e91d85e71e638cd3d upstream.
Signed-off-by: Anil Gurumurthy
Tested-by : Sudarasana
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Anil Gurumurthy
commit b7f4d6343820af5c2dc3979e91d85e71e638cd3d upstream.
Signed-off-by: Anil Gurumurthy
Tested-by : Sudarasana Kalluru
Reviewed-by: Ewan D. Milne
Signed-off-by: James
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
We get a warning about a broken pointer conversion on 64-bit architectures:
drivers/message/i2o/i2o_config.c: In function 'i2o_cfg_passthru':
3.16.50-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
The advansys driver was converted to the proper DMA API in linux-4.2, but
the 3.18-stable kernel still warns about this:
drivers/scsi/advansys.c:71:2: warning:
401 - 500 of 3176 matches
Mail list logo