From: Markus Elfring
Date: Sat, 1 Oct 2016 12:42:50 +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: Sat, 1 Oct 2016 14:38:12 +0200
Adjust a jump label according to the Linux coding style convention
Signed-off-by: Markus Elfring
---
drivers/md/md-cluster.c | 4 ++--
1 file changed, 2 insertions(+), 2
On 10/1/2016 2:19 AM, Vinod Koul wrote:
>> Making it atomic so that it can be updated from multiple contexts.
> How is it multiple contexts? It's either existing context of MSI, not both!
>
I was trying to mean multiple processor contexts here. The driver allocates 11
MSI interrupts. Each MSI
On 2016-09-30 14:43, Robin Murphy wrote:
+* so LSE needs an explicit barrier here as well. Without this, the
+* changed contents of the area protected by the spinlock could be
+* observed prior to the lock.
What is that last sentence supposed to mean? If the lock is
On 28/09/16 19:00, William Breathitt Gray wrote:
> The ACCES 104-QUAD-8 is a general purpose quadrature encoder
> counter/interface board. The 104-QUAD-8 is capable of monitoring the
> outputs of eight encoders via four on-board LSI/CSI LS7266R1 24-bit
> dual-axis quadrature counter chips. Core
On 28/09/16 18:59, William Breathitt Gray wrote:
> Quadrature encoders, such as rotary encoders and linear encoders, are
> devices which are capable of encoding the relative position and
> direction of motion of a shaft. This patch introduces several IIO
> constants for supporting quadrature
Hi Tejun,
as we discussed, i include some discussion content in the commit message.
could you give some new comments or acknowledgment for this patch?
On 2016/9/30 19:30, zijun_hu wrote:
> From: zijun_hu
>
> it will cause memory leakage for pcpu_embed_first_chunk() to go to
Hi Russell,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f51fdffad5b7709d0ade40736b58a2da2707fa15
commit: b2c0b2cbb282f0cf42518ffacbe197e6f2884168 nmi: create generic NMI
backtrace implementation
date: 1 year,
Add node corresponding to OCOTP IP block.
Signed-off-by: Andrey Smirnov
---
arch/arm/boot/dts/vfxxx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
index 2c13ec6..75850c0 100644
---
Since padata has a maximum number of inflight jobs, currently 1000, it's
very useful to know how many jobs are currently queued up. This adds a
simple helper function to expose this information.
Signed-off-by: Jason A. Donenfeld
---
include/linux/padata.h | 2 ++
Because test for color support of the running shell does not aware ANSI
type terminals, it does not print colorful messages on some environemnt.
This commit modifies the test to aware ANSI type terminal, too.
Signed-off-by: SeongJae Park
---
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f51fdffad5b7709d0ade40736b58a2da2707fa15
commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error
with binutils 2.24 and earlier
On Sat, Oct 01, 2016 at 08:00:49PM -0400, Rich Felker wrote:
> > > > > > - During the whole sequence, hrtimer expiration times are being set
> > > > > > to
> > > > > > exact jiffies (@ 100 Hz), whereas before it they're quite
> > > > > > arbitrary.
> > > > >
> > > > > When a CPU goes into
Hi Alex,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f51fdffad5b7709d0ade40736b58a2da2707fa15
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation
of a VDSO
date: 11 months ago
On 10/01/2016 02:47 AM, Thomas Gleixner wrote:
On Fri, 30 Sep 2016, Waiman Long wrote:
+ WRITE_ONCE(state->owner, current);
+ preempt_disable();
+ for (;;) {
+ ret = futex_trylock(uaddr, vpid,, true);
Did you actually read what I said? You CANNOT access
I2C3 bus was only brought out in revision A1 of the board and revision
B1 only brings out 3 I2C busses (I2C0, I2C1 and I2C2).
Signed-off-by: Andrey Smirnov
---
arch/arm/boot/dts/vf610-zii-dev-rev-b.dts | 14 --
1 file changed, 14 deletions(-)
diff --git
Hi Dave,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f51fdffad5b7709d0ade40736b58a2da2707fa15
commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new
lightweight SGL iterators
date: 5
Rename CamelCased macro roundedDiv to rounded_div.
This issue was found by checkpatch.pl
Signed-off-by: Moshe Green
---
drivers/staging/sm750fb/ddk750_chip.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/sm750fb/ddk750_chip.c
This is in preparation for the patch that transitions
vfs timestamps to use 64 bit time and hence make them
y2038 safe.
CURRENT_TIME macro will be deleted before merging the
aforementioned patch.
Filesystem times will use current_fs_time() instead of
CURRENT_TIME.
Use ktime_get_real_ts() here as
Drop the variable irq which ceased to be a parameter in bd0b9ac4.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
drivers/irqchip/irq-metag-ext.c |1 -
1 file changed, 1 deletion(-)
diff --git
Correct spelling mistakes in the documentation associated with two
functions in fs/crypto/crypto.c.
Use actual function names in the documentation associated with two
functions in fs/crypto/fname.c.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
Use the names of the corresponding functions.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
drivers/gpu/drm/omapdrm/omap_drv.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Adjust variables to correspond to the names used in the parameter list of
the function. Move the struct device * variable up to the place where it
appears in the parameter list.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
Rename a variable in the documentation so that it corresponds to the name
of the function parameter.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
lib/nlattr.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Use the actual function name in the function documentation.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
drivers/clk/sunxi/clk-mod0.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
These patches fix cases where the documentation above a function definition
is not consistent with the function header. Issues are detected using the
semantic patch below (http://coccinelle.lip6.fr/). Basically, the semantic
patch parses a file to find comments, then matches each function
This is in preparation for the change that transitions
filesystem timestamps to use 64 bit time and hence make
them y2038 safe.
CURRENT_TIME macro will be deleted before merging the
aforementioned patch.
Filesystems will use current_time() instead of
CURRENT_TIME.
Use ktime_get_real_seconds()
Fix various inconsistencies in the documentation associated with various
functions.
In the case of fs/ubifs/lprops.c, the second parameter of
ubifs_get_lp_stats was renamed from st to lst in 84abf972.
In the case of fs/ubifs/lpt_commit.c, the excess variables have never
existed in the associated
On Sat, 2016-10-01 at 21:46 +0200, Julia Lawall wrote:
> These patches fix cases where the documentation above a function definition
> is not consistent with the function header. Issues are detected using the
> semantic patch below (http://coccinelle.lip6.fr/). Basically, the semantic
> patch
Joe Perches writes:
> On Sat, 2016-10-01 at 14:53 -0400, Jes Sorensen wrote:
>> Joe Perches writes:
>> > Make the init arrays const to reduce data.
>> > $ size drivers/net/wireless/realtek/rtl8xxxu/built-in.o*
>> > (allyesconfig: x86-32)
>> > text
On 10/01/2016 12:04 PM, Dmitry Torokhov wrote:
On Sat, Oct 01, 2016 at 10:27:42AM -0700, Andrew Duggan wrote:
On Fri, Sep 30, 2016, at 08:44 PM, Guenter Roeck wrote:
On 09/30/2016 04:02 PM, Dmitry Torokhov wrote:
On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote:
On Thu, Sep
From: Rik van Riel
Need to ensure that the FPU save code and the lazy restore code
do not use invalid kernel or floating point register state and
copy it over to the other location.
I am pretty sure this is incomplete.
Signed-off-by: Rik van Riel
---
This series is an attempt at making the x86 FPU context switching
code much lazier. By only reloading the FPU context when a task
switches to user mode, we can avoid switching FPU context for tasks
that spin in kernel mode, and avoid reloading the FPU context for
tasks that get interrupted by a
Drop the variable irq which ceased to be a parameter in commit bd0b9ac405e1
("genirq: Remove irq argument from irq flow handlers")
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
Acked-by: James Hogan
---
From: Rik van Riel
Most kernel FPU contexts are transient, but a KVM VCPU context
persists. Add a kernel FPU argument to __kernel_fpu_begin, so
we can know whether or not the KVM VCPU context got clobbered
by another kernel FPU context.
Signed-off-by: Rik van Riel
From: Rik van Riel
Move all handling of the next state FPU state handling into
switch_fpu_finish, in preparation for more lazily switching
FPU states.
CR0.TS state is mirrored in a per-cpu variable, instead of
being passed around in a local variable, because that will
not be
Removing warnings caught by checkpatch.pl
Signed-off-by: Harman Kalra
---
drivers/staging/media/omap4iss/iss_video.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/media/omap4iss/iss_video.c
On Sat, 2016-10-01 at 16:32 -0400, Jes Sorensen wrote:
> Your output shows it moving to the text segment - if it's in a different
> segment, eg. rodata, you should use output demonstrating that to justify
> the change.
For size, rodata _is_ text
From: Rafał Miłecki
Broadcom's Northstar XHCI controllers seem to need a special start
procedure to work correctly. There isn't any official documentation on
this, the problem is that controller doesn't detect any connected
devices with default setup. Moreover connecting USB
On Sat, 2016-10-01 at 14:53 -0400, Jes Sorensen wrote:
> Joe Perches writes:
> > Make the init arrays const to reduce data.
> > $ size drivers/net/wireless/realtek/rtl8xxxu/built-in.o* (allyesconfig:
> > x86-32)
> > textdata bss dec hex filename
> >
Delete a reference to a variable that has never been used by the function
in the first case, and rename a variable to that of the corresponding
parameter name in the second case.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
Adjust the documentation to use the actual function names.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
drivers/clk/keystone/pll.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Use the correct function name in one case and adjust a variable name to
that of the corresponding function parameter in another case.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
drivers/mfd/tc3589x.c |4 ++--
1 file
In drivers/power/supply/ab8500_fg.c, fix two typos and adjust the function
name in two cases to correspond to the names of the defined functions.
In drivers/power/supply/power_supply_core.c, change two variable names to
the names of the corresponding parameters.
Issue detected using Coccinelle
The associated function, vic_init_cascaded, has never had a variable
irq_start.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
drivers/irqchip/irq-vic.c |1 -
1 file changed, 1 deletion(-)
diff --git
Adjust the documentation to use the names that appear in the function
parameter list.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
drivers/dma-buf/sw_sync.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Use the actual function name and reorder the listed variables to correspond
to their order in the function parameter list.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia Lawall
---
lib/lru_cache.c |4 ++--
1 file changed, 2
In the first case, rename the second variable to correspond to the name
found in the function parameter list.
In the remaining cases, reorder the variables to correspond to their order
in the parameter list.
Issue detected using Coccinelle (http://coccinelle.lip6.fr/)
Signed-off-by: Julia
I am Mrs. Kimberly Hills the wife of late Engineer William Hills We has been
married for years before his
sudden death although we were childless. I have been diagnosed with cancer and
I have been battling with the
sickness when my late lovely husband was alive.
My Husband left the sum of
Hi Julia,
On 1 October 2016 at 20:46, Julia Lawall wrote:
> Drop the variable irq which ceased to be a parameter in bd0b9ac4.
I think 12 nibbles of the hash is recommended now due to collisions,
as is quoting the subject line, e.g. commit bd0b9ac405e1 ("genirq:
Remove irq
On Sat, 1 Oct 2016, Joe Perches wrote:
> On Sat, 2016-10-01 at 21:46 +0200, Julia Lawall wrote:
> > These patches fix cases where the documentation above a function definition
> > is not consistent with the function header. Issues are detected using the
> > semantic patch below
Dne 1.10.2016 v 09:10 Jonathan Corbet napsal(a):
> On Fri, 30 Sep 2016 07:57:51 -0600
> Shuah Khan wrote:
>
>>> This patch series contains the last 2 patches to complete moving runnable
>>> code from Documentation to selftests, samples, and tools.
>>>
>>> The first patch
From: Rik van Riel
Delay the loading of FPU registers until a process switches back to
userspace. This allows us to skip FPU saving & restoring for kernel
threads, the idle task, and tasks that are spinning in kernel space.
It also allows us to not repeatedly save & restore the
Fix various inconsistencies in the documentation associated with various
functions.
In the case of fs/ubifs/lprops.c, the second parameter of
ubifs_get_lp_stats was renamed from st to lst in commit 84abf972ccff
("UBIFS: add re-mount debugging checks")
In the case of fs/ubifs/lpt_commit.c, the
From: Rik van Riel
When the FPU register set has not been touched by anybody else,
we can lazily skip the restore.
Intel has a number of clever optimizations to reduce the FPU
restore overhead, but those optimizations do not work across
the guest/host virtualization boundary,
Dne 21.9.2016 v 17:48 Julia Lawall napsal(a):
> Memdup_user encapsulates a memory allocation with the flag GFP_KERNEL, so
> only allow this flag in the original code.
>
> Signed-off-by: Julia Lawall
Applied to kbuild.git#misc.
Thanks,
Michal
Dne 22.9.2016 v 10:28 Julia Lawall napsal(a):
> pm_runtime.cocci starts with one rule that searches for a variety of
> functions calls, followed by various rules that report errors. Previously,
> the only connection between the first rule and the rest was to check that
> the first rule had
On 30/09/16 03:39, R. Parameswaran wrote:
>
>>> + /* Adjust MTU, factor overhead - underlay L3 hdr, overlay L2 hdr*/
>>> + if (tunnel->sock->sk_family == AF_INET)
>>> + overhead += (ETH_HLEN + sizeof(struct iphdr));
>>> + else if (tunnel->sock->sk_family == AF_INET6)
>>> +
CURRENT_TIME is not y2038 safe.
Replace it with ktime_get_real_ts64().
Inode time formats are already 64 bit long and
accommodates time64_t.
Signed-off-by: Deepa Dinamani
Cc: Evgeniy Dushistov
---
fs/ufs/ialloc.c | 6 --
1 file changed, 4
Make the init arrays const to reduce data.
$ size drivers/net/wireless/realtek/rtl8xxxu/built-in.o* (allyesconfig: x86-32)
textdata bss dec hex filename
80107 13651 58 93816 16e78
drivers/net/wireless/realtek/rtl8xxxu/built-in.o.new
65303 28435 58 93796
On Wednesday 28 September 2016 04:05 PM, Peter Ujfalusi wrote:
> Hi,
>
> The drivers for davinci MMC and SPI have been converted to the new DMAengine
> API
> and no longer rely on the IORESOURCE_DMA.
> This is the case for at least one release cycle so now we can remove the
> IORESOURCE_DMA for
This reverts commit 9e5ed6d1fb87 ("ACPI,PCI,IRQ: remove SCI penalize
function"). SCI penalty API was replaced by the runtime penalty calculation
based on the value of acpi_gbl_FADT.sci_interrupt.
acpi_gbl_FADT.sci_interrupt type does not get updated at the right time
for some platforms and
This reverts commit 5c5087a55390 ("ACPI,PCI,IRQ: reduce static IRQ array
size to 16").
The code maintains a fixed size array for IRQ penalties. The array
gets updated by external calls such as acpi_penalize_sci_irq,
acpi_penalize_isa_irq to reflect the actual interrupt usage of the
system. Since
The change introduced in commit 103544d86976 ("ACPI,PCI,IRQ: reduce
resource requirements") removed PCI_USING penalty from
acpi_pci_link_allocate function as there is no longer a fixed size penalty
array for both PCI and IRQ interrupts.
We need to add the PCI_USING penalty for ISA interrupts too
On Sat, Oct 1, 2016, at 10:45 AM, Guenter Roeck wrote:
> On 10/01/2016 10:27 AM, Andrew Duggan wrote:
> >
> >
> > On Fri, Sep 30, 2016, at 08:44 PM, Guenter Roeck wrote:
> >> On 09/30/2016 04:02 PM, Dmitry Torokhov wrote:
> >>> On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote:
>
On Sat, Oct 01, 2016 at 01:05:08PM -0400, Rich Felker wrote:
> On Fri, Sep 30, 2016 at 06:48:35AM -0700, Paul E. McKenney wrote:
> > On Fri, Sep 30, 2016 at 03:15:11PM +0200, Thomas Gleixner wrote:
> > > On Tue, 27 Sep 2016, Rich Felker wrote:
> > > > I've managed to get a trace with a stall. I'm
Hi Brent,
Evidently my questions weren't sufficiently clear; even with your answers it's
not clear to me what precise issue you're attempting to solve. I've tried to be
more specific this time.
At a high-level, can you clarify whether you're attempting to solve is:
(a) a functional correctness
On Sat, Oct 01, 2016 at 10:23:34AM -0700, Deepa Dinamani wrote:
> btrfs_root_item maintains the ctime for root updates.
> This is not part of vfs_inode.
>
> Since current_time() uses struct inode* as an argument
> as Linus suggested, this cannot be used to update root
> times unless, we modify
Hi Joe,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f51fdffad5b7709d0ade40736b58a2da2707fa15
commit: cb984d101b30eb7478d32df56a0023e4603cba7f compiler-gcc: integrate the
various compiler-gcc[345].h files
Joe Perches writes:
> On Sat, 2016-10-01 at 16:32 -0400, Jes Sorensen wrote:
>> Your output shows it moving to the text segment - if it's in a different
>> segment, eg. rodata, you should use output demonstrating that to justify
>> the change.
>
> For size, rodata _is_ text
On Oct 1, 2016 1:49 PM, wrote:
>
> From: Rik van Riel
>
> Move all handling of the next state FPU state handling into
> switch_fpu_finish, in preparation for more lazily switching
> FPU states.
>
> CR0.TS state is mirrored in a per-cpu variable, instead of
>
On Sat, Oct 1, 2016 at 9:43 AM, Lukas Wunner wrote:
> On Thu, Sep 29, 2016 at 02:38:04AM +0200, Rafael J. Wysocki wrote:
>> +static int device_reorder_to_tail(struct device *dev, void *not_used)
>> +{
>> + struct device_link *link;
>> +
>> + /*
>> + * Devices that
CURRENT_TIME_SEC is not y2038 safe.
Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds
in segment timestamps used by GC algorithm including the
segment mtime timestamps.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: Jaegeuk Kim
struct timespec is not y2038 safe.
Use time64_t which is y2038 safe to represent orphan
scan times.
time64_t is sufficient here as only the seconds delta
times are relevant.
Also use appropriate time functions that return time in
time64_t format. Time functions now return monotonic
time instead
struct timespec is not y2038 safe.
Audit timestamps are recorded in string format into
an audit buffer for a given context.
These mark the entry timestamps for the syscalls.
Use y2038 safe struct timespec64 to represent the times.
The log strings can handle this transition as strings can
hold upto
CURRENT_TIME is not y2038 safe.
Use y2038 safe ktime_get_real_seconds() here for timestamps.
struct heartbeat_block's hb_seq and deletetion time are already
64 bits wide and accommodate times beyond y2038.
Also use y2038 safe ktime_get_real_ts64() for on disk inode
timestamps.
These are also
On Sat, Oct 1, 2016 at 1:31 PM, wrote:
> From: Rik van Riel
>
> Delay the loading of FPU registers until a process switches back to
> userspace. This allows us to skip FPU saving & restoring for kernel
> threads, the idle task, and tasks that are spinning in
Hi Nicolas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f51fdffad5b7709d0ade40736b58a2da2707fa15
commit: 461a5e51060c93f5844113f4be9dba513cc92830 do_div(): generic optimization
for constant divisor on 32-bit
boot_time is represented as a struct timespec.
struct timespec and CURRENT_TIME are not y2038 safe.
Overall, the plan is to use timespec64 and ktime_t for
all internal kernel representation of timestamps.
CURRENT_TIME will also be removed.
boot_time is used to construct the nfs client boot
trace timestamps use struct timespec and CURRENT_TIME which
are not y2038 safe.
These timestamps are only part of the trace log on the machine
and are not shared with the fnic.
Replace then with y2038 safe struct timespec64 and
ktime_get_real_ts64(), respectively.
Signed-off-by: Deepa Dinamani
On Sat, Oct 01, 2016 at 10:58:37AM -0700, Paul E. McKenney wrote:
> On Sat, Oct 01, 2016 at 01:05:08PM -0400, Rich Felker wrote:
> > On Fri, Sep 30, 2016 at 06:48:35AM -0700, Paul E. McKenney wrote:
> > > On Fri, Sep 30, 2016 at 03:15:11PM +0200, Thomas Gleixner wrote:
> > > > On Tue, 27 Sep 2016,
On Sat, 2016-10-01 at 16:44 -0700, Andy Lutomirski wrote:
> On Sat, Oct 1, 2016 at 1:31 PM, wrote:
> >
> > #define CREATE_TRACE_POINTS
> > #include
> > @@ -197,6 +198,9 @@ __visible inline void
> > prepare_exit_to_usermode(struct pt_regs *regs)
> > if
On Sat, Sep 24, 2016 at 12:37:05PM +0800, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/dma/virt-dma.c:22:14: warning: no previous prototype for
> 'vchan_tx_submit' [-Wmissing-prototypes]
> drivers/dma/virt-dma.c:52:5: warning: no previous prototype for
>
On Wed, Sep 28, 2016 at 10:12:41PM -0400, Sinan Kaya wrote:
> Configure the DMA bindings for the device tree based firmware.
>
> Signed-off-by: Sinan Kaya
> ---
> drivers/dma/qcom/hidma_mgmt.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git
On Wed, Sep 28, 2016 at 10:12:42PM -0400, Sinan Kaya wrote:
> Getting ready for the MSI interrupts. The pending_tre_count is used
> in the interrupt handler to make sure all outstanding requests are
> serviced.
>
> Making it atomic so that it can be updated from multiple contexts.
How is it
Please click outlookteam.ulcraft.com to update your outlook account to
the new secured version.
Thank You
On Fri, 30 Sep 2016, Waiman Long wrote:
> + WRITE_ONCE(state->owner, current);
> + preempt_disable();
> + for (;;) {
> + ret = futex_trylock(uaddr, vpid, , true);
Did you actually read what I said? You CANNOT access userspace in a preempt
disabled region without disabling
On Fri, 30 Sep 2016 07:57:51 -0600
Shuah Khan wrote:
> > This patch series contains the last 2 patches to complete moving runnable
> > code from Documentation to selftests, samples, and tools.
> >
> > The first patch moves blackfin gptimers-example to samples and removes
> >
From: Dmitry Torokhov
Date: Fri, 30 Sep 2016 15:24:31 -0700
> From: Tyler Hicks
>
> The capability check should not be audited since it is only being used
> to determine the inode permissions. A failed check does not indicate a
> violation of security policy but, when an LSM is enabled, a
One final fix before 4.8: there's a memory leak triggered by turning
scsi mq off due to the fact that we assume on host release that the
already running hosts weren't mq based because that's the state of the
global flag (even though they were), so fix it by tracking this on a
per host host basis.
From: Markus Elfring
Date: Sat, 1 Oct 2016 09:35:43 +0200
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (9):
Use kmalloc_array() in realloc_argv()
Reduce the scope for a variable in dm_table_verify_integrity()
Delete an unnecessary
From: Markus Elfring
Date: Sat, 1 Oct 2016 06:47:16 +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 software.
On Thu, Sep 29, 2016 at 02:38:04AM +0200, Rafael J. Wysocki wrote:
> +static int device_reorder_to_tail(struct device *dev, void *not_used)
> +{
> + struct device_link *link;
> +
> + /*
> + * Devices that have not been registered yet will be put to the ends
> + * of the lists
From: Markus Elfring
Date: Sat, 1 Oct 2016 07:10:43 +0200
Move the definition for the variable "template_disk" into an if branch
so that an extra initialisation can be avoided at the beginning
by this refactoring.
Signed-off-by: Markus Elfring
---
drivers/md/dm-table.c | 5 ++---
1 file
From: Markus Elfring
Date: Sat, 1 Oct 2016 07:25:43 +0200
The local variable "template_disk" is reassigned by a statement
at the beginning. Thus omit the explicit initialisation.
Signed-off-by: Markus Elfring
---
drivers/md/dm-table.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Markus Elfring
Date: Sat, 1 Oct 2016 07:37:27 +0200
The local variable "argv" will be set to an appropriate pointer
a bit later. Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
drivers/md/dm-table.c | 2 +-
1 file changed, 1 insertion(+), 1
From: Markus Elfring
Date: Sat, 1 Oct 2016 07:51:55 +0200
Move the assignment for the local variable "end" behind the source code
for the initial two condition checks by this function.
Signed-off-by: Markus Elfring
---
drivers/md/dm-table.c | 3 ++-
1 file changed, 2 insertions(+), 1
From: Markus Elfring
Date: Sat, 1 Oct 2016 08:39:58 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: quoted string split across lines
Thus fix the affected source code places.
Signed-off-by: Markus Elfring
---
drivers/md/dm-table.c | 32
From: Markus Elfring
Date: Sat, 1 Oct 2016 08:53:37 +0200
The script "checkpatch.pl" pointed information out like the following.
ERROR: do not use assignment in if condition
Thus fix the affected source code place.
Signed-off-by: Markus Elfring
---
drivers/md/dm-table.c | 3 ++-
1 file
From: Markus Elfring
Date: Sat, 1 Oct 2016 09:04:06 +0200
The script "checkpatch.pl" pointed information out like the following.
ERROR: space prohibited after that '-' (ctx:WxW)
Thus fix the affected source code place.
Signed-off-by: Markus Elfring
---
drivers/md/dm-table.c | 2 +-
1 file
101 - 200 of 364 matches
Mail list logo