On Wed, Sep 30, 2015 at 09:10:41AM +0200, Peter Zijlstra wrote:
> Now that nothing tests for PREEMPT_ACTIVE anymore, stop setting it.
>
> Reviewed-by: Thomas Gleixner
> Reviewed-by: Steven Rostedt
> Signed-off-by: Peter Zijlstra (Intel)
Great news!
Reviewed-by: Frederic Weisbecker
--
To unsu
On 2015-10-01 10:45, sascha a. wrote:
Hello,
Okay, i was wrong with FUSE and NFS thanks for the hint.
About the Problem:
Without digging deep into the kernel sources, your explaination is
more or less that was i thinking about whats happening.
Anyways, the reason why i report the Problem is tha
On Thu, Oct 01, 2015 at 09:50:51AM -0500, Chris J Arges wrote:
>
> > +
> > +$(STACKTOOL_IN): FORCE
> > + @$(MAKE) $(build)=stacktool
> > +
> > +$(STACKTOOL): $(STACKTOOL_IN)
> > + @(test -d ../../kernel -a -d ../../tools -a -d ../stacktool && (( \
> > + diff -I'^#include' arch/x86/insn/insn.
On Thu, Oct 01, 2015 at 03:00:12PM +0200, Lars Svensson wrote:
> Member screen_base in struct fb_info is declared __iomem causing
> a sparse warning as below when passed to vfree(). This adds typecast
> (__force void *) to silence the warning.
>
> fbtft-core.c:922:39: warning: incorrect type in ar
On Thu, Oct 01, 2015 at 07:50:37AM -0700, Stephen Hemminger wrote:
> On Thu, 1 Oct 2015 11:33:06 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Wed, Sep 30, 2015 at 03:28:58PM -0700, Stephen Hemminger wrote:
> > > This driver allows using PCI device with Message Signalled Interrupt
> > > from users
Remove uapi header for i2o subsystem that has been removed by
commit 4a72a7af462d ("staging: remove i2o subsystem")
CC: Greg Kroah-Hartman
Signed-off-by: Gabriel Laskar
---
include/uapi/linux/i2o-dev.h | 421 ---
1 file changed, 421 deletions(-)
delete m
On 09/30/2015 07:43 PM, Florian Fainelli wrote:
> On 30/09/15 01:21, Neil Armstrong wrote:
>> In order to cleanly unbind the dsa core, either as a module removal,
>> or a platform device unbind, switch the allocation the their devm_
>> counterparts and complete the destroy functions.
>>
>> The last
This patch is a simplification of the logic introduced as part of
commit 63914aca8f7e ('perf tools: Show better error message in case we fail to
open counters due to EBUSY error'):
if EBUSY is reported by perf_event_open(), it will not be possible
to probe PERF_FLAG_FD_CLOEXEC, so it's safe to lea
In case of failure, unrelated to PERF_FLAG_FD_CLOEXEC,
perf_flag_probe() reports the error twice. For example:
$ perf record ls
Error:
perf_event_open(..., PERF_FLAG_FD_CLOEXEC) failed with unexpected error 16
(Device or resource busy)
perf_event_open(..., 0) failed unexpectedly with erro
Hi,
Following the EBUSY errors reported by Jiri Olsa [1], I've tryed to
improve a bit the way perf_flag_probe() handle errors.
In case EBUSY is returned by perf_event_open(), testing the function
again without PERF_FLAG_FD_CLOEXEC is meaningless: EBUSY is not
related to close-on-exec flag, so the
On 09/30/2015 08:47 PM, Darrick J. Wong wrote:
> Change the journal's checksum functions to gate on whether or not the
> crc32c driver is loaded, and gate the loading on the superblock bits.
> This prevents a journal crash if someone loads a journal in no-csum
> mode and then randomizes the super
> Why not just reject it earlier instead of allocating more data?
I agree on your point.
But we have to make different mechanism for that and my patch is only
to fix the current code.
regards
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to maj
On Thu, Oct 01, 2015 at 08:15:43AM -0700, David Miller wrote:
>
> A patch with this and more should be in the 'net' tree already.
Yes this looks much better. Thanks!
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
On 30/09/15 11:45, Julien Grall wrote:
> Hi all,
>
> ARM64 Linux is supporting both 4KB and 64KB page granularity. Although, Xen
> hypercall interface and PV protocol are always based on 4KB page granularity.
>
> Any attempt to boot a Linux guest with 64KB pages enabled will result to a
> guest c
On Thu, Oct 01, 2015 at 02:36:26PM +0200, Peter Zijlstra wrote:
> On Thu, Oct 01, 2015 at 02:27:15PM +0200, Peter Zijlstra wrote:
> > On Wed, Sep 16, 2015 at 11:49:33PM +0800, Boqun Feng wrote:
> > > Unlike other atomic operation variants, cmpxchg{,64}_acquire and
> > > atomic{,64}_cmpxchg_acquire
acpi_parse_entries passes the table end pointer to the sub-table entry
handler. acpi_parse_entries itself could validate the end of an entry
against the table end using the length in the sub-table entry.
This patch adds the validation of the sub-table entry end using the
length field.This will hel
On Thu, Oct 01, 2015 at 02:36:26PM +0200, Peter Zijlstra wrote:
> On Thu, Oct 01, 2015 at 02:27:15PM +0200, Peter Zijlstra wrote:
> > On Wed, Sep 16, 2015 at 11:49:33PM +0800, Boqun Feng wrote:
> > > Unlike other atomic operation variants, cmpxchg{,64}_acquire and
> > > atomic{,64}_cmpxchg_acquire
Hi Nicolas,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: ia64-allmodconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin
acpi_tbl_entiry_handler expects `table_end` pointer to be passed so that
the individual subtable entry handler can use it to validate the entries.
However, acpi_parse_entries now validates the end of an entry against
the table end using the length in the sub-table entry. The only user
of that argu
On Thu, Oct 01, 2015 at 02:24:40PM +0200, Peter Zijlstra wrote:
> On Wed, Sep 16, 2015 at 11:49:32PM +0800, Boqun Feng wrote:
> > Implement xchg_relaxed and define atomic{,64}_xchg_* as xchg_relaxed,
> > based on these _relaxed variants, release/acquire variants can be built.
> >
> > Note that xch
On Wed, Sep 30, 2015 at 03:59:04PM -0700, Yang Shi wrote:
> diff --git a/arch/arm64/kernel/debug-monitors.c
> b/arch/arm64/kernel/debug-monitors.c
> index cebf786..eb520d0 100644
> --- a/arch/arm64/kernel/debug-monitors.c
> +++ b/arch/arm64/kernel/debug-monitors.c
> @@ -292,11 +292,11 @@ static in
Hi Brian,
On Mon, 24 Aug 2015 19:10:19 +0200
Boris Brezillon wrote:
> The ->read_xxx() methods are all passed the page number the NAND controller
> is supposed to read, but ->write_xxx() do not have such a parameter.
>
> This is a problem if we want to properly implement data
> scrambling/rando
On 09/30/2015 07:43 PM, Florian Fainelli wrote:
> On 30/09/15 01:21, Neil Armstrong wrote:
>> In order to cleanly unbind the dsa core, either as a module removal,
>> or a platform device unbind, switch the allocation the their devm_
>> counterparts and complete the destroy functions.
>>
>> The last
On Thu, Oct 01, 2015 at 09:11:31AM +0530, Ronit Halder wrote:
> The existing dgap_parsefile() rejects invalid config file.
> But before we know that config file is invalid a lot of memory leak
> can happen. Removing the chances of memory leak won't heart anyone.
>
Why not just reject it earlier i
On 10/01, Michal Hocko wrote:
>
> On Wed 30-09-15 20:24:05, Oleg Nesterov wrote:
> [...]
> > It is possible that the group leader
> > has the pending SIGKILL because its sub-thread originated the coredump,
> > in this case we must not skip this process.
>
> I do not understand this. If the group le
From: Herbert Xu
Date: Thu, 1 Oct 2015 19:34:07 +0800
> In skb_postpull_rcsum the skb has already been pulled so we should
> be testing whether the checksum start offset is non-negative rather
> than how it compares to the length that we have pulled.
>
> Fixes: 6ae459bdaaee ("skbuff: Fix skb che
The ->init_size() hook was introduced to let NAND controller drivers
support NAND devices that could not be described in the nand_ids table.
Since then, the core has added support for extended-id parsing and
full-id description, thus allowing to describe pretty much all existing
NANDs.
Moreover, th
On Thu, 1 Oct 2015 13:59:02 +0300
Avi Kivity wrote:
> On 10/01/2015 01:28 AM, Stephen Hemminger wrote:
> > This is a new UIO device driver to allow supporting MSI-X and MSI devices
> > in userspace. It has been used in environments like VMware and older
> > versions
> > of QEMU/KVM where no IOM
On Thu, 01 Oct 2015, Andy Shevchenko wrote:
> There is at least one board on the market, i.e. Intel Galileo Gen2, that uses
> _ADR to distinguish the devices under one actual device. Due to this we have
> to
> improve the quirk in the MFD core to handle that board.
>
> Signed-off-by: Andy Shevch
On Thu, Oct 01, 2015 at 04:24:24PM +0200, Thomas Gleixner wrote:
> On Thu, 1 Oct 2015, tip-bot for Yang Yingliang wrote:
>
> > Commit-ID: f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
> > Gitweb:
> > http://git.kernel.org/tip/f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
> > Author: Yang Yingliang
On 09/17/2015 06:59 PM, Jason Gunthorpe wrote:
> On Thu, Sep 17, 2015 at 04:04:19PM -0400, Sasha Levin wrote:
>> Allocating a workqueue might fail, which wasn't checked so far and would
>> lead to NULL ptr derefs when an attempt to use it was made.
>
> Indeed.
>
> Yishai, please check this and ch
On Thu, 01 Oct 2015, Andy Shevchenko wrote:
> On Intel Galileo boards the GPIO expander is connected to i2c bus. Moreover it
> is able to generate interrupt, but interrupt line is connected to GPIO. That's
> why we have to have GPIO driver in place when we will probe i2c host with
> device connect
The memset and scatter gathered memset are going to use some common logic
to create their descriptors.
Move that logic into a function of its own so that we can share it with the
future memset_sg callback.
Signed-off-by: Maxime Ripard
---
drivers/dma/at_hdmac.c | 98 +++
Hi Vinod,
Here is a patch serie that adds support in the Atmel HDMAC for memset
over a discontiguous memory area.
Just like for the memset, it's used on those SoCs to support
framebuffer related operations that cannot be performed either by the
display engine or the (non-existent) GPU.
Let me kn
Just like memset support, the HDMAC might be used to do a memset over a
discontiguous memory area.
In such a case, we'll just build up a chain of memset descriptors over the
contiguous chunks of memory to set, in order to allow such a support.
Signed-off-by: Maxime Ripard
---
drivers/dma/at_hdm
On 09/30, Hugh Dickins wrote:
>
> On Tue, 29 Sep 2015, Oleg Nesterov wrote:
>
> > "mm->locked_vm += grow" and vm_stat_account() in acct_stack_growth()
> > are not safe; multiple threads using the same ->mm can do this at the
> > same time trying to expans different vma's under down_read(mmap_sem).
> +
> +$(STACKTOOL_IN): FORCE
> + @$(MAKE) $(build)=stacktool
> +
> +$(STACKTOOL): $(STACKTOOL_IN)
> + @(test -d ../../kernel -a -d ../../tools -a -d ../stacktool && (( \
> + diff -I'^#include' arch/x86/insn/insn.c ../../arch/x86/lib/insn.c
> >/dev/null && \
> + diff -I'^#include'
On Thu, 2015-09-17 at 17:41 +0100, Mark Rutland wrote:
> On Thu, Sep 17, 2015 at 03:56:56PM +0100, Yingjoe Chen wrote:
> > On Thu, 2015-09-17 at 14:51 +0100, Sudeep Holla wrote:
> > >
> > > On 16/09/15 03:04, Yingjoe Chen wrote:
> > > > From: Daniel Kurtz
> > > >
> > > > Add device node to enable
On Thu, 1 Oct 2015 11:33:06 +0300
"Michael S. Tsirkin" wrote:
> On Wed, Sep 30, 2015 at 03:28:58PM -0700, Stephen Hemminger wrote:
> > This driver allows using PCI device with Message Signalled Interrupt
> > from userspace. The API is similar to the igb_uio driver used by the DPDK.
> > Via ioctl
Hi Joerg,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: ia64-allyesconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/m
Acked-by: Matthew R. Ochs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon 28-09-15 15:24:06, David Rientjes wrote:
> On Fri, 25 Sep 2015, Michal Hocko wrote:
>
> > > > I am still not sure how you want to implement that kernel thread but I
> > > > am quite skeptical it would be very much useful because all the current
> > > > allocations which end up in the OOM ki
On Thu, 01 Oct 2015, Andy Shevchenko wrote:
> Jim Davis reported the compilation error with a random configuration which
> apparently has CONFIG_PM=y and CONFIG_PM_SLEEP=n. With that conditions we have
> missed definition of INTEL_LPSS_SLEEP_PM_OPS macro. Add it here.
>
> Reported-by: Jim Davis
Hello Maciek-
Some architectural questions below:
On Thu, Oct 01, 2015 at 04:04:31PM +0200, Maciek Borzecki wrote:
> The patch adds LED triggers for indicating an activity on a selected
> device. The drivers that intend to use triggers need to register
> respective devices using ledtrig_dev_add()
On Wed, 30 Sep 2015, Rafael J. Wysocki wrote:
> > If that's so then won't this change defeat all the work being done by
> > people trying to prevent unneeded runtime resumes during system resume?
> > direct_complete would be useful only on non-ACPI systems.
>
> To me at least the main motivation
Hello,
Okay, i was wrong with FUSE and NFS thanks for the hint.
About the Problem:
Without digging deep into the kernel sources, your explaination is
more or less that was i thinking about whats happening.
Anyways, the reason why i report the Problem is that during this 120
Seconds (until the Ker
On Thu, 01 Oct 2015, Andy Shevchenko wrote:
> On Thu, Oct 1, 2015 at 3:29 PM, Lee Jones wrote:
> > On Sun, 27 Sep 2015, Andy Shevchenko wrote:
> >
> >> On Tue, Sep 22, 2015 at 2:33 PM, Andy Shevchenko
> >> wrote:
> >> > On Tue, 2015-09-22 at 13:22 +0200, Geert Uytterhoeven wrote:
> >> >> On Tue,
On Tue, 08 Sep 2015, Stephen Boyd wrote:
> On 09/07, Lee Jones wrote:
> > On Sun, 06 Sep 2015, Eric Anholt wrote:
> >
> > > clk-bcm2835.c predates the drivers under bcm/, but all the new BCM
> > > drivers are going in there so let's follow them.
> > >
> > > Signed-off-by: Eric Anholt
> > > ---
On Thu, 1 Oct 2015, Ville Syrjälä wrote:
> > since I've updated on my thinkpad x200s to latest Linus' tree (3235031), I
> > am getting a lot of
> >
> > [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't
> > calculate constants, dotclock = 0!
>
> What's a lot? I think you sh
On Thu, Oct 01, 2015 at 09:40:52AM -0400, Mike Snitzer wrote:
> On Thu, Oct 01 2015 at 8:55am -0400,
> Seth Forshee wrote:
>
> > On Wed, Sep 30, 2015 at 07:42:15PM -0400, Mike Snitzer wrote:
> > > On Wed, Sep 30 2015 at 4:15pm -0400,
> > > Seth Forshee wrote:
> > >
> > > > When mounting a fil
> -Original Message-
> From: mrgarna...@gmail.com [mailto:mrgarna...@gmail.com] On Behalf Of Carlos
> Garnacho
> Sent: 30 September, 2015 17:02
> To: Bastien Nocera
> Cc: Tirdea, Irina; linux-in...@vger.kernel.org; Cosimo Cecchi; Christian
> Hergert; linux-kernel@vger.kernel.org; Rob He
Commit-ID: a51e80d002b63bbdaff3229f3ebf4fbb53c75c33
Gitweb: http://git.kernel.org/tip/a51e80d002b63bbdaff3229f3ebf4fbb53c75c33
Author: Axel Lin
AuthorDate: Thu, 1 Oct 2015 22:26:44 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 1 Oct 2015 16:32:54 +0200
irqchip/i8259: Convert to use
When device_register() fails, kfree() is called in hsi_client_release(),
hence there is no need to call kfree in err3 again.
Signed-off-by: Geliang Tang
---
Changes in v2:
- Just to make myself clearer that what I did in this patch.
---
drivers/hsi/hsi.c | 1 -
1 file changed, 1 deletion(-)
Hi,
here is a patch-set to fix a remaining RMRR issue in the
VT-d driver. The problem was that RMRR mappings are only
created for boot-time (or hotplug-time) allocated domains.
Domains allocated on demand don't get RMRR mappings, which
is bad for the kdump case, for example. With this patch-set
t
Hi Hugh,
I've hit this (actual) lockup during testing. It seems that we were trying to
allocate
a new page to break KSM on an existing page, ended up in the oom killer who
killed our
process, and locked up in __ksm_exit() trying to get a write lock while already
holding
a read lock.
A very sim
From: Joerg Roedel
Split the part of the function that fetches the domain out
and put the rest into into a domain_prepare_identity_map, so
that the code can also be used with when the domain is
already known.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 40
From: Joerg Roedel
Currently the RMRR entries are created only at boot time.
This means they will vanish when the domain allocated at
boot time is destroyed.
This patch makes sure that also newly allocated domains will
get RMRR mappings.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iomm
On Thu, 2015-09-17 at 17:13 +0100, Sudeep Holla wrote:
>
> On 17/09/15 15:56, Yingjoe Chen wrote:
> > On Thu, 2015-09-17 at 14:51 +0100, Sudeep Holla wrote:
> >>
> >> On 16/09/15 03:04, Yingjoe Chen wrote:
> >>> From: Daniel Kurtz
> >>>
> >>> Add device node to enable GPT timer. This timer will b
On Thu, 1 Oct 2015, Mika Westerberg wrote:
> Now if I plug/unplug the card I may get few interrupts to CPU0 but rest
> of the interrupts never happen. Probably because IO-APIC forwards them
> to the lowest priority CPU which is offline at this point.
>
> There is following check in fixup_irqs():
>
drivers/media/i2c/ml86v7667.c:430:3-8: No need to set .owner here. The core
will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Geert Uytterhoeven
Signed-off-by: Fengguang Wu
---
ml86v7667.c |
Chained irq handlers usually set up handler data as well. We now have
a function to set both under irq_desc->lock. Replace the two calls
with one.
Signed-off-by: Axel Lin
---
drivers/irqchip/irq-i8259.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/irqchip/irq-i
On Thu, 1 Oct 2015, tip-bot for Yang Yingliang wrote:
> Commit-ID: f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
> Gitweb: http://git.kernel.org/tip/f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
> Author: Yang Yingliang
> AuthorDate: Thu, 24 Sep 2015 17:32:13 +0800
> Committer: Thomas Gleixner
>
On 2015-10-01 09:06, sascha a. wrote:
Hello,
I want to report a Bug with NFS / FuseFS.
Theres trouble with mounting a NFS FS with FuseFS, if the NFS Server
is slowly responding.
The problem occurs, if you mount a NFS FS with FuseFS driver for
example with this command:
mount -t nfs -o vers=3
Hi Thomas,
On Intel Braswell system (this affect others if they are using chained
interrupts on x86) both CPUs can handle interrupts which trigger when
GPIO line changes state if programmed to do so.
We have SD-card card detection signal that is connected to a GPIO line:
# cat /proc/interrupts
Commit-ID: f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
Gitweb: http://git.kernel.org/tip/f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
Author: Yang Yingliang
AuthorDate: Thu, 24 Sep 2015 17:32:13 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 1 Oct 2015 14:51:15 +0200
genirq: Introduce gene
When device_register() fails, kfree(devfreq) is called already in
devfreq_dev_release(), hence there is no need to call kfree(devfreq)
in err_dev again.
Signed-off-by: Geliang Tang
---
drivers/devfreq/devfreq.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/devfreq
On Thu, 1 Oct 2015, Frederic Weisbecker wrote:
> On Mon, Sep 28, 2015 at 04:40:56PM -0400, Andy Lutomirski wrote:
> > On Mon, Sep 28, 2015 at 11:17 AM, Chris Metcalf wrote:
> > > While the current fallback to 1-second tick is still helpful for
> > > maintaining completely correct kernel semantics,
On Thu, Oct 01, 2015 at 10:18:57PM +0900, Krzysztof Kozlowski wrote:
> 2015-10-01 20:39 GMT+09:00 Sudip Mukherjee :
> > The value of emul_con was getting overwritten if the selected soc is
> > SOC_ARCH_EXYNOS5260. And so as a result we were reading from the wrong
> > register in the case of SOC_ARC
On Tue 29-09-15 14:37:21, Mel Gorman wrote:
[...]
> mm: page_alloc: Hide some GFP internals and document the bits and flag
> combinations
>
> Andrew started the following
>
> We have quite a history of remote parts of the kernel using
> weird/wrong/inexplicable combinations of __GFP_
On Sat, Sep 19, 2015 at 12:42 PM, Marek Vasut wrote:
> This change is similar to e001bbae7147b111fe1aa42beaf835635f3c016e
> ARM: cmpxchg: avoid warnings from macro-ized cmpxchg() implementations
>
> A recent change in kernel/acct.c added a new warning for many
> configurations using generic __xchg
This patch adds documentation for ledtrig-device trigger.
Signed-off-by: Maciek Borzecki
---
Documentation/leds/00-INDEX | 3 +++
Documentation/leds/ledtrig-device.txt | 35 +++
2 files changed, 38 insertions(+)
create mode 100644 Documentation/leds/le
A series of patches that add yet another LED trigger, a device
activity trigger.
The motivation is to have a LED trigger that is associated with a
device and can be fired from cetrain points in the code that have been
chosen by the developer. With this this device activity trigger it is
possible f
Add debugfs entries for device activity trigger. Three entries are
created under /sys/kernel/debug/ledtrig-dev when the driver gets
loaded. These are:
devices - cat'ing will produce a list of currently registered devices
in : format, a line for each device.
register - echo'ing : w
The patch adds LED triggers for indicating an activity on a selected
device. The drivers that intend to use triggers need to register
respective devices using ledtrig_dev_add(). Triggers are generated by
explicitly calling ledtrig_dev_activity().
Signed-off-by: Maciek Borzecki
---
drivers/leds/t
On Sun, Sep 27, 2015 at 10:47:05PM +0800, Geliang Tang wrote:
> Fixes the following sparse warnings:
>
> crypto/skcipher.c:94:5:
> warning: symbol 'crypto_init_skcipher_ops_blkcipher'
> was not declared. Should it be static?
>
> crypto/skcipher.c:185:5:
> warning: symbol 'crypto_init_skciphe
On Wed, Sep 23, 2015 at 01:55:24PM +0200, LABBE Corentin wrote:
>
> Hello
>
> Some drivers use two dma_map_sg path according to SG are chained or not.
> Since dma_map_sg can handle both case, this patch series clean all code
> with references to sg chained.
>
> Note that I could only compile tes
On Wed, Sep 23, 2015 at 01:55:26PM +0200, LABBE Corentin wrote:
> The qce driver use two dma_map_sg path according to SG are chained
> or not.
> Since dma_map_sg can handle both case, clean the code with all
> references to sg chained.
>
> Thus removing qce_mapsg, qce_unmapsg and qce_countsg funct
Hi Sakari,
On 10/01/2015 03:22 PM, Sakari Ailus wrote:
Hi Jacek,
Jacek Anaszewski wrote:
This is a second version of the patch set preparing the
ground for removing work queues from LED class drivers.
Andrew and Sakari - thanks for a review.
Changes from v1:
On Thu, Oct 01 2015 at 8:55am -0400,
Seth Forshee wrote:
> On Wed, Sep 30, 2015 at 07:42:15PM -0400, Mike Snitzer wrote:
> > On Wed, Sep 30 2015 at 4:15pm -0400,
> > Seth Forshee wrote:
> >
> > > When mounting a filesystem on a block device there is currently
> > > no verification that the us
On Sat, 2015-09-26 at 10:38 +0100, Russell King - ARM Linux wrote:
> On Thu, Sep 24, 2015 at 11:38:58PM +0800, Yingjoe Chen wrote:
> > +struct mtk_smp_boot_info {
> > + unsigned long smp_base;
> ...
> > +static const struct mtk_smp_boot_info mtk_mt8135_tz_boot = {
> > + 0x80002000, 0x3fc,
> ...
On Wed, Sep 30, 2015 at 9:04 PM, Arnd Bergmann wrote:
> create_request_message() computes the maximum length of a message,
> but uses the wrong type for the time stamp: sizeof(struct timespec)
> may be 8 or 16 depending on the architecture, while sizeof(struct
> ceph_timespec) is always 8, and tha
On Thu 01-10-15 16:18:43, Pintu Kumar wrote:
> This patch maintains number of oom calls and number of oom kill
> count in /proc/vmstat.
> It is helpful during sluggish, aging or long duration tests.
> Currently if the OOM happens, it can be only seen in kernel ring buffer.
> But during long duratio
On Wed, 2015-09-30 at 10:11 +0200, Richard Weinberger wrote:
> > {
> > - if (new_valid_dev(rdev)) {
> > - dev->new = cpu_to_le32(new_encode_dev(rdev));
> > - return sizeof(dev->new);
> > - } else {
> > - dev->huge = cpu_to_le64(huge_encode_dev(
On Wed, 30 Sep 2015 21:43:38 +0200
Rasmus Villemoes wrote:
> On Wed, Sep 09 2015, Rasmus Villemoes wrote:
>
> ping
Both your patches look good. I applied both of them to my tree for the
4.4 window.
I'll post them to linux-next after they've gone through my test suite.
But currently my tests a
On Thu, Oct 01, 2015 at 08:10:26AM +0200, mini...@ld-linux.so wrote:
> On Tue, Sep 22, 2015 at 10:47:04AM -0500, Josh Poimboeuf wrote:
> > aesni-intel_asm.S has several callable non-leaf functions which don't
> > honor CONFIG_FRAME_POINTER, which can result in bad stack traces.
> >
> > Create stac
On 10/01/2015 04:18 PM, Pintu Kumar wrote:
> This patch maintains number of oom calls and number of oom kill
> count in /proc/vmstat.
> It is helpful during sluggish, aging or long duration tests.
> Currently if the OOM happens, it can be only seen in kernel ring buffer.
> But during long duration
On Wed, Sep 30, 2015 at 09:10:36AM +0200, Peter Zijlstra wrote:
> As per commit d86ee4809d03 ("sched: optimize cond_resched()") we need
> PREEMPT_ACTIVE to avoid cond_resched() from working before the
> scheduler is setup.
>
> However, keeping preemption disabled should do the same thing already,
On Wed, Sep 30, 2015 at 5:54 PM, Alexandre Belloni
wrote:
> On 30/09/2015 at 17:16:10 -0500, Rob Herring wrote :
>> On Wed, Sep 30, 2015 at 4:42 PM, Alexandre Belloni
>> wrote:
>> > Use "qiaodian" as the vendor prefix for QiaoDian Xianshi Corporation in
>> > device tree compatible strings.
>> >
>
Hi Jacek,
Jacek Anaszewski wrote:
> This is a second version of the patch set preparing the
> ground for removing work queues from LED class drivers.
> Andrew and Sakari - thanks for a review.
>
>
> Changes from v1:
>
> - removed useless use of else in led_set_br
2015-10-01 20:39 GMT+09:00 Sudip Mukherjee :
> The value of emul_con was getting overwritten if the selected soc is
> SOC_ARCH_EXYNOS5260. And so as a result we were reading from the wrong
> register in the case of SOC_ARCH_EXYNOS5260.
How the value is overwritten if the soc is Exynos5260? I can't
On Tue 29-09-15 13:24:20, Vineet Gupta wrote:
> This came up when implementing HIHGMEM/PAE40 for ARC.
> The kmap() / kmap_atomic() generated code seemed needlessly bloated due
> to the way PageHighMem() macro is implemented.
> It derives the exact zone for page and then does pointer subtraction
> w
On Wed, Sep 30, 2015 at 5:47 PM, David Daney wrote:
> From: David Daney
>
> The device tree property "msi-map" specifies how to create the PCI
> requester id used in some MSI controllers. Add a new function
> of_msi_map_rid() that finds the msi-map property and applies its
> translation to a giv
Jim Davis reported the compilation error with a random configuration which
apparently has CONFIG_PM=y and CONFIG_PM_SLEEP=n. With that conditions we have
missed definition of INTEL_LPSS_SLEEP_PM_OPS macro. Add it here.
Reported-by: Jim Davis
Signed-off-by: Andy Shevchenko
---
drivers/mfd/intel-
On Mon, Sep 28, 2015 at 04:40:56PM -0400, Andy Lutomirski wrote:
> On Mon, Sep 28, 2015 at 11:17 AM, Chris Metcalf wrote:
> > While the current fallback to 1-second tick is still helpful for
> > maintaining completely correct kernel semantics, processes using
> > prctl(PR_SET_TASK_ISOLATION) seman
From: "Kweh, Hock Leong"
This patch export efi_capsule_supported() function symbol for capsule
kernel module to use.
Cc: Matt Fleming
Signed-off-by: Kweh, Hock Leong
---
drivers/firmware/efi/capsule.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/firmware/efi/capsule.c b/driv
From: "Kweh, Hock Leong"
Dear maintainers & communities,
This patchset is created on top of Matt's patchset:
1.)https://lkml.org/lkml/2014/10/7/390
"[PATCH 1/2] efi: Move efi_status_to_err() to efi.h"
2.)https://lkml.org/lkml/2014/10/7/391
"[PATCH 2/2] efi: Capsule update support"
It expose a m
From: "Kweh, Hock Leong"
Introducing a kernel module to expose capsule loader interface
(misc char device file note) for user to upload capsule binaries.
Example method to load the capsule binary:
cat firmware.bin > /dev/efi_capsule_loader
Cc: Matt Fleming
Signed-off-by: Kweh, Hock Leong
---
Hello,
I want to report a Bug with NFS / FuseFS.
Theres trouble with mounting a NFS FS with FuseFS, if the NFS Server
is slowly responding.
The problem occurs, if you mount a NFS FS with FuseFS driver for
example with this command:
mount -t nfs -o vers=3,nfsvers=3,hard,intr,tcp server /dest
W
Unused space between the end of __ex_table and the start of rodata
can be left W+x in the kernel page tables. Extend the setting
of the NX bit to cover this gap by starting from text_end rather than
rodata_start.
Before:
---[ High Kernel Mapping ]---
0x8000-0x8100
On Wed, 30 Sep 2015 21:43:00 +0200
Rasmus Villemoes wrote:
> On Wed, Sep 09 2015, Rasmus Villemoes wrote:
>
> ping
Thanks for the reminder. I'll take a look at your patches today.
-- Steve
>
> > The kernel now has kstrdup_const/kfree_const for reusing .rodata
> > (typically string literals)
501 - 600 of 986 matches
Mail list logo
