Hi,
On Wed, Jul 15, 2015 at 05:54:40PM +0100, David Daney wrote:
> From: David Daney
>
> The subject pretty much says it all. The first four patches tweak the
> infrastructure a little so that we can get required behavior. The
> final patch adds the drivers.
>
> David Daney (5):
> pci: Add
On Fri, Jul 3, 2015 at 5:40 AM, Krzysztof Kozlowski
wrote:
> The structure zbud_ops is not modified so make the pointer to it as
> pointer to const.
>
> Signed-off-by: Krzysztof Kozlowski
Acked-by: Dan Streetman
> ---
> include/linux/zbud.h | 2 +-
> mm/zbud.c| 6 +++---
> 2 files
On Fri, Jul 3, 2015 at 5:40 AM, Krzysztof Kozlowski
wrote:
> The structure zpool_ops is not modified so make the pointer to it as
> pointer to const.
>
> Signed-off-by: Krzysztof Kozlowski
Acked-by: Dan Streetman
> ---
> include/linux/zpool.h | 4 ++--
> mm/zbud.c | 4 ++--
> mm/z
FROM:MR HASSAN SAIDU
BILL AND EXCHANGE MANAGER,
AFRICAN DEVELOPMENT BANK (A D B)
OUAGADOUGOU BURKINA-FASO.
Dear Friend
This message might come to you as a surprise. However, it all just my
urgent needs for a foreign partner that made me to contact you for
this transaction. I saw your brief contac
[ adding Tejun ]
On Tue, Jul 14, 2015 at 3:34 PM, Laurent Pinchart
wrote:
> Hello,
>
> I came to realize not too long ago that the following sequence of events will
> lead to a crash with any platform driver that uses devm_* and creates device
> nodes.
>
> 1. Get a platform device bound it its dr
Hi Stephen,
On Thu, Jul 02, 2015 at 11:46:48AM -0400, cp...@redhat.com wrote:
> +static int i8042_kbd_bind_notifier(struct notifier_block *nb,
> +unsigned long action, void *data)
> +{
> + struct device *dev = data;
> + struct serio *serio = to_serio_port(de
On Wed, 15 Jul 2015 12:26:26 +0200 Jan Kara wrote:
> From: Jan Kara
>
> The functionality of ext3 is fully supported by ext4 driver. Major
> distributions (SUSE, RedHat) already use ext4 driver to handle ext3
> filesystems for quite some time. There is some ugliness in mm resulting
> from jbd c
From: David Daney
Signed-off-by: David Daney
---
drivers/pci/host/Kconfig| 12 +
drivers/pci/host/Makefile | 2 +
drivers/pci/host/pcie-thunder-pem.c | 462
drivers/pci/host/pcie-thunder.c | 422
From: David Daney
Needed to map SPI interrupt sources.
Signed-off-by: David Daney
---
drivers/irqchip/irq-gic-v3.c | 5 +
include/linux/irqchip/arm-gic-v3.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
index c52f7ba
From: David Daney
The subject pretty much says it all. The first four patches tweak the
infrastructure a little so that we can get required behavior. The
final patch adds the drivers.
David Daney (5):
pci: Add is_pcierc element to struct pci_bus
gic-its: Allow pci_requester_id to be overri
From: David Daney
Signed-off-by: David Daney
---
drivers/irqchip/irq-gic-v3-its.c | 14 +-
include/linux/irqchip/arm-gic-v3.h | 2 ++
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 1b7e155..
From: David Daney
... and use is to force only_one_child() to return true.
Needed because the ThunderX PCIe RC cannot be identified by existing methods.
Signed-off-by: David Daney
---
drivers/pci/probe.c | 2 ++
include/linux/pci.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers
From: David Daney
The default is to continue doing the what we have done before, but add
a hook so that this can be overridden.
Signed-off-by: David Daney
---
arch/arm64/include/asm/pci.h | 3 +++
arch/arm64/kernel/pci.c | 10 ++
2 files changed, 13 insertions(+)
diff --git a/ar
On Jul 02 2015 or thereabouts, cp...@redhat.com wrote:
> From: Stephen Chandler Paul
>
> A big problem with the current i8042 debugging option is that it outputs
> data going to and from the keyboard by default. As a result, many dmesg
> logs uploaded by users will unintentionally contain sensiti
My Makefile-fu has always been lacking and I know there's a better way to
do this. I'm trying to avoid heavily modifying the tools/ Makefiles because
I see that every author has their own way of doing things and I didn't want
to get in the way of specific use-case and design decisions.
P.
---8<-
Hello, Vivek.
On Wed, Jul 15, 2015 at 12:29:52PM -0400, Vivek Goyal wrote:
> Ok. I am personally little apprehensive of changing the meaning of
> current stat, but I can live with it.
Sure, if there are use cases which actually get impacted by this,
reverting the original stats shouldn't be diff
N�Р骒r��yb�X�肚�v�^�)藓{.n�+�伐�{��赙zXФ�≤�}��财�z�&j:+v�����赙zZ+��+zf＂�h���~i���z� �wア�?�ㄨ��&�)撷f��^j谦y�m��@A�a囤�
0鹅h���i
On Wed, Jul 15, 2015 at 05:01:09PM +0100, Will Deacon wrote:
> On Thu, Jul 09, 2015 at 06:28:59PM +0100, Peter Zijlstra wrote:
> > Implement atomic logic ops -- atomic_{or,xor,and}.
> >
> > These will replace the atomic_{set,clear}_mask functions that are
> > available on some archs.
> >
> >
> >
Hello Kukjin,
On 07/14/2015 12:10 PM, Kukjin Kim wrote:
> Javier Martinez Canillas wrote:
>>
>> The old drivers/usb/phy/phy-samsung-usb{2,3} are now deleted since
>> were replaced by newers drivers that use the Generic PHY framework
>> but their Kconfig options were left over in multi_v7_defconfig
I haven't checked the patch correctness but just noticed that the
block maintainer and author of the fixed commit are not cc'ed.
Catalin
On 15 July 2015 at 16:52, Andrey Vagin wrote:
> They are allocated in blkcg_css_alloc().
>
> This bug is reported by the kmemleak subsystem:
> unreferenced obj
Commit 2a1ed24 ("sched/numa: Prefer NUMA hotness over cache hotness")
sets sched feature NUMA to true. However this can enable numa hinting
faults on a uma system.
This commit ensures that numa hinting faults occur only on a numa system
by setting/resetting sched_numa_balancing.
This commit
- Ren
On Tue, Jul 14, 2015 at 06:28:50PM +0200, Michal Kubecek wrote:
> On Tue, Jul 14, 2015 at 05:38:47PM +0200, Pablo Neira Ayuso wrote:
> > On Tue, Jul 14, 2015 at 02:23:11PM +0200, Michal Kubecek wrote:
> > > @@ -658,6 +696,18 @@ static struct ctl_table sctp_sysctl_table[] = {
> > > .mode
On Wed, Jul 15, 2015 at 11:55:20AM +0300, Andrey Ryabinin wrote:
> On 07/14/2015 06:04 PM, Catalin Marinas wrote:
> > On Fri, Jul 10, 2015 at 08:11:03PM +0300, Andrey Ryabinin wrote:
> >>> kasan_early_pte_populate();
> >>> kasan_early_pmd_populate(..., pte);
> >>> kasan_early_pud_populate(...
Even if the signal was handled using signal(2) the message
would be printed. Fix that by checking whether the signal
is handled.
Signed-off-by: Levente Kurusa
---
arch/arm/mm/fault.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mm/fault.c b/arch/arm/mm/fault.
On Wed, 15 Jul 2015 18:27:42 +0200,
Laurent Pinchart wrote:
>
> On Wednesday 15 July 2015 18:20:02 Takashi Iwai wrote:
> > On Wed, 15 Jul 2015 18:08:34 +0200, Laurent Pinchart wrote:
> > > On Wednesday 15 July 2015 17:51:28 Takashi Iwai wrote:
> > > > On Wed, 15 Jul 2015 00:34:53 +0200, Laurent Pi
The Maxim max77802 Power Management IC has besides other devices, a set of
regulators. Commit f3caa529c6f5 ("ARM: multi_v7_defconfig: Enable max77802
regulator, rtc and clock drivers") was supposed to enable the config option
for the regulator driver as a module but the final version that landed di
The Exynos5420 Peach Pit and Exynos5800 Peach Pi Chromebooks have
IIO based ADC thermistors. Enable built-in support for its driver.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/exynos_defconf
The Exynos5420 Peach Pit and Exynos5800 Peach Pi Chromebooks have
IIO based ADC thermistors. Enable module support for its driver
and also for the needed Exynos ADC driver.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
d
Hello Kukjin and Krzysztof,
This series enables support in exynos_defconfig and multi_v7_defconfig
for the NTC Thermistors found on the Exynos5 Peach Chromebooks and
also enables support for the max77802 regulators in multi_v7_defconfig.
The series is composed of the following patches:
Javier M
On Wed, Jul 15 2015 at 11:30am -0400,
Jens Axboe wrote:
> On 07/15/2015 05:46 AM, Austin S Hemmelgarn wrote:
> >On 2015-07-14 17:48, Jens Axboe wrote:
> >>On 07/14/2015 02:45 PM, Jens Axboe wrote:
> >>>On 07/14/2015 02:44 PM, Mike Snitzer wrote:
> On Tue, Jul 14 2015 at 2:48pm -0400,
> J
On Wed, Jul 15, 2015 at 12:04:25PM -0400, Tejun Heo wrote:
> Hello, Vivek.
>
> On Tue, Jul 14, 2015 at 12:09:08PM -0400, Vivek Goyal wrote:
> > So now blkio.io_serviced will switch to accounting number of bios
> > instead of number of requests? I feel given other stats, things
> > are still confus
New title, I originally posted this last night but I've now made
a little progress in identifying what changed. Previous thread was
labelled for AMD Phenom, but it is more general. CC'ing Jeff
because he replied to the original, I guess he probably won't be
interested after this.
Yesterday was t
On Wednesday 15 July 2015 18:20:02 Takashi Iwai wrote:
> On Wed, 15 Jul 2015 18:08:34 +0200, Laurent Pinchart wrote:
> > On Wednesday 15 July 2015 17:51:28 Takashi Iwai wrote:
> > > On Wed, 15 Jul 2015 00:34:53 +0200, Laurent Pinchart wrote:
> > > > Hello,
> > > >
> > > > I came to realize not too
In case of CONFIG_X86_64, vdso32/vclock_gettime.c fakes a 32bit
kernel configuration by re-defining it to CONFIG_X86_32. However,
it does not re-define CONFIG_PGTABLE_LEVELS leaving it as 4 levels.
Fix it by re-defining CONFIG_PGTABLE_LEVELS to 2 as X86_PAE is not
set.
Signed-off-by: Toshi Kani
/sys/kernel/debug/kernel_page_tables does not show the PAT bit
for PUD and PMD mappings. This is because walk_pud_level(),
walk_pmd_level() and note_page() mask the flags with PTE_FLAGS_MASK,
which does not cover their PAT bit, _PAGE_PAT_LARGE.
Fix it by replacing the use of PTE_FLAGS_MASK with p
PUD_SHIFT is defined according to a kernel configuration, which
allows it be commonly used by any kernels. However, PUD_PAGE_SIZE
and PUD_PAGE_MASK, which are calculated from PUD_SHIFT, are defined
in page_64_types.h, which allows them be used by a 64-bit kernel
only.
Move PUD_PAGE_SIZE and PUD_P
The PAT bit gets relocated to bit 12 when PUD and PMD mappings are
used. This bit 12, however, is not covered by PTE_FLAGS_MASK, which
is corrently used for masking pfn and flags for all cases.
Fix pud/pmd interfaces to handle pfn and flags properly by using
P?D_PAGE_MASK when PUD/PMD mappings ar
The PAT bit gets relocated to bit 12 when PUD and PMD mappings are used.
This bit 12, however, is not covered by PTE_FLAGS_MASK, which is corrently
used for masking pfn and flags for all cases.
Patch 1/4-2/4 make changes necessary for patch 3/4 to use P?D_PAGE_MASK.
Patch 3/4 fixes pud/pmd interf
On Wed, Jul 15, 2015 at 12:16:28PM +0200, Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > On Tue, Jul 14, 2015 at 12:14:06PM -0500, Josh Poimboeuf wrote:
> > > Posting a listing of reported warnings in a reply to this email.
> >
> > These are the reported stackvalidate warnings on tip/mast
On Wednesday 15 July 2015 06:17 PM, Peter Zijlstra wrote:
> On Wed, Jul 15, 2015 at 02:38:36PM +0530, Aravinda Prasad wrote:
>> Current tracing infrastructure such as perf and ftrace reports system
>> wide data when invoked inside a container. It is required to restrict
>> events specific to a co
From: Oleg Drokin
ldlm_namespace_sysfs_unregister needs to be called ldlm_namespace_free_post
so that we don't have this dangling object there after the namespace
has disappeared.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/ldlm/ldlm_resource.c | 1 +
1 file changed, 1 inserti
On Wed, 15 Jul 2015 18:08:34 +0200,
Laurent Pinchart wrote:
>
> Hello Takashi,
>
> On Wednesday 15 July 2015 17:51:28 Takashi Iwai wrote:
> > On Wed, 15 Jul 2015 00:34:53 +0200, Laurent Pinchart wrote:
> > > Hello,
> > >
> > > I came to realize not too long ago that the following sequence of eve
On 07/14/2015 11:17 PM, Jiang Liu wrote:
> On 2015/7/15 1:22, Joseph Salisbury wrote:
>> On 07/13/2015 10:42 PM, Jiang Liu wrote:
>>> On 2015/7/14 3:36, Joseph Salisbury wrote:
Hello Jiang,
A kernel bug report was opened against Ubuntu [0]. It was found that
reverting the follow
On Wed, 15 Jul 2015 10:55:36 -0400
Steven Rostedt wrote:
> I'll take a look at it and try to clean up the code.
Does the following patch make sense for you?
-- Steve
diff --git a/kernel/trace/trace_stack.c b/kernel/trace/trace_stack.c
index 3f34496244e9..9384647d07c3 100644
--- a/kernel/trac
Hello, Vivek.
On Tue, Jul 14, 2015 at 12:09:08PM -0400, Vivek Goyal wrote:
> So now blkio.io_serviced will switch to accounting number of bios
> instead of number of requests? I feel given other stats, things
> are still confusing as other stats will similar name give stats
> about requests and no
On 7/9/2015 12:03 AM, Shubhrajyoti Datta wrote:
@@ -330,8 +310,18 @@ static irqreturn_t xadc_zynq_interrupt_handler(int irq,
void *devid)
xadc_zynq_update_intmsk(xadc, 0, 0);
ret = IRQ_WAKE_THREAD;
}
+
+ alarm = xadc->zy
Hi Michal,
On Wed, Jul 15, 2015 at 01:52:27PM +0200, Marek Vasut wrote:
> The problem is, if you add a new DT binding, you'd have to support it
> forever, no matter how bad idea that binding turned out to be.
Agreed, and a solid NAK to this patch. I could have sworn I gave such a
response when th
Removes the limits of supported CPU cores and max core ID.
Patch is based on Kirill A. Shutemov's work from 2012.
Signed-off-by: Lukasz Odzioba
---
drivers/hwmon/coretemp.c | 120 -
1 files changed, 75 insertions(+), 45 deletions(-)
diff --git a/dr
Hi,
my qemu test for mipsel crashes with next-20150715 as follows.
...
Btrfs loaded
console [netcon0] enabled
netconsole: network logging started
Freeing unused kernel memory: 284K (808f9000 - 8094)
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0008
Bisect points to
Hello Takashi,
On Wednesday 15 July 2015 17:51:28 Takashi Iwai wrote:
> On Wed, 15 Jul 2015 00:34:53 +0200, Laurent Pinchart wrote:
> > Hello,
> >
> > I came to realize not too long ago that the following sequence of events
> > will lead to a crash with any platform driver that uses devm_* and
>
Hi Juergen,
Am 15.07.2015 um 09:36 schrieb Juergen Borleis:
> Whenever the UART device driver gets closed from userland, the driver
> disables the UART unit and then stops its clock to save power.
>
> The bit which disabled the UART unit is described as:
>
> "UART Enable. If this bit is set to 1
On Wed, Jul 15, 2015 at 05:07:08AM -0700, Christoph Hellwig wrote:
> Many years ago we decided to move setting of IRQ to core affnities to
> userspace with the irqbalance daemon.
>
> These days we have systems with lots of MSI-X vector, and we have
> hardware and subsystem support for per-CPU I/O
On Mon, 2015-07-13 at 18:19 +0800, Daniel Kurtz wrote:
> On Mon, Jul 13, 2015 at 5:04 PM, YH Huang wrote:
> > Add display PWM driver support to modify backlight for MT8173 and MT6595.
> > The PWM has one channel to control the brightness of the display.
> > When the (high_width / period) is closer
On Wed, Jul 15, 2015 at 02:12:54PM +, Ranjit Abhimanyu Waghmode wrote:
> > > What is stacked mode?
> > > -
> > > ZynqMP GQSPI controller supports stacked mode with following
> > functionalities:
> > > 1) The Generic Quad-SPI controller also supports two SPI flash memories
>
On Thu, Jul 09, 2015 at 06:28:59PM +0100, Peter Zijlstra wrote:
> Implement atomic logic ops -- atomic_{or,xor,and}.
>
> These will replace the atomic_{set,clear}_mask functions that are
> available on some archs.
>
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> arch/arm64/include/asm/atomi
On 7/14/2015 9:28 AM, Sebastian Andrzej Siewior wrote:
* Xander Huff | 2015-07-08 16:38:22 [-0500]:
drivers/iio/adc/xilinx-xadc-core.c | 35 ---
1 file changed, 12 insertions(+), 23 deletions(-)
diff --git a/drivers/iio/adc/xilinx-xadc-core.c
b/drivers/iio/adc/x
Hello Mark,
On 07/15/2015 05:52 PM, Mark Brown wrote:
> On Wed, Jul 15, 2015 at 02:46:25PM +0200, Javier Martinez Canillas wrote:
>> On 07/15/2015 01:27 PM, Mark Brown wrote:
>
>>> using _regulator_get() I think. A separate, rarely used, path is likely
>>> to have this sort of issue.
>
>> Exact
On Wed, Jul 08, 2015 at 01:06:12PM -0400, Mikulas Patocka wrote:
> I have a ST4000DM000 disk. If Linux is booted while the disk is spun down,
> the command that sets transfer mode causes the disk to spin up. The
> spin-up takes longer than the default 5s timeout, so the command fails and
> timeout
On 07/15/2015 05:12 AM, Thomas Gleixner wrote:
On Wed, 15 Jul 2015, Christoph Hellwig wrote:
Many years ago we decided to move setting of IRQ to core affnities to
userspace with the irqbalance daemon.
These days we have systems with lots of MSI-X vector, and we have
hardware and subsystem suppo
On Wed, Jul 15, 2015 at 02:46:25PM +0200, Javier Martinez Canillas wrote:
> On 07/15/2015 01:27 PM, Mark Brown wrote:
> > using _regulator_get() I think. A separate, rarely used, path is likely
> > to have this sort of issue.
> Exactly, do you agree then that a try_module_get() is missing in set
They are allocated in blkcg_css_alloc().
This bug is reported by the kmemleak subsystem:
unreferenced object 0x88007d004d60 (size 32):
comm "systemd", pid 1, jiffies 4294668449 (age 34.455s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
This patch depends on "drm: add support for for clk and de polarity".
Since "drm: add support for for clk and de polarity", clock and data
polarity set in devicetree are passed correctly through drm_display_mode
to videomode flags used by ipuv3.
Removes custom configuration flags for clock and de p
On Wed, 15 Jul 2015 00:34:53 +0200,
Laurent Pinchart wrote:
>
> Hello,
>
> I came to realize not too long ago that the following sequence of events will
> lead to a crash with any platform driver that uses devm_* and creates device
> nodes.
>
> 1. Get a platform device bound it its driver
> 2.
To get full support for parallel and LVDS displays with drm:
Add representation for clock and data enable polarity in drm_display_mode
flags (similar to HSYNC/VSYNC polarity) and update conversion functions
from/to videomode accordingly.
This is especially important for embedded devices where para
Hello!
These patches address a problem we ran into using parallel displays
with Freescale i.MX53 and i.MX6 SoC's.
In short: We wanted to change the clock signal polarity by using
display-timing in the devicetree description, but the output signal stayed
unchanged.
Parallel displays may have diffe
On Wed, Jul 15, 2015 at 03:45:07PM +0100, Russell King - ARM Linux wrote:
> On Wed, Jul 15, 2015 at 02:46:03PM +0100, Lorenzo Pieralisi wrote:
> > On Tue, Jul 14, 2015 at 09:41:38PM +0100, Russell King - ARM Linux wrote:
> > > Sorry, NAK, and end of discussion. There is nothing more to be said
> >
Hello,
On Thu, May 14, 2015 at 5:40 PM, Javier Martinez Canillas
wrote:
> The Maxim max77802 Power Management IC is used on many Exynos machines.
> Besides a bunch of regulators, this chip has a Real-Time-Clock (RTC)
> and 2-channel 32kHz clock outputs.
>
> Enable the kernel config options to hav
On Mon, 2015-07-13 at 18:20 +0800, Daniel Kurtz wrote:
> On Mon, Jul 13, 2015 at 5:04 PM, YH Huang wrote:
> > Document the device-tree binding of MediatTek display PWM.
> > The PWM has one channel to control the backlight brightness for display.
> > It supports MT8173 and MT6595.
> >
> > Signed-of
sorry. My mistake. i saw both as 8064.
On Wed, Jul 15, 2015 at 8:34 PM, Stanimir Varbanov wrote:
> On 07/15/2015 05:53 PM, Vinay Simha BN wrote:
>> repeatation of the same configs
>> obj-$(CONFIG_PINCTRL_APQ8084) += pinctrl-apq8084.o
>
> hm you might be kidding, apq8064 and apq8084 are differen
Florian Fainelli :
>
> Does it behave properly for you?
Yes, I've just checked and can't reproduce the problem
you mentioned. And I can't think of the possible reason:
fixed_phy.c keeps the private copy of the status, which
should have link speed kept unchanged, and used as
long as link is up agai
On 07/15/2015 05:46 AM, Austin S Hemmelgarn wrote:
On 2015-07-14 17:48, Jens Axboe wrote:
On 07/14/2015 02:45 PM, Jens Axboe wrote:
On 07/14/2015 02:44 PM, Mike Snitzer wrote:
On Tue, Jul 14 2015 at 2:48pm -0400,
Jens Axboe wrote:
Lots of devices exhibit very high latencies for big discard
On 10/07/15 18:41, Kirill A. Shutemov wrote:
With new refcounting we don't need to mark PMDs splitting. Let's drop
code to handle this.
pmdp_splitting_flush() is not needed too: on splitting PMD we will do
pmdp_clear_flush() + set_pte_at(). pmdp_clear_flush() will do IPI as
needed for fast_gup.
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 65ea03e31e5ab47f784b1a701419264af97d3205:
Merge tag 'perf-urgent-for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent
(2015-07-15 13:31:21 +0200)
are available in the g
On 2015-07-15 11:11, Eric Sandeen wrote:
On 7/15/15 10:09 AM, Randy Dunlap wrote:
On 07/15/15 08:05, Randy Dunlap wrote:
On 07/15/15 07:18, Theodore Ts'o wrote:
On Wed, Jul 15, 2015 at 12:26:24PM +0200, Jan Kara wrote:
so I have created this patch set which removes ext3 driver (and some r
On 07/15/15 03:11, Masanari Iida wrote:
> This patch fix following warnings.
>
> Warning(.//fs/namei.c:2422): No description found for parameter 'nd'
> Warning(.//fs/namei.c:2422): Excess function parameter 'nameidata'
> description in 'path_mountpoint'
>
> Signed-off-by: Masanari Iida
Acked-by
From: Adrian Hunter
Move the checking for HAVE_SYNC_COMPARE_AND_SWAP_SUPPORT for AUX area mmaps
until after checking if such mmaps are used anyway.
Reported-by: Alexey Brodkin
Signed-off-by: Adrian Hunter
Tested-by: Alexey Brodkin
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: N
From: Alexey Brodkin
Commit 5ef7bbb09f7b ("perf tools: Allow to specify custom linker
command") was meant to enable usage non $(CROSS_COMPILE)ld linker during
perf building.
But implementation didn't take into account the fact that LD is a
pre-defined variable in GNU Make. I.e. it is always defi
On Wed, Jul 15, 2015 at 12:37 AM, Michael Ellerman wrote:
> Wire up the syscall number and regs so the tests work on powerpc.
>
> Signed-off-by: Michael Ellerman
Acked-by: Kees Cook
-Kees
> ---
> tools/testing/selftests/seccomp/seccomp_bpf.c | 9 -
> 1 file changed, 8 insertions(+),
On Wed, Jul 15, 2015 at 12:37 AM, Michael Ellerman wrote:
> The seccomp_bpf test uses BPF_LD|BPF_W|BPF_ABS to load 32-bit values
> from seccomp_data->args. On big endian machines this will load the high
> word of the argument, which is not what the test wants.
>
> Borrow a hack from samples/seccom
On 07/15/15 08:11, Eric Sandeen wrote:
> On 7/15/15 10:09 AM, Randy Dunlap wrote:
>> On 07/15/15 08:05, Randy Dunlap wrote:
>>> On 07/15/15 07:18, Theodore Ts'o wrote:
On Wed, Jul 15, 2015 at 12:26:24PM +0200, Jan Kara wrote:
>
> so I have created this patch set which removes ext3 dr
On Wed, Jul 15, 2015 at 12:37 AM, Michael Ellerman wrote:
> SIG_SYS was added in commit a0727e8ce513 "signal, x86: add SIGSYS info
> and make it synchronous."
>
> Because we use the asm-generic struct siginfo, we got support for
> SIG_SYS for free as part of that commit.
>
> However there was no c
On 7/15/15 10:09 AM, Randy Dunlap wrote:
> On 07/15/15 08:05, Randy Dunlap wrote:
>> On 07/15/15 07:18, Theodore Ts'o wrote:
>>> On Wed, Jul 15, 2015 at 12:26:24PM +0200, Jan Kara wrote:
so I have created this patch set which removes ext3 driver (and some
related support
code
On 07/15/15 08:05, Randy Dunlap wrote:
> On 07/15/15 07:18, Theodore Ts'o wrote:
>> On Wed, Jul 15, 2015 at 12:26:24PM +0200, Jan Kara wrote:
>>>
>>> so I have created this patch set which removes ext3 driver (and some
>>> related support
>>> code) from the kernel. See changelog of patch 2/3 for
On 07/15/15 07:18, Theodore Ts'o wrote:
> On Wed, Jul 15, 2015 at 12:26:24PM +0200, Jan Kara wrote:
>>
>> so I have created this patch set which removes ext3 driver (and some
>> related support
>> code) from the kernel. See changelog of patch 2/3 for more details. If noone
>> objects,
>> I will
On 07/15/2015 05:53 PM, Vinay Simha BN wrote:
> repeatation of the same configs
> obj-$(CONFIG_PINCTRL_APQ8084) += pinctrl-apq8084.o
hm you might be kidding, apq8064 and apq8084 are different SoCs.
>
> Signed-off-by: Vinay Simha BN
> ---
> drivers/pinctrl/qcom/Makefile | 1 -
> 1 file change
On Wed, 15 Jul 2015 20:41:34 +0900
AKASHI Takahiro wrote:
> Thank you for the explanation. But what I don't really understand here
> is why we need to add the "current function" to the stack dump list
> returned by save_stack_trace():
>
> In check_stack(),
> >/*
> > * Add the
On Wed, 2015-07-15 at 12:26 +0200, Jan Kara wrote:
> I have created this patch set which removes ext3 driver (and some related
> support
> code) from the kernel. See changelog of patch 2/3 for more details.
It'd be nice if you regenerate 2/3 using
git format-patch -M and resend it.
--
To unsubs
If dma-debug is disabled due to a memory error, DMA unmaps do not affect
the dma_active_cacheline radix tree anymore, and debug_dma_assert_idle()
can print false warnings.
Disable debug_dma_assert_idle() when dma_debug_disabled() is true.
Fixes: 0abdd7a81b7e ("dma-debug: introduce debug_dma_asser
On Wed, Jul 15, 2015 at 08:52:13AM -0500, Timothy Pearson wrote:
> On 07/15/2015 01:24 AM, Sreekanth Reddy wrote:
> > On Tue, Jul 14, 2015 at 10:36:58PM -0700, Yinghai Lu wrote:
> >> On Tue, Jul 14, 2015 at 9:49 PM, Sreekanth Reddy
> >> wrote:
> >>> Driver crashes if the BIOS do not set up at leas
On 07/15/2015 04:47 PM, Roger Quadros wrote:
Hi,
On 15/07/15 15:07, Tony Lindgren wrote:
* Kishon Vijay Abraham I [150715 04:24]:
Hi Roger,
On Tuesday 02 June 2015 02:40 PM, Roger Quadros wrote:
This register is required to be passed to the SATA PHY driver
to workaround errata i783 (SATA Lo
> -Original Message-
> From: Austin S Hemmelgarn [mailto:ahferro...@gmail.com]
> Sent: Wednesday, July 15, 2015 10:07 AM
> To: Pavel Machek; Len Brown
> Cc: r...@rjwysocki.net; linux...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Brown, Len
> Subject: Re: [PATCH 1/1] suspend: make s
On 15/07/15 13:07, Christoph Hellwig wrote:
> Many years ago we decided to move setting of IRQ to core affnities to
> userspace with the irqbalance daemon.
>
> These days we have systems with lots of MSI-X vector, and we have
> hardware and subsystem support for per-CPU I/O queues in the block
> l
On Wednesday 15 July 2015 10:29:55 Yao Yuan wrote:
> Hi Arnd,
>
> Thanks for your review.
> And can you give me more information?
> In my opinion, The fsl_edma_pm_state will just be used when CONFIG_PM
> support. So why not use the #ifdefs to remove the
> unnecessary code? Since the PM will not
repeatation of the same configs
obj-$(CONFIG_PINCTRL_APQ8084) += pinctrl-apq8084.o
Signed-off-by: Vinay Simha BN
---
drivers/pinctrl/qcom/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/pinctrl/qcom/Makefile b/drivers/pinctrl/qcom/Makefile
index 3666c70..d26a878 100644
---
Define Vybrid's UART0, connected to the Colibri pinout UART_A, as
standard output.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
b/arch/arm/boot/dts/vf-colib
callers of vhost_kvzalloc() expect the same behaviour on
allocation error as from kmalloc/vmalloc i.e. NULL return
value. So just return vzmalloc() returned value instead of
returning ERR_PTR(-ENOMEM)
issue introduced by
4de7255f7d2be5e51664c6ac6011ffd6e5463571 in vhost-next tree
Spotted-by: Da
On 07/15/2015 04:26 AM, Jan Kara wrote:
Hello,
so I have created this patch set which removes ext3 driver (and some related
support
code) from the kernel. See changelog of patch 2/3 for more details. If noone
objects,
I will queue the series in my tree for the next merge window.
Jens, a
On Wed, Jul 15, 2015 at 02:46:03PM +0100, Lorenzo Pieralisi wrote:
> On Tue, Jul 14, 2015 at 09:41:38PM +0100, Russell King - ARM Linux wrote:
> > Sorry, NAK, and end of discussion. There is nothing more to be said
> > here.
>
> I beg to differ. To solve the issue that you brought up with this se
On Sat, Jul 04, 2015 at 11:48:28PM +0100, jon wrote:
> It solves these problems:
> 1) It solves the problem of processes writing data into the mount point
> when not mounted (as does, I accept a user space automounter, but as I
> explained the usage scenario differs).
>
> 2) It would be useful fo
The GIC controller doesn't provides any facility to configure the wakeup
sources. For the same reason, GIC chip implementation can't provide
irq_set_wake functionality, but that results in the irqchip core
preventing the systems from entering sleep states like "suspend to RAM".
The GICv1/v2 contro
601 - 700 of 1185 matches
Mail list logo
