The ses->auth_key.len field should be zeroed out during error paths,
along with the 'response' field.
Rationale:
It is possible with a specially crafted SMB2 server to cause the setup
to free the key but keep the session. When the session is recovered
(after a connection drop, for example), the
Sudhir Sreedharan writes:
> In ST16650V2 based serial uarts, while initalizing the PM state,
> LCR registers are being initialized to 0 in serial8250_set_sleep().
> If console port is already initialized and being used, this will
> throws garbage in the console.
>
> Signed-off-by: Sudhir
On Mon, 20 Oct 2014, Krzysztof Kozlowski wrote:
> Add a "maxim,max77693-charger" of_compatible to the mfd_cell so the MFD
> child device (the charger) will have its own of_node set. This will be
> used by the max77693 charger driver in next patches to obtain battery
> configuration from DTS.
>
>
On Mon, Sep 08, 2014 at 02:37:50PM -0300, Henrique de Moraes Holschuh wrote:
> Enhance the logging in the Intel early microcode update driver to
> be able to report errors.
>
> Signed-off-by: Henrique de Moraes Holschuh
> ---
> arch/x86/kernel/cpu/microcode/intel_early.c | 94
>
On pon, 2014-10-20 at 16:06 +0100, Lee Jones wrote:
> On Mon, 20 Oct 2014, Krzysztof Kozlowski wrote:
>
> > Add a "maxim,max77693-charger" of_compatible to the mfd_cell so the MFD
> > child device (the charger) will have its own of_node set. This will be
> > used by the max77693 charger driver in
Sebastian,
On Mon, Oct 20, 2014 at 04:37:51PM +0200, Sebastian Hesselbarth wrote:
> On 16.10.2014 11:53, Antoine Tenart wrote:
> >On Thu, Oct 09, 2014 at 02:38:58PM +0200, Sebastian Hesselbarth wrote:
> >>This patch series deals with a removing a IP feature that can be found
> >>on all currently
On 10/17/2014 06:46 PM, Martin K. Petersen wrote:
>> "Petr" == Petr Vandrovec writes:
>
> Petr> is there any reason to do blacklisting? Why not let first request
> Petr> fail, and switch to non-write-same code path once that happens?
>
> Well, we do. But we try to avoid confusing users
The activate_kmem_mutex is used to serialize memcg.kmem.limit updates,
but we already serialize them with memcg_limit_mutex so let's remove the
former.
Signed-off-by: Vladimir Davydov
---
mm/memcontrol.c | 24 +---
1 file changed, 5 insertions(+), 19 deletions(-)
diff
On Fri, 2014-10-10 at 12:51 +0100, Stefano Stabellini wrote:
> The feature has been removed from Xen. Also Linux cannot use it on ARM32
> without CONFIG_ARM_LPAE.
>
> Signed-off-by: Stefano Stabellini
> Reviewed-by: David Vrabel
Acked-by: Ian Campbell
--
To unsubscribe from this list: send
On Sun, 19 Oct 2014 19:39:17 -0700
Randy Dunlap wrote:
> Fix media DocBook build errors by making the orderedlist balanced.
That definitely makes things work better. Will send upward if need be.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Fri 17-10-14 18:10:21, Oleg Nesterov wrote:
> On 10/17, Michal Hocko wrote:
> >
> > I think we should rather get back to __thaw_task here.
>
> Yes, agreed.
>
> > Andrew could you replace the previous version by this one, please?
>
> Yes, that patch should be dropped...
>
>
> And can't
Do not look up the page_cgroup when the memory controller is
runtime-disabled, but do assert that the locking protocol is followed
under DEBUG_VM regardless. Also remove the unused flags variable.
Signed-off-by: Johannes Weiner
---
mm/memcontrol.c | 7 ---
1 file changed, 4 insertions(+),
Am 20.10.2014 um 16:46 schrieb Artem Bityutskiy:
> On Thu, 2014-10-16 at 12:06 +0200, Richard Weinberger wrote:
>> Am 14.10.2014 um 12:23 schrieb Artem Bityutskiy:
>>> On Mon, 2014-10-13 at 23:04 +0200, Richard Weinberger wrote:
Am 13.10.2014 um 17:23 schrieb Artem Bityutskiy:
> Well,
On Fri, 2014-10-10 at 12:51 +0100, Stefano Stabellini wrote:
> Use is_dma_coherent to check whether we need to issue cache maintenance
> operations rather than checking on the existence of a particular
> dma_ops function for the device.
>
> Signed-off-by: Stefano Stabellini
Acked-by: Ian
On Fri, 2014-10-10 at 12:51 +0100, Stefano Stabellini wrote:
> Merge xen/mm32.c into xen/mm.c.
> As a consequence the code gets compiled on arm64 too: introduce a few
> compat functions to actually be able to compile it.
>
> Signed-off-by: Stefano Stabellini
Acked-by: Ian Campbell
--
To
On 10/07/2014 11:33 AM, Vlastimil Babka wrote:
Deferred compaction is employed to avoid compacting zone where sync direct
compaction has recently failed. As such, it makes sense to only defer when
a full zone was scanned, which is when compact_zone returns with
COMPACT_COMPLETE. It's less useful
[Re: [PATCH 3/7] wait.[ch]: Introduce the simple waitqueue (swait)
implementation] On 18/10/2014 (Sat 19:05) Steven Rostedt wrote:
> On Sat, 2014-10-18 at 23:34 +0200, Peter Zijlstra wrote:
>
> > Same comment as before, that is an unbounded loop in a non preemptible
> > section and therefore
Hi,
this series gets rid of the remaining page_cgroup flags, thus cutting
the memcg per-page overhead down to one pointer.
include/linux/page_cgroup.h | 12
mm/memcontrol.c | 154 ++
2 files changed, 64 insertions(+), 102 deletions(-)
pc->mem_cgroup had to be left intact after uncharge for the final LRU
removal, and !PCG_USED indicated whether the page was uncharged. But
since 0a31bc97c80c ("mm: memcontrol: rewrite uncharge API") pages are
uncharged after the final LRU removal. Uncharge can simply clear the
pointer and the
PCG_MEM is a remnant from an earlier version of 0a31bc97c80c ("mm:
memcontrol: rewrite uncharge API"), used to tell whether migration
cleared a charge while leaving pc->mem_cgroup valid and PCG_USED set.
But in the final version, mem_cgroup_migrate() directly uncharges the
source page, rendering
Now that mem_cgroup_swapout() fully uncharges the page, every page
that is still in use when reaching mem_cgroup_uncharge() is known to
carry both the memory and the memory+swap charge. Simplify the
uncharge path and remove the PCG_MEMSW page flag accordingly.
Signed-off-by: Johannes Weiner
---
mem_cgroup_swapout() is called with exclusive access to the page at
the end of the page's lifetime. Instead of clearing the PCG_MEMSW
flag and deferring the uncharge, just do it right away. This allows
follow-up patches to simplify the uncharge code.
Signed-off-by: Johannes Weiner
---
Commit-ID: 961b6a7003acec4f9d70dabc1a253b783cb74272
Gitweb: http://git.kernel.org/tip/961b6a7003acec4f9d70dabc1a253b783cb74272
Author: Jiang Liu
AuthorDate: Mon, 20 Oct 2014 22:45:27 +0800
Committer: Thomas Gleixner
CommitDate: Mon, 20 Oct 2014 17:23:00 +0200
x86: ACPI: Do not
On 10/07/2014 11:33 AM, Vlastimil Babka wrote:
Compaction caches the migration and free scanner positions between compaction
invocations, so that the whole zone gets eventually scanned and there is no
bias towards the initial scanner positions at the beginning/end of the zone.
The cached
Fix checkpatch.pl "space prohibited before that close parenthesis ')'" errors
Signed-off-by: Greg Donald
---
drivers/staging/lustre/lustre/include/lustre_capa.h | 2 +-
drivers/staging/lustre/lustre/llite/dir.c | 2 +-
drivers/staging/lustre/lustre/llite/vvp_io.c| 2 +-
On Mon, Oct 20, 2014 at 3:49 AM, Catalin Marinas
wrote:
>
> Since you mention symmetry, something like below makes the barriers more
> explicit.
Borken, for two reasons:
> diff --git a/kernel/futex.c b/kernel/futex.c
> index f3a3a071283c..5b9d857d0816 100644
> --- a/kernel/futex.c
> +++
Commit 9447057eaff8 ("platform_device: use a macro instead of
platform_driver_register") introduced a codepath which could result into
drivers having no owner. This went unnoticed for months, so add a
warning in case this happens again somewhere else somewhen.
Signed-off-by: Wolfram Sang
---
Since platform_register_driver() was converted to set the .owner of a driver,
there was a codepath on which the owner would have been erased. This series
fixes that and adds a warning to prevent such cases go unnoticed in the future.
For consistency, a semantic patch is also added which reports
Since commit 9447057eaff8 ("platform_device: use a macro instead of
platform_driver_register"), platform_driver_register() always overwrites
the .owner field of a platform_driver with THIS_MODULE. This breaks
platform_driver_probe() which uses it from within the platform core
instead of the module
Since commit 9447057eaff8 ("platform_device: use a macro instead of
platform_driver_register"), platform_driver_register() always overwrites
the .owner field of a platform_driver with THIS_MODULE. This breaks
platform_create_bundle() which uses it via platform_driver_probe() from
within the
There are calls which silently set the owner of a module. This is the
preferred way [1], so avoid setting it manually. Currently, we only care
about platform drivers, but there might be more calls to be added later.
[1] https://lkml.org/lkml/2014/10/12/87
Signed-off-by: Wolfram Sang
---
From: Hao Liang
Date: Mon, 20 Oct 2014 16:55:08 +0800
> I can't quite seize David's meaing whether the ->mac->xxx should
> inside the lock or outside the lock. In my opinion, the ->mac->xxx
> calls did not operate any shared data or struct. The calls just
> control the hardware by write data to
On Sun, Oct 19, 2014 at 12:13:10AM +0200, Rickard Strandqvist wrote:
> Ensures that the string is null-terminate in connection with the
> use of strncpy, by switching from strncpy to strzcpy.
>
I wish the changelogs were more clear that we have no reason to think
this is a real issue.
>
On 20.10.14 19:26:32, Abhilash Kesavan wrote:
> >> > > > > Robert Richter (6):
> >> > > > > dts, arm64: Add dtbs_install make target
> >> > > > > dts, kbuild: Factor out dtbs install rules to Makefile.dtbinst
> >> > > > > dts, arm/arm64: Remove dtbs build rules in sub-makes
> >> > > > >
On Fri, Oct 17, 2014 at 10:10:26AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Fri, Oct 17, 2014 at 04:53:25PM +0800, Huang Rui wrote:
> > The series of patches add AMD NL SoC support for DesignWare USB3 OTG
> > IP with PCI bus glue layer. This controller supported hibernation, LPM
> > erratum and
On Mon, 20 Oct 2014 11:21:44 -0400
Paul Gortmaker wrote:
> > Right, and we should slap Paul for not showing up for it ;-)
>
> And miss turkey day? ;-)
Replace it with Alt Beer day!
> I'd like to hear more details on what you had in mind here, so I don't
> go chasing down the wrong road. So
On Mon, 2014-10-20 at 17:17 +0200, Richard Weinberger wrote:
> > That's just fastmap code not doing the right thing. We should not touch
> > the work queue directly at all. What we _should_ do instead is to make
> > it empty by asking the subsystem which manages it to flush it.
> >
> > 1. Lock
On Fri, 10 Oct 2014 18:26:42 +0800
Wanpeng Li wrote:
> > ERROR: Please use 12 or more chars for the git commit ID like: 'commit
> > 10447917551e ("sched/rt: Do not try to push tasks if pinned task switches
> > to RT")'
> > #12:
> > which introduced by commit 104479 (sched/rt: Do not try to
On 10/07/2014 11:33 AM, Vlastimil Babka wrote:
The goal of memory compaction is to create high-order freepages through page
migration. Page migration however puts pages on the per-cpu lru_add cache,
which is later flushed to per-cpu pcplists, and only after pcplists are
drained the pages can
On 10/07/2014 11:33 AM, Vlastimil Babka wrote:
Compaction relies on zone watermark checks for decisions such as if it's worth
to start compacting in compaction_suitable() or whether compaction should stop
in compact_finished(). The watermark checks take classzone_idx and alloc_flags
parameters,
On Tue, 14 Oct 2014 10:25:52 +0100
Mark Rutland wrote:
> Following the discussion around [1], this makes sense to me, so:
>
> Acked-by: Mark Rutland
Applied to my shiny new docs tree in case nobody else grabs it.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Fri, 2014-10-10 at 12:51 +0100, Stefano Stabellini wrote:
> Introduce support for new hypercall GNTTABOP_cache_flush.
> Use it to perform cache flashing on pages used for dma when necessary.
>
> If GNTTABOP_cache_flush is supported by the hypervisor, we don't need to
> bounce dma map
If we fail to reclaim anything from a cgroup during a soft reclaim pass
we want to get the next largest cgroup exceeding its soft limit. To
achieve this, we should obviously remove the current group from the tree
and then pick the largest group. Currently we have a weird loop instead.
Let's
On Mon, Oct 20, 2014 at 10:37 AM, Geert Uytterhoeven
wrote:
> Hi all,
>
> Below is the bloat-o-meter output when comparing an m68k/atari_defconfig
> kernel for v3.17 and v3.18-rc1.
>
> Major culprit seems to be bpf. Can this become modular or optional?
> Currently it's always included if
Fix checkpatch.pl 'that open brace { should be on the previous line' errors
Signed-off-by: Greg Donald
---
drivers/staging/lustre/lustre/ldlm/ldlm_pool.c | 3 +--
drivers/staging/lustre/lustre/libcfs/hash.c| 25 +
2 files changed, 10 insertions(+), 18 deletions(-)
Am 20.10.2014 um 17:40 schrieb Artem Bityutskiy:
> On Mon, 2014-10-20 at 17:17 +0200, Richard Weinberger wrote:
>>> That's just fastmap code not doing the right thing. We should not touch
>>> the work queue directly at all. What we _should_ do instead is to make
>>> it empty by asking the
On Mon, Oct 20, 2014 at 04:32:00PM +0100, Linus Torvalds wrote:
> On Mon, Oct 20, 2014 at 3:49 AM, Catalin Marinas
> wrote:
> > Since you mention symmetry, something like below makes the barriers more
> > explicit.
>
> Borken, for two reasons:
>
> > diff --git a/kernel/futex.c b/kernel/futex.c
[Re: [PATCH 3/7] wait.[ch]: Introduce the simple waitqueue (swait)
implementation] On 20/10/2014 (Mon 11:40) Steven Rostedt wrote:
> On Mon, 20 Oct 2014 11:21:44 -0400
> Paul Gortmaker wrote:
>
> > > Right, and we should slap Paul for not showing up for it ;-)
> >
> > And miss turkey day?
On Sun, Oct 19, 2014 at 7:39 PM, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix media DocBook build errors by making the orderedlist balanced.
>
> DOC1/Documentation/DocBook/compat.xml:2576: parser error : Opening and ending
> tag mismatch: orderedlist line 2560 and section
>
On Mon, 2014-10-20 at 17:59 +0200, Richard Weinberger wrote:
> > Also, say, PEB X is in the work queue waiting for erasure. Fastmap comes
> > along and saves it as "must be erased" in the fastmap. Fastmap finishes
> > its job, PEB X gets erased, and I write my data there, so PEB X is
> > referred
Fix checkpatch.pl "'foo * bar' should be 'foo *bar'" errors
Signed-off-by: Greg Donald
---
drivers/staging/lustre/lustre/include/dt_object.h | 2 +-
drivers/staging/lustre/lustre/include/lprocfs_status.h | 2 +-
drivers/staging/lustre/lustre/include/lustre_dlm.h | 2 +-
Am 20.10.2014 um 18:09 schrieb Artem Bityutskiy:
> On Mon, 2014-10-20 at 17:59 +0200, Richard Weinberger wrote:
>>> Also, say, PEB X is in the work queue waiting for erasure. Fastmap comes
>>> along and saves it as "must be erased" in the fastmap. Fastmap finishes
>>> its job, PEB X gets erased,
On Thu, Oct 16, 2014 at 7:41 PM, David Cohen
wrote:
> Hi Bjorn and Sathya,
>
> On Thu, Oct 16, 2014 at 05:42:11PM -0700, sathyanarayanan kuppuswamy wrote:
>> Hi Bjorn,
>>
>> On 10/15/2014 04:26 PM, Bjorn Helgaas wrote:
>> >[+cc David, Kuppuswamy, x86; sorry, I botched my "stg mail" so you
>>
(Cc'ing Peter Zijlstra for comments)
On Thu, 16 Oct, at 11:44:10AM, vikas wrote:
> Hi All , We have put together a draft design document for cache
> allocation technology below. Please review the same and let us know any
> feedback.
>
> Make sure you cc my email vikas.shiva...@linux.intel.com
On Fri, Oct 17, 2014 at 1:59 AM, Vineet Gupta
wrote:
> On Thursday 16 October 2014 07:08 PM, Vineet Gupta wrote:
>> On Thursday 16 October 2014 05:05 AM, Bjorn Helgaas wrote:
>>> > [+cc Harvey, Vineet, linux-sh; arc, sh, and x86 have kgdb_arch_pc()
>>> > definitions and could see issues from
After a long stint maintaining the audit tree, Eric asked me to step
in and handle the day-to-day management of the audit tree. We should
also update the linux-audit mailing list entry to better reflect
current usage.
Signed-off-by: Paul Moore
---
MAINTAINERS |5 +++--
1 file changed, 3
In order to prevent a pointless forward declaration, just move the function
at the beginning of the file.
This patch does not change the behavior of the governor, it is just code
reordering.
Signed-off-by: Daniel Lezcano
---
drivers/cpuidle/governors/menu.c | 149
Javier,
On Thu, Oct 16, 2014 at 3:13 AM, Javier Martinez Canillas
wrote:
> The regulator framework has a set of helpers functions to be used when
> the system is entering and leaving from suspend but these are not called
> on Exynos platforms. This means that the .set_suspend_* function handlers
The first time the 'get_typical_function' is called, it computes an average
of zero as no data is filled yet. That leads the 'data->predicted_us' variable
to be set to zero too.
The caller, 'menu_select' will then do:
interactivity_req = data->predicted_us /
In the current code, the check to reflect or not the outcoming state is done
against the idle state which has been choose and its value.
Instead of doing a check in each of the reflect functions, just don't call
reflect
if something went wrong in the idle path.
Signed-off-by: Daniel Lezcano
When the pmqos latency requirement is set to zero that means "poll in all the
cases".
That is correctly implemented on x86 but not on the other archs.
As how is written the code, if the latency request is zero, the governor will
return zero, so corresponding, for x86, to the poll function, but
Following the logic of the previous patch, retrieve from the idle task the
expected timer sleep duration and pass it to the cpuidle framework.
Take the opportunity to remove the unused headers in the menu.c file.
This patch does not change the current behavior.
Signed-off-by: Daniel Lezcano
Am 2014-10-03 15:31, schrieb Stefan Agner:
> So far, the required PLL's (PLL1/PLL2/PLL5) have been initialized
> by boot loader and the kernel code defined fixed rates according
> to those default configurations. Beginning with the USB PLL7 the
> code started to initialize the PLL's itself (using
Debian backports security patches (etc) to its stable distribution, which can
be used for years and years.
RHEL does too, but this costs subscription money.
If debian becomes unstable (via systemd etc) and ever more subject to churn,
that's some competition out of the way.
Future: if you want
When CONFIG_MIPS_MT is defined, code is enabled that tries to call
'set_vi_handler()'. This function is declared in but the
header is never included. Therefore, the compilation breaks.
arch/mips/pmcs-msp71xx/msp_irq.c:133: error: implicit declaration of function
'set_vi_handler'
This error was
Fix checkpatch.pl "spaces required around that '='" errors
Signed-off-by: Greg Donald
---
drivers/staging/lustre/lustre/llite/super25.c | 2 +-
drivers/staging/lustre/lustre/obdclass/genops.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
The driver was also using own method to do 32bit copy, turns out
we have a kernel API so use that instead
Signed-off-by: Vinod Koul
---
drivers/mtd/nand/mxc_nand.c | 10 +++---
1 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/mtd/nand/mxc_nand.c
The driver was also using own method to do 32bit copy, turns out
we have a kernel API so use that instead
Signed-off-by: Vinod Koul
---
drivers/mtd/nand/atmel_nand.c | 10 +++---
1 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/mtd/nand/atmel_nand.c
Ok, I will describe my problem. Guenter, maybe you can find
another solution/fix for it.
Calling i8k_get_temp(3) on my laptop without I8K_TEMPERATURE_BUG
always returns value 193 (which is above I8K_MAX_TEMP).
When I8K_TEMPERATURE_BUG is enabled (by default) then
i8k_get_temp(3) returns value
* Pavel Machek [141020 06:10]:
> Hi!
>
> > My N900 can boot kernel from v3.12-rc5-n900 branch compiled with
> > arch/arm/configs/rx51_defconfig. Also it can boot full Maemo5
> > system (with CSSU and some minor system changes) and usb network
> > via g_nokia.ko gadget working fine...
> >
> >
On Mon, 20 Oct 2014 12:05:42 -0400
Paul Gortmaker wrote:
> > No. You move the items off the main list head and add it to the local
> > list and they never go back. Just start processing that local list.
> > Anything added to the main list after that will not get woken up by
> > that current
On Mon, Oct 20, 2014 at 1:33 AM, Peter Zijlstra wrote:
> On Sun, Oct 19, 2014 at 03:57:54PM -0700, Andy Lutomirski wrote:
>> > Maybe, but at that point we commit to yet another ABI... I'd rather just
>> > put a 'sane' implementation in a library or so.
>>
>> This cuts both ways, though. For vdso
On 10/20/2014 05:04 AM, Vidya Sagar wrote:
Enables root port to advertise its ASPM-L1 capability
resulting in possible link entry to L1 when an ASPM-L1 capable
device is connected
Enables per-controller & per-TMS clock clamping by default
Enabling above features result in more power saving
It
On 10/20/2014 4:51 PM, Artem Bityutskiy wrote:
On Tue, 2014-10-14 at 09:05 -0700, Joe Perches wrote:
It's pretty trivial when all the lines are already
being touched.
OK, but then the same change should done in UBIFS, because it's
ubifs_msg() and so on macros are consistent with UBI macros.
If there is more then one UBI device mounted, there is no way to
distinguish between messages from different UBI devices.
Add device number to all ubi layer message types.
The R/O block driver messages were replaced by pr_* since
ubi_device structure is not used by it.
Signed-off-by: Tanya
[adding Chris Zong as cc who posted a similar patch for Rockchip]
Hello Doug,
On 10/20/2014 06:26 PM, Doug Anderson wrote:
> Javier,
>
> On Thu, Oct 16, 2014 at 3:13 AM, Javier Martinez Canillas
> wrote:
>> The regulator framework has a set of helpers functions to be used when
>> the system is
On 10/20, Oleg Nesterov wrote:
>
> Again, perhaps we will need to change the lifetime rules for task_struct
> anyway, if we have more problems like this. But until then this looks like
> an overkill to me. Plus rq_curr_if_not_put() looks too subtle, and it is
> not generic.
Yes... otoh, perhaps
On 10/20/14 07:53, Masanari Iida wrote:
> This patch fix spelling typos found in drm.xml.
> It is because the file is generated from comments in
> source codes, I have to fix the typos within source files.
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
>
On Mon, Oct 20, 2014 at 3:40 AM, Neil Zhang wrote:
> Greg,
>
>
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: 2014年10月20日 14:48
> To: Neil Zhang
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] drivers: base: update cpu offline info when do
On 20/10/2014 at 16:10:31 +0300, Vladimir Zapolskiy wrote :
> Hi Alexandre,
>
> On 20.10.2014 13:29, Alexandre Belloni wrote:
> > Hi,
> >
> > On 20/10/2014 at 00:22:57 +0300, Vladimir Zapolskiy wrote :
> >>> +struct sun4i_pwm_chip {
> >>> + struct pwm_chip chip;
> >>> + struct clk *clk;
> >>> +
do_gettimeofday() only can get 32-bit time types
but the driver should be able to use dates that are
after January 2038.
Remove do_gettimeofday() and use
jiffies comparison to supply 64-bit time types.
Signed-off-by: Ebru Akagunduz
---
drivers/scsi/ips.c | 25 +
On Thursday 16 October 2014 14:47:41 Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman
>
> The Android binder code has been "stable" for many years now. No matter
> what comes in the future, we are going to have to support this API, so
> might as well move it to the "real" part of the kernel
On 10/20/14 09:06, Vincent Palatin wrote:
> On Sun, Oct 19, 2014 at 7:39 PM, Randy Dunlap wrote:
>> From: Randy Dunlap
>>
>> Fix media DocBook build errors by making the orderedlist balanced.
>>
>> DOC1/Documentation/DocBook/compat.xml:2576: parser error : Opening and
>> ending tag mismatch:
On Mon, Oct 20, 2014 at 10:05 AM, Michael S. Tsirkin wrote:
> On Mon, Oct 20, 2014 at 03:58:49PM +0200, Cornelia Huck wrote:
>> Commit f5866db6 (virtio_console: enable VQs early) tried to make
>> sure that DRIVER_OK was set when virtio_console started using its
>> virtqueues. Doing this in
Hi,
On Thu, Aug 21, 2014 at 2:12 PM, Frank Seidel wrote:
> Am Wed, 20 Aug 2014 14:09:53 -0700 Jim Davis
> wrote:
>> On Wed, Aug 20, 2014 at 2:05 PM, SeongJae Park
>> wrote:
>> > On Thu, Aug 21, 2014 at 5:29 AM, Jim Davis
>> > wrote:
>> >> The linux-next wiki at
This patch swaps the use "tail" and "head" to fit the semantic of the linux
circular buffer documentation:
- head: the point at which the producer (the DMA controller) inserts items.
- tail: the point at which the consumer (the serial framework) finds the next
item.
Besides the former
On 10/17/2014 02:11 AM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.31 release.
> There are 197 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
On Mon, Oct 20, 2014 at 10:08 AM, Randy Dunlap wrote:
> On 10/20/14 09:06, Vincent Palatin wrote:
>> On Sun, Oct 19, 2014 at 7:39 PM, Randy Dunlap wrote:
>>> From: Randy Dunlap
>>>
>>> Fix media DocBook build errors by making the orderedlist balanced.
>>>
>>>
On Wed, Oct 15, 2014 at 04:06:52AM +0100, Yijing Wang wrote:
> Saving msi chip in pci_sys_data can make pci bus and
> devices don't need to know msi chip detail, it also
> make pci enumeration code be decoupled from msi chip.
> In fact, all pci devices under the same pci hostbridge
> share same
On Sat, Oct 11, 2014 at 02:15:34AM +0100, Guenter Roeck wrote:
> Fix:
>
> In file included from ./arch/arm64/include/asm/irq_work.h:4:0,
> from include/linux/irq_work.h:46,
> from include/linux/perf_event.h:49,
> from include/linux/ftrace_event.h:9,
> from
Fix media DocBook build errors by re-adding the orderedlist tag
and putting back the section tags lost during merge.
Signed-off-by: Vincent Palatin
---
Documentation/DocBook/media/v4l/compat.xml | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/DocBook/media/v4l/compat.xml
Hi,
Am 20.10.2014 um 11:35 schrieb Mark Rutland :
> Hi,
>
> On Fri, Oct 17, 2014 at 08:55:50PM +0100, Dr. H. Nikolaus Schaller wrote:
>>
>> Am 17.10.2014 um 13:00 schrieb Mark Rutland :
>>
>>> On Fri, Oct 17, 2014 at 11:16:42AM +0100, Dr. H. Nikolaus Schaller wrote:
Am 17.10.2014
On Mon, 2014-10-20 at 19:54 +0300, Tanya Brokhman wrote:
> On 10/20/2014 4:51 PM, Artem Bityutskiy wrote:
> > On Tue, 2014-10-14 at 09:05 -0700, Joe Perches wrote:
> >> It's pretty trivial when all the lines are already
> >> being touched.
> >
> > OK, but then the same change should done in UBIFS,
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
(The term "fine" is exceptional to this already reported issue :
$> modprobe nf_reject_ipv4
modprobe: ERROR: could not insert 'nf_reject_ipv4': Unknown symbol in module,
On Mon, Oct 20, 2014 at 07:06:04PM +0200, Alexandre Belloni wrote:
> Because the PWM is getting configured from either a kernel thread or a
> userspace thread accessing /sys. So you probably want the current thread
> to sleep so the other thread accessing the register can finish. Unless
> you are
Javier,
On Mon, Oct 20, 2014 at 9:58 AM, Javier Martinez Canillas
wrote:
>> It turns out that regulator_suspend_finish() actually returns an error
>> code. Could you print a warning if you see it?
>>
>
> Yes, I noticed this when looking at Chris patch for Rockchip but didn't
> re-spin
>
On Mon, Oct 20, 2014 at 9:49 AM, Andy Lutomirski wrote:
> On Mon, Oct 20, 2014 at 1:33 AM, Peter Zijlstra wrote:
>> On Sun, Oct 19, 2014 at 03:57:54PM -0700, Andy Lutomirski wrote:
>>> > Maybe, but at that point we commit to yet another ABI... I'd rather just
>>> > put a 'sane' implementation in
On Mon, 2014-10-20 at 20:06 +0300, Ebru Akagunduz wrote:
> do_gettimeofday() only can get 32-bit time types
> but the driver should be able to use dates that are
> after January 2038.
>
> Remove do_gettimeofday() and use
> jiffies comparison to supply 64-bit time types.
>
> Signed-off-by: Ebru
On 20.10.2014 20:06, Alexandre Belloni wrote:
> On 20/10/2014 at 16:10:31 +0300, Vladimir Zapolskiy wrote :
>> Hi Alexandre,
>>
>> On 20.10.2014 13:29, Alexandre Belloni wrote:
>>> Hi,
>>>
>>> On 20/10/2014 at 00:22:57 +0300, Vladimir Zapolskiy wrote :
> +struct sun4i_pwm_chip {
> + struct
On 10/20, Michal Hocko wrote:
>
> On Fri 17-10-14 18:10:21, Oleg Nesterov wrote:
>
> > And if this is not safe, it is not clear how/why cgroup_freezing() can
> > save us, both pm_freezing and CGROUP_FREEZING can be true?
>
> You mean that the pm_freezer would race with cgroup one?
Yes, so if we
301 - 400 of 1578 matches
Mail list logo
