On Thu, 2016-12-08 at 11:10 +0100, Daniel Vetter wrote:
> > With drmfb you basically have to shadow everything into memory & copy
> > over everything, and locks you out of simple 2D accel. For a simple text
> > console the result is orders of magnitude slower and memory hungry than
> > a simple fbd
On Thu, Dec 8, 2016 at 2:56 AM, Dan Carpenter wrote:
> My static checker complains that we put an upper bound on the "size"
> variable but not a lower bound. The checker is not smart enough to know
> the possible ranges of "old_mm->context.ldt->size" from
> init_new_context_ldt() so it thinks may
On Tue, 6 Dec 2016, Prarit Bhargava wrote:
> The current unhandled IRQ warning doesn't output enough information on x86 to
> determine which device issued an interrupt. For example,
>
> irq 16: nobody cared (try booting with the "irqpoll" option)
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0
On Tue, Dec 6, 2016 at 7:52 PM, John Youn wrote:
> On 12/6/2016 5:48 PM, John Stultz wrote:
>> Hey John,
>> Just wanted to send this by you, as it seems something is
>> slightly off with the GOTGCTL state when removing a otg adapter
>> cable. The following seems to work around the issue I'm seei
On 08.12.2016 23:18, Pavel Machek wrote:
> On Thu 2016-12-08 23:12:10, Lino Sanfilippo wrote:
>> Hi,
>>
>> On 08.12.2016 22:54, Pavel Machek wrote:
>> > On Thu 2016-12-08 21:32:12, Lino Sanfilippo wrote:
>> >> Hi,
>> >>
>> >> On 08.12.2016 00:15, Francois Romieu wrote:
>> >> > Lino Sanfilippo :
On Thu, Dec 08, 2016 at 09:46:35PM +, Abel Vesa wrote:
> From: Jean-Jacques Hiblot
>
> From: Jean-Jacques Hiblot
>From statement twice in the commit message. Will resend.
>
> The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible for a ftrace
> operation to specify if registers need
On Wed, Dec 7, 2016 at 3:06 AM, Greg KH wrote:
> On Tue, Dec 06, 2016 at 08:09:30PM -0600, Chris Bostic wrote:
>> From: Jeremy Kerr
>>
>> Signed-off-by: Jeremy Kerr
>> Signed-off-by: Chris Bostic
>> ---
>> drivers/fsi/fsi-core.c | 20
>> drivers/fsi/fsi-master.h | 37 +++
From: Jean-Jacques Hiblot
The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible for a ftrace
operation to specify if registers need to saved/restored by the ftrace handler.
This is needed by kgraft and possibly other ftrace-based tools, and the ARM
architecture is currently lacking this fe
The LCD bus width does not need to align with the pixel format. The
LCDIF controller automatically converts between pixel formats and
bus width by padding or dropping LSBs.
The DRM subsystem has the notion of bus_format which allows to
determine what bus_formats are supported by the display. Choos
On Thu, 8 Dec 2016, Geert Uytterhoeven wrote:
> On Wed, Dec 7, 2016 at 11:36 PM, Finn Thain
> wrote:
> > On Wed, 7 Dec 2016, Geert Uytterhoeven wrote:
> >> - Convert from printk() to pr_*(),
> >> - Add missing continuations, to fix user-visible breakage,
> >> - Drop useless WARNING prefix
On Thu, 8 Dec 2016, Pavel Machek wrote:
> On Thu 2016-12-08 10:18:13, Thomas Gleixner wrote:
> > I'm dealing with low-speed systems for 20 years now and that LED was never
> > important for me, quite the contrary, it's annoying to have the extra work
> > in the idle wakeup path which causes extra p
On 12/08/2016 11:27 PM, Ksenija Stanojevic wrote:
> Add core files for low resolution analog-to-digital converter (mxs-lradc)
> MFD driver.
>
> Signed-off-by: Ksenija Stanojevic
Just a nit below.
> +++ b/include/linux/mfd/mxs-lradc.h
> @@ -0,0 +1,187 @@
> +/*
[...]
> +#define LRADC_CTRL1_MX28
On 12/08/2016 11:27 PM, Ksenija Stanojevic wrote:
> Split existing driver mxs-lradc into MFD with touchscreen and
> IIO part.
>
> Tested on I.MX28
>
> Ksenija Stanojevic (5):
> mfd: mxs-lradc: Add support for mxs-lradc MFD
> iio: adc: mxs-lradc: Add support for adc driver
> input: touchscre
Hi Dave,
(CC'ing LKML and Greg KH)
On Thursday 08 Dec 2016 12:31:55 Dave Stevenson wrote:
> Hi All.
>
> I'm working with a USB webcam which has been seen to spontaneously
> disconnect when in use. That's a separate issue, but when it does it
> throws a load of warnings into the kernel log if the
On 11/25, Y.T. Tang wrote:
> Hi Scott,
>
> > -Original Message-
> > From: Scott Wood
> > Sent: Thursday, November 24, 2016 4:21 PM
> > To: Y.T. Tang ; mturque...@baylibre.com
> > Cc: sb...@codeaurora.org; linux-...@vger.kernel.org; linux-
> > ker...@vger.kernel.org; linux-arm-ker...@lists.
On 11/23, Stephen Boyd wrote:
> The broadcom clk driver Kconfig file selects and depends on the
> COMMON_CLK_IPROC config for different SoC specific drivers. Let's
> simplify this by always selecting the COMMON_CLK_IPROC config,
> turning it into a set of library code. We still want to retain
> the
On Thu, 8 Dec 2016, Dan Carpenter wrote:
> My static checker complains that we put an upper bound on the "size"
> variable but not a lower bound. The checker is not smart enough to know
> the possible ranges of "old_mm->context.ldt->size" from
> init_new_context_ldt() so it thinks maybe it could b
On Thu, 8 Dec 2016, Geert Uytterhoeven wrote:
> On Wed, Dec 7, 2016 at 11:45 PM, Finn Thain
> wrote:
> > On Wed, 7 Dec 2016, Geert Uytterhoeven wrote:
> >
> >> - Introduce helpers for printing debug messages, incl. dummies for
> >> validating format strings when debugging is disabled,
> >
From: "Jason A. Donenfeld"
Date: Thu, 8 Dec 2016 23:20:04 +0100
> Hi David,
>
> On Thu, Dec 8, 2016 at 1:37 AM, David Miller wrote:
>> You really have to land the IP header on a proper 4 byte boundary.
>>
>> I would suggest pushing 3 dummy garbage bytes of padding at the front
>> or the end of
On 11/11, Christophe JAILLET wrote:
> It is likely that instead of '1>64', 'q>64' was expected.
>
> Moreover, according to datasheet,
>http://www.ti.com/lit/ds/symlink/cdce925.pdf
>SCAS847I - JULY 2007 - REVISED OCTOBER 2016
> PLL settings limits are: 16 <= q <= 63
> So change the upper li
On Nov 23, 2016 10:16 AM, "Dmitry Safonov" wrote:
>
> From commit 90954e7b9407 ("x86/coredump: Use pr_reg size, rather that
> TIF_IA32 flag") elf coredump file is constructed according to register
> set size - and that's good: if binary crashes with 32-bit code selector,
> generate 32-bit ELF core
On 11/01, Paul Cercueil wrote:
> Previously, the clocks with a fixed divider would report their rate
> as being the same as the one of their parent, independently of the
> divider in use. This commit fixes this behaviour.
>
> This went unnoticed as neither the jz4740 nor the jz4780 CGU code
> have
Lino Sanfilippo :
[...]
> OTOH Pavel said that he actually could produce a deadlock. Now I wonder if
> this is caused by that locking scheme (in a way I have not figured out yet)
> or if it is a different issue.
stmmac_tx_err races with stmmac_xmit.
--
Ueimor
On Wed, 7 Dec 2016, Doug Anderson wrote:
> Hi,
>
> On Wed, Nov 23, 2016 at 12:57 PM, Mikulas Patocka wrote:
> > Hi
> >
> > The GFP_NOIO allocation frees clean cached pages. The GFP_NOWAIT
> > allocation doesn't. Your patch would incorrectly reuse buffers in a
> > situation when the memory is f
On 12/8/2016 2:43 PM, John Stultz wrote:
> On Tue, Dec 6, 2016 at 7:52 PM, John Youn wrote:
>> On 12/6/2016 5:48 PM, John Stultz wrote:
>>> Hey John,
>>> Just wanted to send this by you, as it seems something is
>>> slightly off with the GOTGCTL state when removing a otg adapter
>>> cable. The f
From: "Strashko, Grygorii"
The below call chain generates "scheduling while atomic" backtrace and
causes system crash when Keystone 2 IRQ chip driver is used with RT-kernel:
gic_handle_irq()
|-__handle_domain_irq()
|-generic_handle_irq()
|-keystone_irq_handler()
|-regmap_read()
|-
On 12/08/2016 05:10 PM, sb...@codeaurora.org wrote:
> On 11/25, Y.T. Tang wrote:
>> Hi Scott,
>>
>>> -Original Message-
>>> From: Scott Wood
>>> Sent: Thursday, November 24, 2016 4:21 PM
>>> To: Y.T. Tang ; mturque...@baylibre.com
>>> Cc: sb...@codeaurora.org; linux-...@vger.kernel.org; lin
On 12/08/2016 09:46 PM, Stefan Agner wrote:
> On 2016-12-07 18:37, Marek Vasut wrote:
>> On 12/08/2016 02:26 AM, Stefan Agner wrote:
>>> On 2016-12-07 16:59, Stefan Agner wrote:
On 2016-12-07 16:49, Marek Vasut wrote:
> On 12/08/2016 01:27 AM, Stefan Agner wrote:
>> The DRM subsystem s
Hi Shuah,
On Thu, Dec 08, 2016 at 07:46:03AM -0700, Shuah Khan wrote:
> Hi Sakari,
>
> On 12/07/2016 03:27 PM, Sakari Ailus wrote:
> > Hi Shuah,
> >
> > On Wed, Dec 07, 2016 at 01:03:59PM -0700, Shuah Khan wrote:
> >> Hi Sakari,
> >>
> >> On 12/07/2016 03:52 AM, Sakari Ailus wrote:
> >>> Hi Shua
Hi Bjorn,
Today's linux-next merge of the pci tree got a conflict in:
drivers/pci/msi.c
between commit:
62c61514191b ("doc: Add missing parameter for msi_setup")
from Linus' tree and commit:
67f1e4473857 ("PCI/MSI: Document new parameter for msi_capability_init()")
from the pci tree.
On Thu, Dec 08, 2016 at 08:49:32PM -, Thomas Gleixner wrote:
> The clocksource delta to nanoseconds conversion is using signed math, but
> the delta is unsigned. This makes the conversion space smaller than
> necessary and in case of a multiplication overflow the conversion can
> become negativ
On Thu, Dec 08, 2016 at 08:49:34PM -, Thomas Gleixner wrote:
> Propagating a unsigned value through signed variables and functions makes
> absolutely no sense and is just prone to (re)introduce subtle signed
> vs. unsigned issues as happened recently.
>
> Clean it up.
>
> Signed-off-by: Thoma
On Thu, Dec 08, 2016 at 08:49:38PM -, Thomas Gleixner wrote:
> The resume code must deal with a clocksource delta which is potentially big
> enough to overflow the 64bit mult.
>
> Replace the open coded handling with the proper function.
>
> Signed-off-by: Thomas Gleixner
Reviewed-by: David
On Thu, Dec 08, 2016 at 08:49:45PM -, Thomas Gleixner wrote:
> Kill the ever confusing typedef and use u64.
>
> NOT FOR INCLUSION - Must be regenerated at some point via coccinelle
>
> Not-Signed-off-by: Thomas Gleixner
Not-Reviewed-by: David Gibson
The concept seems sensible to me, I hav
On Thu, Dec 08, 2016 at 08:49:36PM -, Thomas Gleixner wrote:
> cycles_t is defined as u64, so casting it to u64 is a pointless and
> confusing exercise. cycles_t should simply go away and be replaced with a
> plain u64 to avoid further confusion.
>
> Signed-off-by: Thomas Gleixner
Reviewed-b
Hi,
this patch series removes unnecessary private locks in the sxgbe and the
stmmac driver.
v2:
- adjust commit message
The driver uses a private lock for synchronization of the xmit function and
the xmit completion handler, but since the NETIF_F_LLTX flag is not set,
the xmit function is also called with the xmit_lock held.
On the other hand the completion handler uses the reverse locking order by
first taking the
The driver uses a private lock for synchronization of the xmit function and
the xmit completion handler, but since the NETIF_F_LLTX flag is not set,
the xmit function is also called with the xmit_lock held.
On the other hand the completion handler uses the reverse locking order by
first taking the
Hi Srinivas,
On 12/07/2016 07:32 PM, Srinivas Kandagatla wrote:
> This patch add support to return value from host_init() callback from drivers,
> so that the designware libary can handle or pass it to proper place. Issue
> with
> void return type is that errors or error handling within host_ini
Hi Colin
> From: Colin Ian King
>
> On an error, snd_ctl_add already free's kctrl, so calling snd_ctl_free_one
> to free it again leads to a double free error. Fix this by removing
> the extraneous snd_ctl_free_one call.
>
> Issue found using static analysis with CoverityScan, CID 1372908
>
On Thu, Dec 8, 2016 at 8:30 AM, Dmitry Vyukov wrote:
> Chain exists of:
> Possible unsafe locking scenario:
>
>CPU0CPU1
>
> lock(sb_writers#5);
>lock(&u->bindlock);
>l
On 9 December 2016 at 07:28, Benjamin Herrenschmidt
wrote:
> On Thu, 2016-12-08 at 11:10 +0100, Daniel Vetter wrote:
>> > With drmfb you basically have to shadow everything into memory & copy
>> > over everything, and locks you out of simple 2D accel. For a simple text
>> > console the result is o
From: Andi Kleen
An earlier patch allowed enabling PT and LBR at the same
time on Goldmont. However it also allowed enabling BTS and LBR
at the same time, which is still not supported. Fix this by
bypassing the check only for PT.
Marking for stable because this allows crashing kernels. Also
shou
On Thu, Dec 8, 2016 at 10:02 AM, Dmitry Vyukov wrote:
> Chain exists of:
> Possible unsafe locking scenario:
>
>CPU0CPU1
>
> lock(nlk->cb_mutex);
>lock(&table[i].mutex);
>
On 09/20, Arvind Yadav wrote:
> From: Arvind Yadav
>
> Free memory, if init is not successful.
>
> Signed-off-by: Arvind Yadav
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 09/20, Arvind Yadav wrote:
> From: Arvind Yadav
>
> Free memory and memory mapping , if pxa910_clk_init is not successful.
>
> Signed-off-by: Arvind Yadav
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Proje
Hi Stephen
> > @@ -111,14 +112,13 @@ int asoc_simple_card_parse_clk(struct device_node
> > *node,
> > * or "system-clock-frequency = "
> > * or device's module clock.
> > */
> > - clk = of_clk_get(node, 0);
> > + clk = devm_get_clk_from_child(dev, node, NULL);
> > if (!I
On 09/20, Arvind Yadav wrote:
> From: Arvind Yadav
>
> Free memory and memory mapping , if mmp2_clk_init is not successful.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/clk/mmp/clk-of-mmp2.c | 15 ---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/drivers
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, December 8, 2016 7:56 AM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com; lean
Hi Stephen
> > From: Kuninori Morimoto
> >
> > Current simple-card is supporting this style for clocks
> >
> > sound {
> > ...
> > simple-audio-card,cpu {
> > sound-dai = <&xxx>;
> > clocks = <&cpu_clock>;
> > };
>
Hi Stephen
> > From: Kuninori Morimoto
> >
> > Current simple-card is supporting this style for clocks
> >
> > sound {
> > ...
> > simple-audio-card,cpu {
> > sound-dai = <&xxx>;
> > clocks = <&cpu_clock>;
> > };
>
On 12/07, Irina Tirdea wrote:
> The BayTrail and CherryTrail platforms provide platform clocks
> through their Power Management Controller (PMC).
>
> The SoC supports up to 6 clocks (PMC_PLT_CLK[5:0]) with a
> frequency of either 19.2 MHz (PLL) or 25 MHz (XTAL) for BayTrail
> an a frequency of 19.
Hi Stephen, Mark
> > This is v5 of "clkdev: add devm_of_clk_get()", but new series.
> > I hope my understanding was correct with your idea.
>
> Yes this looks good. Given that we're so close to the merge
> window, perhaps I should just merge the first patch into clk-next
> and then it will be re
On 12/09, Kuninori Morimoto wrote:
>
> Hi Stephen
>
> > > From: Kuninori Morimoto
> > >
> > > Current simple-card is supporting this style for clocks
> > >
> > > sound {
> > > ...
> > > simple-audio-card,cpu {
> > > sound-dai = <&xxx>;
> > >
On 12/09, Kuninori Morimoto wrote:
>
> Hi Stephen
>
> > > @@ -111,14 +112,13 @@ int asoc_simple_card_parse_clk(struct device_node
> > > *node,
> > >* or "system-clock-frequency = "
> > >* or device's module clock.
> > >*/
> > > - clk = of_clk_get(node, 0);
> > > + clk = devm_get_cl
On 12/08, Scott Wood wrote:
> On 12/08/2016 05:10 PM, sb...@codeaurora.org wrote:
> > On 11/25, Y.T. Tang wrote:
> >> Hi Scott,
> >>
> >>> -Original Message-
> >>> From: Scott Wood
> >>> Sent: Thursday, November 24, 2016 4:21 PM
> >>> To: Y.T. Tang ; mturque...@baylibre.com
> >>> Cc: sb...@
On Thu, Dec 8, 2016 at 9:16 AM, Dmitry Vyukov wrote:
> Chain exists of:
> Possible unsafe locking scenario:
>
>CPU0CPU1
>
> lock(genl_mutex);
>lock(nlk->cb_mutex);
>lo
Hi Stephen
> > Documentation/devicetree/bindings/sound/simple-card.txt
> > explains 1st of_clk_get will be used as "if needed",
> > 2nd of_clk_get will be used as "not needed pattern".
> > 1st pattern will use specific clock, 2nd pattern will use
> > "cpu" or "codec" clock.
> > 2nd one was added
On Thu, Dec 08, 2016 at 05:31:13PM +, David Howells wrote:
> Lukas Wunner wrote:
> > > +out_efi_err:
> > > + pr_efi_err(sys_table_arg, "Could not determine UEFI Secure Boot
> > > status.\n");
> > > + if (status == EFI_NOT_FOUND)
> > > + return efi_secureboot_mode_disabled;
> > > + ret
On 09/20, Arvind Yadav wrote:
> From: Arvind Yadav
>
> Free memory mapping, if of_pll_div_clk_init is not successful.
>
> Signed-off-by: Arvind Yadav
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
In file included from include/linux/byteorder/big_endian.h:4:0,
from arch/powerpc/include/uapi/asm/byteorder.h:13,
from include/asm-generic/bitops/l
Joel Fernandes writes:
> Usage llist_del_first needs lock protection, however the table in the
> comments of llist.h show a '-'. Correct this, and also add better
> comments on top.
>
> Cc: Huang Ying
> Cc: Ingo Molnar
> Cc: Will Deacon
> Cc: Paul McKenney
> Signed-off-by: Joel Fernandes
> -
On 09/19, Arvind yadav wrote:
> From: Arvind Yadav
>
> Free memory mapping, if probe is not successful.
>
> Signed-off-by: Arvind Yadav
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On (12/08/16 11:17), Cory Pruce wrote:
>Just wondering if it was really necessary to use the disk struct. It seems
>like the struct is more used for record keeping/io config than actually
>holding the data (actual data is worked with via page operations).
>
>Is this correct? What w
On Thu, Dec 8, 2016 at 4:35 PM, Huang, Ying wrote:
> Joel Fernandes writes:
>
>> Usage llist_del_first needs lock protection, however the table in the
>> comments of llist.h show a '-'. Correct this, and also add better
>> comments on top.
>>
>> Cc: Huang Ying
>> Cc: Ingo Molnar
>> Cc: Will Dea
On Thu, Dec 8, 2016 at 4:42 PM, Joel Fernandes wrote:
> On Thu, Dec 8, 2016 at 4:35 PM, Huang, Ying wrote:
>> Joel Fernandes writes:
>>
>>> Usage llist_del_first needs lock protection, however the table in the
>>> comments of llist.h show a '-'. Correct this, and also add better
>>> comments on
On 12/06, Grygorii Strashko wrote:
> Subject: [PATCH] cpts refclk sel
>
> Signed-off-by: Grygorii Strashko
> ---
> arch/arm/boot/dts/keystone-k2e-netcp.dtsi | 10 +-
> drivers/net/ethernet/ti/cpts.c| 52
> ++-
> 2 files changed, 60 insertions(+), 2 de
Hi Stephen
> > > I don't see any reason why we need this patch though. The binding
> > > works as is, so supporting different styles doesn't seem like a
> > > good idea to me. Let's just keep what we have? Even if a sub-node
> > > like cpu or codec gets more than one element in the clocks list
>
On 12/08/2016 11:52 PM, Stefan Agner wrote:
> The LCD bus width does not need to align with the pixel format. The
> LCDIF controller automatically converts between pixel formats and
> bus width by padding or dropping LSBs.
>
> The DRM subsystem has the notion of bus_format which allows to
> determ
* Memory
memblock for DDR3 1GB
* Regulator
3.3V for panel and backlight.
* Display
Enable HDMI and LVDS panel. Savageboard supports AVIC TM097TDH02 panel
which is compatible with Hannstar HSD100PXN1, so reuse it.
* Clock
The commit d28be499c45e6 is applied to support LVDS and HDMI outp
Use common board file and support SATA interface additionally.
Specify this dtb file for i.MX6 build.
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/imx6q-savageboard.dts | 54 +
2 files changed, 55 insertions(+)
cre
Poslab Savageboard is i.MX6 SoC base, but BSP code from the vendor is
not mainline u-boot and kernel. Personal reason of using this board is
testing etnaviv user-space driver, so I re-write device tree files based on
mainline kernel for the first step.
This patchset includes common DT file, dual
Common savageboard DT file is used for board support.
Specify this dtb file for i.MX6Q build.
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/imx6dl-savageboard.dts | 50
2 files changed, 51 insertions(+)
create mod
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, December 08, 2016 10:05 AM
> To: Stuart Yoder
> Cc: de...@driverdev.osuosl.org; ag...@suse.de; a...@arndb.de;
> linux-kernel@vger.kernel.org; Leo Li
> ; Catalin Horghidan ; Ioana
> Ciornei
> ; Laur
Basically when plugging in various cables in different orders, I'm
occasionally seeing the following BUG splat:
[ 86.215403] BUG: scheduling while atomic: kworker/u16:2/53/0x0002
[ 86.219164] usb 1-1: USB disconnect, device number 9
[ 86.226845] Preemption disabled at:[ 86.230218]
[] d
On Thu, Dec 08, 2016 at 04:08:27PM -0800, Cong Wang wrote:
> On Thu, Dec 8, 2016 at 8:30 AM, Dmitry Vyukov wrote:
> > Chain exists of:
> > Possible unsafe locking scenario:
> >
> >CPU0CPU1
> >
> > lock(sb_writers#5);
> >
On Thu, Dec 08, 2016 at 11:33:00AM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> Using kmalloc with the vmalloc fallback for larger allocations is a
> common pattern in the kernel code. Yet we do not have any common helper
> for that and so users have invented their own helpers. Some of the
The commit 10efbf5f1633 introduced NanoPi M1 board but it's missing in
Allwinner H3 DTB build.
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index cccdbcb..4cbdf6f 100644
--- a/ar
Hi, Dan
Good to see you here!
> From: dan.j.willi...@gmail.com [mailto:dan.j.willi...@gmail.com] On Behalf Of
> Dan Williams
> Subject: Re: [PATCH 08/11] ACPICA: Tables: Back port
> acpi_get_table_with_size() and
> early_acpi_os_unmap_memory() from Linux kernel
>
> On Tue, Nov 29, 2016 at 11:2
On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook wrote:
> Hi,
>
> I'd like to get the GCC plugins building under
> allyesconfig/allmodconfig for -next soon (with the intention of
> landing the change in v4.11). Specifically, I intend to revert
> a519167e753e ("gcc-plugins: disable under COMPILE_TEST").
Rob,
Could you please respond on these comments? I've got some free time, so I wanna
rewrite the code until I've not got busy again.
Regards,
-Sergey
On Mon, Dec 05, 2016 at 10:04:56PM +0300, Serge Semin
wrote:
> On Mon, Dec 05, 2016 at 11:27:07AM -0600, Rob Herring wrote:
> > On Mon, Dec 5, 2
On Thu, Dec 8, 2016 at 5:49 PM, Zheng, Lv wrote:
> Hi, Dan
>
> Good to see you here!
>
>> From: dan.j.willi...@gmail.com [mailto:dan.j.willi...@gmail.com] On Behalf
>> Of Dan Williams
>> Subject: Re: [PATCH 08/11] ACPICA: Tables: Back port
>> acpi_get_table_with_size() and
>> early_acpi_os_unmap
Hi, Rafael and Dan
> From: Dan Williams [mailto:dan.j.willi...@intel.com]
> Subject: Re: [PATCH 08/11] ACPICA: Tables: Back port
> acpi_get_table_with_size() and
> early_acpi_os_unmap_memory() from Linux kernel
>
> On Thu, Dec 8, 2016 at 5:18 AM, Rafael J. Wysocki wrote:
> > On Thu, Dec 8, 2016
On Fri, Dec 09, 2016 at 12:44:17PM +1100, Dave Chinner wrote:
> On Thu, Dec 08, 2016 at 11:33:00AM +0100, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > Using kmalloc with the vmalloc fallback for larger allocations is a
> > common pattern in the kernel code. Yet we do not have any common hel
On Thu, Dec 8, 2016 at 5:59 PM, Zheng, Lv wrote:
> Hi, Rafael and Dan
>
>> From: Dan Williams [mailto:dan.j.willi...@intel.com]
>> Subject: Re: [PATCH 08/11] ACPICA: Tables: Back port
>> acpi_get_table_with_size() and
>> early_acpi_os_unmap_memory() from Linux kernel
>>
>> On Thu, Dec 8, 2016 at
On Fri, Dec 9, 2016 at 2:59 AM, Zheng, Lv wrote:
> Hi, Rafael and Dan
>
>> From: Dan Williams [mailto:dan.j.willi...@intel.com]
>> Subject: Re: [PATCH 08/11] ACPICA: Tables: Back port
>> acpi_get_table_with_size() and
>> early_acpi_os_unmap_memory() from Linux kernel
>>
>> On Thu, Dec 8, 2016 at
> On 08/12/16 18:33, Bharat Kumar Gogada wrote:
> >> On 08/12/16 15:29, Bharat Kumar Gogada wrote:
> >>
> >> Two things:
> >>
> >>> Here is the cat /proc/interrupts (after we do interface up):
> >>>
> >>> root@:~# ifconfig wlan0 up
> >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not
On Fri, 2 Dec 2016 07:49:52 -0800
"Luis R. Rodriguez" wrote:
> On Thu, Dec 1, 2016 at 10:31 PM, Nicholas Piggin
> wrote:
> >
> > On 2 Dec 2016 2:35 AM, "Luis R. Rodriguez" wrote:
> >>
> >> On Wed, Nov 30, 2016 at 9:20 PM, Nicholas Piggin
> >> wrote:
> >> > On Thu, 1 Dec 2016 16:04:30 +1100
Joel Fernandes writes:
> On Thu, Dec 8, 2016 at 4:42 PM, Joel Fernandes wrote:
>> On Thu, Dec 8, 2016 at 4:35 PM, Huang, Ying wrote:
>>> Joel Fernandes writes:
>>>
Usage llist_del_first needs lock protection, however the table in the
comments of llist.h show a '-'. Correct this, and
Hi, Dan
> -Original Message-
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Dan
> Williams
> Sent: Friday, December 9, 2016 10:05 AM
> To: Zheng, Lv
> Cc: Rafael J. Wysocki ; Wysocki, Rafael J
> ; Rafael J.
> Wysocki ; Brown, Len ; Lv Z
The returned size is still used by the drivers.
Reported-by: Dan Williams
Cc: Dan Williams
Signed-off-by: Lv Zheng
---
drivers/acpi/osl.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
index 5bef0f65..adf1ec4 100644
--- a/
On Thu, Dec 8, 2016 at 6:12 PM, Huang, Ying wrote:
> Joel Fernandes writes:
>
>> On Thu, Dec 8, 2016 at 4:42 PM, Joel Fernandes wrote:
>>> On Thu, Dec 8, 2016 at 4:35 PM, Huang, Ying wrote:
Joel Fernandes writes:
> Usage llist_del_first needs lock protection, however the table in
Hi, Rafael
> From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of Rafael J.
> Wysocki
> Subject: Re: [PATCH 08/11] ACPICA: Tables: Back port
> acpi_get_table_with_size() and
> early_acpi_os_unmap_memory() from Linux kernel
>
> On Fri, Dec 9, 2016 at 2:59 AM, Zheng, Lv wrote:
> >
Joel Fernandes writes:
> On Thu, Dec 8, 2016 at 6:12 PM, Huang, Ying wrote:
>> Joel Fernandes writes:
>>
>>> On Thu, Dec 8, 2016 at 4:42 PM, Joel Fernandes wrote:
On Thu, Dec 8, 2016 at 4:35 PM, Huang, Ying wrote:
> Joel Fernandes writes:
>
>> Usage llist_del_first needs loc
Hi, Dan
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Dan
> Williams
> Subject: Re: [PATCH 08/11] ACPICA: Tables: Back port
> acpi_get_table_with_size() and
> early_acpi_os_unmap_memory() from Linux kernel
>
> On Thu, Dec 8, 2016 at 5:59 PM, Z
From: Arnd Bergmann
Date: Thu, 8 Dec 2016 22:57:05 +0100
> In some configurations, gcc cannot trace the state of variables
> across a spin_unlock() barrier, leading to a warning about
> correct code:
>
> xgene_enet_main.c: In function 'xgene_enet_start_xmit':
> ../../../phy/mdio-xgene.h:112:14:
From: Arnd Bergmann
Date: Thu, 8 Dec 2016 22:57:03 +0100
> On 32-bit ARM with 64-bit dma_addr_t I get this warning about an
> incorrect format string:
>
> In file included from
> /git/arm-soc/drivers/net/ethernet/mellanox/mlx5/core/alloc.c:42:0:
> drivers/net/ethernet/mellanox/mlx5/core/alloc.
From: Arnd Bergmann
Date: Thu, 8 Dec 2016 22:57:04 +0100
> The array for initializing the cle is set up on the stack with
> almost entirely constant data and then passed to a function that
> converts it into HW specific bit patterns. With the latest
> addition, the size of this array has grown t
> 7)
^
Caused by commit
d9fc6452af47 ("spi: mvebu: fix baudrate calculation for armada variants")
I have used the spi tree from next-20161208 for today.
--
Cheers,
Stephen Rothwell
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/pci/msi.c
between commit:
67f1e4473857 ("PCI/MSI: Document new parameter for msi_capability_init()")
from the pci tree and commit:
61e1c5905290 ("PCI/MSI: Propagate IRQ affinity description through the MSI
code
601 - 700 of 857 matches
Mail list logo
