4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Fabio Estevam
commit 0f933328f018c118ded2035f12068bbdfdef399d upstream.
According to the eLCDIF initialization steps listed in the MX6SX
Reference Manual the eLCDIF block reset is mandatory.
On Monday 19 June 2017 18:13:13 mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Pali Rohár [mailto:pali.ro...@gmail.com]
> > Sent: Monday, June 19, 2017 11:08 AM
> > To: Andy Lutomirski
> > Cc: platform-driver-...@vger.kernel.org; Andy Shevchenko
> > ; Andy Lutomirski
>
> This is identical to the patch [0], that I send 3 months
> ago and got zero feedback from I2C maintainers.
I2C has not enough reviewers, this is a known issue. Pointing it out
alone does not really help. You could have reviewed your own patch;
after 3 months, one sometimes sees issues not notic
> > 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-stopper, or am I wrong?
>
> I wo
Hi Magnus,
On 15/06/17 11:29, Magnus Damm wrote:
> iommu/ipmmu-vmsa: 32-bit ARM update
>
> [PATCH 01/04] iommu/ipmmu-vmsa: Use iommu_device_register()/unregister()
> [PATCH 02/04] iommu/ipmmu-vmsa: Consistent ->of_xlate() handling
> [PATCH 03/04] iommu/ipmmu-vmsa: Use fwspec on both 32 and 64-bit
The patch
ASoC: Intel: bxt: Move codec sysclk config to codec_init function
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: stm32: change configuration flag
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus du
On Mon, Jun 19, 2017 at 9:19 AM, Pali Rohár wrote:
> On Monday 19 June 2017 18:13:13 mario.limoncie...@dell.com wrote:
>> > -Original Message-
>> > From: Pali Rohár [mailto:pali.ro...@gmail.com]
>> > Sent: Monday, June 19, 2017 11:08 AM
>> > To: Andy Lutomirski
>> > Cc: platform-driver-..
The patch
ASoC: da7219: Fix HP detection procedure for all MCLK frequencies
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Wed, Jun 14, 2017 at 01:23:29PM -0700, Paul E. McKenney wrote:
> On Wed, Jun 14, 2017 at 04:33:22PM +0200, Andrea Parri wrote:
> > On Tue, Jun 13, 2017 at 09:33:17PM -0700, Paul E. McKenney wrote:
> > > On Wed, Jun 14, 2017 at 04:54:04AM +0200, Andrea Parri wrote:
> > > > On Mon, Jun 12, 2017 at
+++ Corentin Labbe [06/06/17 14:17 +0200]:
This patch just swap del_usage_link() before add_usage_link().
Signed-off-by: Corentin Labbe
Could you combine this with the 2nd patch? By itself this patch
doesn't tell us much. Additionally, could you explain in the changelog
(of the 2nd patch) why
On Wed, Jun 14, 2017 at 11:43:24AM +0100, Luis Oliveira wrote:
> - Definitions were added to core library
> - A example was added to designware-core.txt Documentation that shows
> how the slave can be setup using DTS
>
> SLAVE related definitions were added to the core of the controller.
>
> Si
On Wed, Jun 14, 2017 at 11:43:23AM +0100, Luis Oliveira wrote:
> - The functions related to I2C master mode of operation were transformed
> in a single driver.
> - Common definitions were moved to i2c-designware-core.h
> - The i2c-designware-core is now only a library file, the functions
> asso
On Wed, Jun 14, 2017 at 11:43:22AM +0100, Luis Oliveira wrote:
> - Factor out all _master() part of code from i2c-designware-core
> and i2c-designware-platdrv to separate functions.
> - Standardize all code related with MASTER mode.
> - I have to take off DW_IC_INTR_TX_EMPTY from DW_IC_INTR_DEFAU
On 15/06/17 11:29, Magnus Damm wrote:
> From: Magnus Damm
>
> Extend the driver to make use of iommu_device_register()/unregister()
> functions together with iommu_device_set_ops() and iommu_set_fwnode().
>
> These used to be part of the earlier posted 64-bit ARM (r8a7795) series but
> it turns
On 2017-06-19 18:14:52 [+0200], Mike Galbraith wrote:
>
> BTW back, I reran virgin 4.9-rt21 on desktop box while off doing the
> have something resembling a life thing, and it did not stall in 50
> iterations of performance/run.sh (bloody fickle thing). Hohum, take it
> for whatever you think it'
On Wed, Jun 14, 2017 at 11:43:21AM +0100, Luis Oliveira wrote:
> The purpose of this commit is to fix some comments and styling in the
> existing code due to the need of reuse this code. What is being made
> here is:
>
> - Sorted the headers files
> - Corrected some comments style (capital letters
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->savestate is true. And that should always be false for futex.
> >
> >
Although header is included only once but still having an include guard
is a good practice. To avoid confusion, add SoC prefix to existing
Exynos5433 header include guard.
Signed-off-by: Krzysztof Kozlowski
---
include/video/exynos5433_decon.h | 6 +++---
include/video/exynos7_decon.h| 5 ++
The DECON headers contain only defines for registers. There are no
other drivers using them so this should be put locally to the Exynos DRM
driver. Keeping headers local helps managing the code.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
---
drivers/gpu/drm/exynos/exyno
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 memory regardless of the container.
What the hell? __user i
There is nothing in the IP that prevents us from enabling TSO for IPv6.
Before patch:
ftp fe80::2aa:bbff:fecc:1336%eth0
ftp> get /dev/zero
882512708 bytes received in 00:14 (56.11 MiB/s)
After patch:
ftp fe80::2aa:bbff:fecc:1336%eth0
ftp> get /dev/zero
1203326784 bytes received in 00:12 (94.52 Mi
Perf script can report the dso for "addr" and "ip" fields.
This adds the same support for the "brstack" and "brstacksym" fields.
This can be helpful for AutoFDO: we can ignore LBR entries unless the
source and target address are both in the target module we are about to
build.
I built a small test
On Mon, Jun 19, 2017 at 11:17:41AM +0100, Mark Brown wrote:
> On Sat, Jun 17, 2017 at 11:30:12PM +0200, Michał Mirosław wrote:
> > Extend regulator's info line with enabled/disabled status.
> Why is the use count not enough information here?
Regulators can be enabled without any users, because of
Hi Masahiro,
El Mon, Jun 19, 2017 at 11:00:42AM +0900 Masahiro Yamada ha dit:
> Sorry, the code I suggested introduced a slight behavior change.
>
> With this patch, cc-option adds a space before the returned option.
>
>
> Please see line 46 of arch/sh/Makefile.
>
> ifeq ($(cflags-y),)
>
>
The idea here is to make AutoFDO easier in cloud environment with ASLR.
It's easiest to show how this is useful by example. I built a small test
akin to "while(1) { do_nothing(); }" where the do_nothing function is
loaded from a dso:
~/src/burncpu$ cat burncpu.cpp
#include
int main() {
> Good catch. Let me add a disclaimer here and state that this example is
> definitely contrived as I was trying to minimize its size. Applying
> shadow variables to a more real life use case would drag in a bunch of
> "changed" function dependencies. I didn't want to work around those
> with a
From: Colin Ian King
The comparison of main_rate < 0 has no effect because main_rate is
an unsigned int. Make it signed so that any -ve error returns from the
call to rsnd_clk_query can be detected.
Detected by CoverityScan, CID#1446152 ("Unsigned compared against 0")
Fixes: ef4cf5d6a143e0 ("AS
On Mon, 2017-06-19 at 18:27 +0200, Sebastian Andrzej Siewior wrote:
> On 2017-06-19 18:14:52 [+0200], Mike Galbraith wrote:
> >
> > BTW back, I reran virgin 4.9-rt21 on desktop box while off doing the
> > have something resembling a life thing, and it did not stall in 50
> > iterations of performa
On Fri, Jun 16, 2017 at 03:57:32PM +0200, olivier moysan wrote:
> Add SPDIFRX support to STM32.
This doesn't apply against current code, please check and resend. Looks
good code wise.
signature.asc
Description: PGP signature
On Mon, Jun 19, 2017 at 06:41:34PM +0200, Michał Mirosław wrote:
> On Mon, Jun 19, 2017 at 11:17:41AM +0100, Mark Brown wrote:
> > On Sat, Jun 17, 2017 at 11:30:12PM +0200, Michał Mirosław wrote:
> > > Extend regulator's info line with enabled/disabled status.
> > Why is the use count not enough in
v3: Fix arch specific implementations
Signed-off-by: Thomas Meyer
---
arch/mips/kernel/module.c | 3 ++-
arch/mips/kernel/traps.c | 3 ++-
arch/sh/mm/extable_64.c | 34 ++
arch/sparc/mm/extable.c | 28 ++--
include/linux/extable.h
This patch fixes the checkpatch.pl warnings on the driver
file.
Signed-off-by: Aravind Thokala
---
drivers/spi/spi-bcm63xx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-bcm63xx.c b/drivers/spi/spi-bcm63xx.c
index 247f71b..84c7356 100644
--- a/drivers/s
On Fri, Jun 16, 2017 at 02:49:58PM +, Ghannam, Yazen wrote:
> The code block being removed here was added in the following commit to decide
> whether or not to schedule work.
>
> fa92c58 x86, mce: Support memory error recovery for both UCNA and Deferred
> error in machine_check_poll
Are you
Hi David, Rob,
I will address all of Rob's comments below.
Since a part of the patch was applied to 'net-next', would you like me to
send a new patch (based on the applied one), or a 'V2' of this patch ?
Thanks
Arun
On 17-06-18 07:04 AM, Rob Herring wrote:
> On Mon, Jun 12, 2017 at 01:26:00PM -0
> > > I often wonder whether it's really a good idea to even allow the
> > > unloading of patch modules at all. It adds complexity to the livepatch
> > > code. Is it worth it? I don't have an answer but I'd be interested in
> > > other people's opinion.
> >
> > I could imagine a situation when
On Sat, 17 Jun 2017 18:24:25 +0100
Salil Mehta wrote:
> +
> +/* This struct defines the operation on the handle.
> + *
> + * init_ae_dev(): (mandatory)
> + * Get PF configure from pci_dev and initialize PF hardware
> + * uninit_ae_dev()
> + * Disable PF device and release PF resource
> + * re
On Mon, Jun 19, 2017 at 05:47:33PM +0100, Mark Brown wrote:
> On Mon, Jun 19, 2017 at 06:41:34PM +0200, Michał Mirosław wrote:
> > On Mon, Jun 19, 2017 at 11:17:41AM +0100, Mark Brown wrote:
> > > On Sat, Jun 17, 2017 at 11:30:12PM +0200, Michał Mirosław wrote:
> > > > Extend regulator's info line
On Wed, May 24, 2017 at 07:31:06PM +0530, Arvind Yadav wrote:
> clk_prepare_enable() can fail here and we must check its return value.
>
> Signed-off-by: Arvind Yadav
Applied to for-next, thanks!
signature.asc
Description: PGP signature
Remove helper functions from vimc-core and add it in vimc-common to
clean up the core.
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4: None
Changes in v3:
[media] vimc: Move common code from the core
- This is a new patch in the series
Changes in v2: None
---
drive
As all the subdevices in the topology will be initialized in the same
way, to avoid code repetition the vimc_ent_sd_{register, unregister}
helper functions were created
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4: None
Changes in v3:
[media] vimc: common: Add vimc_ent_sd_*
Initialize the test pattern generator on the sensor
Generate a colored bar image instead of a grey one
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4: None
Changes in v3:
[media] vimc: sen: Integrate the tpg on the sensor
- Declare frame_size as a local variable
Allow user space to change the image format as the frame size, the
pixel format, colorspace, quantization, field YCbCr encoding
and the transfer function
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4:
[media] vimc: cap: Support several image formats
- add vimc_colorim
Hi Andrew,
This is v5 of the patchset to update the hugetlb code to support
contiguous hugepages. Previous version of the patchset can be found at
[0].
The main changes in this version are updating Patch 4 and 7 due to
issues highlighted in the previous postings (ltp and build failure).
Please u
Colorimetry value will always be checked in the same way. Adding a
helper macro for that
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4:
[media] vimc: common: Add vimc_colorimetry_clamp
- this is a new patch in the series
Changes in v3: None
Changes in v2: None
---
Implement scaler and integrated with the core
Signed-off-by: Helen Koike
---
Changes in v5:
[media] vimc: sca: Add scaler
- declare vimc_sca_video_ops as static, remove sparse warning
Changes in v4:
[media] vimc: sca: Add scaler
- use vimc_colorimetry_clamp
- replace V4
Declare vimc_sen_video_ops as static, remove warning from sparse tool
Signed-off-by: Helen Koike
---
Changes in v5:
[media] vimc: sen: Declare vimc_sen_video_ops as static
- This is a new patch in the series
Changes in v4: None
Changes in v3: None
Changes in v2: None
---
drivers/med
Implement the debayer filter and integrate it with the core
Signed-off-by: Helen Koike
---
Changes in v5:
[media] vimc: deb: Add debayer filter
- delare vimc_deb_video_ops as static, remove sparse warning
Changes in v4:
[media] vimc: deb: Add debayer filter
- Rebase without [me
From: Steve Capper
We don't need to call huge_ptep_offset as our accessors are already
supplied with the pte_t *. This patch removes those spurious calls.
Cc: David Woods
Signed-off-by: Steve Capper
[ Resolved rebase conflicts due to patch re-ordering ]
Signed-off-by: Punit Agrawal
---
arch/
When speculatively taking references to a hugepage using
page_cache_add_speculative() in gup_huge_pmd(), it is assumed that the
page returned by pmd_page() is the head page. Although normally true,
this assumption doesn't hold when the hugepage comprises of successive
page table entries such as whe
A poisoned or migrated hugepage is stored as a swap entry in the page
tables. On architectures that support hugepages consisting of contiguous
page table entries (such as on arm64) this leads to ambiguity in
determining the page table entry to return in huge_pte_offset() when a
poisoned entry is en
When unmapping a hugepage range, huge_pte_clear() is used to clear the
page table entries that are marked as not present. huge_pte_clear()
internally just ends up calling pte_clear() which does not correctly
deal with hugepages consisting of contiguous page table entries.
Add a size argument to ad
From: Will Deacon
When operating on hugepages with DEBUG_VM enabled, the GUP code checks the
compound head for each tail page prior to calling page_cache_add_speculative.
This is broken, because on the fast-GUP path (where we don't hold any page
table locks) we can be racing with a concurrent inv
On Sat, Jun 17, 2017 at 10:24:31PM +, Levin, Alexander (Sasha Levin) wrote:
> From: Eric Biggers
>
> [ Upstream commit a75467d910135905de60b3af3f11b3693625781e ]
>
> The ubifs encryption ioctls did not work when called by a 32-bit program
> on a 64-bit kernel. Since 'struct fscrypt_policy'
set_huge_pte_at(), an architecture callback to populate hugepage ptes,
does not provide the range of virtual memory that is targeted. This
leads to ambiguity when dealing with swap entries on architectures that
support hugepages consisting of contiguous ptes.
Fix the problem by introducing an over
Using set_pte_at() does not do the right thing when putting down
HWPOISON swap entries for hugepages on architectures that support
contiguous ptes.
Fix this problem by using set_huge_swap_pte_at() which was introduced to
fix exactly this problem.
Signed-off-by: Punit Agrawal
Acked-by: Steve Capp
Hi Bjorn,
Thank you for the feedback.
On Fri, Jun 16, 2017 at 3:57 AM, Bjorn Helgaas wrote:
> Hi Srinath,
>
> On Tue, May 30, 2017 at 02:38:17PM +0530, Srinath Mannam wrote:
>> We found a concurrency issue in NVMe Init when we initialize
>> multiple NVMe connected over PCIe switch.
>>
>> Setup d
From: Steve Capper
As we regularly check for contiguous pte's in the huge accessors, remove
this extra check from find_num_contig.
Cc: David Woods
Signed-off-by: Steve Capper
[ Resolved rebase conflicts due to patch re-ordering ]
Signed-off-by: Punit Agrawal
---
arch/arm64/mm/hugetlbpage.c |
Change the core structure for adding subdevices in the topology.
Instead of calling the specific create function for each subdevice,
inject a child platform_device with the driver's name.
Each type of node in the topology (sensor, capture, debayer, scaler)
will register a platform_driver with the c
Allow user space to change the image format as the frame size, the
media bus pixel format, colorspace, quantization, field YCbCr encoding
and the transfer function
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4:
[media] vimc: sen: Support several image formats
- use vi
Move the vimc_cap_pipeline_s_stream from the vimc-cap.c to vimc-common.c
as this core will be reused by other subdevices to activate the stream
in their directly connected nodes
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4: None
Changes in v3:
[media] vimc: Add vimc_pipeline
All links will be checked in the same way. Adding a helper function for
that
Signed-off-by: Helen Koike
---
Changes in v5: None
Changes in v4:
[media] vimc: common: Add vimc_link_validate
- remove vimc_fmt_pix_to_mbus(), replaced by
v4l2_fill_mbus_format()
- remove EXPOR
On Mon, Jun 19, 2017 at 07:00:05PM +0300, Kirill A. Shutemov wrote:
> On Mon, Jun 19, 2017 at 04:22:29PM +0100, Catalin Marinas wrote:
> > On Thu, Jun 15, 2017 at 05:52:22PM +0300, Kirill A. Shutemov wrote:
> > > We need an atomic way to setup pmd page table entry, avoiding races with
> > > CPU set
On Thu, Jun 15, 2017 at 12:24:35PM -0700, Ricardo Neri wrote:
> OK. This makes sense. Perhaps I can use a couple of #define's to set and
> get the the address and operand sizes in a single u8. This would make
> the code more readable.
Sure but don't get too tangled in defines if it is going to be
Kirill A. Shutemov wrote:
> We need an atomic way to setup pmd page table entry, avoiding races with
> CPU setting dirty/accessed bits. This is required to implement
> pmdp_invalidate() that doesn't loose these bits.
>
> On PAE we have to use cmpxchg8b as we cannot assume what is value of new pm
Unset-KVM and decrement-assignment only when we find the group in our
list. Otherwise we can get out of sync if the user triggers this for
groups that aren't currently on our list.
Signed-off-by: Alex Williamson
Cc: Paolo Bonzini
Cc: Eric Auger
Cc: Alexey Kardashevskiy
Cc: sta...@vger.kernel.
If vfio_iommu_group_notifier() acquires a group reference and that
reference becomes the last reference to the group, then vfio_group_put
introduces a deadlock code path where we're trying to unregister from
the iommu notifier chain from within a callout of that chain. Use a
work_struct to release
Generally we don't know about vfio bus drivers until a device is
added to the vfio-core with vfio_add_group_dev(), this optional
registration with vfio_register_bus_driver() allows vfio-core to
track known drivers. Our current use for this information is to
know whether a driver is vfio compatible
At the point where the kvm-vfio pseudo device wants to release its
vfio group reference, we can't always acquire a new reference to make
that happen. The group can be in a state where we wouldn't allow a
new reference to be added. This new helper function allows a caller
to match a file to a grou
Hook into vfio bus driver register/unregister support.
Signed-off-by: Alex Williamson
Reviewed-by: Eric Auger
Cc: Baptiste Reynal
Cc: Kirti Wankhede
---
drivers/vfio/mdev/vfio_mdev.c | 13 -
drivers/vfio/pci/vfio_pci.c |7 +++
drivers/vfio/platform/vfio
The driver core supports a BUS_NOTIFY_DRIVER_NOT_BOUND notification
sent if a driver fails to bind to a device. Extend IOMMU group
notifications to include a version of this.
Signed-off-by: Alex Williamson
Acked-by: Joerg Roedel
Reviewed-by: Eric Auger
---
drivers/iommu/iommu.c |3 +++
in
v2:
* Added received acks and reviews, thanks!
* Rebased and resolved conflict in patch 2/, dropped reviews due
to changes and added Alexey to cc as spapr code is moved too
* Added stable tag for patches 1-3
* Resolved comment typo Eric noted in patch 1
* Split AMBA out to patches 8 & 9 as
If a device is bound to a non-vfio, non-whitelisted driver while a
group is in use, then the integrity of the group is compromised and
will result in hitting a BUG_ON. This code tries to avoid this case
by mangling driver_override to force a no-match for the driver. The
driver-core will either fo
This allows modules to match struct device.bus to amba_bustype for the
purpose of casting the device to an amba_device with to_amba_device().
Signed-off-by: Alex Williamson
Reported-by: Eric Auger
Cc: Russell King
---
drivers/amba/bus.c |1 +
1 file changed, 1 insertion(+)
diff --git a/dr
On Wed, Jun 14, 2017 at 4:01 PM, Steven Rostedt wrote:
> On Wed, 14 Jun 2017 13:47:17 -0400
> Will Hawkins wrote:
>
>
>> > That's how trace-cmd parses it.
>>
>> In the kernel version that I am running (again, pretty old) I do not
>> have this file. I do, however, have
>
> It may be due to the ker
AMBA also supports driver_override, but amba_bustype was not exported
to be able to identify an amba device.
Signed-off-by: Alex Williamson
---
drivers/vfio/vfio.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
index 20e57fecf652..36f0fcfde
A vendor with a system having more than 128 CPUs occasionally encounters
the following crash during shutdown. This is not an easily reproduceable
event, but the vendor was able to provide the following analysis of the
crash, which exhibits the same footprint each time.
crash> bt
PID: 0 TASK:
Hi Jeremy,
[auto build test ERROR on next-20170619]
[cannot apply to linus/master linux/master v4.12-rc5 v4.12-rc4 v4.12-rc3
v4.12-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jeremy
On Thu, Jun 15, 2017 at 11:33:41AM -0500, Tom Lendacky wrote:
> Changing the signature back reverts to the original way, so this can be
> looked at separate from this patchset then.
Right, the patch which added the volatile thing was this one:
4bf5beef578e ("iommu/amd: Don't put completion-wait
On 19/06/17 10:14, Magnus Damm wrote:
> From: Magnus Damm
>
> Add root device handling to the IPMMU driver by allowing certain
> DT compat strings to enable has_cache_leaf_nodes that in turn will
> support both root devices with interrupts and leaf devices that
> face the actual IPMMU consumer de
This patch removes typedefs from enum _logical_chip_type_t and enum
_clock_type_t and rename them to logical_chip_type_t and clock_type_t
respectively.
Fix checkpatch warning:
WARNING: do not add new typedefs
Signed-off-by: Simran Singhal
---
drivers/staging/sm750fb/ddk750_chip.c | 4 ++--
dri
On 06/19/2017 09:49 AM, Aravind Thokala wrote:
> This patch fixes the checkpatch.pl warnings on the driver
> file.
>
> Signed-off-by: Aravind Thokala
The subject should be spi/bcm63xx: Fix checkpatch warnings to be
consistent with previous submissions done to that file.
With that:
Reviewed-by:
Hi Al,
On Mon, Jun 19, 2017 at 5:08 PM, Al Viro wrote:
> Fixed in vfs.git#ufs-fixes; see commit
> 77e9ce327d9b607cd6e57c0f4524a654dc59c4b1
> there. Not sure if it's worth splitting...
I can confirm that commit fixes the build for m68k.
Let's hope it fixes the build for all other 32-bit platfor
On 06/19/2017 01:17 PM, Tony Camuso wrote:
A vendor with a system having more than 128 CPUs occasionally encounters
the following crash during shutdown. This is not an easily reproduceable
event, but the vendor was able to provide the following analysis of the
crash, which exhibits the same footp
On 18 June 2017 at 07:05, Rob Herring wrote:
> On Tue, Jun 13, 2017 at 03:37:09PM -0700, Markus Mayer wrote:
>> From: Markus Mayer
>>
>> Provide bindings for the Broadcom STB DDR PHY Front End (DPFE).
>>
>> Signed-off-by: Markus Mayer
>> ---
>> .../devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt
On 06/19/2017 08:18 AM, Yury Norov wrote:
> On Mon, Jun 19, 2017 at 02:51:08AM +0300, Yury Norov wrote:
>> Hi Florian,
>>
>> Some questions and thoughts inline.
>>
>> Yury
>>
>> On Fri, Jun 16, 2017 at 05:07:42PM -0700, Florian Fainelli wrote:
>>> Define a generic fncpy() implementation largely bas
This patch on its own doesn't make much sense to me... any chance of
seeing the full series please?
Thanks.
On Mon, Jun 19, 2017 at 11:15:29AM -0600, Alex Williamson wrote:
> This allows modules to match struct device.bus to amba_bustype for the
> purpose of casting the device to an amba_device w
On Mon, 2017-06-19 at 09:24 -0400, Benjamin Coddington wrote:
> Since commit c69899a17ca4 "NFSv4: Update of VFS byte range lock must be
> atomic with the stateid update", NFSv4 has been inserting locks in rpciod
> worker context. The result is that the file_lock's fl_nspid is the
> kworker's pid i
On Mon, Jun 19, 2017 at 10:55:01PM +0800, Greg Kroah-Hartman wrote:
> On Mon, Jun 19, 2017 at 04:48:05PM +0200, Luis R. Rodriguez wrote:
> > On Sat, Jun 17, 2017 at 06:16:35AM +0200, Greg Kroah-Hartman wrote:
> > > On Fri, Jun 16, 2017 at 09:47:21PM +0200, Luis R. Rodriguez wrote:
> > > > Some of t
On 06/19/2017 05:24 AM, Mark Rutland wrote:
> On Fri, Jun 16, 2017 at 05:07:40PM -0700, Florian Fainelli wrote:
>> Hi all,
>
> Hi Florian,
>
>> This patch series makes ARM's fncpy() implementation more generic (dropping
>> the
>> Thumb-specifics) and available in an asm-generic header file.
>>
>
On Mon, Jun 19, 2017 at 07:22:39PM +0200, Geert Uytterhoeven wrote:
> Hi Al,
>
> On Mon, Jun 19, 2017 at 5:08 PM, Al Viro wrote:
> > Fixed in vfs.git#ufs-fixes; see commit
> > 77e9ce327d9b607cd6e57c0f4524a654dc59c4b1
> > there. Not sure if it's worth splitting...
>
> I can confirm that commit
Em Mon, Jun 19, 2017 at 10:55:58AM +0800, Jin Yao escreveu:
> For marking the fused instructions clearly, This patch adds a
> line before the first instruction of pair and joins it with the
> arrow of the jump.
>
> For example, when je is selected in annotate view, the line
> before cmpl is displa
Hi Johannes,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc6 next-20170619]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Johannes-P-hlmann/one-wire-ds1wm-patch
On 16/06/17 15:19, Thomas Petazzoni wrote:
> The Marvell ICU unit is found in the CP110 block of the Marvell Armada
> 7K and 8K SoCs. It collects the wired interrupts of the devices located
> in the CP110 and turns them into SPI interrupts in the GIC located in
> the AP806 side of the SoC, by using
On Mon, Jun 19, 2017 at 06:18:18PM +0300, Yury Norov wrote:
> One else thing I forgot to ask - now you have the generic
> implementation for fncpy(), so do you really need to save arm
> version of it?
This was covered in the review of v1, which took the ARM version
and incorrectly used it as an as
On Mon, Jun 19, 2017 at 06:59:39PM +0200, Michał Mirosław wrote:
> On Mon, Jun 19, 2017 at 05:47:33PM +0100, Mark Brown wrote:
> > We should probably just have always-on be incrementing the use count
> > instead if it's an issue.
> That's another way of tackling the issue. This file is a debuging
Hi Florian,
On 19 June 2017 at 22:51, Florian Fainelli wrote:
> On 06/19/2017 09:49 AM, Aravind Thokala wrote:
>> This patch fixes the checkpatch.pl warnings on the driver
>> file.
>>
>> Signed-off-by: Aravind Thokala
>
> The subject should be spi/bcm63xx: Fix checkpatch warnings to be
> consist
On Mon, Jun 19, 2017 at 11:30:18AM +0800, Kai-Heng Feng wrote:
> On Sat, Jun 17, 2017 at 1:30 AM, Alan Stern wrote:
> > On Sat, 17 Jun 2017, Kai-Heng Feng wrote:
> >
> >> On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng
> >> wrote:
> >> > On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern
> >> > wrote
On Mon, Jun 12, 2017 at 9:40 AM, Geert Uytterhoeven
wrote:
> If you don't mind, I plan to queue this up in the m68k tree for v4.13.
> There are no conflicts with current linux-next.
>
> If you prefer to take this through a signal tree with my
> Acked-by: Geert Uytterhoeven
> please let me know.
>
Hi Hans,
Thanks for reviewing this
On 2017-06-19 08:15 AM, Hans Verkuil wrote:
On 06/14/2017 06:50 AM, Helen Koike wrote:
Add V4L2_CAP_IO_MC to be used in struct v4l2_capability to indicate that
input and output are controlled by the Media Controller instead of V4L2
API.
When this flag is set,
801 - 900 of 1571 matches
Mail list logo
