On Thu, Apr 14, 2016 at 10:03:48PM +0800, Nicolas Boichat wrote:
>
> We've run into the following lockdep warning while using a system with
> ecryptfs, under heavy memory pressure.
>
> If I understand the issue correctly,
> fs/ecryptfs/crypto.c:ecryptfs_calculate_md5:
> - Locks &crypt_stat->cs_h
A recent cleanup patch accidentally moved the initial assignment
of the register resource after its first use, as shown by this
gcc warning:
drivers/staging/media/omap1/omap1_camera.c: In function 'omap1_cam_probe':
include/linux/ioport.h:191:12: error: 'res' may be used uninitialized in this
fun
On Sat, Apr 16, 2016 at 12:09 AM, Arnd Bergmann wrote:
> On Friday 15 April 2016 19:06:43 Tomasz Nowicki wrote:
>> -MODULE_DEVICE_TABLE(of, thunder_pem_of_match);
>> -
>> -static int thunder_pem_probe(struct platform_device *pdev)
>> +static int thunder_pem_init(struct device *dev, struct pci_conf
page is guaranteed to be set before it is read with or without the
initialisation.
Signed-off-by: Mel Gorman
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index f5ddb342c967..df03ccc7f07c 100644
--- a/mm/page_alloc.c
+++
On Saturday 16 April 2016 12:50:13 Jayachandran C wrote:
> >
> > I still think it would be better to keep the loadable PCI host drivers
> > separate from the ACPI PCI infrastructure. There are a number of
> > simplifications that we want to do to the DT based drivers in the long
> > run, so it's be
On Fri, 15 Apr 2016 21:54:03 +0200
Rafał Miłecki wrote:
> This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
> enum nand_ecc_algo).
Not sure we really need to add this ->ecc_algo field: none of the
existing AVR32 boards use software BCH implementation, and I don't
expect to
On Fri, 15 Apr 2016 21:54:04 +0200
Rafał Miłecki wrote:
> Set it to value obtained from platform data with fallback to Hamming.
> This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
> enum nand_ecc_algo).
>
> Signed-off-by: Rafał Miłecki
> ---
> drivers/mtd/nand/atmel_nand.
On Friday 15 April 2016 07:45:19 Ingo Molnar wrote:
>
> * Denys Vlasenko wrote:
>
> > > In fact, the following patch seems to fix it:
> > >
> > > diff --git a/include/scsi/scsi_transport_fc.h
> > > b/include/scsi/scsi_transport_fc.h
> > > index bf66ea6..56b9e81 100644
> > > --- a/include/scsi/
On Friday 15 April 2016 14:30:56 Duc Dang wrote:
> On Wed, Feb 10, 2016 at 6:28 AM, Arnd Bergmann wrote:
> > On Tuesday 09 February 2016 17:49:44 Duc Dang wrote:
> >> X-Gene PCIe controller does not fully support ECAM.
> >> This patch adds required ECAM fixup to allow X-Gene
> >> PCIe controller t
On Fri, 15 Apr 2016 21:54:08 +0200
Rafał Miłecki wrote:
> This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
> enum nand_ecc_algo).
>
> Signed-off-by: Rafał Miłecki
> ---
> drivers/mtd/nand/hisi504_nand.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mt
On Fri, 15 Apr 2016 21:54:10 +0200
Rafał Miłecki wrote:
> Now we have all drivers properly setting this new field we can start
> using it and proceed with deprecating NAND_ECC_SOFT_BCH.
>
> Signed-off-by: Rafał Miłecki
> ---
> drivers/mtd/nand/nand_base.c | 98
> --
On Sat, 16 Apr 2016 10:00:43 +0200
Boris Brezillon wrote:
> On Fri, 15 Apr 2016 21:54:11 +0200
> Rafał Miłecki wrote:
>
> > There isn't any difference between handling NAND_ECC_SOFT and
> > NAND_ECC_SOFT_BCH now. What matters is the new field called "algo".
> > Please note we're keeping backwar
On Fri, 15 Apr 2016 21:54:11 +0200
Rafał Miłecki wrote:
> There isn't any difference between handling NAND_ECC_SOFT and
> NAND_ECC_SOFT_BCH now. What matters is the new field called "algo".
> Please note we're keeping backward DT compatibility. We are still
> treating "soft_bch" value as the one
Thanks for the review, updated with comments inline with Shardar.
> On Fri, Apr 15, 2016 at 06:51:47PM +0530, Shardar Shariff Md wrote:
> > From: Shardar Shariff Md
> >
> > To summarize the issue observed in error cases:
> >
> > In SW: For i2c message transfer, packet header and data payload is
>
Vinod Koul writes:
> On Thu, Apr 14, 2016 at 08:23:26PM +0200, Robert Jarzmik wrote:
>> Vinod Koul writes:
>>
>> > So what exactly are you trying to fix/achive here?
>> Euh you mean the first chapter about the "endless spin" is not clear ?
>> This is what I'm trying to fix, the unstoppable endl
On Sat, 16 Apr 2016 09:58:07 +0200
Boris Brezillon wrote:
> On Fri, 15 Apr 2016 21:54:10 +0200
> Rafał Miłecki wrote:
>
> > Now we have all drivers properly setting this new field we can start
> > using it and proceed with deprecating NAND_ECC_SOFT_BCH.
> >
> > Signed-off-by: Rafał Miłecki
>
Some sensors (like the one in Nokia N900) provide metadata in the first
couple of lines. Make that information information available to the
pipeline.
Signed-off-by: Ivaylo Dimitrov
---
drivers/media/i2c/smiapp/smiapp-core.c | 12
drivers/media/i2c/smiapp/smiapp.h | 1 +
2 file
ext4_find_extent(), stripped down to the parts relevant to this patch,
reads as
ppos = 0;
i = depth;
while (i) {
--i;
++ppos;
if (unlikely(ppos > depth)) {
...
ret = -EFSCORRUPTED;
goto err;
}
}
Due to the loop's bounds, the condition ppos > depth can nev
The previous text was confusing, leading readers to think this
driver was a duplicate, and so didn't need to be enabled.
After the removal of the older staging driver, this is the only
driver in mainline for these devices.
Signed-off-by: Lauri Kasanen
---
drivers/net/wireless/ath/carl9170/Kconf
* Kees Cook wrote:
> > Also note the assertive tone: if this Kconfig feature is eanbled, we say
> > that
> > the kernel address _will_ be randomized, and we should make sure it is. (If
> > for some weird reason randomization fails we should warn prominently during
> > bootup.)
>
> This will
On Fri, 15 Apr 2016 09:19:51 -0700
Tony Lindgren wrote:
>
> > Or should I just pull this immutable branch in my current nand/next and
> > let you pull the same immutable branch in omap-soc. I mean, would this
> > prevent conflicts when our branches are merged into linux-next, no
> > matter the o
* Kees Cook wrote:
> > So can we rename it to something more expressive, such as kernel_total_size
> > or
> > so?
>
> You got it. Thanks again for digging through all this!
You are welcome! A couple of logistical suggestions:
Could you please split up the series a bit and limit the next ser
* Josh Poimboeuf wrote:
> > I don't think we know yet if there's a reliable way to turn the bug off.
> >
> > Also, according to the gcc guys, this bug won't always result in a
> > truncated function, and may sometimes just make some inline function
> > call sites disappear:
> >
> > https://g
Hi Han,
On Fri, 1 Apr 2016 14:54:26 +0200
Boris Brezillon wrote:
> The core now takes care of parsing generic DT properties in
> nand_scan_ident() when nand_set_flash_node() has been called.
> Rely on this initialization instead of calling of_get_nand_xxx()
> manually.
Can you review/test this
Linus,
Please pull the latest efi-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
efi-urgent-for-linus
# HEAD: f4d5b8adf3668a2fb69a411974057ec3b150b747 Merge tag 'efi-urgent' of
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi into efi/
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 0b22cd276cec21107d9d69453fa58abba73e71df:
>
> Merge tag 'perf-core-for-mingo-20160414' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into pe
Linus,
Please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
# HEAD: 5c8a010c2411729a07cb1b90c09fa978ac0ac6c0 locking/lockdep: Fix
print_collision() unused warning
Fixes a build warning on certai
Commit-ID: de446b40d5ddb2c3f1fe453ac405543663f9ac5d
Gitweb: http://git.kernel.org/tip/de446b40d5ddb2c3f1fe453ac405543663f9ac5d
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 14:56:06 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 14:56:06 -0300
pe
Commit-ID: 91d7b2de318ff701451dfc7ede1c029b150ef0e9
Gitweb: http://git.kernel.org/tip/91d7b2de318ff701451dfc7ede1c029b150ef0e9
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 14:48:07 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 14:48:07 -0300
pe
Commit-ID: bfbba189b681c86b9ae380358e5f50ce1e33d240
Gitweb: http://git.kernel.org/tip/bfbba189b681c86b9ae380358e5f50ce1e33d240
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 15:54:36 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 19:46:53 -0300
pe
Commit-ID: d327e60cfae2201bcdee5aeb9b5a42e3988b184f
Gitweb: http://git.kernel.org/tip/d327e60cfae2201bcdee5aeb9b5a42e3988b184f
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 17:53:49 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 19:46:57 -0300
pe
Commit-ID: bbf86c43eace367e805199f94ad8b5a45636f805
Gitweb: http://git.kernel.org/tip/bbf86c43eace367e805199f94ad8b5a45636f805
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 13:53:10 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 13:53:10 -0300
pe
Commit-ID: 6f736735e30f51805f6be31d20a4bf5b0ae91bae
Gitweb: http://git.kernel.org/tip/6f736735e30f51805f6be31d20a4bf5b0ae91bae
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 17:45:51 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 19:46:56 -0300
pe
Commit-ID: 6125cc8dac432948a31df4d4ac20dd2d4f8c6c27
Gitweb: http://git.kernel.org/tip/6125cc8dac432948a31df4d4ac20dd2d4f8c6c27
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 18:15:18 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 19:46:57 -0300
pe
Commit-ID: e519bd9a07fe5b13c47b506d0fbadb7498e60607
Gitweb: http://git.kernel.org/tip/e519bd9a07fe5b13c47b506d0fbadb7498e60607
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Apr 2016 10:20:10 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 15 Apr 2016 13:14:19 -0300
pe
Commit-ID: 25da4fab5f66e659da768cd61dbf8c3861104d7c
Gitweb: http://git.kernel.org/tip/25da4fab5f66e659da768cd61dbf8c3861104d7c
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 19:45:01 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 19:46:58 -0300
pe
Commit-ID: c6d4a494a207a336b45e52a44550150964daf1ce
Gitweb: http://git.kernel.org/tip/c6d4a494a207a336b45e52a44550150964daf1ce
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Apr 2016 18:29:08 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 14 Apr 2016 19:46:58 -0300
pe
Commit-ID: 5cf9c84e21067ec7a44648aedbc38c197d707258
Gitweb: http://git.kernel.org/tip/5cf9c84e21067ec7a44648aedbc38c197d707258
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Apr 2016 11:10:31 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 15 Apr 2016 13:14:20 -0300
pe
* Toshi Kani wrote:
> On x86, ioremap() and remap_pfn_range() already fail on a conflicting cache
> type if it is not allowed by the rule defined in is_new_memtype_allowed().
> This exception handling is necessary for remap_pfn_range() called by
> /dev/mem, but I do not think it's necessary for
Commit-ID: 056149932602ef905f1e26fc4fe242ef0533a597
Gitweb: http://git.kernel.org/tip/056149932602ef905f1e26fc4fe242ef0533a597
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Apr 2016 16:41:19 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 15 Apr 2016 16:41:19 -0300
pe
Commit-ID: 0883e820a0ac18e04f036dbebc3580351d7fd6cf
Gitweb: http://git.kernel.org/tip/0883e820a0ac18e04f036dbebc3580351d7fd6cf
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Apr 2016 16:37:17 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 15 Apr 2016 16:37:17 -0300
pe
Commit-ID: f3e459d16a8493b617ccf2a940330279679e0291
Gitweb: http://git.kernel.org/tip/f3e459d16a8493b617ccf2a940330279679e0291
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Apr 2016 17:52:34 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 15 Apr 2016 17:52:34 -0300
pe
Commit-ID: b1547d3101e74e809b9790174b27f1080747b009
Gitweb: http://git.kernel.org/tip/b1547d3101e74e809b9790174b27f1080747b009
Author: Josh Poimboeuf
AuthorDate: Fri, 15 Apr 2016 09:17:10 -0500
Committer: Ingo Molnar
CommitDate: Sat, 16 Apr 2016 11:14:17 +0200
objtool: Detect falling t
Currently dw_pcie_setup_rc configures memory base and memory
limit in the type1 configuration header for the root complex.
In doing so it uses the cpu address (pp->mem_base) rather than
the bus address (pp->mem_bus_addr): this is wrong and it is
useless since the configuration is overwritten later
he wrong git tree, please drop us a note
> to help improving the system]
>
> url:https://github.com/0day-ci/linux/commits/Gabriele-Paoloni/PCI-
> Designware-remove-wrong-RC-memory-base-limit-configuration/20160416-
> 000746
> base: https://git.kernel.org/pub/scm/linux/kernel/git
Dear Sir
Hello!
Our company is the Guangzhou Honda and China FAW suppliers. We have been
providing quality products and services for them.
Our company's main products:
Graphite machining end mill
The denture machining tool
Zirconia processing tool
PCD tools
CNC inserts
Milling toolholder
Boron
Dear Sir
Hello!
Our company is the Guangzhou Honda and China FAW suppliers. We have been
providing quality products and services for them.
Our company's main products:
Graphite machining end mill
The denture machining tool
Zirconia processing tool
PCD tools
CNC inserts
Milling toolholder
Boron
Commit-ID: 1e2ae9ec072f3b7887f456426bc2cf23b80f661a
Gitweb: http://git.kernel.org/tip/1e2ae9ec072f3b7887f456426bc2cf23b80f661a
Author: Vitaly Kuznetsov
AuthorDate: Fri, 15 Apr 2016 15:50:32 +0200
Committer: Ingo Molnar
CommitDate: Sat, 16 Apr 2016 11:18:21 +0200
x86/hyperv: Avoid repor
Commit-ID: a3819e3e71d5000c176918309284a1fa2f133fcf
Gitweb: http://git.kernel.org/tip/a3819e3e71d5000c176918309284a1fa2f133fcf
Author: Denys Vlasenko
AuthorDate: Fri, 15 Apr 2016 19:00:26 +0200
Committer: Ingo Molnar
CommitDate: Sat, 16 Apr 2016 13:21:40 +0200
x86: Fix non-static inlin
Mat Martineau wrote:
> > The interface for the active ops is a bit clunky as the syscall interface
> > doesn't provide sufficient argument space to pass everything I need to
> > specify. Some basic integer arguments are specified in a struct and more
> > complex options through a string of key=v
Here's v2 of the patch with the reported errors fixed. It's still untested by
me, however.
David
---
KEYS: Provide keyctls to do public key operations
From: David Howells
Provide keyctl functions to do public key operations (sign, verify, encrypt
and decrypt) if the target key supports them, p
On 15/04/16 16:06, Daniel Baluta wrote:
> BMI160 is an Inertial Measurement Unit (IMU) which provides acceleration
> and angular rate measurement. It also offers a secondary I2C interface
> for connecting a magnetometer sensor (usually BMM160).
>
> Current driver offers support for accelerometer a
Hi Javier,
On 16 April 2016 at 03:34, Javier Martinez Canillas
wrote:
> The exynos5 I2C controller driver always prepares and enables a clock
> before using it and then disables unprepares it when the clock is not
> used anymore.
>
> But this can cause a possible ABBA deadlock in some scenarios s
On Fri, 2016-04-15 at 12:17 +1000, Dave Chinner wrote:
> On Thu, Apr 14, 2016 at 09:57:07AM +0200, Florian Margaine wrote:
> > This lets userland get the filesystem freezing status, aka whether
> > the
> > filesystem is frozen or not. This is so that an application can
> > know if
> > it should fre
From: Colin Ian King
It is entirely possible for of_count_phandle_wit_args to
return a -ve error return value so we need to check for this
otherwise we end up allocating a negative number of clk objects.
Signed-off-by: Colin Ian King
---
drivers/base/power/clock_ops.c | 2 +-
1 file changed, 1
On Sat 2016-04-16 13:50:03, Colin King wrote:
> From: Colin Ian King
>
> It is entirely possible for of_count_phandle_wit_args to
> return a -ve error return value so we need to check for this
> otherwise we end up allocating a negative number of clk objects.
>
> Signed-off-by: Colin Ian King
Around Fri 15 Apr 2016 21:54:03 +0200 or thereabout, Rafał Miłecki wrote:
> This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
> enum nand_ecc_algo).
>
> Signed-off-by: Rafał Miłecki
Acked-by: Hans-Christian Noren Egtvedt
> ---
> arch/avr32/boards/atngw100/setup.c |
On Fri, Apr 15, 2016 at 04:52:02PM -0700, Paul E. McKenney wrote:
> Hello, Frederic,
>
> One thing that I have had on my list for some time is to rearrange the
> RCU source code to make it easier to find things. Given our discussion
> yesterday, this seemed like a good time to take that step with
On 10/04/16 18:35, Laxman Dewangan wrote:
>
> On Sunday 10 April 2016 07:35 PM, Jonathan Cameron wrote:
>> On 06/04/16 15:58, Laxman Dewangan wrote:
>>> Hi Daniel,
>>>
>>>
>>> On Wednesday 06 April 2016 07:19 PM, Daniel Baluta wrote:
On Wed, Apr 6, 2016 at 1:31 PM, Laxman Dewangan
wrot
On 04/13/2016 10:27 AM, Wenwei Tao wrote:
> Calculate rrpc total blocks and sectors up front, make sense
> to use them. For example, we use rrpc->nr_sects to calculate rrpc
> area size, but it makes no sense if we don't initialize it up front,
> since it would be zero until we finish rrpc luns init
On 16/04/16 13:52, Pavel Machek wrote:
> On Sat 2016-04-16 13:50:03, Colin King wrote:
>> From: Colin Ian King
>>
>> It is entirely possible for of_count_phandle_wit_args to
>> return a -ve error return value so we need to check for this
>> otherwise we end up allocating a negative number of clk o
On 04/13/2016 10:27 AM, Wenwei Tao wrote:
> Since we mainly use soffset in device sector size, we store
> that value in rrpc->soffset to reduce doing "(ilog2(dev->sec_size) - 9)".
>
> Signed-off-by: Wenwei Tao
> ---
> drivers/lightnvm/rrpc.c | 17 ++---
> 1 file changed, 10 insertion
The previous text was confusing, leading readers to think this
driver was a duplicate, and so didn't need to be enabled.
After the removal of the older staging driver, this is the only
driver in mainline for these devices.
Signed-off-by: Lauri Kasanen
---
v2: Remove the mention of the previous d
On 04/13/2016 02:15 PM, Simon A. F. Lund wrote:
> A target name must be unique. However, a per-device registration of
> targets is maintained on a dev->online_targets list, with a per-device
> search for targets upon registration.
>
> This results in a name collision when two targets, with the sam
On 04/13/2016 02:15 PM, Simon A. F. Lund wrote:
> The functions nvm_register_target(), nvm_unregister_target() and
> associated list refers to a target type that is being registered by a
> target type module. Rename nvm_*_targets() to nvm_*_tgt_type(), so that
> the intension is clear.
>
> This en
On Sat, Apr 16, 2016 at 1:01 PM, Arnd Bergmann wrote:
> On Saturday 16 April 2016 12:50:13 Jayachandran C wrote:
>> >
>> > I still think it would be better to keep the loadable PCI host drivers
>> > separate from the ACPI PCI infrastructure. There are a number of
>> > simplifications that we want
Hi Arnd,
2016-04-16 3:48 GMT+09:00 Arnd Bergmann :
> On Friday 15 April 2016 22:13:55 Masahiro Yamada wrote:
>> 2016-04-15 22:05 GMT+09:00 Mark Rutland :
>> > On Fri, Apr 15, 2016 at 07:30:47PM +0900, Masahiro Yamada wrote:
>> >> The 8-byte register located at 0x59801200 on this SoC is dedicated
Hi Paul,
On Tue, Apr 12, 2016 at 08:18:21AM -0700, Paul E. McKenney wrote:
> This commit adds documentation for RCU's major data structures,
> including rcu_state, rcu_node, rcu_data, rcu_dynticks, and rcu_head.
>
One small thing, you are using term TREE_PREEMPT_RCU throughout the
whole document
Hi experts.
2016-04-15 3:38 GMT+09:00 Russell King - ARM Linux :
>
> Their stance is not something I agree with - if we have something,
> it should be correct, even if it's not what we would ultimately
> desire, _or_ it should be removed. This half-way house that we
> have today is total madnes
- On Apr 16, 2016, at 9:08 AM, Frederic Weisbecker fweis...@gmail.com wrote:
> On Fri, Apr 15, 2016 at 04:52:02PM -0700, Paul E. McKenney wrote:
>> Hello, Frederic,
>>
>> One thing that I have had on my list for some time is to rearrange the
>> RCU source code to make it easier to find things
On Sat, Apr 16, 2016 at 09:09:40AM +0300, Leon Romanovsky wrote:
On Fri, Apr 15, 2016 at 07:28:01PM -0400, Ira Weiny wrote:
On Sat, Apr 16, 2016 at 12:23:28AM +0300, Leon Romanovsky wrote:
Do you have a technical reason that this patch series does not fix the
write/writev issue brought up by Al?
On Fri, Apr 15, 2016 at 11:49 PM, Jon Masters wrote:
> On 04/15/2016 01:06 PM, Tomasz Nowicki wrote:
>> From the functionality point of view this series might be split into the
>> following logic parts:
>> 1. Necessary fixes as the preparation for using driver on ARM64.
>> 2. New ECAM API and upda
On Saturday, April 16, 2016 05:18:56 PM Lauri Kasanen wrote:
> The previous text was confusing, leading readers to think this
> driver was a duplicate, and so didn't need to be enabled.
>
> After the removal of the older staging driver, this is the only
> driver in mainline for these devices.
>
>
On Fri, Apr 15, 2016 at 04:16:02AM +, Grumbach, Emmanuel wrote:
> [1] https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-iwlwi
> fi.git/
It is very strange to pull from this repo, git fetch is doing something
for a while now without any forward progress.
In any case, 4.5 is bad too
On Saturday 16 April 2016 06:55 PM, Jonathan Cameron wrote:
On 10/04/16 18:35, Laxman Dewangan wrote:
Yaah, possibly race for very small time possible.
The limitation of devm_ api usage is that, we can keep using this
till we have devm_ api continuous and if some resource are not there
for de
Hello Maxime,
On Fri, Apr 15, 2016 at 1:28 AM, Maxime Ripard
wrote:
> On Mon, Apr 04, 2016 at 11:07:29AM +0800, Vishnu Patekar wrote:
>> Hello Maxime,
>>
>> On Thu, Mar 17, 2016 at 6:40 PM, Maxime Ripard
>> wrote:
>> > On Thu, Mar 17, 2016 at 12:04:25AM +0800, Vishnu Patekar wrote:
>> >> AHB1 on
On Fri, Apr 15, 2016 at 06:28:32PM +0100, Sudeep Holla wrote:
> Hi Greg,
>
> I just noticed this now. I am having similar issue with MPS2 UART driver
> posted @[1], hence I am asking here to get some clarification myself.
> Sorry for replying on very old thread.
>
> On Thu, Jan 14, 2016 at 1:15 A
On Fri, Apr 15, 2016 at 06:04:47PM -0400, Javier Martinez Canillas wrote:
> The exynos5 I2C controller driver always prepares and enables a clock
> before using it and then disables unprepares it when the clock is not
> used anymore.
>
> But this can cause a possible ABBA deadlock in some scenario
Hi Peter,
On 04/15, Peter Hurley wrote:
> >
> > If we just want to add a preemption point then perhaps we should use
> > cond_resched/might_resched ?
>
> Yeah, it's just a preemption point that pre-dates cond_resched.
OK, so perhaps s/schedule/might_reched/ makes sense to make it more
clear.
> >
On Sat, 16 Apr 2016 09:18:46 +0900
SeongJae Park wrote:
> Obsolete info about regression postings were removed by commit
> 5645a717c6ee61e67d38aa9f15cb9db074e1e99d ("Documentation: HOWTO: remove
> obsolete info about regression postings") but not applied to
> translations. This commit applies th
Hi Guodong,
On 13/04/2016 00:55, Guodong Xu wrote:
> This patchset include dts changes for hi6220 SoC and HiKey board. These
> patches apply well one by one on top of next-20160401. All tested on HiKey
> and pass.
>
> To avoid merge conflicts with patches already ack'ed by maintainers,
> I picked
All other devices are disabled by default and not all boards will use
these devices, so these should be disabled too..
da850-evm.dtb already had status = "okay" for these devices.
da850-enbw-cmc.dts did not, so they were added.
Signed-off-by: David Lechner
Tested-by: Kevin Hilman
---
no change
Add device node and pinmux for SoC spi0.
Signed-off-by: David Lechner
---
Device tree portion of previous "ARM: davinci: add spi0 to da850 device tree"
patch.
Added pinmux definitions.
arch/arm/boot/dts/da850.dtsi | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
Split "ARM: davinci: add spi0 to da850 device tree" into two patches and added
pinmux device tree nodes.
David Lechner (4):
ARM: DTS: da850: add spi0 to device tree
ARM: davinci: Add spi0 lookup to da8xx-dt for clock matching
ARM: davinci: disable mdio and eth0 in da850.dtsi
ARM: davinci:
Fix off by one error in da850 device tree.
Signed-off-by: David Lechner
Tested-by: Kevin Hilman
---
no change
arch/arm/boot/dts/da850.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
index 26fc0812..cf1aad8 10
This is needed to match the device-tree node for spi0 to the
non-device-tree clock.
Signed-off-by: David Lechner
Tested-by: Kevin Hilman
---
code portion of previous "ARM: davinci: add spi0 to da850 device tree" patch.
no change.
arch/arm/mach-davinci/da8xx-dt.c | 1 +
1 file changed, 1 inse
We already have a number of calls converted, but still a decent
amount of ACCESS_ONCE callers in core-code, which is somewhat
troubling. Convert more users (even if some are scalar types,
we want to someday get rid of ACCESS_ONCE altogether I suppose.
Signed-off-by: Davidlohr Bueso
---
Documenta
Hello Linus,
Please conside pulling to recives dmaengine for 4.6-rc4.
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaeng
Hi.
I have wondered how to handle reset signals for my SoCs.
I notice reset controllers are less supported in Linux than clock controllers.
I grepped "clk_register" and "reset_controller_register".
I know this does not give us the precise number of
clk/reset providers, but I think it is en
... as the call obviously already implies unlock/RC semantics,
therefore lets get rid of the superfluous smp_mb calls.
Signed-off-by: Davidlohr Bueso
---
lib/irq_poll.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/lib/irq_poll.c b/lib/irq_poll.c
index 836f7db4e548..2a6ae2720ccb 100644
--
On Fri, Apr 15, 2016 at 10:06 AM, Tomasz Nowicki wrote:
> From the functionality point of view this series might be split into the
> following logic parts:
> 1. Necessary fixes as the preparation for using driver on ARM64.
> 2. New ECAM API and update for users of the pci-host-common API
> 3. Use
So I've looked at the devpts patches some more, and I'm still not happy
with them.
And one thing I really detest about them is that the 16-patch series
didn't really make me warm and fuzzy in general. Some of the patches were
fine, but on the whole it all still looked rather hacky.
So I start
With Linux 3.5.0 I suddenly had Firefox which suddenly seemed
to get stuck, and then I tried to kill it. I also noticed that
the ps aux command was hanging. Then I found this in my kernel
logs:
Apr 16 20:21:53 piranha kernel: [27926.414148] BUG: Bad page state in process
Compositor pfn:16834f
For A31 ahb1 and a83t ahb1 clocks have predivider for certain parent.
To handle this, this patch adds predivider table with parent index,
prediv shift and width, parents with predivider will have nonzero width.
Rate adjustment is moved from clock specific recalc function to generic
factors recalc.
For allwinner A31 ahb1 and a83t ahb1 clocks have predivider for certain parent.
Currently, it's being handled in clock specific functions.
A83t ahb1 and a31 ahb1 are similar clocks except a83t parent index 0b10 and 0b11
are pll6/prediv and a31 ahb1 parent index 0x11 is pll6/prediv.
with only thi
For ahb1 clock, move mshift and mwidth to parent specific width and shift.
getter differentiates parents with prediv, with non-zero prediv width.
Also, removed unused ahb1 recalc function, it's now handled in generic
factors recalc.
Signed-off-by: Vishnu Patekar
---
drivers/clk/sunxi/clk-sunxi.
Add a test for use of ACCESS_ONCE that could be written using
READ_ONCE or WRITE_ONCE.
--fix it too if desired.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 22 ++
1 file changed, 22 insertions(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index e3
On 04/01/2016 05:33 PM, Mathieu Poirier wrote:
> On 1 April 2016 at 08:22, Neil Armstrong wrote:
Hi Matthieu,
Thanks for the review.
>> + /* OX810SE Uses a special 24bit width */
>> + if (of_device_is_compatible(np, "oxsemi,ox810se-rps-timer"))
>> + width = 24;
>
> Woul
On Sat, Apr 16, 2016 at 09:00:42AM +0300, Leon Romanovsky wrote:
> On Fri, Apr 15, 2016 at 05:37:32PM -0600, Jason Gunthorpe wrote:
> > On Sat, Apr 16, 2016 at 12:23:28AM +0300, Leon Romanovsky wrote:
> >
> > > Intel as usual decided to do it in their way and the result is presented
> > > on this
On 10/04/16 20:05, Alison Schofield wrote:
> Driver includes struct regmap and struct device in its global data.
> Remove the struct device and use regmap API to retrieve device info.
>
> Patch created using Coccinelle plus manual edits.
>
> Signed-off-by: Alison Schofield
I'm happy with this bu
1 - 100 of 216 matches
Mail list logo
