Sorry for the long delay, I was out for a few weeks due to having become
a dad for the second time.
On Sat, Dec 13, 2014 at 09:30:12AM +0100, Ingo Molnar wrote:
> * Sasha Levin wrote:
>
> > Hi all,
> >
> > I was fuzzing with trinity inside a KVM tools guest, running the latest
> > -next
> > k
Hi Pavel,
> diff --git a/drivers/bluetooth/Kconfig b/drivers/bluetooth/Kconfig
> index 4547dc2..0fc7d3a 100644
> --- a/drivers/bluetooth/Kconfig
> +++ b/drivers/bluetooth/Kconfig
> @@ -243,4 +243,14 @@ config BT_WILINK
> Say Y here to compile support for Texas Instrument's WiLink7 driver
>
On Fri, Dec 12, 2014 at 1:58 PM, Martin van Es wrote:
> On Sat, Dec 6, 2014 at 9:09 PM, Linus Torvalds
> I will give 3.18 a try on production J1900. Knowing I can go back to
> safety in 3.16.7 won't hurt too much of my reputation I hope.
3.18 froze twice (just to be sure) as well. Will commence t
On 11/12/14 18:04, Juergen Gross wrote:
> Instead of manually list each hypercall in arch/x86/xen/xen-head.S
> use the auto generated symbol list.
>
> This also corrects the wrong address of xen_hypercall_mca which was
> located 32 bytes higher than it should.
>
> Symbol addresses have been verif
On Mon, Dec 15, 2014 at 10:40:29AM +, Russell King - ARM Linux wrote:
> Including details like this (because ASoC needs a separate DT node) is
> the wrong approach.
And indeed there should be no Linux-internal reason for that - we should
be able to use whatever DT node makes sense, if there's
ST's Common Clk Framework is now available. This patch ensures the FSM
makes use of it by obtaining and enabling the EMI clock. If system fails
to provide the EMI clock, we bomb out.
Signed-off-by: Lee Jones
---
drivers/mtd/devices/st_spi_fsm.c | 40 ++--
1 fi
This driver now obtains platform information via DT matching, which requires
a compatible string per platform. This change introduces the new specific
strings and deprecates the old generic one.
We also take out all of the old, unused properties which are no longer
required.
Signed-off-by: Lee J
The previous code was based on 3-byte JEDEC IDs, with a possible 2-byte
extension. However, devices are now emerging that return 6 or more bytes of
READID data and the additional bytes are required to differentiate between
variants or generations of similar devices.
This patch refactors the devic
From: Angus Clark
In this patch, the fsm_wait_busy() function is updated to a take a timeout
parameter. This allows us to specify different timeout delays depending on
the operation being performed. Previously, a fixed, worst-case delay
(corresponding to the Chip Erase operation, ~300s!) was us
From: Angus Clark
This patch adds support for the Micron N25Q512 and N25Q00A Serial Flash devices.
Unlike previous Micron devices, it is now mandatory to check the Flags Status
Register following a Write or Erase operation. The N25Q512A device presents a
further complication in that different va
drivers/mtd/devices/st_spi_fsm.c:1647:17:
warning: comparison between signed and unsigned integer expressions
Signed-off-by: Lee Jones
---
drivers/mtd/devices/st_spi_fsm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/devices/st_spi_fsm.c b/drivers/mtd/devices
Due to the nature of the port (lots of copy/paste) much of the white-space
is taken up by spaces instead of tab separators. This patch aims to change
that.
Signed-off-by: Lee Jones
---
drivers/mtd/devices/st_spi_fsm.c | 280 +++
1 file changed, 140 insertions(
I haven't seen any bugs caused by lack of type safety with "!foo"...
I prefer !foo because it is more common in the kernel and I think it's
easier to read but I don't feel strongly about this.
I kind of hate "if (foo != NULL) though, because it's a double negative.
But I really hate when people st
On Mon, Dec 15, 2014 at 07:52:06PM +0800, Kuankuan.Yang wrote:
> Hi Russell:
>
> thks for your replay, actually you also have send me those
> dw-hdmi-audio.c patches, and I also agree it's an beautiful way to make
> hdmi-audio works. Beside,
> I try to reuse it into our platform, and actual
From: Angus Clark
This patch updates various Spansion device entries in the flash_types[] table:
- Define full 6-byte READIDs for S25FL128Sx devices (and fix the 4th
byte). This allows us to differentiate between S25FL129P and S25FL128S
devices.
- Add S25FL128Px device entries.
Signe
The FSM SPI NOR driver now obtains syscfg particulars using DT match. In
order for this to happen each platform is required to supply their own
specific compatible string.
We're also remove the old, now unused vendor properties from the node.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih4
While we're at it we're also adding a new human readable define for the
aforementioned clock.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih416.dtsi | 2 +-
include/dt-bindings/clock/stih416-clks.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/
From: Nunzio Raciti
This patch adds support for the Micron N25Q512A device as required
by the B2147 (STiD127) board.
Signed-off-by: Nunzio Raciti
Signed-off-by: Lee Jones
---
drivers/mtd/devices/st_spi_fsm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mtd/devices/st_spi_fsm.
Under certain conditions, the SPI-FSM Controller can be left in a state where
the data FIFO is not entirely empty. This can lead to problems where subsequent
data transfers appear to have been shifted by a number of unidentified bytes.
One simple example would be an errant FSM sequence which load
To trim down on the amount of properties used by this driver and to conform
to the newly agreed method of acquiring syscfg registers/offsets, we now
obtain this information using match tables.
In the process we are deprecating the old generic compatible string and
providing 3 shiny new ones for ea
Hi Brian, all,
[x] Bulid test
[x] Bisectable
[x] Smatch
[x] Sparse
v3:
Further aligned with upstream changes as suggested by Peter Griffin.
The clk_ignore_unused kernel command line parameter is due to be turned
off on STiH4* platforms, so we no longer give the driver the chance to
o
Hello Luis,
On 09/12/14 23:35, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> This lets you build a kernel which can support xen dom0
> or xen guests by just using:
>
>make xenconfig
>
> on both x86 and arm64 kernels. This also splits out the
> options which are available current
Child has the same decay_count as parent. If it's not zero,
we add it to parent's cfs_rq->removed_load:
wake_up_new_task()->set_task_cpu()->migrate_task_rq_fair().
Child's load is a just garbade after copying of parent,
it hasn't been on cfs_rq yet, and it must not be added to
cfs_rq::removed_lo
Hi Russell:
thks for your replay, actually you also have send me those
dw-hdmi-audio.c patches, and I also agree it's an beautiful way to make
hdmi-audio works. Beside,
I try to reuse it into our platform, and actually the system have
created the DW_HDMI sound card successfully, but i c
On 12/15/2014 08:52 AM, Jongman Heo wrote:
>> --- Original Message ---
>> Sender : Juergen Gross
>> Date : 2014-12-15 14:04 (GMT+09:00)
>> Title : Re: [3.18+] Can't boot with commit bd809af1 ("x86: Enable PAT to use
>> cache mode translation tables")
>>
>> On 12/14/2014 06:07 AM, 허종만 wrote
On Sat, 13 Dec 2014 22:20:52 +0100
Loic Pefferkorn wrote:
> On Sat, Dec 13, 2014 at 07:07:05PM +, One Thousand Gnomes wrote:
> >
> > Pointless churn. It makes it less readable if anything, and it removes
> > the type safety as you are now checking against 0 not (void *)0
> >
> > NAK
> >
>
>>> On 15.12.14 at 12:38, wrote:
> On 11/12/14 18:04, Juergen Gross wrote:
>> --- a/arch/x86/syscalls/Makefile
>> +++ b/arch/x86/syscalls/Makefile
>
> Why are these changes here and not in arch/x86/xen/Makefile?
Because this needs to be done in a step that (afaict) has no hook
in the Xen-specifi
On 11/12/14 18:04, Juergen Gross wrote:
> Instead of manually list all hypervisor calls in arch/x86/xen/trace.c
> use the auto generated list.
Reviewed-by: David Vrabel
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.ker
On Mon, Dec 15, 2014 at 8:31 AM, Daniel Vetter wrote:
[---snip---]
> Sorry for the delay. Absolutely no difference in the relevant parts of the
> log. There could be the chance that something is hidden somewhere, so can
> please grab a new set of logs but this time with drm.debug=0xe?
Thanks fo
On 11/12/14 18:04, Juergen Gross wrote:
> The header include/xen/interface/xen.h doesn't contain all definitions
> from Xen's version of that header. Update it accordingly.
Reviewed-by: David Vrabel
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Sat, 13 Dec 2014 11:46:47 -0800
Jeremiah Mahler wrote:
> Loïc,
>
> On Sat, Dec 13, 2014 at 07:22:38PM +0100, Loic Pefferkorn wrote:
> > > Whose convention is this? I can't find any mention in
> > > Documention/CodingStyle. checkpatch.pl doesn't complain about them.
> > > And there are almost
hallo
Groet van Springleaf Financial Services, zijn wij goed ingeburgerd en
goedgekeurd UK lening bedrijven, door de jaren heen, hebben we een
goed begrip van uw wensen en individuele behoeften ontwikkeld. we zijn
ons toegewijd aan onze klanten eerlijk te behandelen en bieden een
dienst
On Thu, Dec 11, 2014 at 03:02:31PM +0200, Octavian Purdila wrote:
> Without suspend/resume functionality in the USB driver the USB core
> will disconnect and reconnect the DLN2 port and because the GPIO
> framework does not yet support removal of an in-use controller a
> suspend/resume operation wi
hallo
Groet van Springleaf Financial Services, zijn wij goed ingeburgerd en
goedgekeurd UK lening bedrijven, door de jaren heen, hebben we een
goed begrip van uw wensen en individuele behoeften ontwikkeld. we zijn
ons toegewijd aan onze klanten eerlijk te behandelen en bieden een
dienst
> > Am I missing some w2sg004 specific bits here ?
>
> There is particular behaviour that the device is both turned on and turned
> off by toggling a GPIO, and the only way to detect which state it is in is
> to watch the RX uart line (by reconfiguring it as a GPIO).
Ok so it is somewhat differen
On Thu, Dec 11, 2014 at 11:48 PM, Linux Kernel Mailing List
wrote:
> Gitweb:
> http://git.kernel.org/linus/;a=commit;h=b487b9ce9340a6e98d7f8277399304b23b7be456
> Commit: b487b9ce9340a6e98d7f8277399304b23b7be456
> Parent: bda157a40077447b25a1172a17b8ef81a2905cb7
> Refname:refs/head
On Mon, Dec 15, 2014 at 09:28:41AM +0100, Andrzej Hajda wrote:
> On 12/12/2014 05:52 PM, Mark Brown wrote:
> > On Wed, Dec 10, 2014 at 04:48:20PM +0100, Andrzej Hajda wrote:
> > I don't know about anyone else but I'm having a hard time reading the
> > restrack name, it looks like a misspelling of
The TI DAC8554 is a quad-channel Digital-to-Analog Converter with an SPI
interface.
Changes in v3:
* Small fixes in the documentation of struct dac8554_state
* Replace some magic constants with macros
* Replace memset on powerdown state arrays with explicit loop
* If probing fails due to invalid D
On 11/12/14 18:04, Juergen Gross wrote:
> Today there are several places in the kernel which build tables
> containing one entry for each possible Xen hypercall. Create an
> infrastructure to be able to generate these tables at build time.
Does arm and arm64 need something similar? If so are the
Signed-off-by: Nikolaus Schulz
---
.../devicetree/bindings/iio/dac/ti-dac8554.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt
diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt
The code bothers to probe for the device, but on failing to find it proceeds
to try and release a NULL resource, thereby ruining it's prior good
behaviour
Resolves-Bug: https://bugzilla.kernel.org/show_bug.cgi?id=88581
Signed-off-by: Alan Cox
---
drivers/staging/speakup/speakup_dtlk.c |7 +++
Hi Linus,
On 15-12-14 00:06, Linus Torvalds wrote:
On Sun, Dec 14, 2014 at 2:35 PM, Greg KH wrote:
Hans de Goede (1):
uas: Make uas work with blk-mq
So I got some fairly trivial conflicts on this one (conflicting with
the scsi cleanups mainly by Christoph Hellwig.
I resolved the con
On Mon, Dec 15, 2014 at 11:23:11AM +, Russell King - ARM Linux wrote:
> On Mon, Dec 15, 2014 at 11:17:16AM +, Will Deacon wrote:
> > On Sun, Dec 14, 2014 at 04:52:09PM +, Michael S. Tsirkin wrote:
> > > virtio wants to read bitwise types from userspace using get_user. At the
> > > mome
On 12/15/2014, 11:06 AM, Richard Farthing wrote:
> I installed the kernel via YAST2 which makes and installs the initrd
> too, and have done this many times before on this test machine, so it
> seems unlikely to be my mistake, but it's always possible! I will have
> a look at it again
Oh, yast...
On Fri, Dec 12, 2014 at 06:52:35AM +, Sascha Hauer wrote:
> On Thu, Dec 11, 2014 at 06:02:46PM +, Mark Rutland wrote:
> > Hi,
> >
> > On Wed, Dec 10, 2014 at 10:50:01AM +, Eddie Huang wrote:
> > > Add device tree support for MT8173 SoC and evalutaion board based on it.
> > >
> > > Sig
Signed-off-by: Lee Jones
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 99a8a4a..e34d5c6 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_d
ST's Low Power Controller can currently operate in two supported modes;
Watchdog and Real Time Clock. These defines will aid engineers to easily
identify the selected mode.
Signed-off-by: Lee Jones
---
include/dt-bindings/mfd/st-lpc.h | 15 +++
1 file changed, 15 insertions(+)
crea
If CONFIG_OF is not set:
drivers/net/ethernet/stmicro/stmmac/dwmac-sti.c: In function
‘sti_dwmac_parse_data’:
drivers/net/ethernet/stmicro/stmmac/dwmac-sti.c:318: warning: ‘rs’ is used
uninitialized in this function
of_property_read_string() will return -ENOSYS in this case, and rs will
be an u
On current ST platforms the LPC controls a number of functions including
Watchdog and Real Time Clock. This patch provides the bindings used to
choose and configure the devices.
Signed-off-by: Lee Jones
---
Documentation/devicetree/bindings/mfd/st-lpc.txt | 36
1 file c
Signed-off-by: David Paris
Signed-off-by: Lee Jones
---
drivers/watchdog/Kconfig | 13 ++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/st_wdt.c | 312 ++
3 files changed, 326 insertions(+)
create mode 100644 drivers/watchdog/st_wdt.c
diff --
ST's Low Power Controller (LPC) controls two devices; watchdog and RTC.
Only one of the devices can be used at any one time. This is enforced
by the correlating MFD driver. This portion of the driver-set controls
the Real Time Clock.
Signed-off-by: Lee Jones
---
drivers/rtc/Kconfig | 13
Signed-off-by: Lee Jones
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index e34d5c6..09b8bce 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_d
On current ST platforms the LPC controls a number of functions. This
patch enables possible support for the LPC Watchdog and LPC RTC devices
and ensures only one of them operates at any one time.
Signed-off-by: Lee Jones
---
drivers/mfd/Kconfig | 8 +
drivers/mfd/Makefile | 1 +
drivers/
On current ST platforms the LPC controls a number of functions. This
patch enables support for the LPC Watchdog and LPC RTC devices on LPC1
and LPC2 respectively.
Signed-off-by: David Paris
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih407.dtsi | 20
1 file changed, 2
ST's Low Power Controller (LPC) controls two devices; watchdog and RTC.
Only one of the devices can be used at any one time, which is enforced
by the correlating MFD driver.
This driver set provides everything you need to choose one (and only
one) of the LPC devices to run per I/P block, of which
On Mon, Dec 15, 2014 at 11:17:16AM +, Will Deacon wrote:
> On Sun, Dec 14, 2014 at 04:52:09PM +, Michael S. Tsirkin wrote:
> > virtio wants to read bitwise types from userspace using get_user. At the
> > moment this triggers sparse errors, since the value is passed through an
> > integer.
This is a corner case fix. In general, cpu-to-node relationship is
fixed when cpu/memory are visible to kernel based on firmware
information. But in some case, cpu-to-node relationship is updated
at CPU_ONLINE.
In arch/x86/mm/numa.c::numa_init_array(), a cpu will be tied to
a random numa node if t
Workqueue keeps cpu<->node relationship including all possible cpus.
The original information was made at boot but it may change when
a new node is added.
Update information if a new node is ready with using node-hotplug callback.
Signed-off-by: KAMEZAWA Hiroyuki
---
include/linux/memory_hotplu
On Sun, Dec 14, 2014 at 04:52:09PM +, Michael S. Tsirkin wrote:
> virtio wants to read bitwise types from userspace using get_user. At the
> moment this triggers sparse errors, since the value is passed through an
> integer.
>
> Fix that up using __force.
>
> Signed-off-by: Michael S. Tsirki
The percpu workqueue pool are persistend and never be freed.
But cpu<->node relationship can be changed by cpu hotplug and pool->node
can point to an offlined node.
If pool->node points to an offlined node,
following allocation failure can happen.
==
SLUB: Unable to allocate memory on nod
On Sat, 13 Dec 2014, One Thousand Gnomes wrote:
> Is it the year for a Google summer of code project or similar to turn
> patchwork into a proper patch management tool (one that collects the
> patches, provides a good maintainer interface, tells people automatically
> that their patches are queued,
Unbound wq pool's node attribute is calculated at its allocation.
But it's now calculated based on possible cpu<->node information
which can be wrong after cpu hotplug/unplug.
If wrong pool->node is set, following allocation error will happen.
==
SLUB: Unable to allocate memory on node 2 (gfp=0x8
On Mon, Dec 15, 2014 at 12:06 AM, Linux Kernel Mailing List
wrote:
> Gitweb:
> http://git.kernel.org/linus/;a=commit;h=21a9476a7ba847e413bf1c144d7c614532aed6dd
> Commit: 21a9476a7ba847e413bf1c144d7c614532aed6dd
> Parent: 5ca8d3ec9970f4798e68bd21a9d44db3d0ff4da7
> Refname:refs/head
Lai-san, Tejun-san,
Thank you for review, this a fix v3. This has been tested on NUMA node hotplug
machine and seems work well.
The probelm is memory allocation failure because pool->node information can be
stale
after node hotplug. This patch(1,2) tries to fix pool->node calculation.
Patch (3,4
On Mon, Dec 15, 2014 at 08:59:08AM +, Howard Chen wrote:
> add device tree for psci-0.2 on mt8173 platform
> add device tree for cupidle-arm64 on mt8173 platform
>
> Signed-off-by: Howard Chen
> ---
> arch/arm64/boot/dts/mt8173.dtsi | 51
> +
> 1 file
On 14 December 2014 at 19:26, Paul Walmsley wrote:
> Hi
>
> I have not reviewed this code closely, but a few items just caught my eye
> at a brief glance.
>
> On Tue, 9 Dec 2014, Tomeu Vizoso wrote:
>
>> The ACTMON block can monitor several counters, providing averaging and firing
>> interrupts ba
Hi Yamada-san,
On Mon, Dec 15, 2014 at 11:51 AM, Masahiro Yamada
wrote:
> Geert Uytterhoeven wrote:
>> On Mon, Dec 15, 2014 at 10:32 AM, Masahiro Yamada
>> wrote:
>> > I read through Documentation/printk-formats.txt
>> >
>> > It clearly says to use "%zu" or "%zx" to print size_t variables,
>> >
The proposed patch introduces a way for supporting device specific switch port
attributes.
Can we expect user-space tools such as iproute2 to be aware of such attributes
from every device?
A generic tool like iproute2 can't be aware of all the specific attributes of
all the devices that will us
Hi Geert,
On Mon, 15 Dec 2014 10:38:23 +0100
Geert Uytterhoeven wrote:
> Hi Yamada-san,
>
>
> On Mon, Dec 15, 2014 at 10:32 AM, Masahiro Yamada
> wrote:
> > I read through Documentation/printk-formats.txt
> >
> > It clearly says to use "%zu" or "%zx" to print size_t variables,
> > but I st
On Mon, Dec 15, 2014 at 12:43 AM, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 03.12.2014 um 14:31:
>> Minimal implementation for KMX61 6-axis accelerometer/magnetometer. It
>> exports
>> raw accel/magn readings together with scale and sampling frequency.
>>
>> This driver uses two IIO device
On Wed, Dec 10, 2014 at 03:23:29PM +0100, David Hildenbrand wrote:
Did you look at the -rt patches where this comes from?
https://git.kernel.org/cgit/linux/kernel/git/clrkwllms/rt-linux.git/commit/?h=v3.14.21-rt9&id=b389ced19ab649438196d132768fe6522d2f052b
https://git.kernel.org/cgit/linux/kernel
On Monday 15 December 2014 00:10:06 Robert Jarzmik wrote:
> +
> + platform_set_drvdata(pdev, cot);
> + cot->gpio0 = gpiod_get(&pdev->dev, "lubbock_irq", 0);
> + if (IS_ERR(cot->gpio0)) {
> + dev_err(&pdev->dev, "Couldn't request GPIO : ret = %d\n",
> ret);
> +
On 12 December 2014 at 08:44, Alexandre Courbot wrote:
> Hi Tomeu,
>
> On Tue, Dec 9, 2014 at 10:15 PM, Tomeu Vizoso
> wrote:
>> The ACTMON block can monitor several counters, providing averaging and firing
>> interrupts based on watermarking configuration. This implementation monitors
>> the MCA
On Mon, 15 Dec 2014 11:29:14 +0100
Alexander Stein wrote:
> On Monday 15 December 2014 11:22:30, Boris Brezillon wrote:
> > Hi Alexander,
> >
> > On Tue, 09 Dec 2014 21:53:12 +0100
> > Alexander Stein wrote:
> >
> > > Hi,
> > >
> > > On Monday 01 December 2014, 11:27:21 wrote Boris Brezillon:
On Fri, Dec 12, 2014 at 6:18 PM, Nishanth Menon wrote:
> CONFIG_GENERIC_CPUFREQ_CPU0 disappeared with commit bbcf071969b20f
> ("cpufreq: cpu0: rename driver and internals to 'cpufreq_dt'")
>
> Use the renamed CONFIG_CPUFREQ_DT generic driver. It looks like with
> v3.18-rc1, commit bbcf071969b20f a
On Mon, Dec 15, 2014 at 10:55:14AM +0800, Yakir Yang wrote:
> Required properties:
> - compatible: platform specific
> - cpu-of-node: the device node of cpu_dai
> - codec-name: the dw-hdmi codec's device name
> - codec-dai-name: the dw-hdmi codec's dai name
This is not actually a separate physical
On Mon, Dec 15, 2014 at 10:11:28AM +0800, Yakir Yang wrote:
>
> rk3288 use Designware HDMI IP, Designware HDMI supports four interfaces to
> config hdmi audio(I2S, S/PDIF, Generic Parallel Audio, AHB Audio DMA), but
> rk3288 only support two ways to config hdmi audio(I2S, S/PDIF), So we take
> I2S
On Wed, Dec 10, 2014 at 10:52:52AM -0500, Tejun Heo wrote:
> Convert the existing user of cpu{mask|list}_scnprintf() and
> node{mask|list}_scnprintf() which use them just to printk or
> seq_printf() the resulting buffer to use the following functions
> instead respectively.
>
> * For printk: cpu{m
- Original Message -
> From: "Richard Weinberger"
> To: user-mode-linux-de...@lists.sourceforge.net
> Cc: a...@arndb.de, mik...@szeredi.hu, "Richard Weinberger" ,
> linux-kernel@vger.kernel.org,
> ge...@linux-m68k.org, lf...@altera.com
> Sent: Wednesday, December 10, 2014 1:02:15 PM
> Sub
On Sun, Dec 14, 2014 at 11:39:14PM +0100, Rickard Strandqvist wrote:
> There is otherwise a risk of a possible null pointer dereference.
>
> Was largely found by using a static code analysis program called cppcheck.
>
> Signed-off-by: Rickard Strandqvist
> ---
> drivers/staging/rtl8723au/os_dep
On pią, 2014-12-12 at 12:42 +0900, Chanwoo Choi wrote:
> Hi Krzysztof,
>
> I replied again this mail because I'll use the mutex for
> set_event()/get_event()
> according to your comment. But, of_parse_phandle() seems that this function
> don't need the of_node_put() function.
>
>
> On 12/11/201
On Monday 15 December 2014 11:22:30, Boris Brezillon wrote:
> Hi Alexander,
>
> On Tue, 09 Dec 2014 21:53:12 +0100
> Alexander Stein wrote:
>
> > Hi,
> >
> > On Monday 01 December 2014, 11:27:21 wrote Boris Brezillon:
> > > +static int at91_ebi_probe(struct platform_device *pdev)
> > > +{
> > >
On Sun, Dec 14, 2014 at 11:37:18PM +0100, Rickard Strandqvist wrote:
> There is otherwise a risk of a possible null pointer dereference.
>
> Was largely found by using a static code analysis program called cppcheck.
>
> Signed-off-by: Rickard Strandqvist
> ---
> drivers/staging/lustre/lustre/os
On Thu, Dec 11, 2014 at 03:29:52PM -0800, Jeremiah Mahler wrote:
> If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
> unplugged, a bunch of -ENODEV and -EPROTO errors will be produced in the
> logs. This patch set quiets these messages without changing the
> original behavior.
On Mon, Dec 15, 2014 at 11:40:52AM +1100, Michael Ellerman wrote:
> On Sun, 2014-12-14 at 18:51 +0200, Michael S. Tsirkin wrote:
> > At the moment, if p and x are both tagged as bitwise types,
> > get_user(x, p) produces a sparse warning on many architectures.
> > This is because *p on these archit
Hi Alexander,
On Tue, 09 Dec 2014 21:53:12 +0100
Alexander Stein wrote:
> Hi,
>
> On Monday 01 December 2014, 11:27:21 wrote Boris Brezillon:
> > +static int at91_ebi_probe(struct platform_device *pdev)
> > +{
> > + const struct of_device_id *match;
> > + struct device_node *child;
> > +
Hello,
On Mon 15-12-14 16:25:55, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> commit 75cbe701a4251fcd8b846d52ae42f88c9a8e5e93 ("vfs: Remove i_dquot
> field from inode")
>
> testbox/testcase/testparams: lkp-nex05/will-it-scale/performance-pwrite3
So in the first test is there a
On Sat, 2014-12-13 at 11:09 -0800, Dmitry Torokhov wrote:
> Hi Andy,
>
> On Wed, Dec 10, 2014 at 08:32:56PM +0200, Andy Shevchenko wrote:
> > On Sun, 2014-12-07 at 23:21 -0800, Dmitry Torokhov wrote:
> > > We do not need to roll our own implementation of delayed work now that we
> > > have proper
On Sat, Dec 13, 2014 at 12:29:57PM +0100, Lars-Peter Clausen wrote:
> On 11/24/2014 08:50 PM, Nikolaus Schulz wrote:
> [...]
> >+const struct iio_chan_spec dac8554_channels[] = {
>
> static
>
> [...]
> >+ret = of_property_read_u32(spi->dev.of_node, "address", &addr);
>
> This should probably
Dudley,
On Mon, Dec 15, 2014 at 06:31:25AM +, Dudley Du wrote:
> Jeremiah,
>
> Thanks for your review and comments.
> I have updated v15 based on your comments and suggestions.
> Could you help review again please.
>
> Thank you very much,
> Dudley
>
Will do.
[...]
--
- Jeremiah Mahler
On Sun, Dec 14, 2014 at 10:09:48PM -0800, Kevin Cernekee wrote:
> Currently the checklist does not provide an indication of appropriate
> times to send patches; add a brief note on the topic.
>
> Signed-off-by: Kevin Cernekee
> ---
> Documentation/SubmitChecklist | 5 +
> 1 file changed, 5 i
On Mon, Dec 15, 2014 at 06:03:10PM +0800, LF.Tan wrote:
> On Mon, Dec 15, 2014 at 12:51 AM, Michael S. Tsirkin wrote:
> > At the moment, if p and x are both tagged as bitwise types,
> > get_user(x, p) produces a sparse warning on many architectures.
> > This is because *p on these architectures is
On Thu, Dec 11, 2014 at 10:59:55AM -0500, Josef Bacik wrote:
> The schedule stats currently spit out once the entity is being queued, which
> means if we have stack traces enabled we will get the stack trace of the
> waker,
> not of the task being woken. This makes the backtrace completely useles
On Sun, Dec 14, 2014 at 10:09:49PM -0800, Kevin Cernekee wrote:
> This has been a recurring source of confusion for the new submitters who
> I've helped; let's see if adding a small illustration improves the
> situation.
>
> Signed-off-by: Kevin Cernekee
> ---
> Documentation/development-process
On Sun, Dec 14, 2014 at 10:09:50PM -0800, Kevin Cernekee wrote:
> Give submitters a rough idea of how long to wait before reposting, to
> help avoid situations where a series is reposted before the original
> submission is fully reviewed.
>
> Suggested-by: Thomas Gleixner
> Signed-off-by: Kevin C
On Wed, Dec 10, 2014 at 10:23 PM, David Hildenbrand
wrote:
> This patch adds the pagefault_count to the thread_info of all
> architectures. It will be used to count the pagefault_disable() levels
> on a per-thread basis.
>
> We are not reusing the preempt_count as this is per cpu on x86 and we wan
On Sat, Dec 13, 2014 at 05:17:42PM +0530, Muthu Mani wrote:
> Adds support for USB-I2C/GPIO interfaces of Cypress Semiconductor
> CYUSBS234 USB-Serial Bridge controller.
>
> Details about the device can be found at:
> http://www.cypress.com/?rID=84126
>
> Separate cell drivers are available for I
I installed the kernel via YAST2 which makes and installs the initrd
too, and have done this many times before on this test machine, so it
seems unlikely to be my mistake, but it's always possible! I will have
a look at it again
Richard
On 15/12/2014 09:28, Jiri Slaby wrote:
On 12/14/2014,
On 12/15/2014 06:13 AM, Peter Chen wrote:
> On Fri, Dec 12, 2014 at 02:17:28PM +0100, Robert Baldyga wrote:
>> As usb function drivers assumes that all usb request will be completed
>> before function unbind call, we should supply such behavior. In some
>> cases ep_disable() won't kill all request
On Mon, Dec 15, 2014 at 12:51 AM, Michael S. Tsirkin wrote:
> At the moment, if p and x are both tagged as bitwise types,
> get_user(x, p) produces a sparse warning on many architectures.
> This is because *p on these architectures is loaded into long
> (typically using asm), then cast back to typ
801 - 900 of 954 matches
Mail list logo
