On Fri, 14 Nov 2014 10:30:53 -0600 Daniel Forrest
wrote:
> There have been a couple of inquiries about the status of this patch
> over the last few months, so I am going to try pushing it out.
>
> Andrea Arcangeli has commented:
>
> > Agreed. The only thing I don't like about this patch is the
On Mon, Nov 17, 2014 at 2:43 PM, Thomas Gleixner wrote:
>>
>> No, that won't work for synchronous calls:\
Right you are.
> So a combo of both (Jens and yours) might do the trick. Patch below.
Yeah, I guess that would work. The important part is that *if*
somebody really reuses the csd, we'd bet
On Tue, Nov 18, 2014 at 12:38:14AM +0100, Thomas Gleixner wrote:
> Well a bitmask is a pretty indescriptive item as well. Putting my user
> hat on: Where is the documentation for the bits?
$ cat /sys/devices/system/cpu/bugs
0xXX - currently enabled workarounds are the set bits.
bit 0: workarou
On Mon, Nov 17, 2014 at 01:11:57PM -0800, Alexander Duyck wrote:
> On 11/17/2014 12:18 PM, Paul E. McKenney wrote:
> >On Mon, Nov 17, 2014 at 09:18:13AM -0800, Alexander Duyck wrote:
> >>There are a number of situations where the mandatory barriers rmb() and
> >>wmb() are used to order memory/memor
Hi Felipe,
On Mon, Nov 17, 2014 at 3:12 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Nov 17, 2014 at 02:41:39PM -0800, Andrew Bresticker wrote:
>> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
>> index a3ca137..e2415d3 100644
>> --- a/drivers/usb/host/Kconfig
>> +++ b/drivers/usb/
On Mon, Nov 17, 2014 at 09:42:57AM +0900, Chanwoo Choi wrote:
> This patch adds S2MPS13 regulator device to existing S2MPS11 device driver.
> The S2MPS13 has just different number of regulators from S2MPS14.
> The S2MPS13 regulator device includes LDO[1-40] and BUCK[1-10].
Acked-by: Mark Brown
On Tue, 2014-11-18 at 00:14 +0100, Rafael J. Wysocki wrote:
> I'll drop the commit for now, but this looks strange.
>
> Had you cleaned up the kernel configuration after dropping the PM_RUNTIME
> select
> from ARCH_EXYNOS?
I retested this again:
[linux * (next-2014111
On Mon, Nov 10, 2014 at 8:59 PM, Bjorn Helgaas wrote:
> [+cc lkml, linux-arch, Linus]
>
> On Sat, Nov 01, 2014 at 02:11:19PM -0400, Prarit Bhargava wrote:
>> The kernel should boot PCI without the use of kernel parameters. Display
>> a FW_BUG warning when pci= is used.
>>
>> Cc: Myron Stowe
>> C
On Mon, Nov 17, 2014 at 03:40:23PM +0800, Flora Fu wrote:
This looks mostly good but there are a few fairly straightfoward things:
> @@ -725,5 +725,11 @@ config REGULATOR_WM8994
> This driver provides support for the voltage regulators on the
> WM8994 CODEC.
>
> +config REGULATO
On Tue, Nov 11, 2014 at 12:32 PM, Wolfram Sang wrote:
> On Tue, Oct 07, 2014 at 05:06:47PM -0700, Feng Kan wrote:
>> Add SLIMpro I2C device driver on APM X-Gene platform. This I2C
>> device driver use the SLIMpro Mailbox driver to tunnel message to
>> the SLIMpro coprocessor to do the work of acce
On Tue, 18 Nov 2014, Borislav Petkov wrote:
> On Mon, Nov 17, 2014 at 08:07:05PM +0100, Stephane Eranian wrote:
> > From: Maria Dimakopoulou
> >
> > This patch adds a sysfs entry:
> >
> > /sys/devices/cpu/ht_bug_workaround
> >
> > to activate/deactivate the PMU HT bug workaround.
> >
> > T
On Mon, Nov 17, 2014 at 03:40:24PM +0800, Flora Fu wrote:
> + pmic {
> + compatible = "mediatek,mt6397";
> + }
This looks like it's missing a closing brace and is just generally weird
(having a subnode like this).
> +- regulators : The regulators of mt6397
> +
On Mon, Nov 17, 2014 at 01:00:09PM -0800, Guenter Roeck wrote:
> On Fri, Oct 17, 2014 at 08:17:03AM -0700, Guenter Roeck wrote:
> > To avoid the problem, prepend the debugfs directory name for a regulator
> > with its parent device name if available, but only if no explicit
> > regulator name was
On 17 November 2014 21:02, Kees Cook wrote:
> This prefixes all crypto module loading with "crypto-" so we never run
> the risk of exposing module auto-loading to userspace via a crypto API,
> as demonstrated by Mathias Krause:
>
> https://lkml.org/lkml/2013/3/4/70
>
> Signed-off-by: Kees Cook
>
Hi,
This patch adds USB3 support to the legacy gadget printer driver.
Applies cleanly on fc14f9c Linux 3.18-rc5.
Please could it be considered for inclusion?
regards,
Jorge
>From f46d9b0d2160b30f14dee104657de865e9e2bc38 Mon Sep 17 00:00:00 2001
From: Jorge Ramirez-Ortiz
Date: Thu, 25 Sep 201
Different drivers request API extensions in of-thermal. For this reason,
additional callbacks are required to fit the new drivers needs.
The current API implementation expects the registering sensor driver
to provide a get_temp and get_trend callbacks as function parameters.
As the amount of callb
On Mon, 17 Nov 2014, Jens Axboe wrote:
> On 11/17/2014 02:22 PM, Linus Torvalds wrote:
> > On Fri, Nov 14, 2014 at 5:59 PM, Linus Torvalds
> > wrote:
> >>
> >> Judging by the code disassembly, it's the "csd_lock_wait(csd)" at the
> >> end.
> >
> > Btw, looking at this, I grew really suspicious of
> I still wonder whether the timeout code is the real culprit. My patch
> will slow down entry into do_machine_check by tens of cycles, several
> cachelines, and possibly a couple of TLB misses. Given that the
> timing seemed marginal to me, it's possible (albeit not that likely)
> that it pushed
On Mon, Nov 17, 2014 at 02:50:10PM -0800, Andy Lutomirski wrote:
> On Mon, Nov 17, 2014 at 2:41 PM, Eric W.Biederman
> wrote:
> >
> >
> > On November 17, 2014 1:46:59 PM EST, Andy Lutomirski
> > wrote:
> >>On Mon, Nov 17, 2014 at 10:31 AM, Andy Lutomirski
> >>wrote:
> >>> On Mon, Nov 17, 2014
Hi,
On Mon, Nov 17, 2014 at 02:41:39PM -0800, Andrew Bresticker wrote:
> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
> index a3ca137..e2415d3 100644
> --- a/drivers/usb/host/Kconfig
> +++ b/drivers/usb/host/Kconfig
> @@ -50,6 +50,15 @@ config USB_XHCI_RCAR
> Say 'Y' to
On Monday, November 17, 2014 01:28:54 PM Alexandre Courbot wrote:
> On Fri, Nov 14, 2014 at 5:58 PM, Linus Walleij
> wrote:
> > On Mon, Nov 3, 2014 at 11:56 PM, Rafael J. Wysocki
> > wrote:
> >> On Monday, November 03, 2014 02:22:10 PM Linus Walleij wrote:
> >
> >>> With that change:
> >>> Revi
On Mon, Nov 17, 2014 at 09:58:01AM +, Richard Fitzgerald wrote:
> On Mon, Nov 17, 2014 at 07:41:53AM +0100, Linus Walleij wrote:
> > Apart from the whitespace fix pointed out by Mark,
> THe line Mark commented on isn't a whitespace error. It matches
> the copyright line style used by Cirrus i
On Mon, Nov 17, 2014 at 1:21 PM, Markus Trippelsdorf
wrote:
> On 2014.11.17 at 13:02 -0800, Kees Cook wrote:
>>
>> Eek, well, the warning worked, at least (".bss and .brk lack common
>> file offset") since that was kind of an assumption in the script I
>> wanted to make sure we'd catch if it wasn'
On Mon, Nov 17, 2014 at 12:54:33PM +, Richard Fitzgerald wrote:
> On Mon, Nov 17, 2014 at 12:16:48PM +, Lee Jones wrote:
> > Looks like I was a little hasty with my comments. However 8000 lines
> > over 4 platforms just to describe which registers are readable is all
> > a little bit grim
On Sat, 15 Nov 2014 21:49:57 -0500 Zhihui Zhang wrote:
> When nodes is true, nsc->mask2 has already been filtered by nsc->mask1, which
> has
> already factored in node_states[N_MEMORY].
>
Please be more specific. Where does that filtering occur?
--
To unsubscribe from this list: send the lin
On Mon, Nov 17, 2014 at 10:21 PM, Kevin Cernekee wrote:
> Currently the bootloader is responsible for decompressing the image.
> On STB the bootloader typically loads a gzipped ELF file; on DSL/CM
> the bootloader unpacks a custom image format containing an
> LZMA-compressed kernel in some form.
On 11/17/2014 02:22 PM, Linus Torvalds wrote:
> On Fri, Nov 14, 2014 at 5:59 PM, Linus Torvalds
> wrote:
>>
>> Judging by the code disassembly, it's the "csd_lock_wait(csd)" at the
>> end.
>
> Btw, looking at this, I grew really suspicious of this code in csd_unlock():
>
> WARN_ON((csd->
On Mon, Nov 17, 2014 at 02:41:31PM -0800, Andrew Bresticker wrote:
> xhci_gen_setup() sets the hcd_priv field for the primary HCD, but not
> for the shared HCD, requiring xHCI host-controller drivers to set it
> between usb_create_shared_hcd() and usb_add_hcd(). There's no reason
> xhci_gen_setup(
Different drivers request API extensions in of-thermal. For this reason,
additional callbacks are required to fit the new drivers needs.
The current API implementation expects the registering sensor driver
to provide a get_temp and get_trend callbacks as function parameters.
As the amount of callb
Since commit 8a0a9bd4db63 ('random: make get_random_int() more
random'), get_random_int() returns a random value for each call,
so comment and hack introduced in mmap_rnd() as part of commit
1d18c47c735e ('arm64: MMU fault handling and page table management')
are incorrects.
Commit 1d18c47c735e se
On Mon, Nov 17, 2014 at 08:07:05PM +0100, Stephane Eranian wrote:
> From: Maria Dimakopoulou
>
> This patch adds a sysfs entry:
>
> /sys/devices/cpu/ht_bug_workaround
>
> to activate/deactivate the PMU HT bug workaround.
>
> To activate (activated by default):
> # echo 1 > /sys/devices/
On Mon, Nov 17, 2014 at 9:35 PM, Kevin Cernekee wrote:
> On Mon, Nov 17, 2014 at 6:44 AM, Jonas Gorski wrote:
>> On Sun, Nov 16, 2014 at 1:17 AM, Kevin Cernekee wrote:
>>> bmips_be_defconfig supports Linux running on the following CM and DSL
>>> SoCs:
>>>
>>> - BCM3384 (BMIPS5000) cable modem a
On 11/17/2014 03:43 PM, Thomas Gleixner wrote:
> On Mon, 17 Nov 2014, Thomas Gleixner wrote:
>> On Mon, 17 Nov 2014, Linus Torvalds wrote:
>>> llist_for_each_entry_safe(csd, csd_next, entry, llist) {
>>> - csd->func(csd->info);
>>> + smp_call_func_t func = csd->func;
>>> +
On Mon, Nov 17, 2014 at 2:35 PM, Pantelis Antoniou
wrote:
> Hi Grant,
>
>> On Nov 14, 2014, at 01:36 , Grant Likely wrote:
>>
>> On Tue, 28 Oct 2014 22:35:58 +0200
>> , Pantelis Antoniou
>> wrote:
>>> Introduce DT overlay support.
>>>
>>> Makes it possible to dynamically overlay a part of the ke
y commit 9cdd5fd742e6 ("PM / domains: Kconfig: always enable
> > PM_RUNTIME when genpd enabled").
>
> This error also popped up when I fiddled with omap2plus_defconfig on top
> of next-20141117. Note that I ended up with a .config which has
> CONFIG_ARCH_MULTI_V7 set. Th
Hi,
this patchset adds a driver for the SPIFC (SPI flash controller)
available in Amlogic Meson6 and Meson8 SoCs. The driver has been
tested on a Meson8 based device to communicate with a Macronix
mx25l1606e serial flash.
The first patch adds a field to the spi_transfer structure that allows
the
Some drivers need to know whether the current transfer is the last in
the message in order to properly handle CS. A common way to achieve
this is to reimplement transfer_one_message() but this leads to
undesirable code duplication.
This patch adds a 'last' field to the spi_transfer structure and
p
On Mon, Nov 17, 2014 at 2:41 PM, Eric W.Biederman wrote:
>
>
> On November 17, 2014 1:46:59 PM EST, Andy Lutomirski
> wrote:
>>On Mon, Nov 17, 2014 at 10:31 AM, Andy Lutomirski
>>wrote:
>>> On Mon, Nov 17, 2014 at 10:06 AM, Casey Schaufler
>>> wrote:
On 11/15/2014 1:01 AM, Josh Triplett w
Add device-tree bindings for the Tegra XUSB mailbox which will be used
for communication between the Tegra xHCI controller's firmware and the
host processor.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
---
No changes from v3/v4.
Changes from v2:
- Dropped channel specifier.
-
From: Benson Leung
mbox_request_channel() currently returns EBUSY in the event the controller
is not present or if of_xlate() fails, but in neither case is EBUSY really
appropriate. Return EPROBE_DEFER if the controller is not yet present
and change of_xlate() to return an ERR_PTR instead of NUL
This is a driver for the Amlogic Meson SPIFC (SPI flash controller),
which is one of the two SPI controllers available on the SoC. It
doesn't support DMA and has a 64-byte unified transmit/receive buffer.
The device is optimized for interfacing with SPI NOR memories and
allows the execution of sta
This adds documentation of device tree bindings for the Amlogic Meson
SPIFC (SPI Flash Controller).
Signed-off-by: Beniamino Galvani
---
.../devicetree/bindings/spi/spi-meson.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/b
This adds a node for the SPI Flash Controller to the Amlogic Meson
DTS.
Signed-off-by: Beniamino Galvani
Acked-by: Mark Brown
---
arch/arm/boot/dts/meson.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/meson.dtsi b/arch/arm/boot/dts/meson.dtsi
index e6539ea..
Add device-tree binding documentation for the xHCI controller present
on Tegra124 and later SoCs.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
---
Changes from v4:
- Updated regulator names, as suggested by Thierry.
No changes from v3.
Changes from v2:
- Added mbox-names proper
On Mon, Nov 17, 2014 at 02:23:48PM -0800, Juston Li wrote:
> FMODE_EXEC is type fmode_t but is used in operations
> with integers which leads to sparse warnings:
> drivers/staging/lustre/lustre/mdc/mdc_lib.c:198:21: warning: restricted
> fmode_t degrades to integer
> drivers/staging/lustre/lustre/
Quoting Thomas Petazzoni (2014-11-14 07:21:28)
> This commit adds suspend/resume support for the gatable clock driver
> used on Marvell EBU platforms. When getting out of suspend, the
> Marvell EBU platforms go through the bootloader, which re-enables all
> gatable clocks. However, upon resume, the
This series adds support for xHCI on NVIDIA Tegra SoCs. This includes:
- patches 1, 2, and 3: minor cleanups for mailbox framework and xHCI,
- patches 4 and 5: adding a driver for the mailbox used to communicate
with the xHCI controller's firmware,
- patches 6 and 7: extending the XUSB pad c
On November 17, 2014 1:46:59 PM EST, Andy Lutomirski
wrote:
>On Mon, Nov 17, 2014 at 10:31 AM, Andy Lutomirski
>wrote:
>> On Mon, Nov 17, 2014 at 10:06 AM, Casey Schaufler
>> wrote:
>>> On 11/15/2014 1:01 AM, Josh Triplett wrote:
Currently, unprivileged processes (without CAP_SETGID) can
The mailbox controller's channel ops ought to be read-only.
Signed-off-by: Andrew Bresticker
---
New for v5.
---
include/linux/mailbox_controller.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mailbox_controller.h
b/include/linux/mailbox_controller.h
index d
Assign ports previously owned by the EHCI controllers to the xHCI
controller. There are two external USB ports (UTMI ports 0/2 and
USB3 ports 0/1) and an internal USB port (UTMI port 1). PCIe lanes
0 and 1 are used by the USB3 ports.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
Add nodes for the Tegra XUSB mailbox and Tegra xHCI controller and
add the PHY mailbox channel to the XUSB padctl node.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
---
No changes from v4.
No changes from v3.
Changes from v2:
- Dropped channel specifier from mailbox bindings.
-
Assign USB ports previously owned by the EHCI controllers to the xHCI
controller. There is a mini-PCIe USB port (UTMI port 1) and a USB A
connector (UTMI port 2, USB3 port 0). PCIe lane 0 is used for USB3
port 0.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
---
Changes from v4:
The Tegra xHCI controller's firmware communicates requests to the host
processor through a mailbox interface. While there is only a single
physical channel, messages sent by the controller can be divided
into two groups: those intended for the PHY driver and those intended
for the host-controller
Add support for the on-chip xHCI host controller present on Tegra SoCs.
The controller requires external firmware which must be loaded before
using the controller. This driver loads the firmware, starts the
controller, and is able to service host-specific messages sent by
the controller's firmware
On Mon, 17 Nov 2014, Thomas Gleixner wrote:
> On Mon, 17 Nov 2014, Linus Torvalds wrote:
> > llist_for_each_entry_safe(csd, csd_next, entry, llist) {
> > - csd->func(csd->info);
> > + smp_call_func_t func = csd->func;
> > + void *info = csd->info;
> > c
In addition to the PCIe and SATA PHYs, the XUSB pad controller also
supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single
PCIe or SATA lane and is mapped to one of the three UTMI ports.
The xHCI controller will also send messages intended for the PHY driver,
so request and listen
Add new bindings used for USB support by the Tegra XUSB pad controller.
This includes additional PHY types, USB-specific pinconfig properties, etc.
Signed-off-by: Andrew Bresticker
Acked-by: Linus Walleij
Reviewed-by: Stephen Warren
---
Changes from v4:
- nvidia,usb2-port-num -> nvidia,usb2-po
xhci_gen_setup() sets the hcd_priv field for the primary HCD, but not
for the shared HCD, requiring xHCI host-controller drivers to set it
between usb_create_shared_hcd() and usb_add_hcd(). There's no reason
xhci_gen_setup() can't set the shared HCD's hcd_priv as well, so move
that bit out of the
This is a patch to the ftdi_sio_ids.h and ftdi_sio.c files that adds PIDs for
new Matrix Orbital GTT series products
Signed-off-by: Troy Clark
---
drivers/usb/serial/ftdi_sio.c | 33 +
drivers/usb/serial/ftdi_sio_ids.h | 39 +++-
On Mon, Nov 17, 2014 at 02:22:59PM -0800, Andy Lutomirski wrote:
> On Mon, Nov 17, 2014 at 2:11 PM, Eric W.Biederman
> wrote:
> >
> >
> > On November 17, 2014 1:07:30 PM EST, Andy Lutomirski
> > wrote:
> >>On Nov 17, 2014 3:37 AM, "One Thousand Gnomes"
> >> wrote:
> >>>
> >>> > optional), I can
On Mon, 17 Nov 2014, Linus Torvalds wrote:
> On Fri, Nov 14, 2014 at 5:59 PM, Linus Torvalds
> wrote:
> >
> > Judging by the code disassembly, it's the "csd_lock_wait(csd)" at the
> > end.
>
> Btw, looking at this, I grew really suspicious of this code in csd_unlock():
>
> WARN_ON((csd->
On Mon, Nov 17, 2014 at 1:55 PM, Luck, Tony wrote:
>>> However, I'd like to be very sure this thing doesn't introduce any
>>> regressions to the MCA code. So even if Tony's testing passes, I'd like
>>> to be very conservative here and stress it more than usual. Because once
>>> this thing hits ups
FMODE_EXEC is type fmode_t but is used in operations
with integers which leads to sparse warnings:
drivers/staging/lustre/lustre/mdc/mdc_lib.c:198:21: warning: restricted fmode_t
degrades to integer
drivers/staging/lustre/lustre/mdc/mdc_locks.c:300:49: warning: restricted
fmode_t degrades to inte
On Mon, Nov 17, 2014 at 2:11 PM, Eric W.Biederman wrote:
>
>
> On November 17, 2014 1:07:30 PM EST, Andy Lutomirski
> wrote:
>>On Nov 17, 2014 3:37 AM, "One Thousand Gnomes"
>> wrote:
>>>
>>> > optional), I can do that too. The security model of "having a
>>group
>>> > gives you less privilege
(2014/11/18 5:49), Dave Hansen wrote:
> On 11/13/2014 06:49 AM, Masami Hiramatsu wrote:
>> (2014/11/13 7:53), Dave Hansen wrote:
>>> The kprobes code probably needs to be looked at here a bit more
>>> carefully. This patch still respects the MAX_INSN_SIZE limit
>>> there but the kprobes code does
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/pci-txe.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/misc/mei/pci-txe.c b/drivers/misc/mei/pci-txe.c
index bee1c6fb7e75..1b1a6e558c1c 100644
--- a/drivers/misc/mei/pci-txe.c
+++ b/drivers/misc/mei/pci-txe.c
@@ -37,6 +37,7 @@
st
Ivan T. Ivanov schrieb am 12.11.2014 09:55:
>
> On Tue, 2014-11-11 at 23:39 +0100, Hartmut Knaack wrote:
>> Ivan T. Ivanov schrieb am 11.11.2014 09:21:
>>> Hi Hartmut,
>>>
>>> On Mon, 2014-11-10 at 22:11 +0100, Hartmut Knaack wrote:
Ivan T. Ivanov schrieb am 03.11.2014 16:24:
> From: Stan
On November 17, 2014 1:07:30 PM EST, Andy Lutomirski
wrote:
>On Nov 17, 2014 3:37 AM, "One Thousand Gnomes"
> wrote:
>>
>> > optional), I can do that too. The security model of "having a
>group
>> > gives you less privilege than not having it" seems crazy, but
>> > nonetheless I can see a coup
On Mon, Nov 17, 2014 at 1:39 PM, Stephane Viau wrote:
> The core clock rate depends on the hw configuration. Once we have
> read the hardware revision, we can set the core clock to its
> maximum value.
> Before then, the clock is set at a rate supported by all MDP5
> revisions.
>
> Signed-off-by:
(2014/11/17 12:17), Masami Hiramatsu wrote:
> (2014/11/17 12:08), Namhyung Kim wrote:
>> Hi Masami,
>>
>> On Thu, 13 Nov 2014 00:25:57 +0900, Masami Hiramatsu wrote:
>>> (2014/11/11 22:10), Arnaldo Carvalho de Melo wrote:
What I meant was, what is wrong with replacing:
perf cache --
On Nov 17 2014 or thereabouts, Greg KH wrote:
> On Mon, Nov 17, 2014 at 04:43:05PM -0500, Benjamin Tissoires wrote:
> > Hey Antonio,
> >
> > On Nov 16 2014 or thereabouts, Antonio Borneo wrote:
> > > From: Jean-Baptiste Maneyrol
> > >
> > > From: Jean-Baptiste Maneyrol
> > >
> > > Current driv
From: Matt Wagantall
It is sometimes necessary to poll a memory-mapped register until its value
satisfies some condition. Introduce a family of convenience macros that do
this. Tight-looping, sleeping, and timing out can all be accomplished using
these macros.
Cc: Thierry Reding
Cc: Will Deacon
On Mon, 2014-11-17 at 16:35 -0500, David Miller wrote:
> From: Eric Dumazet
> Date: Mon, 17 Nov 2014 13:22:56 -0800
>
> > On Mon, 2014-11-17 at 22:08 +0100, Fabian Frederick wrote:
> >> Signed-off-by: Fabian Frederick
> >> ---
> >> net/core/link_watch.c | 2 +-
> >> 1 file changed, 1 insertion(
On Monday, November 17, 2014 03:51:01 PM Richard Guy Briggs wrote:
> The version field defined in the audit status structure was found to have
> limitations in terms of its expressibility of features supported. This is
> distict from the get/set features call to be able to command those features
>
On Mon, Nov 17, 2014 at 12:33 PM, Arnd Bergmann wrote:
>> This mostly depends on the desired feature set, and the delta from one
>> board to the next. Many of the reference board sections are largely
>> copied from a working design, but sometimes there are changes that
>> affect us. Other times
On 11/17/2014 12:52 PM, Linus Torvalds wrote:
On Mon, Nov 17, 2014 at 9:18 AM, Alexander Duyck
wrote:
There are a number of situations where the mandatory barriers rmb() and
wmb() are used to order memory/memory operations in the device drivers
and those barriers are much heavier than they act
>> However, I'd like to be very sure this thing doesn't introduce any
>> regressions to the MCA code. So even if Tony's testing passes, I'd like
>> to be very conservative here and stress it more than usual. Because once
>> this thing hits upstream and stuff starts breaking, it'll be a serious
>> P
On Mon, Nov 17, 2014 at 01:24:00PM -0800, Sukadev Bhattiprolu wrote:
> Alexander Shishkin [alexander.shish...@linux.intel.com] wrote:
> | From: Peter Zijlstra
> |
> | This patch introduces "AUX space" in the perf mmap buffer, intended for
> | exporting high bandwidth data streams to userspace, su
On Mon, Nov 17, 2014 at 04:43:05PM -0500, Benjamin Tissoires wrote:
> Hey Antonio,
>
> On Nov 16 2014 or thereabouts, Antonio Borneo wrote:
> > From: Jean-Baptiste Maneyrol
> >
> > From: Jean-Baptiste Maneyrol
> >
> > Current driver uses a common buffer for reading reports either
> > synchrono
Arnd Bergmann writes:
> On Monday 17 November 2014 11:14:16 Kevin Hilman wrote:
>> >>
>> >> So, The Keystone 2 Generic PM Controller is just a proxy PM layer here
>> >> between
>> >> device and Generic clock manipulation PM callbacks.
>> >> It fills per-device clock list when device is attached
Hey Antonio,
On Nov 16 2014 or thereabouts, Antonio Borneo wrote:
> From: Jean-Baptiste Maneyrol
>
> From: Jean-Baptiste Maneyrol
>
> Current driver uses a common buffer for reading reports either
> synchronously in i2c_hid_get_raw_report() and asynchronously in
> the interrupt handler.
> Ther
From: Eric Dumazet
Date: Mon, 17 Nov 2014 13:22:56 -0800
> On Mon, 2014-11-17 at 22:08 +0100, Fabian Frederick wrote:
>> Signed-off-by: Fabian Frederick
>> ---
>> net/core/link_watch.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/core/link_watch.c b/net/core/
Em Wed, Nov 12, 2014 at 06:05:18PM -0800, Andi Kleen escreveu:
> [Reworks to address all the review feedback. Rebased to latest tree]
> [Just a repost after a rebase]
> [Even more review feedback and some bugs addressed.]
> [Only port to changes in perf/core. No other changes.]
> [Rebase to latest
On Fri, Oct 31, 2014 at 09:27:16PM +0100, Vlastimil Babka wrote:
> What could help would be to cache one or few free huge pages per
> zone with cache
> re-fill done asynchronously, e.g. via work queues. The cache could
> benefit fault-THP
> allocations as well. And adding some logic that if nobody
On Mon, 2014-11-17 at 09:18 -0800, Alexander Duyck wrote:
> This change makes it so that fast_rmb is used when reading the Rx
> descriptor. The advantage of fast_rmb is that it allows for a much
> lower cost barrier on x86, powerpc, arm, and arm64 architectures than
> a
> traditional memory barrie
On Mon, Nov 17, 2014 at 01:29:00PM -0800, Andrew Morton wrote:
> Looks OK to me. Do you have some patch which depends on this? If
> so, please merge this via whatever tree carries that patch?
The dependant ones will have to go through -mm anyway, so applying to
-mm should be fine.
Thanks.
--
On Nov 16 2014 or thereabouts, Antonio Borneo wrote:
> From: Jean-Baptiste Maneyrol
>
> From: Jean-Baptiste Maneyrol
>
> Report is received in "buffer"; fix the following i2c_hid_dbg()
> to dump data from the correct pointer.
>
> Signed-off-by: Jean-Baptiste Maneyrol
> [Antonio Borneo: cleanu
On Mon, 17 Nov 2014, Bjorn Helgaas wrote:
> Super. Thank you very much for taking care of this; it's a big weight
> off my mind.
>
> You can add my Acked-by to these patches if you want it. I would
> suggest a minor comment expansion here, just because the code *looks
> like* it's setting up som
On 11/17/2014 10:26 PM, Andrew Bresticker wrote:
On Mon, Nov 17, 2014 at 1:21 PM, Daniel Lezcano
wrote:
On 11/12/2014 08:43 PM, Andrew Bresticker wrote:
Parse the GIC timer frequency and interrupt from the device-tree.
Signed-off-by: Andrew Bresticker
Acked-by: Arnd Bergmann
Hi Andrew,
On 11/12/2014 08:43 PM, Andrew Bresticker wrote:
Parse the GIC timer frequency and interrupt from the device-tree.
Signed-off-by: Andrew Bresticker
Acked-by: Arnd Bergmann
Acked-by: Daniel Lezcano
---
Changes from v4:
- don't probe from irqchip; just warn if DT is wrong
Changes from v3:
On Mon, 17 Nov 2014 16:17:23 -0500 Tejun Heo wrote:
> swp_entry_t being defined in include/linux/swap.h instead of
> include/linux/mm_types.h causes cyclic include dependency later when
> include/linux/page_cgroup.h is included from writeback path. Move the
> definition to include/linux/mm_types
On Mon, Nov 17, 2014 at 2:02 PM, Thomas Gleixner wrote:
> On Mon, 17 Nov 2014, Bjorn Helgaas wrote:
>> On Mon, Nov 17, 2014 at 2:38 AM, Thomas Gleixner wrote:
>> > The simplest way to dead with it is that I pull in pci/msi (assuming
>> > that it contains only the above) and base the rest of it on
On Mon, Nov 17, 2014 at 1:21 PM, Daniel Lezcano
wrote:
> On 11/12/2014 08:43 PM, Andrew Bresticker wrote:
>>
>> Parse the GIC timer frequency and interrupt from the device-tree.
>>
>> Signed-off-by: Andrew Bresticker
>> Acked-by: Arnd Bergmann
>
>
> Hi Andrew,
>
> through which tree is this patc
Alexander Shishkin [alexander.shish...@linux.intel.com] wrote:
| From: Peter Zijlstra
|
| This patch introduces "AUX space" in the perf mmap buffer, intended for
| exporting high bandwidth data streams to userspace, such as instruction
| flow traces.
|
| AUX space is a ring buffer, defined by au
Also remove spaces after cast.
Signed-off-by: Fabian Frederick
---
net/core/dev_ioctl.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/net/core/dev_ioctl.c b/net/core/dev_ioctl.c
index 72e899a..b94b1d2 100644
--- a/net/core/dev_ioctl.c
+++ b/net/core/dev_ioctl.c
@@
From: Terence Eden
I found the comments to be slightly confusing. Hopefully I've clarified some
points.
Signed-off-by: Terence Eden
---
drivers/scsi/isci/port_config.c | 158 +---
1 file changed, 83 insertions(+), 75 deletions(-)
diff --git a/drivers/scsi/
On Mon, 2014-11-17 at 22:08 +0100, Fabian Frederick wrote:
> Signed-off-by: Fabian Frederick
> ---
> net/core/link_watch.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/core/link_watch.c b/net/core/link_watch.c
> index bd0767e..49a9e3e 100644
> --- a/net/core/link_
On Mon, Nov 17, 2014 at 12:40 PM, Arnd Bergmann wrote:
>> One possible complication: for BCM63xx/BCM7xxx (MIPS) there is no
>> decompressor in the kernel. The firmware loads an ELF image into
>> memory and jumps directly to kernel_entry.
>>
>
> Right, that complicates it a bit, but is there a rea
On Fri, Nov 14, 2014 at 5:59 PM, Linus Torvalds
wrote:
>
> Judging by the code disassembly, it's the "csd_lock_wait(csd)" at the
> end.
Btw, looking at this, I grew really suspicious of this code in csd_unlock():
WARN_ON((csd->flags & CSD_FLAG_WAIT) && !(csd->flags & CSD_FLAG_LOCK));
be
On 11/12/2014 08:43 PM, Andrew Bresticker wrote:
Parse the GIC timer frequency and interrupt from the device-tree.
Signed-off-by: Andrew Bresticker
Acked-by: Arnd Bergmann
Hi Andrew,
through which tree is this patch supposed to go ?
Is there any dependency ?
---
Changes from v4:
- don'
201 - 300 of 871 matches
Mail list logo
