Dear Sir,
Did you recieved my mail?
I have sent it twice without a response.
Castano Giovanni
On Sat, 2017-03-18 at 19:08 -0700, Nicholas A. Bellinger wrote:
> Hello Linus,
>
> Here are the target-pending fixes for v4.11-rc3 code. Please go ahead
> and pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
>
> The bulk of the changes are in qla2xxx
Fixed style of block comment across whole driver
Found using checkpatch
Signed-off-by: Derek Robson
---
drivers/staging/rtl8192e/rtl8192e/r8190P_def.h | 2 +-
drivers/staging/rtl8192e/rtl8192e/r8190P_rtl8256.c | 2 +-
drivers/staging/rtl8192e/rtl8192e/r8190P_rtl8256.h
Signed-off-by: Ilia Mirkin
Fixes: 590801c1a3 ("drm/nouveau/mpeg: remove dependence on namedb/engctx
lookup")
Cc: sta...@vger.kernel.org # v4.3+
---
This is just a nice-to-have, as it only affects an error print afterwards.
drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv31.c
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
struct timespec is not y2038 safe.
Replace the posix_clock ops interfaces to use
struct timespec64.
The patch also changes struct itimerspec interfaces to
struct itimerspec64 as itimerspec internally uses timespec
and itimerspec64 uses timespec64.
PTP clocks is the only module that sets up
On Sat, Mar 18, 2017 at 08:41:14PM -0400, Nicolas Dufresne wrote:
> Le samedi 18 mars 2017 à 20:43 +, Russell King - ARM Linux a
> écrit :
> > On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote:
> > > Can you share your gstreamer pipeline? For now, until
> > >
From: Herbert Xu
Date: Sun, 19 Mar 2017 00:47:59 +0800
> Eric Dumazet wrote:
>> On Fri, 2017-03-17 at 07:42 +, Reshetova, Elena wrote:
>>
>>> Should we then first measure the actual numbers to understand what we
>>> are talking here
This patch fixes the issue that mmc_blk_issue_rq still
flushes cache when eMMC cache has already been off
through user space tool, such as mmc-utils.
The reason is that card->ext_csd.cache_ctrl isn't reset.
Signed-off-by: beanhuo
---
drivers/mmc/core/block.c | 9 +
1
On Mar 19, 2017, at 12:41 AM, Greg Kroah-Hartman wrote:
> On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote:
>> Ever since sysfs migration, class_process_proc_param stopped working
>> correctly as all the useful params were no longer present as lvars.
>> Replace all the nasty fake proc
The CPU port of the BCM53125 is configured with RGMII (no delays) but
this should actually be RGMII with transmit delay (rgmii-txid) because
STMMAC takes care of inserting the transmitter delay. This fixes
occasional packet loss encountered.
Fixes: d7b9eaff5f0c ("ARM: dts: sun7i: Add BCM53125
This patch fixes the checkpatch.pl warning "multiple assignments
should be avoided."
Signed-off-by: Arushi Singhal
---
changes in v2
- no change.
drivers/staging/speakup/main.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff
Improve readability by fixing multiple checkpatch.pl
issues in speakup driver.
Arushi Singhal (3):
staging: speakup: Moved logical to previous line.
staging: speakup: Remove multiple assignments
staging: speakup: Simplify "NULL" comparisons
drivers/staging/speakup/main.c| 30
Moved logical AND operator to previous line to fix the following
checkpatch issue:
CHECK: Logical continuations should be on the previous line.
Signed-off-by: Arushi Singhal
---
changes in v2
- Change the commit message.
drivers/staging/speakup/main.c | 12
Fixed coding style for null comparisons in speakup driver to be more
consistant with the rest of the kernel coding style.
Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'.
Signed-off-by: Arushi Singhal
---
changes in v2
- no change
Hello Linus,
Here are the target-pending fixes for v4.11-rc3 code. Please go ahead
and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
The bulk of the changes are in qla2xxx target driver code to address
various issues found during Cavium/QLogic's
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
This patch fixes the checks reported by checkpatch.pl
for braces {} should be used on all arms of this statement.
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/main.c | 35 +++-
On Sun, Mar 19, 2017 at 12:41:20AM -0400, Oleg Drokin wrote:
>
> On Mar 19, 2017, at 12:29 AM, Greg Kroah-Hartman wrote:
>
> > On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote:
> >>
> >> On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote:
> >>
> >>> On Sat, Mar 18, 2017 at
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces will be changed in a separate
series.
Call to do_sys_setimeofday() is superfluous as all
the necessary checks and functions
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
Resending to update author id in patch 7/7.
The series is aimed at replacing struct timespec which is not
y2038 safe with y2038 safe struct timespec64 for k_clock interfaces.
The series does not change the syscall interface.
This will be done in a follow up series.
A few existing
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
For mysterious historical reasons, struct user_desc doesn't indicate
whether segments are accessed. set_thread_area() has always
programmed segments as non-accessed, so the first write will set the
accessed bit. This will fault if the GDT is read-only.
Fix it by making TLS segments start out
2017-03-17 22:13 GMT+08:00 Peter Zijlstra :
> On Fri, Mar 17, 2017 at 03:09:09PM +0100, Peter Zijlstra wrote:
>> On Fri, Mar 17, 2017 at 09:24:11PM +0800, Wanpeng Li wrote:
>> > I have another version of patch which utilizes raw_spin_lock_irqsave()
>> > instead of
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa Dinamani
---
struct timespec is not y2038 safe.
Replace the posix_clock ops interfaces to use
struct timespec64.
The patch also changes struct itimerspec interfaces to
struct itimerspec64 as itimerspec internally uses timespec
and itimerspec64 uses timespec64.
PTP clocks is the only module that sets up
From: Deepa Dinamani
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces themselves will be changed
in a separate series.
Signed-off-by: Deepa
struct timespec is not y2038 safe. The plan is to
get rid of all uses of timespec internally in the
kernel. Replace uses of timespec with timespec64.
The syscall interfaces will be changed in a separate
series.
Call to do_sys_setimeofday() is superfluous as all
the necessary checks and functions
The series is aimed at replacing struct timespec which is not
y2038 safe with y2038 safe struct timespec64 for k_clock interfaces.
The series does not change the syscall interface.
This will be done in a follow up series.
A few existing checkpatch-noted style issues, such as the 80 line
The CPU port of the BCM53125 is configured with RGMII (no delays) but
this should actually be RGMII with transmit delay (rgmii-txid) because
STMMAC takes care of inserting the transmitter delay. This fixes
occasional packet loss encountered.
Fixes: d7b9eaff5f0c ("ARM: dts: sun7i: Add BCM53125
Le samedi 18 mars 2017 à 20:43 +, Russell King - ARM Linux a
écrit :
> On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote:
> > Can you share your gstreamer pipeline? For now, until
> > VIDIOC_ENUM_FRAMESIZES is implemented, try a pipeline that
> > does not attempt to specify a
On Mar 19, 2017, at 12:29 AM, Greg Kroah-Hartman wrote:
> On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote:
>>
>> On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote:
>>
>>> On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote:
Ever since sysfs migration,
On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote:
> Ever since sysfs migration, class_process_proc_param stopped working
> correctly as all the useful params were no longer present as lvars.
> Replace all the nasty fake proc writes with hopefully less nasty
> kobject attribute search
On Thu, Mar 16, 2017 at 05:36:33PM -0700, Tony Lindgren wrote:
> The cpcap INTS registers are for getting the value of the line,
> not for configuring the type.
>
> Cc: Lee Jones
> Cc: Marcel Partap
> Cc: Michael Scott
> Cc:
This patch fixes the checkpatch.pl warning "multiple assignments
should be avoided."
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/main.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/speakup/main.c
On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote:
>
> On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote:
>
> > On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote:
> >> Ever since sysfs migration, class_process_proc_param stopped working
> >> correctly as all the useful
On 14/03/17 07:15, Quentin Schulz wrote:
> Hi Jonathan,
>
> On 14/03/2017 06:18, Icenowy Zheng wrote:
>>
>>
>> 14.03.2017, 05:08, "Jonathan Cameron" :
>>> On 10/03/17 10:39, Quentin Schulz wrote:
This adds support for the Allwinner A33 thermal sensor.
Unlike the
From: Suniel Mahesh
Fixed the following checkpatch.pl warning:
Possible unnecessary 'out of memory' message
If it is out of memory, function should return with an
appropriate error code. Since this function is of type void,
a return statement is used.
Signed-off-by:
Technically, calling dma_buf_map_attachment should return a buffer
properly dma_mapped. Add calls to dma_map_sg to begin_cpu_access to
ensure this happens. As a side effect, this lets Ion buffers take
advantage of the dma_buf sync ioctls.
Signed-off-by: Laura Abbott
---
On Thu, Feb 23, 2017 at 07:40:13PM +0100, Pavel Machek wrote:
> On Thu 2017-02-23 17:28:26, Frederic Weisbecker wrote:
> > On Tue, Feb 14, 2017 at 08:27:43PM +0100, Pavel Machek wrote:
> > > On Tue 2017-02-14 18:59:56, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > > > > > Hmm. I moved keyboard
Declare snd_soc_ops structures as const as they are only stored
in the ops field of a snd_soc_dai_link structure. This field is
of type const, so snd_soc_ops structures having this property
can be made const too.
Cross compiled the files arndale_rt5631.o, h1940_uda1380.o, jive_wm8750.o,
On Sat, 2017-03-18 at 08:08 -0400, Paolo Valente wrote:
> > Il giorno 06 mar 2017, alle ore 14:40, Bart Van Assche
> > ha scritto:
> > > +#define BFQ_BFQQ_FNS(name)
> > > \
> > > +static void bfq_mark_bfqq_##name(struct
On Sat, Mar 18, 2017 at 08:31:39PM +0530, Bhumika Goyal wrote:
> Declare snd_soc_ops structures as const as they are only stored
> in the ops field of a snd_soc_dai_link structure. This field is
> of type const, so snd_soc_ops structures having this property
> can be made const too.
>
> Cross
> > +static void mvebu_pwm_free(struct pwm_chip *chip, struct pwm_device *pwmd)
> > +{
> > + struct mvebu_pwm *pwm = to_mvebu_pwm(chip);
> > + struct gpio_desc *desc = gpio_to_desc(pwmd->pwm);
> > + unsigned long flags;
> > +
> > + spin_lock_irqsave(>lock, flags);
> > +
On Thu, Mar 16, 2017 at 07:42:14AM +0100, Ralph Sennhauser wrote:
> Hi everyone
>
> this patch series was originally submitted by Andrew Lunn but got stalled.
> I picked up the series and addressed what was disscussed for the earlier
> submission with some helpful input from Andrew. Hopefully
From: Rafael J. Wysocki
The policy->cpuinfo.max_freq and policy->max updates in
intel_cpufreq_turbo_update() are excessive as they are done for no
good reason and may lead to problems in principle, so they should be
dropped. However, after dropping them
From: Andrew Lunn
Add properties to the gpio nodes to allow them to be also used as pwm
lines.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427294/
Signed-off-by: Ralph Sennhauser
---
From: Andrew Lunn
Armada 370/XP devices can 'blink' gpio lines with a configurable on
and off period. This can be modelled as a PWM.
However, there are only two sets of PWM configuration registers for
all the gpio lines. This driver simply allows a single gpio line per
gpio chip
Commit-ID: cf8178f78645148dc38b28263b9d3f604148e3a8
Gitweb: http://git.kernel.org/tip/cf8178f78645148dc38b28263b9d3f604148e3a8
Author: Colin Ian King
AuthorDate: Wed, 15 Mar 2017 17:10:10 +
Committer: Thomas Gleixner
CommitDate: Sat, 18
From: Rafael J. Wysocki
In the active mode intel_pstate currently uses two sets of global
limits, each associated with one of the possible scaling_governor
settings in that mode: "powersave" or "performance".
The driver switches over from one of those sets to the
From: Andrew Lunn
Now that the gpio driver also supports PWM operation, enable the PWM
framework and fan driver in mvebu_v7_defconfig.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427297/
[Ralph Sennhauser: add fan driver to defconfig]
Hi everyone
This patch series was originally submitted by Andrew Lunn but got stalled.
I picked up the series and addressed what was discussed for the earlier
submission with some helpful input from Andrew. Hopefully this time support
for the PWM fan as found on Linksys WRT1900AC (Mamba) will
On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote:
> On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote:
>> Ever since sysfs migration, class_process_proc_param stopped working
>> correctly as all the useful params were no longer present as lvars.
>> Replace all the nasty fake proc
From: Andrew Lunn
The mvebu gpio driver can also perform PWM on some pins. Us the pwm-fan
driver to control the fan of the WRT1900AC, giving us finer grained
control over its speed and hence noise.
Signed-off-by: Andrew Lunn
URL:
2017-03-18 1:28 GMT+08:00 Ladi Prosek :
> On Fri, Mar 17, 2017 at 3:41 PM, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> The L2 guest hang if shadow page tables on EPT, the trace on L1 shows that
>> L2 kvm_exit reason EXCEPTION_NMI
> Il giorno 07 mar 2017, alle ore 18:22, Jens Axboe ha
> scritto:
>
>> +/**
>> + * bfq_entity_of - get an entity from a node.
>> + * @node: the node field of the entity.
>> + *
>> + * Convert a node pointer to the relative entity. This is used only
>> + * to simplify the
Linus,
please pull the latest smp-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
smp-urgent-for-linus
A single fix preventing the concurrent execution of the CPU hotplug
callback install/invocation machinery. Long standing bug caused by a
massive
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
Hi Will, Michal,
2017-03-11 6:20 GMT+09:00 Michal Marek :
> Dne 10.3.2017 v 18:58 Will Deacon napsal(a):
>> Hi Michael,
>>
>> On Tue, Nov 22, 2016 at 10:34:29PM +0100, Michal Marek wrote:
>>> The KBUILD_IMAGE variable is used by the rpm and deb-pkg targets, which
>>> expect it to
Am Samstag, 18. März 2017, 11:11:57 CET schrieb Jeffrey Walton:
Hi Jeffrey,
> > The design and implementation is driven by a set of goals described in [2]
> > that the LRNG completely implements. Furthermore, [2] includes a
> > comparison with RNG design suggestions such as SP800-90B, SP800-90C,
Hi Luis,
2017-03-17 2:55 GMT+09:00 Luis R. Rodriguez :
> On Thu, Mar 16, 2017 at 10:43 AM, Masahiro Yamada
> wrote:
>> Hi Luis,
>>
>> 2017-03-15 9:53 GMT+09:00 Luis R. Rodriguez :
>>> On Sat, Mar 11, 2017 at 02:37:02PM +0900,
Commit-ID: 73e10a61817dfc97fe7418bfad1f608e562d7348
Gitweb: http://git.kernel.org/tip/73e10a61817dfc97fe7418bfad1f608e562d7348
Author: Kirill A. Shutemov
AuthorDate: Thu, 16 Mar 2017 18:26:54 +0300
Committer: Ingo Molnar
CommitDate:
Declare snd_soc_ops structures as const as they are only stored
in the ops field of a snd_soc_dai_link structure. This field is
of type const, so snd_soc_ops structures having this property
can be made const too.
Cross compiled the .o files for arm architecture.
Signed-off-by: Bhumika Goyal
Are fsnotify events generated per mount namespace?
On Thu, Oct 29, 2015 at 9:29 AM, Marko Rauhamaa wrote:
>
> If I call fanotify_mark(... FAN_MARK_ADD | FAN_MARK_MOUNT ...), I get
> notifications on all files on the file system.
>
> Except I don't.
>
> If a process has mounted
>> > The design and implementation is driven by a set of goals described in [2]
>> > that the LRNG completely implements. Furthermore, [2] includes a
>> > comparison with RNG design suggestions such as SP800-90B, SP800-90C, and
>> > AIS20/31.
>>
>> A quick comment about SP800 and the hardware
Tim at al,
I got this on my desktop at shutdown:
[ cut here ]
kernel BUG at mm/swap_slots.c:270!
invalid opcode: [#1] SMP
CPU: 5 PID: 1745 Comm: (sd-pam) Not tainted 4.11.0-rc1-00243-g24c534bb161b #1
Hardware name: System manufacturer System Product
ia64 allmodconfig build failed as:
In file included from /home/slyfox/linux-2.6/drivers/nfc/nxp-nci/i2c.c:39:0:
linux/include/linux/unaligned/access_ok.h:62:29: error: redefinition of
'put_unaligned_be64'
static __always_inline void put_unaligned_be64(u64 val, void *p)
On Sat, Mar 18, 2017 at 11:51 PM, Jonathan Cameron wrote:
> On 18/03/17 17:34, SIMRAN SINGHAL wrote:
>> On Thu, Mar 16, 2017 at 3:23 AM, Jonathan Cameron wrote:
>>> On 13/03/17 19:53, Alison Schofield wrote:
On Mon, Mar 13, 2017 at 10:01:07PM +0530,
(adding Petr and Steven to cc's)
On Fri, 2017-03-17 at 10:56 +0900, Sergey Senozhatsky wrote:
> On (03/16/17 11:37), Joe Perches wrote:
> > On Thu, 2017-03-16 at 20:30 +0900, Sergey Senozhatsky wrote:
> > > On (03/15/17 18:43), Joe Perches wrote:
> > > [..]
> > > > - printk("active_anon:%lu
Often it is interesting to know how costly a given source line is in
total. Previously, one had to build these sums manually based on all
addresses that pointed to the same source line. This patch introduces
srcline as a sort key, which will do the aggregation for us.
Paired with the recent
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive 2 fixes and a cleanup for device-dax.
The device-dax driver was not being careful to handle falling back to
smaller fault-granularity sizes. The driver already fails fault
On Fri, Mar 17, 2017 at 4:37 PM, Andy Shevchenko
wrote:
> Crystal Cove and Whiskey Cove are two different PMICs which are
> installed on Intel Atom SoC based platforms.
>
> Moreover there are two independent drivers that by some reason were
> supposed (*) to
On Thu, 16 Mar 2017 21:40:58 +0800
Xunlei Pang wrote:
> On 03/16/2017 at 09:18 PM, Baoquan He wrote:
> > On 03/16/17 at 08:36pm, Xunlei Pang wrote:
> >> On 03/16/2017 at 08:27 PM, Baoquan He wrote:
> >>> Hi Xunlei,
> >>>
> >>> Did you really see this ever happened? Because the
On 18/03/17 17:34, SIMRAN SINGHAL wrote:
> On Thu, Mar 16, 2017 at 3:23 AM, Jonathan Cameron wrote:
>> On 13/03/17 19:53, Alison Schofield wrote:
>>> On Mon, Mar 13, 2017 at 10:01:07PM +0530, simran singhal wrote:
The IIO subsystem is redefining iio_dev->mlock to be used by
On Wed, Mar 15, 2017 at 06:07:39PM +, Abel Vesa wrote:
> The support for dynamic ftrace with CONFIG_DEBUG_RODATA involves
> overriding the weak arch_ftrace_update_code() with a variant which makes
> the kernel text writable around the patching.
>
> This override was however added under the
The subject appears to be missing some words. logical what?
On Sun, 19 Mar 2017, Arushi Singhal wrote:
> Moved logical OR operator to previous line to fix the following
> checkpatch issue:
All the instances appear to be && not ||
julia
> CHECK: Logical continuations should be on the previous
From: "Steven Rostedt (VMware)"
When ftrace_regs_caller was created, it was designed to preserve flags as
much as possible as it needed to act just like a breakpoint triggered on the
same location. But the design is over complicated as it treated all
operations as modifying
Hello!
On 3/18/2017 3:58 PM, Elena Reshetova wrote:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by:
Declare snd_soc_ops structures as const as they are only stored
in the ops field of a snd_soc_dai_link structure. This field is
of type const, so snd_soc_ops structures having this property
can be made const too.
Signed-off-by: Bhumika Goyal
---
Notifications may only be 8 bytes so long. Accessing the 9th and
10th byte of unimplemented/unknown notifications may be insecure.
Also check the length of known notifications before accessing anything
behind the 8th byte.
Signed-off-by: Tobias Herzog
---
write_used was introduced with commit 884b600f63dc ("[PATCH] USB: fix acm
trouble with terminals") but never used since.
Signed-off-by: Tobias Herzog
---
drivers/usb/class/cdc-acm.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/class/cdc-acm.h
Hi Matthew,
On Fri, 10 Mar 2017 11:40:27 -0800
matthew.gerl...@linux.intel.com matthew.gerl...@linux.intel.com wrote:
...
>+#include "altera-pr-ip-core.h"
Shouldn't we put this header to include/linux? Compiling the
out-of-tree modules using alt_pr_register/alt_pr_unregister
will not work if
USB devices may have very limitited endpoint packet sizes, so that
notifications can not be transferred within one single usb packet.
This patchset adds the ability to reassemble notifications that are
transmitted fragmented.
v2:
* reuse an allocated buffer for further notifications
* fixed
Adds a similar log message to USB_CDC_NOTIFY_SERIAL_STATE as it is
already done with USB_CDC_NOTIFY_NETWORK_CONNECTION.
Signed-off-by: Tobias Herzog
---
drivers/usb/class/cdc-acm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/class/cdc-acm.c
Hi Matthew,
thanks for the patches. Please see some comments below.
On Fri, 10 Mar 2017 11:40:25 -0800
matthew.gerl...@linux.intel.com matthew.gerl...@linux.intel.com wrote:
...
>+ if (!(info->flags & FPGA_MGR_PARTIAL_RECONFIG)) {
>+ pr_err("%s Partial Reconfiguration flag not
Hi Steve,
I've just been trying to get gstreamer to capture and h264 encode
video from my camera at various frame rates, and what I've discovered
does not look good.
1) when setting frame rates, media-ctl _always_ calls
VIDIOC_SUBDEV_S_FRAME_INTERVAL with pad=0.
2) media-ctl never retrieves
Hi Russell,
On 03/14/2017 10:29 AM, Steve Longerbeam wrote:
On 03/12/2017 02:09 PM, Russell King - ARM Linux wrote:
On Sun, Mar 12, 2017 at 08:40:37PM +, Russell King - ARM Linux
wrote:
On Sun, Mar 12, 2017 at 01:36:32PM -0700, Steve Longerbeam wrote:
But hold on, if my logic is
The NV4A (aka NV44A) is an oddity in the family. It only comes in AGP
and PCI varieties, rather than a core PCIE chip with a bridge for
AGP/PCI as necessary. As a result, it appears that the MMU is also
non-functional. For AGP cards, the vast majority of the NV4A lineup,
this worked out since we
Andrew Morton wrote:
>
> The performance implications of this proposal are terrifying.
>
> I suggest adding a set of non-debug inlined refcount functions which
> just fall back to the simple atomic.h operations.
>
> And add a new CONFIG_DEBUG_REFCOUNT. So the
Btw,
just broke the build with pnd2 due to EDAC_DEBUG + DEBUG_FS dependencies
missing. I'm replying to this mail with potential fixes but would like
to hammer on them more when I get back just to be sure I haven't missed
anything.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when
On Sat, 2017-03-18 at 18:09 +0100, Linus Walleij wrote:
> On Sat, Mar 18, 2017 at 11:52 AM, Paolo Valente
> wrote:
> > > Il giorno 14 mar 2017, alle ore 16:32, Bart Van Assche
> > > ha scritto:
> > > (...) what should
> > > a developer do
Hi,
thank you for your feedback. I tried to fix all issues with v2. I was
just unsure with one point (see comment).
/tobias
> Am Dienstag, den 14.03.2017, 21:14 +0100 schrieb Tobias Herzog:
> >
> > USB devices may have very limitited endpoint packet sizes, so that
> > notifications can not
USB devices may have very limitited endpoint packet sizes, so that
notifications can not be transferred within one single usb packet.
Reassembling of multiple packages may be necessary.
Signed-off-by: Tobias Herzog
---
drivers/usb/class/cdc-acm.c | 106
This patch fixes the checkpatch.pl warning "multiple assignments
should be avoided."
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/main.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git
Fixed coding style for null comparisons in speakup driver to be more
consistant with the rest of the kernel coding style.
Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'.
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/selection.c | 2 +-
1 - 100 of 376 matches
Mail list logo