Theodore Ts'o writes:
> On Mon, Jun 19, 2017 at 10:57:18PM +0200, Jason A. Donenfeld wrote:
>>
>> With rc6 already released and rc7 coming up, I'd really appreciate you
>> stepping in here and either ACKing the above commit, or giving your
>> two cents about it in case I need to roll something d
On 20/06/17 08:54, Zhi Mao wrote:
1.fix clock control
- prepare top/main clk in mtk_pwm_probe() function,
it will increase power consumption
and in original code these clocks is only prepeare but never enabled
- pwm clock should be enabled before setting pwm registers
in function
a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Philipp-Zabel/reset-Add-APIs-to-manage-array-of-resets/20170620-021320
> base: git://git.pengutronix.de/git/pza/linux reset/next
> config: i386-randconfig-c0-06200218 (attached as .config)
On 17 June 2017 at 17:25, Mauro Carvalho Chehab
wrote:
> Each text file under Documentation follows a different
> format. Some doesn't even have titles!
>
> Change its representation to follow the adopted standard,
> using ReST markups for it to be parseable by Sphinx:
>
> - use proper markups for
Thanks Andy, applied to uuid for-next.
Hi Willy,
You can drop this patch.
There's nothing to fix on 3.10.x since the DMA TX support has been
introduced in 3.12.
Thanks !
2017-06-19 20:31 GMT+02:00 Willy Tarreau :
> From: Richard Genoud
>
> commit 31ca2c63fdc0aee725cbd4f207c1256f5deaabde upstream.
>
> If uart_flush_buffer() is call
Thanks Colin,
applied to uuid for-next.
On Mon 2017-06-12 18:56:53, Salvatore Mesoraca wrote:
> Introduction of S.A.R.A. USB Filtering.
> It uses the "usb_device_auth" LSM hook to provide a mechanism to decide
> which USB devices should be authorized to connect to the system and
> which shouldn't.
> The main goal is to narrow the attack
ACPI 6.2 have added SRAT subtable to define proximity domain for ITS
devices. This patchset updates acpi header file from acpica repo and
adds numa node mapping for ITS devices.
v2:
- Incorporated comments from Lorenzo Pieralisi and Marc Zyngier.
v1: first patch
Ganapatrao Kulkarni (2):
ACPIC
Add code to parse SRAT ITS Affinity sub table as defined in ACPI 6.2
Later in per device probe, ITS devices are mapped to
numa node using ITS id to proximity domain mapping.
Signed-off-by: Ganapatrao Kulkarni
---
drivers/irqchip/irq-gic-v3-its.c | 76 +++-
1 f
Hi!
> Memory protection keys enable applications to protect its
> address space from inadvertent access or corruption from
> itself.
>
> The overall idea:
>
> A process allocates a key and associates it with
> a address range withinits address space.
> The process than can dy
Add GIC ITS Affinity (ACPI 6.2) subtable to SRAT table.
ACPICA commit 5bc67f63918da249bfe279ee461d152bb3e6f55b
Link: https://github.com/acpica/acpica/commit/5bc67f6
Signed-off-by: Ganapatrao Kulkarni
---
include/acpi/actbl1.h | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
d
This is a driver for Low Power General Purpose Register (LPGPR)
available on i.MX6 SoCs in Secure Non-Volatile Storage (SNVS)
of this chip.
It is a 32-bit read/write register located in the low power domain.
Since LPGPR is located in the battery-backed power domain, LPGPR can
be used by any applic
changes v7:
- split imx6ul patch and squash it with with main patches.
- spell fixes in the binding documentation
- return regmap_bulk_read directly.
changes v6:
- check if device is writable by reading GPR_SL and GPR_HL bits
- use regmap_bulk_* functions instead of while() { regmap_read/writ
This node is for Low Power General Purpose Register which can
be used as Non-Volatile Storage.
Signed-off-by: Oleksij Rempel
---
arch/arm/boot/dts/imx6qdl.dtsi | 4
arch/arm/boot/dts/imx6ul.dtsi | 4
2 files changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/
Documentation bindings for the Low Power General Purpose Register
available on i.MX6 SoCs in the Secure Non-Volatile Storage.
Signed-off-by: Oleksij Rempel
---
.../devicetree/bindings/nvmem/snvs-lpgpr.txt | 20
1 file changed, 20 insertions(+)
create mode 100644 Doc
On Mon, Jun 19, 2017 at 6:34 PM, Al Viro wrote:
> On Mon, Jun 19, 2017 at 10:15:09AM -0600, Jordan Crouse wrote:
>
>> Which raised a bikeshed debate over whether it is appropriate to mark a
>> scalar
>> type as __user. My opinion is that it is appropriate because __user should
>> mark
>> user m
Exynos5433 has two usb 3.0 controllers: usbhost and usbdrd. usbhost
is host-only controller whereas usbdrd supports both peripheral and
host mode. "drd" means dual-role device, so usbhost cannot be labeled
with the name contains "drd". Howerver, the label usbdrd_dwc3_0 was
used for usbhost's dwc3 n
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> We're currently only checking the first character of the input to the
> debugfs event files, so a string like '0sdfdsf' is valid and indicates
> a falling edge event.
>
> Be more strict and only allow '0', '1', '0\n' & '1\n'.
>
> While
Since commit 9840354ff429 ("usb: dwc3: Add dual-role support") dwc3
node requires extcon property to be initialized as otg mode, and it
can support dual-role mode operation.
Signed-off-by: Dongwoo Lee
---
arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi | 1 +
1 file changed, 1 insertion(+)
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> Invert the logic of the irq_enabled check and only access the private
> data after the input is sanitized.
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
Hi Heiko,
On 2017/6/19 20:30, Heiko Stübner wrote:
Hi Frank,
Am Montag, 19. Juni 2017, 18:34:27 CEST schrieb Frank Wang:
On 2017/6/18 2:12, Heiko Stuebner wrote:
Am Donnerstag, 15. Juni 2017, 15:16:15 CEST schrieb Frank Wang:
Due to some tiny differences between RK3228 and RK3229, this patch
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> Currently we ignore the last odd range value, since each chip is
> described by two values. Be more strict and require the user to
> pass an even number of ranges.
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Wa
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> When the requested number of GPIO lines is 0, return -EINVAL, not
> -1 which is -EPERM.
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> We currently shift bits here and there without actually explaining
> what we're doing. Add some helper variables with names indicating
> their purpose to improve the code readability.
>
> Signed-off-by: Bartosz Golaszewski
Patch appli
On 06/20/2017 11:36 AM, Cédric Le Goater wrote:
> On 06/20/2017 07:08 AM, Shilpasri G Bhat wrote:
>> From: Cédric Le Goater
>>
>> Today, the type of a PowerNV sensor system is determined with the
>> "compatible" property for legacy Firmwares and with the "sensor-type"
>> for newer ones. The same
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> Indicate the error number and make the message a bit more elaborate.
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
On Tuesday 20 June 2017 11:05:19 Kai-Heng Feng wrote:
> Dell Latitude 3160 does not have keyboard backlight, but there is a
> sysfs interface for it, which does nothing at all.
>
> KBD_LED_ON_TOKEN is the only token can be found. Since it doesn't have
> KBD_LED_OFF_TOKEN or KBD_LED_AUTO_*_TOKEN, i
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> Just taking credit for the recent changes and new features. :)
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
On Fri, Jun 9, 2017 at 1:41 PM, Bartosz Golaszewski wrote:
> When allocating a zeroed array of objects use devm_kcalloc() instead
> of manually calculating the required size and using devm_kzalloc().
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
Hi,
commit: 347de24 (powerpc/64s: implement arch-specific hardlockup
watchdog)
linux-next fails to boot on PowerPC Bare-metal box.
Test: boot
Machine type: Power 8 Bare-metal
Kernel: 4.12.0-rc5-next-20170619
gcc: version 4.8.5
In file arch/powerpc/kernel/watchdog.c
void soft_nmi_interrupt(str
On 06/20/2017 07:08 AM, Shilpasri G Bhat wrote:
> From: Cédric Le Goater
>
> Today, the type of a PowerNV sensor system is determined with the
> "compatible" property for legacy Firmwares and with the "sensor-type"
> for newer ones. The same array of strings is used for both to do the
> matching
On Fri, Jun 16, 2017 at 01:50:23PM -0500, Tom Lendacky wrote:
> The ioremap() function is intended for mapping MMIO. For RAM, the
> memremap() function should be used. Convert calls from ioremap() to
> memremap() when re-mapping RAM.
>
> This will be used later by SME to control how the encryption
On 06/20/2017 07:08 AM, Shilpasri G Bhat wrote:
> This patch exports current(A) sensors in inband sensors copied to
> main memory by OCC.
>
> Signed-off-by: Shilpasri G Bhat
Reviewed-by: Cédric Le Goater
Thanks,
C.
> ---
> Changes from V1:
> - Rebased on top of Cedric's patch to remove legay
On 06/17/2017 09:22 AM, Ram Pai wrote:
> Handle Data and Instruction exceptions caused by memory
> protection-key.
>
> Signed-off-by: Ram Pai
> (cherry picked from commit a5e5217619a0c475fe0cacc3b0cf1d3d33c79a09)
To which tree this commit belongs to ?
>
> Conflicts:
> arch/powerpc/includ
Hi Richard,
On Tue, Jun 20, 2017 at 09:04:03AM +0200, Richard Genoud wrote:
> Hi Willy,
>
> You can drop this patch.
>
> There's nothing to fix on 3.10.x since the DMA TX support has been
> introduced in 3.12.
I've already dropped it as it broke some build.
Thanks!
Willy
On Tue, 13 Jun 2017 22:45:34 +0900
Masahiro Yamada wrote:
> This patch series intends to solve various problems.
>
> [1] The driver just retrieves the OOB area as-is
> whereas the controller uses syndrome page layout.
> [2] ONFi devices are not working
> [3] It can not read Bad Block Marker
On Monday 19 June 2017 20:37:25 Darren Hart wrote:
> dell-wmi:
> Type and code, where type may be, for example, "sequence" and then each byte
> of
> buffen length is processed as a key.
It is more complicated. Buffer can contain more sequences (each has own
length) and each sequence can contain d
Hi Archit,
On Tuesday 20 Jun 2017 09:18:00 Archit Taneja wrote:
> On 06/16/2017 08:13 PM, Eric Anholt wrote:
> > Archit Taneja writes:
> >> On 06/16/2017 02:11 AM, Eric Anholt wrote:
> >>> If the panel-bridge is being set up after the drm_mode_config_reset(),
> >>> then the connector's state woul
Hi Stephen,
On mar., juin 20 2017, Stephen Boyd wrote:
> On 06/19, Gregory CLEMENT wrote:
>>
>> Hi Mike, Stephen,
>>
>> This time I turned the series in a pull request so I removed the
>> device tree binding part which will be in an other series for Rob
>> Herring and I also removed the dt p
On Mon, Jun 19, 2017 at 07:19:57PM +0100, Al Viro wrote:
> Speaking of iomap, what's supposed to happen when doing a write into what
> used to be a hole? Suppose we have a file with a megabyte hole in it
> and there's some process mmapping that range. Another process does
> write over the entire
On Fri, Jun 16, 2017 at 01:51:15PM -0500, Tom Lendacky wrote:
> Add support to the early boot code to use Secure Memory Encryption (SME).
> Since the kernel has been loaded into memory in a decrypted state, encrypt
> the kernel in place and update the early pagetables with the memory
> encryption m
Below is the list of build error/warning regressions/improvements in
v4.12-rc6[1] compared to v4.11[2].
Summarized:
- build errors: +2/-1
- build warnings: +27127/-5636
JFYI, when comparing v4.12-rc6[1] to v4.12-rc5[3], the summaries are:
- build errors: +4/-
- build warnings: +565/-5931
Hi,
> Yep that's cargo-culted, but from a quick grep only msm and qxl
> headers do this (the other __user annotations in uapi/drm are for
> pointers, where it's correct). Adding those maintainers.
Yep, those looks pointless indeed.
> Also, if you use u64_to_user_ptr helper macro sparse should
On 19.06.2017 17:05, Daniel Axtens wrote:
Hi Konstantin and Peter,
Just checking if this version was OK with you - I hadn't heard anything
and I noticed it's not in -next so I just wanted to check to see if
there were any other changes you wanted.
Looks good for me. Exactly that debug helped
On Tue, Jun 20, 2017 at 9:39 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.12-rc6[1] to v4.12-rc5[3], the summaries are:
> - build errors: +4/-
+ /home/kisskb/slave/src/arch/sh/boards/mach-sh03/setup.c: error:
implicit declaration of function 'ioremap_prot'
[-Werror=implicit-functio
Since commit 9840354ff429 ("usb: dwc3: Add dual-role support") USB
dual-role operation on TM2 and TM2E can be enabled by simply adding
extcon property. However, exynos5433 dt has the mislabeled dwc3 node,
and thus we should resolve it first to apply the property.
This patchset fixes up the device
On 16/06/17 10:29, Quentin Schulz wrote:
> This adds deepest (Backup+Self-Refresh) PM support to the ATMEL SAMA5D2
> SoC's SDHCI controller.
>
> When resuming from deepest state, it is required to restore preset
> registers as the registers are lost since VDD core has been shut down
> when enterin
On Mon, 2017-06-19 at 18:29 +0200, Mike Galbraith wrote:
> On Mon, 2017-06-19 at 10:41 -0400, Steven Rostedt wrote:
> > On Mon, 19 Jun 2017 16:13:41 +0200
> > Sebastian Andrzej Siewior wrote:
> >
> >
> > > > Hmm, it shouldn't affect futexes, as it's only called by rtmutex when
> > > > waiter->sa
On Mon, Jun 19, 2017 at 05:58:19PM -0700, Brendan Higgins wrote:
> On Mon, Jun 19, 2017 at 7:21 AM, Wolfram Sang wrote:
> >
> > And any chance for a MAINTAINERS entry?
> >
>
> We already have one:
> http://elixir.free-electrons.com/linux/v4.11.5/source/MAINTAINERS#L1090
>
> However, if you would
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/video/backlight/pwm_bl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi Hugh! We're running our tests on latest vanilla kernel all the time,
and recently we've got an issue on restore:
https://github.com/xemul/criu/issues/322
| (00.410614) 4: cg: Cgroups 1 inherited from parent
| (00.410858) 4: Opened local page read 3 (parent 0)
| (00.410961) 4:
2017-06-20 9:07 GMT+02:00 Pavel Machek :
> Hmm. Given that USB device provides vendor id/product id, this does
> not really stop anyone, right?
>
> AFAICT you can still get USB stick with vid/pid of logitech keyboard,
> and kernel will recognize it as a usb stick.
There are a number of ways by whi
On 06/20/2017 09:15 AM, Shilpasri G Bhat wrote:
>
>
> On 06/20/2017 11:36 AM, Cédric Le Goater wrote:
>> On 06/20/2017 07:08 AM, Shilpasri G Bhat wrote:
>>> From: Cédric Le Goater
>>>
>>> Today, the type of a PowerNV sensor system is determined with the
>>> "compatible" property for legacy Firmw
On Tue, Jun 20, 2017 at 09:31:00AM +0200, Rafal Milecki wrote:
> Do you know if my name will appear correctly in git [0]?
>
> [0]
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/?h=linux-3.10.y
I would have almost promised it was going to be OK but it's bogus so
it
On Fri, Jun 9, 2017 at 2:52 PM, Andrew Jeffery wrote:
> So the fttmr010 bindings describe the clocks and clock-names properties
> as optional (a little confusingly, "Optionally required properties").
We should remove that. The timer frequency is strictly required.
> I guess keeping in mind the
Hi Adrian,
On 20/06/2017 09:39, Adrian Hunter wrote:
> On 16/06/17 10:29, Quentin Schulz wrote:
>> This adds deepest (Backup+Self-Refresh) PM support to the ATMEL SAMA5D2
>> SoC's SDHCI controller.
>>
>> When resuming from deepest state, it is required to restore preset
>> registers as the registe
On Fri, Jun 9, 2017 at 6:48 PM, Krzysztof Kozlowski wrote:
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/samsun
On 06/19/2017 07:22 PM, Wolfram Sang wrote:
I wonder if we haven't reached a state where Luis just could fix the
buildbot error (missing 'select I2C_SLAVE') and the thing pointed out by
Andy and we handle further small fixes incrementally during the v4.13
cycle? AFAICS there is no major show-st
Hi Adrian,
On 20/06/2017 08:36, Adrian Hunter wrote:
> On 16/06/17 10:29, Quentin Schulz wrote:
>> The setting of clocks and presets is currently done in probe only but
>> once deep PM support is added, it'll be needed in the resume function.
>>
>> Let's create a function for this setting.
>>
>> S
On Fri, Jun 9, 2017 at 8:33 PM, Jan Kiszka wrote:
> This fixes reloading of the GPIO driver for the same platform device
> instance as created by the exar UART driver: First of all, the driver
> sets drvdata to its own value during probing and does not restore the
> original value on exit. But th
On Fri, Jun 9, 2017 at 8:33 PM, Jan Kiszka wrote:
> Do not allocate resources on behalf of the parent device but on our own.
> Otherwise, cleanup does not properly work if gpio-exar is removed but
> not the parent device.
>
> Signed-off-by: Jan Kiszka
> Reviewed-by: Andy Shevchenko
> Acked-by:
Hey Ted,
On Tue, Jun 20, 2017 at 02:03:44AM -0400, Theodore Ts'o wrote:
> I actually had set up an earlier version of your patch for on Saturday
> while I was in Beijing. (Like Linus, I'm attending the LinuxCon China
> conference Monday and Tuesday.) I had even created the signed tag,
> I've sin
On 06/17/2017 09:22 AM, Ram Pai wrote:
> Replace the magic number used to check for DSI exception
> with a meaningful value.
>
> Signed-off-by: Ram Pai
> ---
> arch/powerpc/include/asm/reg.h | 9 -
> arch/powerpc/kernel/exceptions-64s.S | 2 +-
> 2 files changed, 9 insertions(+), 2
On Fri, Jun 9, 2017 at 8:33 PM, Jan Kiszka wrote:
> First, the logic for translating a register bit to the return code of
> exar_get_direction and exar_get_value were wrong. And second, there was
> a flip regarding the register bank in exar_get_direction.
>
> Signed-off-by: Jan Kiszka
> Reviewed
On Fri, Jun 9, 2017 at 8:33 PM, Jan Kiszka wrote:
> The UART driver already maps the resource for us. Trying to do this here
> only fails and leaves us with a non-working device.
>
> Signed-off-by: Jan Kiszka
> Reviewed-by: Andy Shevchenko
> Acked-by: Linus Walleij
This patch does not apply t
On Mon, 12 Jun 2017, Andrey Smirnov wrote:
> Add a driver for RAVE Supervisory Processor, an MCU implementing
> varoius bits of housekeeping functionality (watchdoging, backlight
> control, LED control, etc) on RAVE family of products by Zodiac
> Inflight Innovations.
>
> This driver implementes
On Fri, Jun 9, 2017 at 8:33 PM, Jan Kiszka wrote:
> This makes the gpio-exar driver usable, which was prevented by a number
> of fatal bugs, and adds support for the SIMATIC IOT2040 to the 8250-exar
> driver and, indirectly, to gpio-exar as well. It's a cross-subsystem
> series, so I'm also cross
On Tue, Jun 20, 2017 at 10:14:05AM +0200, Rafal Milecki wrote:
> On 2017-06-20 09:58, Willy Tarreau wrote:
> > On Tue, Jun 20, 2017 at 09:31:00AM +0200, Rafal Milecki wrote:
> > > Do you know if my name will appear correctly in git [0]?
> > >
> > > [0]
> > > https://git.kernel.org/pub/scm/linux/k
On 30.05.17 17:33:39, Geetha sowjanya wrote:
> From: Linu Cherian
>
> Cavium ThunderX2 implementation doesn't support second page in SMMU
> register space. Hence, resource size is set as 64k for this model.
>
> Signed-off-by: Linu Cherian
> Signed-off-by: Geetha Sowjanya
> ---
> drivers/acpi/
Marc Z pointed out that posting partial series is not ideal.
Collect last-minute fixups into a single patch series.
- Bump series to v9 to avoid any ambiguity
- Add Rob's Ack on patch 1
Marc Gonzalez (3):
PCI: Add DT binding for tango PCIe controller
PCI: Add tango PCIe host bridge support
The MSI controller in Tango supports 256 message-signaled interrupts,
and a single doorbell address.
Signed-off-by: Marc Gonzalez
---
drivers/pci/host/pcie-tango.c | 226 ++
1 file changed, 226 insertions(+)
diff --git a/drivers/pci/host/pcie-tango.c b/dr
Subject is wrong. It should be:
[PATCH 1/11] Staging: ccree: add spaces blah blah blah
On Tue, Jun 20, 2017 at 01:19:44PM +0800, Jhih-Ming Huang wrote:
> From: Jhih-Ming Hunag
>
No need.
> In this series patches, I fix all of the coding style error in
> driver/staging/ccree/ssi_aead.c from
This series are based on 4.12-rc1 and provide 2 patches to support mt2712 IC.
Change in this series:
1. update document to add mt2712;
2. add mt7622_compat.
Leilk Liu (2):
spi: mediatek: Add bindings for mediatek MT2712 soc platform
spi: mediatek: add spi support for mt2712 IC
.../devicetre
This patch adds a DT binding documentation for the MT2712 soc.
Signed-off-by: Leilk Liu
---
.../devicetree/bindings/spi/spi-mt65xx.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
b/Documentation/devicetree/bindings/spi/spi-
this patch add support for mt2712 IC.
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/spi-mt65xx.c
index ec7755b..86bf456 100644
--- a/drivers/spi/spi-mt65xx.c
+++ b/drivers/spi/spi-mt65xx.
On 06/17/2017 09:22 AM, Ram Pai wrote:
> Map the PTE protection key bits to the HPTE key protection bits,
> while creatiing HPTE entries.
>
> Signed-off-by: Ram Pai
> ---
> arch/powerpc/include/asm/book3s/64/mmu-hash.h | 5 +
> arch/powerpc/include/asm/pkeys.h | 7 +++
> ar
This driver is required to work around several hardware bugs
in the PCIe controller.
NB: Revision 1 does not support legacy interrupts, or IO space.
Signed-off-by: Marc Gonzalez
---
drivers/pci/host/Kconfig | 8 +++
drivers/pci/host/Makefile | 1 +
drivers/pci/host/pcie-tango.c | 1
Binding for the Sigma Designs SMP8759 SoC.
Acked-by: Rob Herring
Signed-off-by: Marc Gonzalez
---
.../devicetree/bindings/pci/tango-pcie.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/tango-pcie.txt
diff --git
On Thu, Jun 15, 2017 at 03:52:48PM +0800, Baoquan He wrote:
>Now function process_e820_entry is only used to process e820 memory
>entry. Adapt it for memory region only, not just for e820. Later
>we will use it to process efi mirror regions.
>
>So rename the original process_e820_entry to process_m
On Tue, Jun 20, 2017 at 01:20:59PM +0800, Jhih-Ming Huang wrote:
> From: Jhih-Ming Hunag
>
> Fixed 'ERROR: spaces required around that'
>
You're breaking the patches up in a bad way. This one should be
combined with the previous patch.
regards,
dan carpenter
On Fri, Jun 16, 2017 at 01:51:55PM -0500, Tom Lendacky wrote:
> The cr3 register entry can contain the SME encryption mask that indicates
> the PGD is encrypted. The encryption mask should not be used when
> creating a virtual address from the cr3 register, so remove the SME
> encryption mask in t
On 06/19/2017 04:26 PM, Dan Carpenter wrote:
We want to timeout with try set to zero so this should be a pre-op
instead of post-op.
Signed-off-by: Dan Carpenter
diff --git a/drivers/phy/broadcom/phy-brcm-sata.c
b/drivers/phy/broadcom/phy-brcm-sata.c
index ccbc3d994998..48fb016ce689 100644
-
On Tue, Jun 20, 2017 at 01:21:46PM +0800, Jhih-Ming Huang wrote:
> From: Jhih-Ming Hunag
>
> Fixed "ERROR: space prohibited after that open parenthesis '('".
>
> Signed-off-by: Jhih-Ming Hunag
> ---
> drivers/staging/ccree/ssi_aead.c | 16
> 1 file changed, 8 insertions(+), 8
On 19/06/2017 16:50, Marc Gonzalez wrote:
> On 07/06/2017 10:19, Marc Gonzalez wrote:
>
>> On 31/05/2017 15:33, Marc Gonzalez wrote:
>>
>>> +static int tango_pcie_probe(struct platform_device *pdev)
>>> +{
>>> + int ret = -EINVAL;
>>> + void __iomem *base;
>>> + struct resource *res;
>>> +
Hi!
> >> But as Pavel pointed out, in fact we are missing many
> >> Acks still, for all of the dts source changes (patches
> >> 4-14), as well as really everything else (imx-media staging
> >> driver patches).
> >
> > No Acks needed for the staging part. It's staging, so not held
> > to the same
David Rientjes wrote:
> I would have expected to see down_read_killable() actually used somewhere
> after its implementation as part of this patchset.
There are some places we should be using down_{read|write}_interruptible(), if
it existed, dressed as inode_lock{,_shared}_interruptible().
Dav
在 2017/6/20 15:38, Guodong Xu 写道:
2017年6月20日 上午11:49，"Tao Wang" mailto:kevin.wang...@hisilicon.com>>写道：
Bind thermal sensor driver for Hi3660.
Signed-off-by: Tao Wang mailto:kevin.wang...@hisilicon.com>>
Signed-off-by: Leo Yan mailto:leo@linaro.org>>
---
arch/arm64
On Tue, Jun 20, 2017 at 4:14 AM, Jason A. Donenfeld wrote:
>...
> Specifically, I added `depends on DEBUG_KERNEL`. This means that these
> useful warnings will only poke other kernel developers. This is probably
> exactly what we want. If the various associated developers see a warning
> coming fr
Hi,
> > Hmm, plane isn't really an ID, it is a type, with type being either
> > DRM_PLANE_TYPE_PRIMARY or DRM_PLANE_TYPE_CURSOR, so I don't think
> > the
> > flage above make sense.
>
> The intention was that ..._REGION_ID and ...PLANE_ID are describing
> what the vfio_device_query_gfx_plane.id
On Tue, Jun 20, 2017 at 9:42 AM, Gerd Hoffmann wrote:
>> Yep that's cargo-culted, but from a quick grep only msm and qxl
>> headers do this (the other __user annotations in uapi/drm are for
>> pointers, where it's correct). Adding those maintainers.
>
> Yep, those looks pointless indeed.
>
>> Also
Hi Wei,
On 19 June 2017 at 15:00, Wei Xu wrote:
> Hi Ulf,
>
> On 2017/6/19 13:43, Ulf Hansson wrote:
>> On 14 June 2017 at 10:23, Guodong Xu wrote:
>>> Add bindings for hi3660 mmc support
>>>
>>> Signed-off-by: Li Wei
>>> Signed-off-by: Guodong Xu
>>> ---
>>> Documentation/devicetree/bindings
On Thu, Jun 15, 2017 at 6:20 PM, Jerome Brunet wrote:
> To handle this we tried:
> - [0]: To create the mapping in the gpio_to_irq. Linus, you pointed out that
> this is not allowed as gpio_to_irq is callable in irq context, therefore it
> should not sleep. Actually 3 drivers [2] are calling gpio
On Thu, 15 Jun 2017, Daniel Stone wrote:
> Setting these bits causes libinput to fail to initialize the device;
> setting BTN_TOUCH and BTN_TOOL_FINGER causes it to treat the mouse as a
> touchpad, and it then refuses to continue when it discovers ABS_X is not
> set.
>
> This breaks all known Way
On Mon, Jun 19, 2017 at 12:41:38PM -0600, Baicar, Tyler wrote:
> On 6/19/2017 4:22 AM, Will Deacon wrote:
> >On Mon, Jun 19, 2017 at 01:06:30PM +0300, Andy Shevchenko wrote:
> >>On Mon, 2017-06-19 at 10:19 +0100, Will Deacon wrote:
> >>>Hi Stephen, Christoph, Tyler,
> >>>On Fri, Jun 16, 2017 at 03:
Hi,
Thanks for all the comments. Here are the summaries:
1. Modify the structures to make it more general.
struct vfio_device_gfx_plane_info {
__u64 start;
__u64 drm_format_mod;
__u32 drm_format;
__u32 width;
__u32 height;
__u32 stride;
__u3
On Tue, Jun 20, 2017 at 09:40:08AM +0100, Will Deacon wrote:
> > >>To have better coordination, please, look at my WIP branch regarding
> > >>UUID stuff:
> > >>http://bitbucket.org/andy-shev/linux/branch/topic%2Fuuid
> > >That link doesn't work for me. Is there anything specific Tyler should be
> >
On Tue, Jun 20, 2017 at 01:56:35PM +0530, Vivek Gautam wrote:
>
>
> On 06/19/2017 04:26 PM, Dan Carpenter wrote:
> > We want to timeout with try set to zero so this should be a pre-op
> > instead of post-op.
> >
> > Signed-off-by: Dan Carpenter
> >
> > diff --git a/drivers/phy/broadcom/phy-brc
Hi Bjorn,
On 06/20/2017 12:00 AM, Bjorn Andersson wrote:
> On Mon 19 Jun 05:19 PDT 2017, Stanimir Varbanov wrote:
>
>> Hi Olof,
>>
>> On 06/19/2017 02:25 PM, Stanimir Varbanov wrote:
>>> Hi Olof,
>>>
>>> On 06/19/2017 08:35 AM, Olof Johansson wrote:
Hi,
On Thu, Jun 8, 2017 at 8:23
On Thu, Jun 15, 2017 at 09:24:08AM +0530, Vinod Koul wrote:
> On Wed, Jun 14, 2017 at 11:04:39AM +0200, Maxime Ripard wrote:
> > On Wed, Jun 14, 2017 at 02:15:29PM +0530, Vinod Koul wrote:
> > > > SoC info is in compatible, so there's no reason to make it a property.
> > >
> > > that's why it woul
1 - 100 of 1130 matches
Mail list logo
