On Wed, Mar 25, 2015 at 04:27:48PM +0100, Christoph Hellwig wrote:
> On Wed, Mar 25, 2015 at 03:23:48PM +0800, Ming Lei wrote:
> > > - mm_segment_t old_fs = get_fs();
> > > +
> > > + iov_iter_bvec(, ITER_BVEC, bvec, 1, bvec->bv_len);
> > >
> > > file_start_write(file);
> > > -
On Sat, 2015-04-04 at 04:03 +0200, Mike Galbraith wrote:
> On Fri, 2015-04-03 at 15:21 -0400, Chris Metcalf wrote:
> > On 04/03/2015 02:08 PM, Mike Galbraith wrote:
> > > On Fri, 2015-04-03 at 12:24 -0400, cmetcalf@ezchip.comwrote:
> > > > From: Chris Metcalf
> > > >
> > > > It's not clear that
On Fri, Apr 3, 2015 at 11:59 AM, Bjorn Helgaas wrote:
> On Tue, Mar 31, 2015 at 07:57:47PM -0700, Yinghai Lu wrote:
>> David Ahern found commit d63e2e1f3df9 ("sparc/PCI: Clip bridge windows
>> to fit in upstream windows") broke booting on sparc/T5-8.
>>
>> In the boot log, there is
>> pci
On 04/03/2015 11:37 PM, Yinghai Lu wrote:
> What is NVM here?
nvm == nevermind
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Mon, 30 Mar 2015 13:26:25 -0700 Andrew Morton
wrote:
> d) fincore() is more expensive
Actually, I kinda take that back. fincore() will be faster than
preadv2() in the case of a pagecache miss, and slower in the case of a
pagecache hit.
The breakpoint appears to be a hit rate of 30% - if
On Fri, Apr 3, 2015 at 8:32 PM, Peter Hurley wrote:
Just now noticed, this patch only fix partial problem. Kernel console is
ok.
But later initrd/init scripts revert back to 9600 again.
>>>
>>> Please share the init scripts.
>>
>> I am using opensuse 13.1 rescue disk as
On Fri, Apr 3, 2015 at 1:52 PM, Bjorn Helgaas wrote:
> [+cc Sam (commented on previous versions), Russell, linux-arm-kernel, Ralf,
> linux-mips, Ben, linuxppc-dev, x86]
>
> On Fri, Apr 03, 2015 at 02:32:34PM -0500, Bjorn Helgaas wrote:
>> On Tue, Mar 31, 2015 at 07:57:47PM -0700, Yinghai Lu
On 04/03/2015 11:24 PM, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 8:15 PM, Peter Hurley wrote:
>> On 04/03/2015 11:09 PM, Yinghai Lu wrote:
>>> On Fri, Apr 3, 2015 at 7:19 PM, Yinghai Lu wrote:
On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley
wrote:
> Restore undocumented behavior
On Fri, Apr 3, 2015 at 8:24 PM, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 8:15 PM, Peter Hurley wrote:
>> On 04/03/2015 11:09 PM, Yinghai Lu wrote:
>>> On Fri, Apr 3, 2015 at 7:19 PM, Yinghai Lu wrote:
On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley
wrote:
> Restore undocumented
On Fri, Apr 3, 2015 at 8:09 PM, Peter Hurley wrote:
>
> All this automatic behavior and aliases for the same things just
> adds unnecessary complexity and maintenance burden, without measurable
> gain.
>
> The real tragedy is that all this was totally unnecessary; what was
> wrong with
On Fri, Apr 3, 2015 at 8:15 PM, Peter Hurley wrote:
> On 04/03/2015 11:09 PM, Yinghai Lu wrote:
>> On Fri, Apr 3, 2015 at 7:19 PM, Yinghai Lu wrote:
>>> On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley
>>> wrote:
Restore undocumented behavior of kernel command line parameters of
the
On 04/03/2015 11:09 PM, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 7:19 PM, Yinghai Lu wrote:
>> On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley
>> wrote:
>>> Restore undocumented behavior of kernel command line parameters of
>>> the forms:
>>> console=uart[8250],io|mmio|mmio32,[,options]
>>>
On 04/03/2015 10:56 PM, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 7:29 PM, Peter Hurley wrote:
>> On 04/03/2015 10:19 PM, Yinghai Lu wrote:
>>> On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley
>>> wrote:
Restore undocumented behavior of kernel command line parameters of
the forms:
On Fri, Apr 3, 2015 at 7:19 PM, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley wrote:
>> Restore undocumented behavior of kernel command line parameters of
>> the forms:
>> console=uart[8250],io|mmio|mmio32,[,options]
>> console=uart[8250],[,options]
>> where 'options'
Hi Jiang,
Sorry for my delayed response. I've been on vacation for a week and am
still trying to catch up.
On Mon, Mar 30, 2015 at 10:40:43AM +0800, Jiang Liu wrote:
> Before commit 593669c2ac0f("Use common ACPI resource interfaces to
> simplify implementation"), arch/x86/pci/acpi.c applies
On Fri, Apr 3, 2015 at 7:50 PM, Peter Hurley wrote:
> On 04/03/2015 10:29 PM, Peter Hurley wrote:
>> On 04/03/2015 10:19 PM, Yinghai Lu wrote:
>>> Another regression.
>>> when user have
>>> console=uart8250,io,0x3f8 console=uart8250,io,0x2f8
>>>
>>> before your patchset:
>>> port_0x3f8 is early
On Fri, Apr 3, 2015 at 7:29 PM, Peter Hurley wrote:
> On 04/03/2015 10:19 PM, Yinghai Lu wrote:
>> On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley
>> wrote:
>>> Restore undocumented behavior of kernel command line parameters of
>>> the forms:
>>> console=uart[8250],io|mmio|mmio32,[,options]
On 04/03/2015 10:29 PM, Peter Hurley wrote:
> On 04/03/2015 10:19 PM, Yinghai Lu wrote:
>> Another regression.
>> when user have
>> console=uart8250,io,0x3f8 console=uart8250,io,0x2f8
>>
>> before your patchset:
>> port_0x3f8 is early console, and will be console later.
>> and port_0x2f8 is
wait_for_completion_timeout return >= 0 but never negative so the check
logic looks inconsistent. Further the return value of
wait_for_completion_timeout was being passed up the call chain but the
x call sites as drm_dp_i2c_do_msg()/drm_dp_dpcd_access() check for < 0
thus timeout was being
fix build warning when building edp/edp_aux.o due to missing
prototype for edp_aux_transfer.
Signed-off-by: Nicholas Mc Guire
---
building drivers/gpu/drm/msm/msm.ko gives the following warning:
drivers/gpu/drm/msm/edp/edp_aux.c:118:9: warning: no previous prototype for
'edp_aux_transfer'
The timeout is passed as a constant which makes it HZ dependent because
jiffies are expected so it should be converted to jiffies. The actual
value is not clear from the code - my best guess is that this should be
300 milliseconds given that other timeouts are in milliseconds based on
looking
wait_for_completion_timeout returns 0 in case of timeout so printing the
return value here will always yield 0 and is therefor redundant - dropped.
Signed-off-by: Nicholas Mc Guire
---
This was compile tested with qcom_defconfig +
CONFIG_DRM=m (implies CONFIG_DRM_MSM=m)
Patch is against
On 04/03/2015 10:19 PM, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley wrote:
>> Restore undocumented behavior of kernel command line parameters of
>> the forms:
>> console=uart[8250],io|mmio|mmio32,[,options]
>> console=uart[8250],[,options]
>> where 'options' have not
On Fri, Apr 3, 2015 at 5:04 PM, Peter Hurley wrote:
> Restore undocumented behavior of kernel command line parameters of
> the forms:
> console=uart[8250],io|mmio|mmio32,[,options]
> console=uart[8250],[,options]
> where 'options' have not been specified; in this case, the hardware
> is
On Fri, 3 Apr 2015, Andrey Ryabinin wrote:
> Mempools keep allocated objects in reserved for situations
> when ordinary allocation may not be possible to satisfy.
> These objects shouldn't be accessed before they leave
> the pool.
> This patch poison elements when get into the pool
> and unpoison
On Fri, 2015-04-03 at 15:21 -0400, Chris Metcalf wrote:
> On 04/03/2015 02:08 PM, Mike Galbraith wrote:
> > On Fri, 2015-04-03 at 12:24 -0400, cmetcalf@ezchip.comwrote:
> > > From: Chris Metcalf
> > >
> > > It's not clear that nohz_full is useful without isolcpus also
> > > set, since otherwise
On Wed, 18 Mar 2015, Michal Hocko wrote:
> memcg currently uses hardcoded GFP_TRANSHUGE gfp flags for all THP
> charges. THP allocations, however, might be using different flags
> depending on /sys/kernel/mm/transparent_hugepage/{,khugepaged/}defrag
> and the current allocation context.
>
> The
On Sat, 4 Apr 2015 03:47:12 +0300 Konstantin Khlebnikov
wrote:
> On Sat, Apr 4, 2015 at 1:10 AM, Andrew Morton
> wrote:
> > On Fri, 03 Apr 2015 20:18:18 +0300 Konstantin Khlebnikov
> > wrote:
> >
> >> A lot of filesystems use generic_file_mmap() and filemap_fault(),
> >> f_op->mmap and
On 04/03/2015 08:52 PM, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 11:27 AM, Peter Hurley
> wrote:
>> On 04/03/2015 01:44 PM, Yinghai Lu wrote:
>>> On Fri, Apr 3, 2015 at 10:38 AM, Peter Hurley
>>> wrote:
On 04/03/2015 12:57 PM, Yinghai Lu wrote:
Wait -- you have earlycon in a
On Sat, 4 Apr 2015, Andreas Theodosiou wrote:
> This is a patch to the fb_ili9163.c file that inserts a line break in
> line #92 to make the line fit into the 80 character limit.
>
> Signed-off-by: Andreas Theodosiou
> ---
> drivers/staging/fbtft/fb_ili9163.c | 3 ++-
> 1 file changed, 2
On Fri, Apr 3, 2015 at 11:27 AM, Peter Hurley wrote:
> On 04/03/2015 01:44 PM, Yinghai Lu wrote:
>
> which means you have to have CONFIG_SERIAL_EARLYCON to get a serial console
> at all.
what do you mean? Now in drivers/tty/serial/8250/Kconfig we have
config SERIAL_8250_CONSOLE
bool
On Fri, Apr 3, 2015 at 11:27 AM, Peter Hurley wrote:
> On 04/03/2015 01:44 PM, Yinghai Lu wrote:
>> On Fri, Apr 3, 2015 at 10:38 AM, Peter Hurley
>> wrote:
>>> On 04/03/2015 12:57 PM, Yinghai Lu wrote:
>>>
>>> Wait -- you have earlycon in a product??
>>
>> What do you mean?
>
> I mean, what
On Sat, Apr 4, 2015 at 1:10 AM, Andrew Morton wrote:
> On Fri, 03 Apr 2015 20:18:18 +0300 Konstantin Khlebnikov
> wrote:
>
>> A lot of filesystems use generic_file_mmap() and filemap_fault(),
>> f_op->mmap and vm_ops->fault aren't enough to identify filesystem.
>>
>> This prints file name,
On Sat, 2015-04-04 at 03:23 +0300, Andreas Theodosiou wrote:
> This is a patch to the fb_ili9163.c file that inserts a line break in
> line #92 to make the line fit into the 80 character limit.
[]
> diff --git a/drivers/staging/fbtft/fb_ili9163.c
> b/drivers/staging/fbtft/fb_ili9163.c
[]
> @@
On Fri, 3 Apr 2015 19:08:22 +0530 Kishon Vijay Abraham I
wrote:
> +Extcon MAINTAINERS
>
> Hi,
>
> On Wednesday 01 April 2015 10:11 AM, NeilBrown wrote:
> > On Thu, 26 Mar 2015 05:29:42 +0530 Kishon Vijay Abraham I
> > wrote:
> >
> >> Hi NeilBrown,
> >>
> >> On Thursday 26 March 2015 02:52 AM,
This is a patch to the fb_ili9163.c file that inserts a line break in
line #92 to make the line fit into the 80 character limit.
Signed-off-by: Andreas Theodosiou
---
drivers/staging/fbtft/fb_ili9163.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On 03/31/2015 09:55 AM, Rasmus Villemoes wrote:
> All users of tty_name pass the return value directly to a printf
> function, so we might as well use tty->name directly instead of
> copying it to a user-supplied (stack) buffer.
Reviewed-by: Peter Hurley
--
To unsubscribe from this list: send
If i2c_add_adapter() fails, adap is not deallocated.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/media/platform/marvell-ccic/cafe-driver.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git
On Fri, 3 Apr 2015 08:55:57 +0200
Ingo Molnar wrote:
> So the original commit also has the problem that it unnecessary
> drops/retakes the descriptor lock:
>
> > irq_put_desc_unlock(desc, flags);
> > - /* set the initial affinity to prevent every interrupt being on CPU0 */
> > - if (m)
Restore undocumented behavior of kernel command line parameters of
the forms:
console=uart[8250],io|mmio|mmio32,[,options]
console=uart[8250],[,options]
where 'options' have not been specified; in this case, the hardware
is assumed to be initialized.
Document the required behavior of the
On 2015-04-03 22:09, Russell King - ARM Linux wrote:
> On Fri, Apr 03, 2015 at 09:44:48PM +0200, Stefan Agner wrote:
>> In order to support SoC with heterogenous CPU architectures (such
>> as Freescale Vybrid/i.MXSX) it is preferable to use the same
>> architecture (ARCH_MXC in this case) for the
Restore undocumented behavior of kernel command line parameters of
the forms:
console=uart[],io|mmio|mmio32,[,options]
console=uart[],[,options]
where 'options' have not been specified; in this case, the hardware
is assumed to be initialized.
Document the required behavior of the
The Shared Memory Manager driver implements an interface for allocating
and accessing items in the memory area shared among all of the
processors in a Qualcomm platform.
Signed-off-by: Bjorn Andersson
---
Note that this depends on the hwspinlock device tree patches by Suman Anna [1]
and my
Add device tree binding documentation for the Qualcom Shared Memory
manager.
Signed-off-by: Bjorn Andersson
---
.../devicetree/bindings/soc/qcom/qcom,smem.txt | 49 ++
1 file changed, 49 insertions(+)
create mode 100644
On Thu, Apr 2, 2015 at 11:25 PM, Chen Gang wrote:
> For allmodconfig, it uses BF533 which will cause 3 issues for common
> checking:
>
> - The first 2 issues are about PLL_BYPASS, it needs BF_REV_0_6 (which
>just match the compiler's output for __SILICON_REVISION__).
>
> - The last issue is
On Fri, Apr 3, 2015 at 10:19 PM, Chen Gang wrote:
> The related error with allmodconfig:
BTW: How do you generate this allmodconfig?
"make allmodconfig ARCH=blackfin" cannot work as you need to specify a board...
> CC [M] fs/coda/psdev.o
> In file included from include/linux/coda.h:64:0,
[cc: Boris and Konrad. Whoops]
On Fri, Apr 3, 2015 at 3:51 PM, Andy Lutomirski wrote:
> We don't use irq_enable_sysexit on 64-bit kernels any more. Remove
> all the paravirt and Xen machinery to support it on 64-bit kernels.
>
> Signed-off-by: Andy Lutomirski
> ---
>
> I haven't actually
We don't use irq_enable_sysexit on 64-bit kernels any more. Remove
all the paravirt and Xen machinery to support it on 64-bit kernels.
Signed-off-by: Andy Lutomirski
---
I haven't actually tested this on Xen, but it builds for me.
arch/x86/ia32/ia32entry.S | 6 --
On Fri, Apr 3, 2015 at 10:36 PM, Chen Gang wrote:
> It is copied from asm-generic, the related error with allmodconfig:
>
> CC [M] sound/core/pcm_native.o
> sound/core/pcm_native.c: In function 'snd_pcm_lib_default_mmap':
> sound/core/pcm_native.c:3387:24: error: implicit declaration of
On Sat, Apr 4, 2015 at 12:17 AM, Chen Gang wrote:
> Quite a few of architures (e.g. blackfin, cris, frv ...) do not support
> memfd_create system call which is used in prime_new(). So define a dummy
> one.
Don't paper over the issue, just wire up the system call on blackfin.
For an example see:
On Wed, 2015-04-01 at 22:59 -0700, Jason Low wrote:
> On Wed, 2015-04-01 at 18:04 +0100, Morten Rasmussen wrote:
> > On Wed, Apr 01, 2015 at 07:49:56AM +0100, Preeti U Murthy wrote:
>
> > > I am sorry I don't quite get this. Can you please elaborate?
> >
> > I think the scenario is that we are
On 4/4/15 06:03, Richard Weinberger wrote:
> On Fri, Apr 3, 2015 at 11:51 PM, Chen Gang
> wrote:
>> Under blackfin, only bf527, bf548 and bf609 may use musb. The related
>> error with allmodconfig:
>>
>> CC [M] drivers/usb/misc/trancevibrator.o
>> In file included from
Please respond!!!
Hello friend!
I would like to contact you personally for an important proposal that could of
interest to you.
I send this email only to know if this email address is functional.
I have something very important to discuss with you. Contact me for details by:
Email:
Quite a few of architures (e.g. blackfin, cris, frv ...) do not support
memfd_create system call which is used in prime_new(). So define a dummy
one.
The related error (with allmodconfig under blackfin):
CC [M] samples/kfifo/inttype-example.o
samples/kdbus/kdbus-workers.c: In function
On Sat, Apr 4, 2015 at 1:09 AM, Andy Shevchenko
wrote:
> On Fri, Apr 3, 2015 at 8:01 PM, Maxime Coquelin
> wrote:
>> STM32 MCUs feature 16 and 32 bits general purpose timers with prescalers.
>> The drivers detects whether the time is 16 or 32 bits, and applies a
>> 1024 prescaler value if it is
On Fri, 03 Apr 2015 20:18:18 +0300 Konstantin Khlebnikov
wrote:
> A lot of filesystems use generic_file_mmap() and filemap_fault(),
> f_op->mmap and vm_ops->fault aren't enough to identify filesystem.
>
> This prints file name, vm_ops->fault, f_op->mmap and a_ops->readpage
> (which is almost
On Fri, Apr 3, 2015 at 8:01 PM, Maxime Coquelin
wrote:
> STM32 MCUs feature 16 and 32 bits general purpose timers with prescalers.
> The drivers detects whether the time is 16 or 32 bits, and applies a
> 1024 prescaler value if it is 16 bits.
>
Few comments below.
> Reviewed-by: Linus Walleij
On Fri, 03 Apr 2015 17:47:47 +0300 Andrey Ryabinin
wrote:
> Mempools keep allocated objects in reserved for situations
> when ordinary allocation may not be possible to satisfy.
> These objects shouldn't be accessed before they leave
> the pool.
> This patch poison elements when get into the
On Fri, Apr 3, 2015 at 8:01 PM, Maxime Coquelin
wrote:
> This drivers adds support to the STM32 USART controller, which is a
> standard serial driver.
>
Few minor comments.
> Tested-by: Chanwoo Choi
> Signed-off-by: Maxime Coquelin
> ---
> drivers/tty/serial/Kconfig | 17 +
>
On Fri, Apr 3, 2015 at 11:51 PM, Chen Gang wrote:
> Under blackfin, only bf527, bf548 and bf609 may use musb. The related
> error with allmodconfig:
>
> CC [M] drivers/usb/misc/trancevibrator.o
> In file included from drivers/usb/musb/musb_core.h:70:0,
>from
On Fri, 03 Apr 2015 15:42:40 +0300 Stefan Strogin
wrote:
> From: Dmitry Safonov
>
> Here are two functions that provide interface to compute/get used size
> and size of biggest free chunk in cma region. Add that information to debugfs.
>
> ...
>
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -53,6
On Fri, Apr 03, 2015 at 01:55:07PM -0700, Olof Johansson wrote:
> On Fri, Apr 03, 2015 at 10:43:40AM +0200, Nicolas Ferre wrote:
> > Le 31/03/2015 10:56, Nicolas Ferre a écrit :
> > > After 57a38effa598 (net: phy: micrel: disable broadcast for
> > > KSZ8081/KSZ8091)
> > > the macb1 interface
Under blackfin, only bf527, bf548 and bf609 may use musb. The related
error with allmodconfig:
CC [M] drivers/usb/misc/trancevibrator.o
In file included from drivers/usb/musb/musb_core.h:70:0,
from drivers/usb/musb/musb_core.c:103:
drivers/usb/musb/musb_core.c: In
On Fri, 2015-04-03 at 19:23 +0200, Borislav Petkov wrote:
> On Fri, Apr 03, 2015 at 05:33:03PM +0200, Paul Bolle wrote:
> > Well, "when building on 32 bits" it currently suffices to do:
> > make allnoconfig
> >
> > and the patch changes that.
>
> Hmm, so this would need more staring. The
On Fri, Apr 03, 2015 at 10:26:24PM +0200, Pavel Machek wrote:
> > > + - power-gpios: Reference to the GPIO that controls the power for the
> > > chip.
> >
> > You're using power-gpios in documentation only.
>
> Which is ok, because generic code adds "-gpios" itself.
Do you think you need this
Hi Pavel,
On Fri, Apr 03, 2015 at 10:26:24PM +0200, Pavel Machek wrote:
>
> Documentation for adp1653 binding.
>
> ---
>
> > Please split this as Javier suggested. I'd think both could go through
> > the media-tree unless someone objects.
>
> Please apply.
>
> > > + - power-gpios: Reference
Jens, one of your patches from October 2013 never made it
to the kernel, but would be beneficial for pmem. It helps
IOPS about 15%.
Original patch: https://lkml.org/lkml/2013/10/24/130
> From Jens Axboe
> Subject [PATCH 05/11] direct-io: only inc/dec inode->i_dio_count for file
> systems
>
On Fri, Apr 03, 2015 at 10:29:53PM +0200, Pavel Machek wrote:
> On Fri 2015-04-03 14:23:56, Sakari Ailus wrote:
> > Hi Pavel,
> >
> > On Fri, Apr 03, 2015 at 10:23:44AM +0200, Pavel Machek wrote:
> > > Hi!
> > >
> > > > Hi Pawel,
> > >
> > > I'm still Pavel. v, not w.
> >
> > I know too many
On Fri, 2015-04-03 at 14:45 +0200, Filip Brozović wrote:
> The idea was that boards in the Kconfig file would select these symbols
> in order to enable support for the 8306. I mainly wanted to get this
> patch into mainline in order to make kernel maintenance for a couple of
> custom in-house
On Fri, 2015-04-03 at 11:07 +0300, Purcareata Bogdan wrote:
> On 03.04.2015 02:11, Scott Wood wrote:
> > On Fri, 2015-03-27 at 19:07 +0200, Purcareata Bogdan wrote:
> >> On 27.02.2015 03:05, Scott Wood wrote:
> >>> On Thu, 2015-02-26 at 14:31 +0100, Sebastian Andrzej Siewior wrote:
> On
03.04.2015 22:25, Florian Fainelli пишет:
On 01/04/15 10:30, Stas Sergeev wrote:
- The callback needs to be registered before of_phy_connect() to
avoid running with outdated state, but of_phy_connect() returns the
phy_device pointer, which is needed to register the callback. Registering
it
On Friday, April 03, 2015 05:58:25 PM rhn wrote:
> On Thu, 2 Apr 2015 17:28:05 +0200
> Pavel Machek wrote:
>
> > On Wed 2015-04-01 21:47:43, rhn wrote:
> > > Hello,
> > >
> > > Between kernel 3.16 and 3.17, a regression has been introduced where the
> > > first hibernation after regular
On Fri, 2015-04-03 at 10:12 -0700, Yinghai Lu wrote:
> On Fri, Apr 3, 2015 at 9:14 AM, Toshi Kani wrote:
> > On Wed, 2015-04-01 at 09:12 +0200, Christoph Hellwig wrote:
> > :
> >> @@ -748,7 +758,7 @@ u64 __init early_reserve_e820(u64 size, u64 align)
> >> /*
> >> * Find the highest page
On Thu, Apr 02, 2015 at 05:02:25PM +0200, David Sterba wrote:
> On Wed, Apr 01, 2015 at 08:49:54PM -0700, Omar Sandoval wrote:
> > Hm, yeah, that's unfortunate, thanks for pointing that out. It looks
> > like we can get the subvolume ID reliably:
> >
> >
> > diff --git a/fs/btrfs/super.c
On Fri, Apr 03, 2015 at 10:01:10AM -0700, Joe Perches wrote:
> On Fri, 2015-04-03 at 19:51 +0300, Dan Carpenter wrote:
> > Also strcmp() and similar should always be done as == 0, < 0 or != 0
> > because that is the idiom:
>
> Less true.
>
> When testing for equality, !strcmp is very common.
>
Hi!
> > + pd->max_flash_intensity = val/1000;
> > +
> > + if (of_property_read_u32(child, "max-microamp", ))
> > + return -EINVAL;
> > + pd->max_torch_intensity = val/1000;
>
> I think you need to do of_node_put(child) here and after you're done with
> indicator below.
...and in
On Friday, April 03, 2015 01:44:36 PM Dmitry Torokhov wrote:
> Hi Tomeu,
>
> On Fri, Apr 03, 2015 at 02:57:56PM +0200, Tomeu Vizoso wrote:
> > Have dev_pm_ops.prepare return 1 for USB devices, interfaces, endpoints
> > and ports so that USB devices can remain runtime-suspended when the
> > system
On Fri, Apr 03, 2015 at 10:43:40AM +0200, Nicolas Ferre wrote:
> Le 31/03/2015 10:56, Nicolas Ferre a écrit :
> > After 57a38effa598 (net: phy: micrel: disable broadcast for KSZ8081/KSZ8091)
> > the macb1 interface refuses to work properly because it tries
> > to cling to address 0 which isn't
On Mon, Mar 30, 2015 at 04:40:13PM +0200, Tomeu Vizoso wrote:
> This brings the DevFreq framework in and builds the ACTMON driver that
> on Tegra124 will scale the external memory clock based on current load.
>
> Signed-off-by: Tomeu Vizoso
> ---
Thanks, applied 1-4. In the future you can
On Mon, Mar 30, 2015 at 02:39:08PM +0200, Michal Simek wrote:
> From: Nathan Rossi
>
> When building specific DTBs out of the kernel tree the vendor subdirs
> (boot/dts/) are not created, ensure that they are before
> building the DTB.
>
> Signed-off-by: Nathan Rossi
> Signed-off-by: Michal
[+cc Sam (commented on previous versions), Russell, linux-arm-kernel, Ralf,
linux-mips, Ben, linuxppc-dev, x86]
On Fri, Apr 03, 2015 at 02:32:34PM -0500, Bjorn Helgaas wrote:
> On Tue, Mar 31, 2015 at 07:57:47PM -0700, Yinghai Lu wrote:
> > David Ahern found commit d63e2e1f3df9 ("sparc/PCI: Clip
[+cc Ben, linuxppc-dev, Grant, Rob, devicetree]
On Tue, Mar 31, 2015 at 07:57:48PM -0700, Yinghai Lu wrote:
> Found "no compatible bridge window" warning in boot log from T5-8.
>
> pci :00:01.0: can't claim BAR 15 [mem 0x1-0x4afff pref]: no
> compatible bridge window
>
> That
Hi Tomeu,
On Fri, Apr 03, 2015 at 02:57:56PM +0200, Tomeu Vizoso wrote:
> Have dev_pm_ops.prepare return 1 for USB devices, interfaces, endpoints
> and ports so that USB devices can remain runtime-suspended when the
> system goes to a sleep state, if their wakeup state is correct.
>
> Also
Add delay between chip select and clock signals, before clock starts and
after clock stops.
Signed-off-by: Aaron Brice
---
drivers/spi/spi-fsl-dspi.c | 64 +++---
1 file changed, 60 insertions(+), 4 deletions(-)
diff --git a/drivers/spi/spi-fsl-dspi.c
On Fri, Apr 03, 2015 at 07:48:24PM +0200, Borislav Petkov wrote:
> On Fri, Apr 03, 2015 at 07:33:06PM +0200, Quentin Casasnovas wrote:
> > > Basically, the idea was:
> > >
> > > .skip len(repl1) - len(orig), 0x90
> > > .skip len(repl2) - len(repl1), 0x90
> > >
> > > BUT!, for some reason I
Previous algorithm had an outer loop with the values {2,3,5,7} and an
inner loop with {2,4,6,8,16,32,...,32768}, and would pick the first
value over the required scaling value (where the total scale was the two
numbers multiplied).
Since the inner loop went up to 32768 it would always pick a
Adding fsl,spi-cs-sck-delay and fsl,spi-sck-cs-delay properties to
support delays before and after starting the clock in a transfer.
Signed-off-by: Aaron Brice
---
Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt | 8
1 file changed, 8 insertions(+)
diff --git
We were having intermittent problems writing to SRAM chip on SPI bus on vf610
SoM. Added support for CS setup and hold times to meet the SRAM spec. In the
process noticed that the baud rate was a little high.
Changes since v2:
* Incorporate fixes per Stefen Agner review, namely moved
It is copied from asm-generic, the related error with allmodconfig:
CC [M] sound/core/pcm_native.o
sound/core/pcm_native.c: In function 'snd_pcm_lib_default_mmap':
sound/core/pcm_native.c:3387:24: error: implicit declaration of function
'pgprot_writecombine'
Hi,
On Fri, Mar 27, 2015 at 11:49:26AM -0500, Kumar Gala wrote:
> The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
>
> Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
>
> are available in the git repository at:
>
>
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem: there is a fix for ALPS
driver for issue introduced in the latest update and a tweak for yet
another Lenovo box in Synaptics.
There will be
On Fri 2015-04-03 14:23:56, Sakari Ailus wrote:
> Hi Pavel,
>
> On Fri, Apr 03, 2015 at 10:23:44AM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > Hi Pawel,
> >
> > I'm still Pavel. v, not w.
>
> I know too many Pawels. Sorry about that. :-)
>
> > I guess it uses adp1653_id_table. I'd hade to
Documentation for adp1653 binding.
---
> Please split this as Javier suggested. I'd think both could go through
> the media-tree unless someone objects.
Please apply.
> > + - power-gpios: Reference to the GPIO that controls the power for the
> > chip.
>
> You're using power-gpios in
On Fri, Mar 27, 2015 at 11:38:49AM -0500, Kumar Gala wrote:
> The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
>
> Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
>
> are available in the git repository at:
>
>
On Fri, 2015-04-03 at 14:45 +0200, Filip Brozović wrote:
> On 4/3/2015 2:01 PM, Paul Bolle wrote:
> > On Fri, 2015-04-03 at 12:44 +0200, Filip Brozovic wrote:
> >> --- a/arch/powerpc/platforms/83xx/Kconfig
> >> +++ b/arch/powerpc/platforms/83xx/Kconfig
> >
> >> +# used for gpio
> >> +config
On Fri, Mar 27, 2015 at 11:34:51AM -0500, Kumar Gala wrote:
> The following changes since commit 9eccca0843205f87c00404b663188b88eb248051:
>
> Linux 4.0-rc3 (2015-03-08 16:09:09 -0700)
>
> are available in the git repository at:
>
>
The related error with allmodconfig:
CC [M] fs/coda/psdev.o
In file included from include/linux/coda.h:64:0,
from fs/coda/psdev.c:45:
include/uapi/linux/coda.h:221:2: error: unknown type name 'u_quad_t'
u_quad_t va_size; /* file size in bytes */
^
> > The I2C specs say in 3.1.16 that the recovery procedure should be used
> > when SDA is stuck low. So, I do wonder if we should apply the recovery
> > after a timeout. Stuck SDA might be one reason for timeout, but there
> > may be others...
>
> This is ancient code. And regarding your
On Fri, Apr 03, 2015 at 09:44:48PM +0200, Stefan Agner wrote:
> In order to support SoC with heterogenous CPU architectures (such
> as Freescale Vybrid/i.MXSX) it is preferable to use the same
> architecture (ARCH_MXC in this case) for the MMU enabled and !MMU
> CPU. Hence allow to select
> On 31 March 2015 at 17:17 David Miller wrote:
>
>
> From: YOSHIFUJI Hideaki
> Date: Tue, 31 Mar 2015 12:50:27 +0900
>
> > Hi,
> >
> > Fabian Frederick wrote:
> >> Signed-off-by: Fabian Frederick
> >> ---
> >> net/ipv6/addrconf.c | 3 +--
> >> net/ipv6/esp6.c
1 - 100 of 1158 matches
Mail list logo
