On Fri 04-12-15 09:53:35, Huang, Ying wrote:
> Mel Gorman writes:
[...]
> > What is the result of the __GFP_HIGH patch to give it access to
> > reserves?
>
> Applied Michal's patch on v4.4-rc3 and tested again, now there is no
> page allocation failure.
I still think this is just a coincidence a
On Mon, Dec 7, 2015 at 5:28 AM, Brian Starkey wrote:
> On Fri, Dec 04, 2015 at 05:15:54PM +, Catalin Marinas wrote:
>>
>> On Fri, Dec 04, 2015 at 08:59:10AM -0800, Dan Williams wrote:
>>>
>>> On Fri, Dec 4, 2015 at 2:50 AM, Catalin Marinas
>>> wrote:
>>> > On Fri, Nov 20, 2015 at 02:20:26PM +
On Monday 07 December 2015 18:10:04 Tomi Valkeinen wrote:
> On 20/11/15 23:47, Arnd Bergmann wrote:
> > The auo_k190x framebuffer driver encloses the power-management
> > functions in #ifdef CONFIG_PM, but the auok190x_suspend/resume
> > functions are only really used when CONFIG_PM_SLEEP is also
>
Hi all,
this patch series introduces support for running Linux on top of Xen
inside a virtual machine with virtio devices (nested virt scenario).
The problem is that Linux virtio drivers use virt_to_phys to get the
guest pseudo-physical addresses to pass to the backend, which doesn't
work as expec
On Sun, Dec 06, 2015 at 11:51:41AM -0800, Guenter Roeck wrote:
> The watchdog character device s currently created in watchdog_dev.c,
> and the watchdog device in watchdog_core.c. This results in
> cross-dependencies, as the device creation needs to know the watchdog
> character device number.
>
>
On 07/12/15 18:16, Arnd Bergmann wrote:
> On Monday 07 December 2015 18:10:04 Tomi Valkeinen wrote:
>> On 20/11/15 23:47, Arnd Bergmann wrote:
>>> The auo_k190x framebuffer driver encloses the power-management
>>> functions in #ifdef CONFIG_PM, but the auok190x_suspend/resume
>>> functions are on
When running on Xen inside as virtual machine (nested virt scenario),
addresses need to be translated from phys to machine to get the actual
guest pseudo-physical address.
Introduce a new pair of functions, cpu_to_virtio_addr and
virtio_addr_to_cpu, which call the appriopriate __virtio64_to_cpu an
On Fri, Dec 04, 2015 at 03:53:13AM -0800, tip-bot for Hiroshi Shimamoto wrote:
> Commit-ID: 2541117b0cf79977fa11a0d6e17d61010677bd7b
> Gitweb: http://git.kernel.org/tip/2541117b0cf79977fa11a0d6e17d61010677bd7b
> Author: Hiroshi Shimamoto
> AuthorDate: Thu, 19 Nov 2015 16:47:28 +0100
> Com
On Sat 05-12-15 10:55:42, Geliang Tang wrote:
> On Thu, Dec 03, 2015 at 05:27:18PM +0100, Michal Hocko wrote:
> > On Thu 03-12-15 22:16:55, Geliang Tang wrote:
> > > To make the intention clearer, use list_{first,next}_entry instead
> > > of list_entry.
> >
> > Does this really help readability? T
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Patrick Doyle
commit 5fcf8d1a0e84792b2bc44922c5d833dab96a9c1e upstream.
fncpy() requires that the source and the destination are both 8-byte
aligned.
Signed-off-by: Patrick Doyle
Signed-off-b
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Hauke Mehrtens
commit 4e7d30dba493b60a80e9b590add1b4402265cc83 upstream.
This adds a basic implementation of clk_round_rate()
The clk_round_rate() function is called by multiple drivers and
sub
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit 371f0f085f629fc0f66695f572373ca4445a67ad upstream.
dma_mmap() function in IOMMU-based dma-mapping implementation lacked
a check for valid range of mmap parameters (offse
This is the start of the stable review cycle for the 4.1.14 release.
There are 95 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Dec 9 14:27:02 UTC 2015.
Anything receive
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit 7e31210349e9e03a9a4dff31ab5f2bc83e8e84f5 upstream.
IOMMU-based dma_mmap() implementation lacked proper support for offset
parameter used in mmap call (it always assumed
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Ujfalusi
commit 696d8b70c09dd421c4d037fab04341e5b30585cf upstream.
In case when the interrupt happened for the second eDMA the channel
number was incorrectly passed to the client driver.
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Osipenko
commit e77b675f8786f38d40fc1562e1275875daf67fef upstream.
Commit 72daceb9a10a ("net: rfkill: gpio: Add default GPIO driver mappings
for ACPI") removed possibility to request GPI
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Holger Busse
commit d1a9c24ad16ab2b26f1574bc3f2c165a7beff5df upstream.
Correcting the dma declaration for i2c1 dma.
Signed-off-by: Holger Busse
Signed-off-by: Nicolas Ferre
Fixes: 4cc7cdf35c
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Phil Reid
[ Upstream commit e6dbe1eb2db0d7a14991c06278dd3030c45fb825 ]
priv->hwts_*_en indicate if timestamping is enabled/disabled at run
time. But priv->dma_cap.time_stamp and priv->dma_cap
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Sasha Levin
[ Upstream commit 74e98eb085889b0d2d4908f59f6e00026063014f ]
There was no verification that an underlying transport exists when creating
a connection, this would cause dereferencing
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
[ Upstream commit 48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 ]
virtio declares support for NETIF_F_FRAGLIST, but assumes
that there are at most MAX_SKB_FRAGS + 2 fragments which isn't
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
[ Upstream commit 1acea4f6ce1b1c0941438aca75dd2e5c6b09db60 ]
We can't rely on PPPOX_ZOMBIE to decide whether to clear po->pppoe_dev.
PPPOX_ZOMBIE can be set by pppoe_disc_rcv()
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Carol L Soto
[ Upstream commit c02b05011fadf8e409e41910217ca689f2fc9d91 ]
When doing memcpy/memset of EQEs, we should use sizeof struct
mlx4_eqe as the base size and not caps.eqe_size which cou
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Sowmini Varadhan
[ Upstream commit 8ce675ff39b9958d1c10f86cf58e357efaafc856 ]
Either of pskb_pull() or pskb_trim() may fail under low memory conditions.
If rds_tcp_data_recv() ignores such fail
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
[ Upstream commit f23d538bc24a83c16127c2eb82c9cf1adc2b5149 ]
We don't have fraglist support in TAP_FEATURES. This will lead
software segmentation of gro skb with frag list. Fixes by
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7e3b6e7423d5f994257c1de88e06b509673fdbcf ]
gre_gso_segment() chokes if SIT frames were aggregated by GRO engine.
Fixes: 61c1db7fae21e ("ipv6: sit: add GSO/TSO su
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Paul Maloy
[ Upstream commit 45c8b7b175ceb2d542e0fe15247377bf3bce29ec ]
The current code for message reassembly is erroneously assuming that
the the first arriving fragment buffer always is
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sasha Levin
[ Upstream commit 74e98eb085889b0d2d4908f59f6e00026063014f ]
There was no verification that an underlying transport exists when creating
a connection, this would cause dereferencin
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
[ Upstream commit 48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 ]
virtio declares support for NETIF_F_FRAGLIST, but assumes
that there are at most MAX_SKB_FRAGS + 2 fragments which isn't
On 17/11/15 22:32, Robert Jarzmik wrote:
> This patch brings a first support of pxa framebuffer devices to a
> devicetree pxa platform, as was before platform data.
>
> There are restrictions with this port, the biggest one being the lack of
> support of smart panels. Moreover the conversion does
On Mon, Dec 07, 2015 at 01:32:30PM +0100, Geert Uytterhoeven wrote:
> Hi Sudip,
>
> On Mon, Dec 7, 2015 at 1:20 PM, Sudip Mukherjee
> wrote:
> > We are having build failure with linux-next for sparc allmodconfig with
> > the error messages:
> >
> > undefined reference to 'of_io_request_and_map'
>
On Mon, Dec 07, 2015 at 09:58:14AM -0500, Mike Snitzer wrote:
> Great. Moving forward it'd be awesome if you could work to get your
> verity FEC support regression tests into cryptsetup's tests.
Sure. These tests would basically involve generating a valid disk
image, corrupting it up to the theor
On 12/04/2015 10:50 PM, Michael Kerrisk (man-pages) wrote:
> On 12/04/2015 02:15 AM, Dave Hansen wrote:
>> From: Dave Hansen
>>
>> mprotect_key() is just like mprotect, except it also takes a
>> protection key as an argument. On systems that do not support
>> protection keys, it still works, but
Hi Dave,
On Mon, Aug 31, 2015 at 3:33 PM, Gavin Guo wrote:
> On Sun, Aug 30, 2015 at 6:31 AM, Dave Chinner wrote:
>> On Fri, Aug 28, 2015 at 08:54:04PM +0800, Gavin Guo wrote:
>>> On Wed, Jul 8, 2015 at 7:37 AM, Dave Chinner wrote:
>>> > On Tue, Jul 07, 2015 at 05:29:43PM +0800, Gavin Guo wrote
On Mon, Dec 07, 2015 at 08:19:27AM -0800, Dan Williams wrote:
> On Mon, Dec 7, 2015 at 5:28 AM, Brian Starkey wrote:
> > On Fri, Dec 04, 2015 at 05:15:54PM +, Catalin Marinas wrote:
> >>
> >> On Fri, Dec 04, 2015 at 08:59:10AM -0800, Dan Williams wrote:
> >>>
> >>> On Fri, Dec 4, 2015 at 2:50
Hi Damien,
On 12/07/2015 08:15 AM, Damien Riegel wrote:
On Sun, Dec 06, 2015 at 11:51:41AM -0800, Guenter Roeck wrote:
The watchdog character device s currently created in watchdog_dev.c,
and the watchdog device in watchdog_core.c. This results in
cross-dependencies, as the device creation need
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Monday, December 07, 2015 3:56 AM
> To: Deucher, Alexander; Koenig, Christian
> Cc: lkml
> Subject: radeon -Wmaybe-uninitialized crap
>
> Hi guys,
>
> this just started appearing when building -rc4. Got fixes y
On 12/05/2015 03:37 AM, Andrew Morton wrote:
> On Thu, 3 Dec 2015 18:50:04 +0300 Andrey Ryabinin
> wrote:
>
>> UBSAN is run-time undefined behaviour checker. It uses compile-time
>> instrumentation to catch undefined behavior (UB). Compiler inserts code
>> that perform certain kinds of checks be
From: Michal Marek
> Sent: 04 December 2015 15:26
> Otherwise make tags can't parse them:
>
> ctags: Warning: arch/ia64/kernel/smp.c:60: null expansion of name pattern "\1"
...
Seems to me you need to fix ctags.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-ker
On 2015-12-07 17:33, David Laight wrote:
> From: Michal Marek
>> Sent: 04 December 2015 15:26
>> Otherwise make tags can't parse them:
>>
>> ctags: Warning: arch/ia64/kernel/smp.c:60: null expansion of name pattern
>> "\1"
> ...
>
> Seems to me you need to fix ctags.
I'm sure the maintainers of
On Mon, Dec 7, 2015 at 3:45 AM, Jani Nikula wrote:
> On Mon, 07 Dec 2015, Archit Taneja wrote:
>> Hi,
>>
>> On 11/30/2015 06:15 PM, kbuild test robot wrote:
>>> Hi Archit,
>>>
>>> [auto build test ERROR on: v4.4-rc3]
>>> [also build test ERROR on: next-20151127]
>>>
>>> url:
>>> https://githu
On Sun, Dec 6, 2015 at 2:49 PM, Saurabh Sengar wrote:
> in case of failed to get iova, function was returning without releasing
> the mutex. Added it.
>
> Signed-off-by: Saurabh Sengar
Reviewed-by: Rob Clark
> ---
> drivers/gpu/drm/msm/dsi/dsi_host.c | 2 +-
> 1 file changed, 1 insertion(+),
On Mon, Dec 7, 2015 at 6:20 AM, Sudip Mukherjee
wrote:
> We are having build failure with linux-next for sparc allmodconfig with
> the error messages:
Please come up with a subject more specific than applicable to any
build failure.
> undefined reference to 'of_io_request_and_map'
Specifying on
A DGTFX virus has been detected in your folders. Your email
account has to be upgraded to our new Secured DGTFX anti-virus
2015 version to prevent damages to our Webmail log and your important
files. re-validate your mailbox please clink the link below or copy and
past it in your broswer to avoid s
When an interface is brought up which was previously suspended (via
runtime PM), it would hang. This happens because napi_disable is called
before napi_enable.
Solve this by avoiding napi_disable before the device is fully up.
While at it, remove WORK_ENABLE check from rtl8152_open (introduced wi
On 05/12/15 08:43, Vinod Koul wrote:
> On Mon, Nov 23, 2015 at 02:22:04PM +, Damien Horsley wrote:
>> From: "Damien.Horsley"
>>
>> Use of the CANCEL bit in mdc_terminate_all creates an
>> additional 'command done' to appear in the registers (in
>> addition to an interrupt).
>>
>> In addition,
On Fri, Dec 04, 2015 at 09:34:57AM -0800, Ray Jui wrote:
> This patch series adds support for the iProc PAXC interface and support for
> event queue based MSI, integrated in the iProc PCIe core
>
> This patch series is based on Linux v4.4-rc1 and is avaliable here:
> https://github.com/Broadcom/cy
On Mon, 2015-12-07 at 17:53 +0100, Michal Marek wrote:
> On 2015-12-07 17:33, David Laight wrote:
> > From: Michal Marek
> > > Sent: 04 December 2015 15:26
> > > Otherwise make tags can't parse them:
> > >
> > > ctags: Warning: arch/ia64/kernel/smp.c:60: null expansion of name pattern
> > > "\1"
On Mon, Dec 07, 2015 at 04:15:22PM +, Deucher, Alexander wrote:
> Odd. Nothing related to these variables has changed in years.
Odd indeed. Building that same config on two other boxes doesn't trip
those up so it must be something gcc-related on that particular box.
Hmmm.
--
Regards/Gruss,
On 29/11/15 12:03, Bharat Kumar Gogada wrote:
> Adding PCIe Root Port driver for Xilinx PCIe NWL bridge IP.
>
> Signed-off-by: Bharat Kumar Gogada
> Signed-off-by: Ravi Kiran Gummaluri
> Acked-by: Rob Herring
I don't have much to add to this, so FWIW:
Reviewed-by: Marc Zyngier
M.
--
On Mon, Dec 7, 2015 at 7:40 AM, Lan, Tianyu wrote:
> On 12/5/2015 1:07 AM, Alexander Duyck wrote:
>>>
>>>
>>> We still need to support Windows guest for migration and this is why our
>>> patches keep all changes in the driver since it's impossible to change
>>> Windows kernel.
>>
>>
>> That is a p
On 12/07/2015 07:04 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.94 release.
> There are 31 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On 12/07/2015 07:26 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.58 release.
> There are 37 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On 12/07/2015 07:34 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.14 release.
> There are 95 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On 12/07/2015 07:54 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.2.7 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On 12/07/2015 08:00 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.3.1 release.
> There are 125 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On 2015-12-07 18:04, Joe Perches wrote:
> On Mon, 2015-12-07 at 17:53 +0100, Michal Marek wrote:
>> On 2015-12-07 17:33, David Laight wrote:
>>> From: Michal Marek
Sent: 04 December 2015 15:26
Otherwise make tags can't parse them:
ctags: Warning: arch/ia64/kernel/smp.c:60: null
Greg Kroah-Hartman writes:
> 4.1-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
>
> [ Upstream commit 0db65fcfcded76fe4f74e3ca9f4e2baf67b683ef ]
>
> New device IDs shamelessly lifted from the vendor driver.
>
Hi Arnd,
On mer., déc. 02 2015, Arnd Bergmann wrote:
> I've updated the series slightly to leave out the last two patches for
> mach-dove. I think the MULTI_IRQ_HANDLER and SPARSE_IRQ use is useful
> to have for all three platforms for consistency, and the watchdog change
> is required to get
On 12/07/2015 01:31 PM, Thierry Reding wrote:
> On Mon, Dec 07, 2015 at 12:46:52PM +0100, Daniel Vetter wrote:
>> On Mon, Dec 07, 2015 at 11:53:01AM +0200, Jani Nikula wrote:
>>> On Mon, 07 Dec 2015, Daniel Vetter wrote:
On Sun, Dec 06, 2015 at 11:16:32AM +0100, Nicolas Iooss wrote:
> On
On 12/05/2015 12:21 PM, Jonathan Cameron wrote:
On 02/12/15 19:57, Andrew F. Davis wrote:
Add driver for the TI AFE4404 heart rate monitor and pulse oximeter.
This device detects reflected LED light fluctuations and presents an ADC
value to the user space for further signal processing.
Datashee
Hi Babu,
On Thu, Dec 03, 2015 at 12:25:19PM -0800, Babu Moger wrote:
> Reading or Writing of PCI VPD data causes system panic.
> We saw this problem by running "lspci -vvv" in the beginning.
> However this can be easily reproduced by running
> cat /sys/bus/devices/XX../vpd
What sort of panic is
- Original Message -
> From: "Peter Zijlstra"
> To: "Jan Stancek"
> Cc: linux...@kvack.org, linux-kernel@vger.kernel.org, "Oleg Nesterov"
>
> Sent: Monday, 7 December, 2015 5:07:15 PM
> Subject: Re: kernel BUG at mm/filemap.c:238! (4.4.0-rc4)
>
> On Mon, Dec 07, 2015 at 04:44:59PM
On 03/12/15 13:35, Stanimir Varbanov wrote:
Hi,
Here is v4, comments from Bjorn and Rob have been addressed.
The previous version can be found at [1].
regards,
Stan
[1] https://lkml.org/lkml/2015/11/23/114
Stanimir Varbanov (5):
PCI: designware: add memory barrier after enabling region
On Mon, Dec 07, 2015 at 10:59:15AM +0100, Wilck, Martin wrote:
> > IS_ERR should address the oops though??
>
> No, see my answer to Jarkko in the other part of the thread.
I'm confused, is there an oops that still need to be fixed?
> As reported before, with "force=1", I get the error message:
>
+Linus W
On Fri, Dec 04, 2015 at 05:31:13PM +, Martyn Welch wrote:
> This patch adds documentation for the gpio-switch binding. This binding
> provides a mechanism to bind named links to gpio, with the primary
> purpose of enabling standardised access to switches that might be standard
> acros
On Mon, Dec 07, 2015 at 09:12:08AM -0800, Alexander Duyck wrote:
> On Mon, Dec 7, 2015 at 7:40 AM, Lan, Tianyu wrote:
> > On 12/5/2015 1:07 AM, Alexander Duyck wrote:
> >>>
> >>>
> >>> We still need to support Windows guest for migration and this is why our
> >>> patches keep all changes in the dr
On Fri, Nov 27, 2015 at 08:15:52PM +0100, Thomas Gleixner wrote:
> Will,
Hi Thomas,
Thanks for the comprehensive review. Comments inline.
> On Fri, 27 Nov 2015, Will Deacon wrote:
>
> > On multi-cluster platforms, a per-cpu interrupt may actually be wired on
> > a per-cluster basis, meaning tha
Dear Mr. John and Mr. Thomas,
Greetings of the day !!
This is Aniroop Mathur working on sensor kernel drivers for last 3 years.
Recently, In my driver code, I have been changing msleep to usleep_range.
But I got stuck at one point and could not find proper answer on internet.
Could you please help
On 12/7/2015 10:51 AM, Rhyland Klein wrote:
> On 12/4/2015 12:04 PM, Jon Hunter wrote:
>> Sparse reports the following warnings for structures and functions that
>> should be declared static:
>>
>> drivers/clk/tegra/clk-tegra-super-gen4.c:70:35: warning: symbol
>> 'tegra_super_gen_info_gen4' was n
On Mon, Dec 7, 2015 at 5:11 PM, Jens Axboe wrote:
> On Sun, Dec 06 2015, Matias Bjørling wrote:
>> Hi Jens,
>>
>> A couple more fixes for LightNVM.
>>
>> The first three patches are fixed from Tao on rrpc and gennvm. The next
>> five patches are small fixes and refactoring to prepare for system
>>
Kalle Valo writes:
> Stephen Rothwell writes:
>
>> Today's linux-next merge of the wireless-drivers-next tree got a
>> conflict in:
>>
>> drivers/net/wireless/ath/ath10k/pci.c
>>
>> between commit:
>>
>> 6419fdbb6f90 ("ath10k: poll HTT send completion when CE 5 is unused")
>>
>> from Linus'
Dear Mr. John and Mr. Thomas,
Greetings of the day !!
This is Aniroop Mathur working on sensor kernel drivers for last 3 years.
Recently, In my driver code, I have been changing msleep to usleep_range.
But I got stuck at one point and could not find proper answer on internet.
Could you please help
blkdev_open() doesn't release the bdev, it attached to a given
inode, if blkdev_get() fails (e.g, due to absence of a device).
This can cause kernel crashes when the original filesystem
tries to flush the data during evict_inode.
This can be triggered easily with virtio-9p fs using the following
s
Hi Sudip,
Sudip Mukherjee writes:
> We were dereferencing cmd first and checking for NULL later. Lets first
> check for NULL.
>
> Signed-off-by: Sudip Mukherjee
I noticed that your name in git log is not your full name:
commit 0a38c8e1b592c16d959da456f425053e323a5153
Author: sudip
Date: Tu
On 12/07/2015 05:31 PM, Sami Tolvanen wrote:
> On Mon, Dec 07, 2015 at 09:58:14AM -0500, Mike Snitzer wrote:
>> Great. Moving forward it'd be awesome if you could work to get your
>> verity FEC support regression tests into cryptsetup's tests.
>
> Sure. These tests would basically involve generat
On 12/07/15 07:25, Steven Rostedt wrote:
> Hi,
>
> The attached config doesn't build on 4.2.6, but changing it to the
> following:
>
> VIDEO_V4L2_SUBDEV_API n -> y
> +V4L2_FLASH_LED_CLASS n
>
> does build.
>
> Sorry, I lost the build error (currently building now with a good
> config), But it'
On Mon, Dec 7, 2015 at 5:30 PM, Sudip Mukherjee
wrote:
>> > --- a/include/linux/of_address.h
>> > +++ b/include/linux/of_address.h
>> > @@ -112,8 +112,6 @@ static inline bool of_dma_is_coherent(struct
>> > device_node *np)
>> > extern int of_address_to_resource(struct device_node *dev, int index
On Sun, Dec 06, 2015 at 08:45:40PM -0600, Rob Herring wrote:
> On Fri, Dec 4, 2015 at 11:19 PM, Brian Norris
> wrote:
> > drivers/of/of_mtd.c| 33 +
>
> BTW, this file should be moved to drivers/mtd/ at some point.
How about s/at some point/now/ ? I ca
Hi Stefan,
On Sun, Dec 06, 2015 at 10:16:25PM +0100, Stefan Wahren wrote:
> Hi Remi,
>
> please send this patch to devicet...@vger.kernel.org.
Ok, just to be sure I understand the process here. I should resend a new
version of the whole patchset including the devicetree mailing list as
recipent.
On 2015-12-06 15:52, Randy Dunlap wrote:
On 12/06/15 07:30, Jonathan Corbet wrote:
On Sun, 6 Dec 2015 01:09:39 -0500
Sanidhya Solanki wrote:
Patch included below. As an aside, thank you for the excellent work on
the books and other documentation.
Thanks for the nice comments. Future praise
Hi,
This patch series adds generic cpufreq-dt driver support for
Exynos542x/5800 (using the new CPU clock type which allows it).
It has been tested on Exynos5422 based ODROID-XU3 Lite board.
Depends on:
- next-20151124 branch of linux-next kernel tree
Changes since v3:
- switched to using cpufr
From: Thomas Abraham
With the addition of the new Samsung specific cpu-clock type, the
arm clock can be represented as a cpu-clock type. Add the CPU clock
configuration data and instantiate the CPU clock type for Exynos5420.
Changes by Bartlomiej:
- split Exynos5420 support from the original pat
Add cluster regulator supply properties as a preparation to
adding generic cpufreq-dt driver support for Exynos542x and
Exynos5800 based boards.
Cc: Kukjin Kim
Cc: Doug Anderson
Cc: Javier Martinez Canillas
Cc: Andreas Faerber
Cc: Sachin Kamat
Cc: Thomas Abraham
Signed-off-by: Bartlomiej Zol
Fix cpu clock configuration data for Exynos5422/5800 SoCs
(they use higher PCLK_DBG divider values than Exynos5420 and
support additional frequencies).
Based on Hardkernel's kernel for ODROID-XU3 board.
Cc: Tomasz Figa
Cc: Mike Turquette
Cc: Javier Martinez Canillas
Cc: Thomas Abraham
Acked-b
From: Thomas Abraham
The new CPU clock type allows the use of cpufreq-dt driver
for Exynos5420.
Changes by Bartlomiej:
- split Exynos5420 support from the original patch
- disable cpufreq if big.LITTLE switcher support is enabled
- switch to using cpufreq-dt driver
Cc: Tomasz Figa
Cc: Kukjin K
From: Thomas Abraham
For Exynos5420 platforms, add CPU operating points for
migrating from Exynos specific cpufreq driver to using
generic cpufreq driver.
Changes by Bartlomiej:
- split Exynos5420 support from the original patch
Changes by Ben Gamari:
- Port to operating-points-v2
Cc: Kukjin K
From: Ben Gamari
The Exynos 5422 is identical to the 5800 except for the fact that it
boots from the A7 cores. Consequently, the core numbering is different:
cores 0-3 are A7s whereas 4-7 are A15s.
We can reuse the device tree of the 5800 for the 5422 but we must take
care to override the OPP ta
Fix CPU operating points for Exynos5800 (it use different
voltages than Exynos5420 and supports additional frequencies).
However don't use 2000MHz & 1900MHz OPPs (for A15 cores) and
1400MHz OPP (for A7 cores) for now as they are not available
on all boards.
Based on Hardkernel's kernel for ODROID-
From: Thomas Abraham
The new CPU clock type allows the use of generic cpufreq-dt driver
for Exynos5422/5800.
Changes by Bartlomiej:
- split Exynos5800 support from the original patch
- disable cpufreq if big.LITTLE switcher support is enabled
- switch to using cpufreq-dt driver
Cc: Tomasz Figa
On 12/07/2015 03:13 AM, Arnd Bergmann wrote:
> On Monday 07 December 2015 10:26:16 Jon Hunter wrote:
>>
>> diff --git a/arch/arm64/mm/mmap.c b/arch/arm64/mm/mmap.c
>> index af461b935137..e59a75a308bc 100644
>> --- a/arch/arm64/mm/mmap.c
>> +++ b/arch/arm64/mm/mmap.c
>> @@ -51,7 +51,7 @@ unsigned lo
Hi,
any comments/update on this? Thanks
Gustavo
2015-11-26 Gustavo Padovan :
> From: Gustavo Padovan
>
> - remove CONFIG_SW_SYNC_USER, it is used only for testing/debugging and
>should not be upstreamed.
> - port CONFIG_SW_SYNC_USER tests interfaces to use debugfs somehow
> - p
Will,
On Mon, 7 Dec 2015, Will Deacon wrote:
> On Fri, Nov 27, 2015 at 08:15:52PM +0100, Thomas Gleixner wrote:
> >Now you want to use the same Linux irq number for the local timer
> >or whatever on all CPUs independent of the cluster, right?
> >
> >So the per cpu timer interrupt is r
On Mon, 7 Dec 2015, Aniroop Mathur wrote:
> As in the kernel documentation, it is mentioned to use msleep for
> 10ms+ delay, I am confused whether there would be any disadvantage in
> using usleep_range for higher delays values because normally drivers
> have variety of delays used (2, 10, 20, 40,
From: Sunil Goutham
Date: Mon, 7 Dec 2015 10:30:31 +0530
> This patch series contains contains couple of cleanup patches.
Series applied to net-next, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More maj
Am 07.12.2015 um 13:25 schrieb Paul Bolle:
>>> Otherwise we'd still be freeing memory
>>> managed through reference counting.
>>
>> Now I#m confused. I thought by following Peter's suggestion to put the
>> kfree() in the release method we'd avoid just that.
>
> Apparently it does, because I can't
On Mon, Dec 7, 2015 at 9:39 AM, Michael S. Tsirkin wrote:
> On Mon, Dec 07, 2015 at 09:12:08AM -0800, Alexander Duyck wrote:
>> On Mon, Dec 7, 2015 at 7:40 AM, Lan, Tianyu wrote:
>> > On 12/5/2015 1:07 AM, Alexander Duyck wrote:
>> > If can't do that, we have to stop DMA in a short time to mark
Hi Remi,
Am 07.12.2015 um 19:17 schrieb Remi Pommarel:
Hi Stefan,
On Sun, Dec 06, 2015 at 10:16:25PM +0100, Stefan Wahren wrote:
Hi Remi,
please send this patch to devicet...@vger.kernel.org.
Ok, just to be sure I understand the process here. I should resend a new
version of the whole patch
On 07/12/15 09:12, Jean-Francois Moine wrote:
> On Fri, 4 Dec 2015 22:24:42 +0100
> Jens Kuske wrote:
>
>> The Allwinner H3 is a home entertainment system oriented SoC with
>> four Cortex-A7 cores and a Mali-400MP2 GPU.
>>
>> Signed-off-by: Jens Kuske
>> ---
>> arch/arm/boot/dts/sun8i-h3.dtsi
On Mon, Dec 7, 2015 at 10:05 AM, Suzuki K. Poulose
wrote:
> blkdev_open() doesn't release the bdev, it attached to a given
> inode, if blkdev_get() fails (e.g, due to absence of a device).
> This can cause kernel crashes when the original filesystem
> tries to flush the data during evict_inode.
U
4.4 isn't going smoothly on my 4 socket Xeon servers (18 core per
socket if that is important). User space is RHEL 7.2. Kernel config
is the RHEL one (with whatever mods happen running "make oldconfig"
and hitting to every question.)
1) there was a problem in drm_calc_timestamping_constants(),
th
701 - 800 of 1260 matches
Mail list logo
