On Mon, Jan 04, 2016 at 04:45:22AM -0800, Christopher S. Hall wrote:
> @@ -138,6 +142,7 @@ long ptp_ioctl(struct posix_clock *pc, unsigned int cmd,
> unsigned long arg)
> caps.n_per_out = ptp->info->n_per_out;
> caps.pps = ptp->info->pps;
> caps.n_pins = p
Hi Brian,
On Mon, 2016-01-04 at 11:11 -0800, Brian Norris wrote:
> This patch is needed in additon to commit 472b444eef93 ("mtd: fix
> cmdlinepart parser, early naming for auto-filled MTD") to fix Heiko's
> reported problem. At this point, I'm not sure if this should be
> targeted toward late 4.4
On Tue, Jan 05, 2016 at 03:37:33PM +0100, Petr Mladek wrote:
> On Fri 2016-01-01 12:13:48, Michael S. Tsirkin wrote:
> > Peter Mladek reported that balloon might never refill completely after
> > restore. This is because fill_balloon is only called once there.
> > Calling fill_balloon repeatedly s
On 2016-01-05 10:24, Greg KH wrote:
On Tue, Jan 05, 2016 at 08:16:52AM -0500, Austin S. Hemmelgarn wrote:
And those embedded devices can almost certainly save more by just not
including the vt layer.
And a few pages can make a difference on _any_ device, not just an embedded
system. For a purp
I checked with Stephen Rothwell too, and he agrees with y'all
that there should be a Orangefs stanza in the MAINTAINERS
file... it will be there next time I push to kernel.org...
Thanks!
-Mike
On Mon, Jan 4, 2016 at 1:45 PM, Dan Carpenter wrote:
> On Mon, Jan 04, 2016 at 11:18:00AM -0500, Mike
On Sun 03-01-16 20:35:14, Al Viro wrote:
[...]
> BTW, far scarier one is not GFP_NOFS or GFP_IO - there's a weird
> caller passing GFP_ATOMIC to __vmalloc(), for no reason I can guess.
>
> _That_ really couldn't be handled without passing gfp_t to page allocation
> primitives, but I very much doub
2016-01-05 12:27 GMT-03:00 Geyslan G. Bem :
> 2016-01-05 12:23 GMT-03:00 Joe Perches :
>> On Tue, 2016-01-05 at 10:12 -0500, Alan Stern wrote:
>>> On Mon, 4 Jan 2016, Geyslan G. Bem wrote:
>>>
>>> > >> @@ -404,12 +422,8 @@ static inline char token_mark(struct ehci_hcd
>>> > >> *ehci, __hc32 token)
On Tue, Jan 05, 2016 at 03:49:18PM +0100, Petr Mladek wrote:
> On Sat 2016-01-02 23:36:03, Michael S. Tsirkin wrote:
> > On Sat, Jan 02, 2016 at 06:43:16AM -0500, Tejun Heo wrote:
> > > On Fri, Jan 01, 2016 at 12:18:17PM +0200, Michael S. Tsirkin wrote:
> > > > > My initial idea was to use a dedica
On 01/05/2016 10:30 AM, Michael S. Tsirkin wrote:
>
> arch/s390/kernel/vdso.c:smp_mb();
>
> Looking at
> Author: Christian Borntraeger
> Date: Fri Sep 11 16:23:06 2015 +0200
>
> s390/vdso: use correct memory barrier
>
> By definition smp_wmb only orde
Hi All,
Also, the latest public version of AMD IOMMU specification that
describes the support for IVHD type 40h and ACPI HID IVHD device type,
implemented by this patch series, is available here
http://support.amd.com/TechDocs/48882_IOMMU.pdf
Thanks,
Suravee
On 01/05/2016 04:07 AM, Wan Zon
Hi Russell,
2015-08-27 10:42 GMT+02:00 Philipp Zabel :
>
> Am Samstag, den 08.08.2015, 17:09 +0100 schrieb Russell King - ARM
> Linux:
> > Following on from the previous sub-series, this sub-series adds audio
> > support to dw-hdmi.
> >
> > The two different variants are now in this patch: AHB aud
2016-01-05 12:15 GMT-03:00 Alan Stern :
> On Mon, 4 Jan 2016, Geyslan G. Bem wrote:
>
>> 2016-01-04 18:01 GMT-03:00 Alan Stern :
>> > On Mon, 4 Jan 2016, Geyslan G. Bem wrote:
>> >
>> >> This patch fixes a coding style issue reported by checkpatch related to
>> >> many leading tabs, removing a 'do
On Tue 05-01-16 15:26:02, Al Viro wrote:
> On Tue, Jan 05, 2016 at 02:59:03PM +0100, Michal Hocko wrote:
>
> > > 3) vmalloc() is for large allocations. They will be page-aligned,
> > > but *not* physically contiguous. OTOH, large physically contiguous
> > > allocations are generally a bad idea.
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Tuesday, January 5, 2016 20:31
> ...
> > To get the payload of hvsock, we need raw=0 to skip the level-1 header
> > (i.e., struct vmpacket_descriptor desc) and we also need to skip the
> > level-2 header (i.e., struct vmpipe_proto_header
Add an initial clock driver for the Arizona series audio CODECs.
Currently this driver only provides support for parsing the two input
clocks (mclk1, mclk2) and providing the internally consumed 32k clock.
Signed-off-by: Charles Keepax
---
MAINTAINERS | 1 +
drivers/clk/K
On Tue, Jan 5, 2016 at 1:27 PM, Geert Uytterhoeven wrote:
> Does it work better if you store the (preferably app-specific) password in
> smtppass in .gitconfig?
No.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Mor
The 32k clock is unconditionally enabled by the MFD core so there is no
need to control it from the extcon device, so this patch removes the
control of the 32k clock.
Signed-off-by: Charles Keepax
---
drivers/extcon/extcon-arizona.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/ex
>> On Wed, Dec 09, 2015 at 10:38:13PM +0530, Niranjan Dighe wrote:
>>> The third argument to function kportal_memhog_alloc is expected to
>>> be gfp_t whereas the actual argument was unsigned int. Fix this by
>>> explicitly typecasting to gfp_t
>>>
>>> Signed-off-by: Niranjan Dighe
>>> ---
>>> dr
Now we have a clock driver that can control the 32k clock use this
rather than directly controlling the 32k clock from the MFD device.
Signed-off-by: Charles Keepax
---
drivers/mfd/Kconfig | 1 +
drivers/mfd/arizona-core.c | 104 +--
inclu
Specify the device tree binding for the input clocks to Arizona devices.
Signed-off-by: Charles Keepax
---
Documentation/devicetree/bindings/mfd/arizona.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
b/Documentation/devicetree/bi
On Mon, Jan 04, 2016 at 08:27:51PM +0800, Chen Feng wrote:
> +/*LDO 2 & LDO 14*/
Please use the normal kernel coding style for comments, I'm surprised
checkpatch didn't warn you about this.
> +static const unsigned int ldo2_voltages[] = {
> + 250, 260, 270, 280,
> + 29000
On 2016-01-05 10:25, Greg KH wrote:
On Tue, Jan 05, 2016 at 09:51:14AM +0100, Pierre Paul MINGOT wrote:
In industrial sector, for obvious security and safety reasons we want
configure our system and have a full control of the devices within it.
So unused or dummy devices are not wanted , not nic
On Mon, Jan 04, 2016 at 08:27:49PM +0800, Chen Feng wrote:
> Add Document for hi655x pmic regulator driver
As indicated in the driver review this seems to be a bit of an unusual
binding that I think needs reworking, also it needs a bit more detail -
for example, listing which regulator names are v
If a certificate is self-signed, don't bother checking the validity of the
signature. The cert cannot be checked by validation against the next one
in the chain as this is the root of the chain. Trust for this certificate
can only be determined by whether we obtained it from a trusted location
(i
On Mon 14-12-15 21:34:26, Jan Kara wrote:
> On Fri 11-12-15 15:54:16, Vegard Nossum wrote:
> > Hit this kernel hang too while fuzzing. Please see this as a tentative
> > patch indicating where the problem is -- I don't really know much about
> > UDF or what an allocation extent is or whether there
On Tue, Jan 05, 2016 at 12:13:46PM +0100, Jan Kara wrote:
> On Sun 03-01-16 10:13:06, Dan Williams wrote:
> > On Wed, Dec 23, 2015 at 11:39 AM, Ross Zwisler
> > wrote:
> > > To properly handle fsync/msync in an efficient way DAX needs to track
> > > dirty
> > > pages so it is able to flush them d
On Tue, Jan 5, 2016 at 1:40 PM, Jean-Michel Hautbois
wrote:
> What is the status of this series ?
> I would like to use audio output in HDMI on my i.MX6 board, but I
> don't know if you have some pending WIP on this ?
This series is in mainline since 4.4-rc1.
--
To unsubscribe from this list: se
Julian Calaby writes:
> Hi Sven,
>
> On Tue, Jan 5, 2016 at 2:29 AM, Sven Dziadek wrote:
>> diff --git a/drivers/staging/rtl8723au/hal/rtl8723a_cmd.c
>> b/drivers/staging/rtl8723au/hal/rtl8723a_cmd.c
>> index 1662c03c..57f5941 100644
>> --- a/drivers/staging/rtl8723au/hal/rtl8723a_cmd.c
>> +++ b
mele...@gmail.com writes:
> From: Daniil Leshchev
>
> use %pM and %ph specifiers instead of placing each byte on stack.
> (staging/rtl8723au/TODO)
>
> Signed-off-by: Daniil Leshchev
> ---
> drivers/staging/rtl8723au/core/rtw_recv.c | 32
> +-
> .../staging/rtl8723au
David Howells wrote:
> If a certificate is self-signed, don't bother checking the validity of the
> signature. The cert cannot be checked by validation against the next one
> in the chain as this is the root of the chain. Trust for this certificate
> can only be determined by whether we obtaine
From: Peter Rosin
Hi!
I have a pair of boards with this i2c topology:
GPIO ---| -- BAT1
| v /
I2C -+--B---+ MUX
| \
EEPROM -- BAT2
(B denotes the bound
Hello,
This email is to restart the discussion around the thread granularity
support for cgroup cpu controller, which got lost around the following
message.
http://thread.gmane.org/gmane.linux.kernel/2021959/focus=14454
While the previous discussion didn't reach a conclusion, it uncovered
the
From: Peter Rosin
Add i2c_lock_bus() and i2c_unlock_bus(), which call the new lock_bus and
unlock_bus ops in the adapter. These funcs/ops take an additional flags
argument that indicates for what purpose the adapter is locked.
There are two flags, I2C_LOCK_ADAPTER and I2C_LOCK_SEGMENT, but they
From: Peter Rosin
The initial core mux structure starts off small with only the parent
adapter pointer, which all muxes have, and a priv pointer for mux
driver private data.
Add i2c_mux_alloc function to unify the creation of a mux.
Where appropriate, pass around the mux core structure instead
From: Peter Rosin
With a i2c topology like the following
GPIO ---| -- BAT1
| v /
I2C -+--+ MUX
| \
EEPROM -- BAT2
there is a locking problem with the GPIO c
From: Peter Rosin
There is a copy of the device pointer in the mux core.
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-pinctrl.c | 23 ---
1 file changed, 8 insertions(+), 15 deletions(-)
diff --git a/drivers/i2c/muxes/i2c-mux-pinctrl.c
b/drivers/i2c/muxes/i2c-
From: Peter Rosin
Instead of checking for i2c parent adapters for every lock/unlock, simply
override the locking for muxes to always lock/unlock the parent adapter
directly.
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-core.c | 21 +++--
drivers/i2c/i2c-mux.c | 27 ++
From: Peter Rosin
All muxes have slave side adapters, many have some arbitrary number of
them. Handle this in the mux core, so that drivers are simplified.
Add i2c_mux_reserve_adapter that can be used when it is known in advance
how many child adapters that is to be added. This avoids reallocati
Hi all,
I've hit the following while fuzzing with trinity inside a KVM tools guest
running the latest
-next kernel:
[2838494.150197]
==
[2838494.152381] BUG: KASAN: use-after-free in task_numa_fault+0xb91/0x37f0 at
addr 88008
On Tue, 2016-01-05 at 16:23 +0100, Rabin Vincent wrote:
> The SKF_AD_ALU_XOR_X ancillary is not like the other ancillary data
> instructions since it XORs A with X while all the others replace A with
> some loaded value. All the BPF JITs fail to clear A if this is used as
> the first instruction i
From: Peter Rosin
The mux select and deselect ops are common to the mux most of the time,
so store the ops in the mux core.
Change the select and deselect op to work in terms of the mux core instead
of the child adapter. No driver uses the child adapter anyway, and if it
is needed in a future mu
[Re: [PATCH] drivers/bus: make uniphier-system-bus.c explicitly non-modular] On
05/01/2016 (Tue 11:31) Masahiro Yamada wrote:
> 2016-01-05 11:26 GMT+09:00 Masahiro Yamada :
> > Hi Paul,
> >
[...]
> >
> >
> > I assume commit 326ea45aa827 ("bus: uniphier: allow only built-in driver")
> > is a tem
On Tue, Jan 05, 2016 at 10:43:45AM -0500, Austin S. Hemmelgarn wrote:
> >I don't understand how reducing the number of vt devices makes anything
> >more or less secure, or better yet, more responsive. Please provide
> >specific details showing how this happens.
> WRT security, the argument isn't t
On Tue, Jan 05, 2016 at 08:00:45AM -0800, Eric Dumazet wrote:
> On Tue, 2016-01-05 at 16:23 +0100, Rabin Vincent wrote:
> > The SKF_AD_ALU_XOR_X ancillary is not like the other ancillary data
> > instructions since it XORs A with X while all the others replace A with
> > some loaded value. All the
On Tue, Jan 05, 2016 at 04:39:37PM +0100, Christian Borntraeger wrote:
> On 01/05/2016 10:30 AM, Michael S. Tsirkin wrote:
>
> >
> > arch/s390/kernel/vdso.c:smp_mb();
> >
> > Looking at
> > Author: Christian Borntraeger
> > Date: Fri Sep 11 16:23:06 2015 +0200
> >
> >
On Tue, Jan 05, 2016 at 04:40:54PM +0100, Jean-Michel Hautbois wrote:
> Hi Russell,
>
> 2015-08-27 10:42 GMT+02:00 Philipp Zabel :
> >
> > Am Samstag, den 08.08.2015, 17:09 +0100 schrieb Russell King - ARM
> > Linux:
> > > Following on from the previous sub-series, this sub-series adds audio
> > >
On Wed, Dec 02, 2015 at 09:18:05AM +1100, Michael Ellerman wrote:
>
> I (still) haven't had a chance to have a good look at it, but I won't this
> week
> anyway. So post v5 and hopefully I can review that and it will be perfect :)
The perfect v5 is there now, for 4 weeks minus the holiday season
From: Peter Rosin
The dev pointer is readily available in the mux core struct, no point in
keeping multiple copies around.
The patch also fixes a bug in rtl2832, which attached its mux slave
adapter to the device owning the mux parent adapter instead of
attaching it to its own device.
Signed-of
On Mon, Jan 4, 2016 at 10:00 PM, Yakir Yang wrote:
> Signed-off-by: Yakir Yang
> Acked-by: Rob Herring
> ---
> Changes in v2:
> - acked by Rob
It doesn't hurt, but there is no point to send a new version just to
add acks. The maintainer should add any for the current version. If
you do send a n
On Tue, 5 Jan 2016, Joe Perches wrote:
> On Tue, 2016-01-05 at 10:12 -0500, Alan Stern wrote:
> > On Mon, 4 Jan 2016, Geyslan G. Bem wrote:
> >
> > > >> @@ -404,12 +422,8 @@ static inline char token_mark(struct ehci_hcd
> > > >> *ehci, __hc32 token)
> > > >>�� return '/';
> > > >>� }
> > > >
On Tue, 2016-01-05 at 15:47 +, David Howells wrote:
> If a certificate is self-signed, don't bother checking the validity of the
> signature. The cert cannot be checked by validation against the next one
> in the chain as this is the root of the chain. Trust for this certificate
> can only be
On 01/04/2016 04:00 PM, Alexandre Belloni wrote:
I'd say that the proper course of action is to refuse to set dates
before 2000 and after 2100. See http://patchwork.ozlabs.org/patch/541037/
Got it.
We have an issue though, Android (or rather any embedded) devices must
continue to function whe
On 01/05/2016 09:53 AM, Jes Sorensen wrote:
Julian Calaby writes:
Hi Sven,
On Tue, Jan 5, 2016 at 2:29 AM, Sven Dziadek wrote:
diff --git a/drivers/staging/rtl8723au/hal/rtl8723a_cmd.c
b/drivers/staging/rtl8723au/hal/rtl8723a_cmd.c
index 1662c03c..57f5941 100644
--- a/drivers/staging/rtl872
On Tue, 2016-01-05 at 11:06 -0500, Alan Stern wrote:
> Trying to come up with hard-and-fast rules for this sort of thing is
> pretty hopeless. Even "Maximize readability" doesn't work too well,
> because different people find different things most readable.
Readability is mostly habituation.
A
On Tue, Jan 05, 2016 at 08:16:52AM -0500, Austin S. Hemmelgarn wrote:
> >We don't do regressions.
> Requiring only a recompilation isn't a regression, especially when it works
> fine without being recompiled, and I have yet to actually see anything that
> changing the number of VT's would break oth
On Wed, Dec 23, 2015 at 08:29:52PM +0800, Jisheng Zhang wrote:
> On Wed, 23 Dec 2015 12:15:12 + Mark Brown wrote:
> > On Wed, Dec 23, 2015 at 07:23:38PM +0800, Jisheng Zhang wrote:
> > > Currently the spi-dw tmode is fixed to SPI_TMOD_TR if cs_control is NULL,
> > > but we
> > > need to set i
On Tue, Jan 05, 2016 at 05:53:41PM +0800, Boqun Feng wrote:
> On Tue, Jan 05, 2016 at 10:51:17AM +0200, Michael S. Tsirkin wrote:
> > On Tue, Jan 05, 2016 at 09:36:55AM +0800, Boqun Feng wrote:
> > > Hi Michael,
> > >
> > > On Thu, Dec 31, 2015 at 09:07:42PM +0200, Michael S. Tsirkin wrote:
> > >
On Tue, Jan 5, 2016 at 1:40 AM, Michael S. Tsirkin wrote:
> On Mon, Jan 04, 2016 at 07:11:25PM -0800, Alexander Duyck wrote:
>> >> The two mechanisms referenced above would likely require coordination with
>> >> QEMU and as such are open to discussion. I haven't attempted to address
>> >> them as
Some Asus notebooks like the Asus E202SA and the Asus X555UB have a
separate ACPI device for notifications from the airplane mode hotkey.
This device is called "Wireless Radio Control" in Asus websites and ASHS
in the DSDT, and its ACPI _HID is ATK4002 in the two models mentioned
above.
For these
On 12/21/2015, 11:30 AM, Mike Galbraith wrote:
> Greetings,
>
> In every tree where 69e5d3f8 is applied,
Hi,
does it mean that upstream is broken too?
> IFF a kvm guest display is set
> up for Spice vs VNC, AND IFF I boot straight into runlevel 5 vs
> stopping at 3 then telinit 5, the X server
The initial s390 vdso code is heavily influenced by the powerpc version
which does have a smp_wmb in vdso_init right before the vdso_ready=1
assignment. s390 has no need for that.
Signed-off-by: Michael S. Tsirkin
---
Untested.
arch/s390/kernel/vdso.c | 2 --
1 file changed, 2 deletions(-)
di
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> > diff --git a/drivers/hv/channel_mgmt.c b/drivers/hv/channel_mgmt.c
> >
> > +/* hvsock related definitions */
> > +enum hvsock_event {
> > + /* The host application is close()-ing the connection */
> > + HVSOCK_RESCIND_CHANNEL,
> > +};
>
On 5 January 2016 at 08:58, Andy Shevchenko wrote:
> On Tue, Jan 5, 2016 at 3:25 PM, João Paulo Rechi Vita
> wrote:
>> This series implements the driver for the "Asus Wireless Radio Control"
>> device,
>> as named on the vendor website, which handles notifications from the airplane
>> mode hotk
smp_mb on vcpu destroy isn't paired with anything, violating pairing
rules, and seems to be useless.
Drop it.
Signed-off-by: Michael S. Tsirkin
---
Untested.
arch/s390/kvm/kvm-s390.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
index 8
Trust for a self-signed certificate can normally only be determined by
whether we obtained it from a trusted location (ie. it was built into the
kernel at compile time), so there's not really any point in checking it -
we could verify that the signature is valid, but it doesn't really tell us
anyth
Hi Charles,
[auto build test WARNING on clk/clk-next]
[also build test WARNING on v4.4-rc8 next-20160105]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Charles-Keepax/extcon-arizona-Remove
At the moment, xchg on sh only supports 4 and 1 byte values, so using it
from smp_store_mb means attempts to store a 2 byte value using this
macro fail.
And this happens to be exactly what virtio drivers want to do.
Add a 2-byte xchg variant.
Suggested-by: Peter Zijlstra
Signed-off-by: Michael
G Gregory wrote:
>I'm confused by this patch. We already have code like this in
>tty-next, in the form of sbsa_uart_probe():
>
>https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/tty/+/tty-next/drivers/tty/serial/amba-pl011.c#2553
>
Because Russell expressed unhappiness at that cod
On Wed 30-12-15 15:33:47, Tetsuo Handa wrote:
> >From 7fcac2054b33dc3df6c5915a58f232b9b80bb1e6 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Wed, 30 Dec 2015 15:24:40 +0900
> Subject: [RFC][PATCH] sysrq: ensure manual invocation of the OOM killer under
> OOM livelock
>
> This patch is si
> Every time you send a set of patches,
I suggested some updates for Linux source files since October 2014.
> there are legitimate issues which people raise,
There was usual feedback.
> and every time they are discussed,
The discussion results were mixed between acceptance
and usual disagree
On 2016-01-05 11:11, Theodore Ts'o wrote:
On Tue, Jan 05, 2016 at 08:16:52AM -0500, Austin S. Hemmelgarn wrote:
We don't do regressions.
Requiring only a recompilation isn't a regression, especially when it works
fine without being recompiled, and I have yet to actually see anything that
changi
Hi Charles,
[auto build test ERROR on clk/clk-next]
[also build test ERROR on v4.4-rc8 next-20160105]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Charles-Keepax/extcon-arizona-Remove
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Tuesday, January 5, 2016 20:39
> ...
> > +/*
> > + * vmbus_sendpacket_hvsock - Send the hvsock payload 'buf' of a length
> > 'len'
> > + */
> > +int vmbus_sendpacket_hvsock(struct vmbus_channel *channel, void *buf,
> u32 len)
> > ...
>
On Fri 01-01-16 06:38:11, Al Viro wrote:
> From: Al Viro
>
> Signed-off-by: Al Viro
Looks good. I guess it's more convenient for you to take this change
through your tree so:
Acked-by: Jan Kara
Honza
> ---
> fs/udf/inode.c |
Hello:
Question: The vm_operations_struct structure contains lots of callback
pointers. Is there any mechanism to prevent the callback routines and
the structure itself being unloaded from memory (if they are built into
modules) while the relevant VMAs are still in use?
Consider a simple example
On Tue, 5 Jan 2016, Joe Perches wrote:
> On Tue, 2016-01-05 at 11:06 -0500, Alan Stern wrote:
> > Trying to come up with hard-and-fast rules for this sort of thing is�
> > pretty hopeless.� Even "Maximize readability" doesn't work too well,�
> > because different people find different things most
On Thu, Dec 31, 2015 at 02:53:29PM +1100, Stephen Rothwell wrote:
> Hi Ulf,
>
> After merging the mmc-uh tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/mmc/host/sdhci-tegra.c:361:38: error: redefinition of
> 'sdhci_tegra210_pdata'
> static const struct s
On Fri, Jan 01, 2016 at 08:03:47AM +0800, Leo Yan wrote:
> Hi Eduardo,
>
> Thanks for review.
>
> On Thu, Dec 31, 2015 at 09:21:26AM -0800, Eduardo Valentin wrote:
> > On Wed, Dec 30, 2015 at 06:38:40PM +0800, Leo Yan wrote:
> > > k_po/k_pu are in essence ratio values compared with sustainable po
On Mon, Jan 04, 2016 at 07:47:58AM +1100, Dave Chinner wrote:
> > I'm recompiling, to try it again.
> > Maybe, in the meanwhile, you can do something with my files. You can find
> > 'em here:
> > http://mail.gelma.net/xfs_kasan
>
> Any update on this problem, Andrea?
Here we are!
Reproduced right
On Mon, Jan 04, 2016 at 11:22:26AM +, Daniel Thompson wrote:
> On 01/01/16 00:03, Leo Yan wrote:
> >Hi Eduardo,
> >
> >Thanks for review.
> >
> >On Thu, Dec 31, 2015 at 09:21:26AM -0800, Eduardo Valentin wrote:
> >>On Wed, Dec 30, 2015 at 06:38:40PM +0800, Leo Yan wrote:
> >>>k_po/k_pu are in e
[CCing David]
On Sun 03-01-16 17:27:28, Dave Jones wrote:
> This is an odd one..
>
> Out of memory: Kill process 5861 (trinity-c10) score 504 or sacrifice child
> BUG: spinlock recursion on CPU#1, trinity-c8/8828
> lock: 0x8800a3635410, .magic: dead4ead, .owner: trinity-c8/8828,
> .owner_cp
On 01/05/2016 05:03 PM, Rabin Vincent wrote:
On Tue, Jan 05, 2016 at 08:00:45AM -0800, Eric Dumazet wrote:
On Tue, 2016-01-05 at 16:23 +0100, Rabin Vincent wrote:
The SKF_AD_ALU_XOR_X ancillary is not like the other ancillary data
instructions since it XORs A with X while all the others replace
On 01/05/2016 04:23 PM, Rabin Vincent wrote:
The SKF_AD_ALU_XOR_X ancillary is not like the other ancillary data
instructions since it XORs A with X while all the others replace A with
some loaded value. All the BPF JITs fail to clear A if this is used as
the first instruction in a filter. This
[as i am not subscribed to lkml, if you answer please reply to my address also]
some MMC updates merged into 4.4 break the wireless (Broadcom 43340 (sdio))
(and possibly other stuff) on Asus X205TA.
I did a git bisect, the offending commit is: 9faac7b95
It was merged with other MMC updates int
Em Tue, Jan 05, 2016 at 07:43:07PM +0900, Namhyung Kim escreveu:
> Hi,
>
> On Tue, Jan 05, 2016 at 02:32:47PM +0800, Wangnan (F) wrote:
> >
> >
> > On 2016/1/5 13:36, Namhyung Kim wrote:
> > >Currently perf report only shows a help message "For a higher level
> > >overview, try: perf report --so
Mimi Zohar wrote:
> You're missing Petko's patch:
> 41c89b6 IMA: create machine owner and blacklist keyrings
It should also be cc'd to the keyrings mailing list.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.or
This patch series adds support for Toradex Apalis iMX6Q/D SoM module [1] and
Ixora carrier board [2].
Petr Štetiar has simply taken content of DTSes from Toradex's Git tree [3],
removed not mainlined stuff and fixed all errors returned by checkpatch script.
Please note that RESET_MOCI# used as m
On Mon, 4 Jan 2016, Joe Perches wrote:
> On Mon, 2016-01-04 at 19:07 -0300, Geyslan G. Bem wrote:
> > 2016-01-04 18:52 GMT-03:00 Sergei Shtylyov :
> > > > > > > This patch fixes coding style issues reported by checkpatch
> > > > > > > concerning
> > > > > > > to unnecessary space after a cast.
>
From: Petr Štetiar
Signed-off-by: Petr Štetiar
Signed-off-by: Marcel Ziswiler
---
Changes in v2:
- clarify exact Apalis iMX6Q/D SoM type in cover letter
- clarify exact Apalis iMX6Q/D module type and Ixora carrier board in model
node
- got rid of obsolete mmc aliases
- working SGTL5000 audio
From: Petr Štetiar
Signed-off-by: Petr Štetiar
Signed-off-by: Marcel Ziswiler
---
Changes in v2: None
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/imx6q-apalis-ixora.dts | 256 +++
2 files changed, 257 insertions(+)
create mode 100644 arch/
Hi,
This may well have been buried with the holidays. It still applies
fine on next-20160105, but I notice patch 2 will trivially conflict
with [2] on some context lines.
As discussed here[1], these patches implement a MEMREMAP_WC flag for
memremap(), which can be used to obtain writecombine
On 01/05/2016 07:57 AM, Peter Rosin wrote:
From: Peter Rosin
The initial core mux structure starts off small with only the parent
adapter pointer, which all muxes have, and a priv pointer for mux
driver private data.
Add i2c_mux_alloc function to unify the creation of a mux.
Where appropriate
Use memset_io() for DMA_MEMORY_IO mappings which are mapped as I/O
memory, and regular memset() for DMA_MEMORY_MAP mappings.
This fixes the below alignment fault on arm64 for DMA_MEMORY_IO
mappings, where memset() uses the DC ZVA instruction which is
invalid on device memory.
Unhandled fault:
When the DMA_MEMORY_MAP flag is used, memory which can be accessed
directly should be returned, so use memremap(..., MEMREMAP_WC) to
provide a writecombine mapping.
Signed-off-by: Brian Starkey
Reviewed-by: Catalin Marinas
---
drivers/base/dma-coherent.c | 20
1 file chan
Add a flag to memremap() for writecombine mappings. Mappings satisfied
by this flag will not be cached, however writes may be delayed or
combined into more efficient bursts. This is most suitable for
buffers written sequentially by the CPU for use by other DMA devices.
Signed-off-by: Brian Starkey
On Sunday 22 March 2015 14:46:11 Pali Rohár wrote:
> This patch adds detection of trackstick for v7 protocol devices. Code in this
> patch is used in official Dell touchpad linux drivers for Dell models:
> Dell Latitude E5250/5250, E5450/5450, E5550/5550
>
> Detection code and base reg for alps v3
Mimi Zohar wrote:
> You're missing Petko's patch:
> 41c89b6 IMA: create machine owner and blacklist keyrings
Hmmm... This is wrong. x509_key_preparse() shouldn't be polling the IMA MOK
keyring under all circumstances.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-ke
Hello,
This patchset implements cgroup v2 interface for cpu controller and a
repost of the following.
http://lkml.kernel.org/g/1438641689-14655-1-git-send-email...@kernel.org
The first patch is folded and applied into v2 documentation. The
second patch is unchanged. The third is unchanged fro
While the cpu controller doesn't have any functional problems, there
are a couple interface issues which can be addressed in the v2
interface.
* cpuacct being a separate controller. This separation is artificial
and rather pointless as demonstrated by most use cases co-mounting
the two contro
Make the following changes in preparation for the cpu controller
interface implementation for the unified hierarchy. This patch
doesn't cause any functional differences.
* s/cpu_stats_show()/cpu_cfs_stats_show()/
* s/cpu_files/cpu_legacy_files/
* Separate out cpuacct_stats_read() from cpuacct_s
301 - 400 of 1146 matches
Mail list logo
