* Kishon Vijay Abraham I [140904 06:51]:
> Hi Tony,
>
> On Thursday 28 August 2014 04:58 AM, Tony Lindgren wrote:
> > We don't need twl4030_phy_power() any longer now that we have
> > the runtime PM calls. Let's get rid of it as it's confusing.
> > No functional changes, just move the code and us
On 09/04, Denys Vlasenko wrote:
>
> or thunk_ra should be renamed to THUNK (like it is in thunk_64.S)
Of course! Thanks a lot Denys.
Oleg.
--
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
On Thu, Sep 4, 2014 at 6:20 AM, Kirill Smelkov wrote:
> Commit 75897d60 (hugetlb: allow sticky directory mount option) added
> support for mounting hugetlbfs with sticky option set, like /tmp is
> usually mounted, but forgot to document that.
>
> Cc: Ken Chen
> Signed-off-by: Kirill Smelkov
> --
I'm not pretending to merge it now (and that why I sent a link to repository
instead of patches), but,
probably, there are guys here, who can try it and save a bit of hardware.
Regards,
Roman
04.09.2014, 20:49, "Peter Zijlstra" :
> No, we're not going to merge a second rt balancer. If you want
___preempt_schedule() does SAVE_ALL/RESTORE_ALL but this is suboptimal,
we do not need to save/restore the callee-saved register. And we already
have arch/x86/lib/thunk_*.S which implements the similar asm wrappers,
so it makes sense to redefine ___preempt_schedule() as "THUNK ..." and
remove preem
On Mon, Sep 1, 2014 at 1:59 PM, Dmitry Eremin-Solenikov
wrote:
> Back in the time before DTS conversion started, the 0 was a correct GPIO
> number. If somebody wanted to specify that no gpio is provided, he provided
> -1 as an invalid number. I have the feeling that allowing users to use 0 as
> '
Il 04/09/2014 18:00, Chris J Arges ha scritto:
> Uptime:
> 15:58:02 up 1:00, 1 user, load average: 0.59, 0.60, 0.31
>
> Here is the output:
>
> ./x86-run x86/kvmclock_test.flat -smp 2 --append "1000 `date +%s`"
> qemu-system-x86_64 -enable-kvm -device pc-testdev -device
> isa-debug-exit,i
The "br_port" local variables obtained through the rcu_dereference() calls are
not dereferenced in the rest of their function.
Therefore, it is recommended to use rcu_access_pointer() instead of
rcu_dereference().
This patch makes the replacements.
The first step to detect this was made with the f
On Tue, Sep 02, 2014 at 10:00:07AM -0500, Christoph Lameter wrote:
> Subject: irqchip: Properly fetch the per cpu offset
>
> The raw_cpu_read() conversion dropped the fetch of the offset
> from base->percpu_base in gic_get_percpu_base.
>
> Signed-off-by: Christoph Lameter
>
> Index: linux/drive
Il 04/09/2014 17:05, Gleb Natapov ha scritto:
>> > if (ctxt->have_exception) {
>> > inject_emulated_exception(vcpu);
>> > - r = EMULATE_DONE;
>> > + return EMULATE_DONE;
> If there was no vmexit we still want to writeback. Perhaps:
> writeback
On Mon, Sep 1, 2014 at 9:46 AM, Dirk Behme wrote:
> On 29.08.2014 21:01, Mark Brown wrote:
>> Any current boards should be using DT and so shouldn't be using fixed
>> GPIO numbers in the first place which will mean they'll not end up
>> getting zero as a valid GPIO.
>
> Hmm? What's wrong with a D
Thanks for the review - pls see comments below.
Mathieu
On 3 September 2014 02:37, Linus Walleij wrote:
> On Wed, Aug 27, 2014 at 7:17 PM, wrote:
>
>> From: Pratik Patel
>>
>> This driver manages CoreSight ETM (Embedded Trace Macrocell) that
>> supports processor tracing. Currently supported
On Wed, Sep 3, 2014 at 8:01 PM, Geert Uytterhoeven
wrote:
> PIN_CONFIG_DRIVE_OPEN_SOURCE enables open source, not open drain.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> Yes, we need more open source ;-)
Yeah, patch applied!
Yours,
Linus Walleij
--
To unsubscribe from this list: send the lin
On Thu, Sep 4, 2014 at 10:03 AM, Will Deacon wrote:
> Hi Kees,
>
> On Wed, Sep 03, 2014 at 10:57:04PM +0100, Kees Cook wrote:
>> This is used from set_fixmap() and clear_fixmap() via asm-generic/fixmap.h.
>> Also makes sure that the fixmap allocation fits into the expected range.
>>
>> Based on pa
On Thu, Sep 04, 2014 at 10:19:17AM +0100, Lee Jones wrote:
> Wim,
>
> Still waiting on a Watchdog Ack, so I can take this set in.
>
Wasn't there a more recent version of this patch ?
Thanks,
Guenter
> > This adds a driver for the watchdog timer available in Ricoh RN5T618
> > PMIC. The device su
From: Andi Kleen
Add support for reading PCU power metrics on Sandy Bridge / Ivy Bridge EP
and Haswell Server in turbostat. This is done using the perf ABI,
using the perf uncore driver. This requires the kernel to
have uncore perf driver support.
The PCU has a large number of events, but only a
On Thu, Sep 04, 2014 at 06:23:42PM +0100, Kees Cook wrote:
> On Thu, Sep 4, 2014 at 10:03 AM, Will Deacon wrote:
> > Hi Kees,
> >
> > On Wed, Sep 03, 2014 at 10:57:04PM +0100, Kees Cook wrote:
> >> This is used from set_fixmap() and clear_fixmap() via asm-generic/fixmap.h.
> >> Also makes sure tha
Am 04.09.2014 16:36, schrieb Austin S Hemmelgarn:
On 2014-09-04 06:16, Alexander Holler wrote:
It's a myth that C++ ends up in bigger code than C. At least in my
experience. Especially when the latest additions to C++ are in effect
(like the move-semantics in C++11 I like quiet a lot and which
On Thu, Sep 4, 2014 at 7:19 PM, Mathieu Poirier
wrote:
> [Me]:
>> I would rewrite the last function like this:
>>
>> static inline unsigned int etm_readl(struct etm_drvdata *drvdata, u32 off)
>> {
>>u32 val;
>>
>>if (drvdata->use_cp14)
>>asm_volatile()...
>>
On Thu, Sep 4, 2014 at 7:06 PM, Mark Brown wrote:
> On Thu, Sep 04, 2014 at 07:04:44PM +0200, Linus Walleij wrote:
>> I need an ACK from Mark Brown on this before I apply.
>> The driver seems to do what it should, but I need Mark to
>> be OK with exporting the CS signals from an SSP/SPI block
>> t
On Wed, Sep 03, 2014 at 09:18:42PM -0700, Doug Anderson wrote:
> Chris,
>
> On Wed, Sep 3, 2014 at 6:12 PM, Chris Zhong wrote:
> > Adding RTC driver for supporting RTC device present inside RK808 PMIC.
> >
> > Signed-off-by: Chris Zhong
> > Signed-off-by: Zhang Qing
> >
> > Tested-by: Heiko Stu
On Thu, Sep 04, 2014 at 10:25:03AM -0700, Guenter Roeck wrote:
> On Thu, Sep 04, 2014 at 10:19:17AM +0100, Lee Jones wrote:
> > Wim,
> >
> > Still waiting on a Watchdog Ack, so I can take this set in.
> >
> Wasn't there a more recent version of this patch ?
Yes, this is superseded by v2.
Beniam
On Sun, Aug 31, 2014 at 11:24:56PM +0800, Wang YanQing wrote:
> PL2303 USB Serial devices may has GPIOs, this patch add
> basic PL2303 gpio support.
>
> Known issue:
> If gpios are in use(export to userspace through sysfs interface, etc),
> then call pl2303_release(unplug usb-serial convertor, mod
Hi Chris,
On Thu, Sep 04, 2014 at 09:12:38AM +0800, Chris Zhong wrote:
> + rk808_clkout->clk_data.clks = clk_table;
> + rk808_clkout->clk_data.clk_num = RK808_NR_OUTPUT;
> +
> + return of_clk_add_provider(node, of_clk_src_onecell_get,
> +&rk808_clkout->c
Il 04/09/2014 17:05, Gleb Natapov ha scritto:
>> >
>> > If you do that, KVM gets down to the "if (writeback)" and writes the
>> > ctxt->eip from L2 into the L1 EIP.
> Heh, that's a bummer. We should not write back if an instruction caused a
> vmexit.
>
You're right, that works.
Paolo
---
On Thu, Sep 04, 2014 at 08:38:28AM -0400, Jeff Layton wrote:
> security_file_set_fowner always returns 0, so make it f_setown and
> __f_setown void return functions and fix up the error handling in the
> callers.
All the LSMs seems to use this purely for setting up pointers, and not
having to hand
On Wed, Sep 03, 2014 at 02:15:51PM -0700, Roland Dreier wrote:
> > I would like to note that we at Los Alamos National Laboratory are very
> > interested in this functionality and it would be great if it gets accepted.
>
> Have you done any review or testing of these changes? If so can you
> shar
On Thu, Sep 04, 2014 at 08:38:27AM -0400, Jeff Layton wrote:
> GFS2 and NFS have setlease routines that always just return -EINVAL.
> Turn that into a generic routine that can live in fs/libfs.c.
Looks good,
Reviewed-by: Christoph Hellwig
--
To unsubscribe from this list: send the line "unsubscr
On Thu, 04 Sep 2014, Borislav Petkov wrote:
> > Yes. It is a stop gap solution, I never claimed it to be anything
> > else.
> >
> > What I did claim is that it is going to be a far more user-friendly
> > stop gap than the "boot from rescue media" option.
>
> Ok, we have it now and we can use it if
On Thu, Sep 04, 2014 at 06:01:27PM +0100, Sonny Rao wrote:
[...]
> > If an OS is booted at PL2 it can access the physical counters, and
> > should do so in case something like KVM will be used later. The OS can
> > write to CNTVOFF at PL2, and if it sets CNTVOFF to zero the physical and
> > virtu
On Thu, Sep 04, 2014 at 08:38:34AM -0400, Jeff Layton wrote:
> In later patches, we're going to add a new lock_manager_operation to
> finish setting up the lease while still holding the i_lock. To do
> this, we'll need to pass a little bit of info in the fcntl setlease
> case (primarily an fasync
On Thu, Sep 04, 2014 at 08:38:35AM -0400, Jeff Layton wrote:
> ...and move the fasync setup into it for fcntl lease calls. At the same
> time, change the semantics of how the file_lock double-pointer is
> handled. Up until now, on a successful lease return you got a pointer to
> the lock on the lis
On Thu, Sep 04, 2014 at 06:01:27PM +0100, Sonny Rao wrote:
> On Fri, Aug 29, 2014 at 3:04 AM, Mark Rutland wrote:
> > On Fri, Aug 29, 2014 at 01:10:49AM +0100, Sonny Rao wrote:
> >> On Thu, Aug 28, 2014 at 2:35 AM, Mark Rutland wrote:
> >> > On Thu, Aug 28, 2014 at 04:33:31AM +0100, Doug Anderson
Looks good, but I'd rather merge it into the patch that changes the
semantics.
Reviewed-by: Christoph Hellwig
--
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-i
On Thu, Sep 04, 2014 at 08:38:39AM -0400, Jeff Layton wrote:
> I think that the intent of this code was to ensure that a process won't
> deadlock if it has one fd open with a lease on it and then breaks that
> lease by opening another fd. In that case it'll treat the __break_lease
> call as if it w
On Thu, Sep 04, 2014 at 08:38:37AM -0400, Jeff Layton wrote:
> There was only one place where we still could free a file_lock while
> holding the i_lock -- lease_modify. Add a new list_head argument to the
> lm_change operation, pass in a private list when calling it, and fix
> those callers to dis
On Thu, Sep 04, 2014 at 08:38:43AM -0400, Jeff Layton wrote:
> The contents of an fl_owner_t have morphed a bit over the years, fix up
> the comments to account for the changes.
Instead of listing all the owners I'd just put something in like:
/* legacy typedef, will go away soon */
--
To unsubsc
On Thu, Sep 04, 2014 at 09:14:12AM +0200, Pavel Machek wrote:
> > When CONFIG_PM_DEBUG=y, we provide a sysfs file (/sys/power/pm_test) for
> > selecting one of a few suspend test modes, where rather than entering a
> > full suspend state, the kernel will perform some subset of suspend
> > steps, wa
Il 04/09/2014 14:58, Paolo Bonzini ha scritto:
> Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
> based, 2014-07-16) forgot to add tk->xtime_sec, thus breaking kvmclock on
> hosts that have a reliable TSC. Add it back; and since the field boot_ns
> is not anymore rela
On 2014-09-04 13:29, Alexander Holler wrote:
> Am 04.09.2014 16:36, schrieb Austin S Hemmelgarn:
>> On 2014-09-04 06:16, Alexander Holler wrote:
>>>
>>> It's a myth that C++ ends up in bigger code than C. At least in my
>>> experience. Especially when the latest additions to C++ are in effect
>>> (
Add an attribute 'wakeup' to the GPIO sysfs interface which allows
marking/unmarking a GPIO as wake IRQ.
The file 'wakeup' is created in each exported GPIOs directory, if an IRQ
is associated with that GPIO and the irqchip implements set_wake().
Writing 'enabled' to that file will enable wake for t
Am Donnerstag, 4. September 2014, 10:40:24 schrieb Dmitry Torokhov:
> Hi Chris,
>
> On Thu, Sep 04, 2014 at 09:12:38AM +0800, Chris Zhong wrote:
> > + rk808_clkout->clk_data.clks = clk_table;
> > + rk808_clkout->clk_data.clk_num = RK808_NR_OUTPUT;
> > +
> > + return of_clk_add_provider(node,
On Thu, 4 Sep 2014 10:51:32 -0700
Christoph Hellwig wrote:
> On Thu, Sep 04, 2014 at 08:38:39AM -0400, Jeff Layton wrote:
> > I think that the intent of this code was to ensure that a process won't
> > deadlock if it has one fd open with a lease on it and then breaks that
> > lease by opening ano
On Thu, Sep 04, 2014 at 08:38:40AM -0400, Jeff Layton wrote:
> Eliminate an unneeded "flock" variable. We can use "fl" as a loop cursor
> everywhere. Add a any_leases_conflict helper function as well to
> consolidate a bit of code.
Looks good,
Reviewed-by: Christoph Hellwig
One thing that came
On Thu, Sep 04, 2014 at 10:27:35AM -0400, Jeff Layton wrote:
> Eliminate the need for a return pointer.
>
> Signed-off-by: Jeff Layton
Looks good,
Reviewed-by: Christoph Hellwig
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vge
On Thu, Sep 04, 2014 at 08:38:41AM -0400, Jeff Layton wrote:
> Christoph suggests:
>
>"Add a return value to lm_break so that the lock manager can tell the
> core code "you can delete this lease right now". That gets rid of
> the games with the timeout which require all kinds of race
Pramod,
sorry for delay in reply as I was travelling, still in Jet lag.
Signed-off-by: Pramod Gurav
---
drivers/pinctrl/pinctrl-st.c | 25 +
1 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-st.c b/drivers/pinctrl/pinctrl-st.c
in
On Thu, Sep 4, 2014 at 6:42 AM, Oleg Nesterov wrote:
> Trivial. We have "lib-y += thunk_$(BITS).o" at the start, no need
> to add thunk_64.o if !CONFIG_X86_32.
>
Acked-by: Andy Lutomirski
> Signed-off-by: Oleg Nesterov
> ---
> arch/x86/lib/Makefile |2 +-
> 1 files changed, 1 insertions(+
Am 04.09.2014 19:58, schrieb Austin S Hemmelgarn:
On 2014-09-04 13:29, Alexander Holler wrote:
Am 04.09.2014 16:36, schrieb Austin S Hemmelgarn:
On 2014-09-04 06:16, Alexander Holler wrote:
It's a myth that C++ ends up in bigger code than C. At least in my
experience. Especially when the late
On 09/04/2014 12:14 PM, Paolo Bonzini wrote:
> Il 04/09/2014 18:00, Chris J Arges ha scritto:
>> Uptime:
>> 15:58:02 up 1:00, 1 user, load average: 0.59, 0.60, 0.31
>>
>> Here is the output:
>>
>> ./x86-run x86/kvmclock_test.flat -smp 2 --append "1000 `date +%s`"
>> qemu-system-x86_64 -en
This script is used by many other projects, and in some of them the
requirement of at least 4 line long description for all Kconfig items
is excessive. This patch adds a command line option to control the
required minimum length.
Tested running this script over a patch including a two line config
On Thu, Sep 4, 2014 at 8:49 AM, Jeff Layton wrote:
> On Thu, 4 Sep 2014 08:41:51 -0400
> Trond Myklebust wrote:
>
>> On Thu, Sep 4, 2014 at 8:38 AM, Jeff Layton wrote:
>> > GFS2 and NFS have setlease routines that always just return -EINVAL.
>> > Turn that into a generic routine that can live in
On Mon, Aug 18, 2014 at 7:15 PM, Alexander Holler wrote:
> Am 13.08.2014 11:00, schrieb Borislav Petkov:
>
>> On Wed, Aug 13, 2014 at 10:27:56AM +0200, Peter Zijlstra wrote:
>>>
>>> And the thing is; we're all very busy so we tend to take the 'easy'
>>> way out for things like this; but wholesale
Align the prototype of lprocfs_wr_uint() in the declaration with the one used
in the definition.
The prototype is:
int lprocfs_wr_uint(struct file *file, const char __user *buffer,
unsigned long count, void *data)
In obdclass/lprocfs_status.c
But in lustre/include/lprocfs_sta
On 09/04/2014 09:58 AM, Pranith Kumar wrote:
> Add a missing path argument buf to printf()
>
> Signed-off-by: Pranith Kumar
> Reviewed-by: David Herrmann
> ---
> tools/testing/selftests/memfd/memfd_test.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/s
Am 04.09.2014 20:27, schrieb Rogelio Serrano:
On Mon, Aug 18, 2014 at 7:15 PM, Alexander Holler wrote:
Am 13.08.2014 11:00, schrieb Borislav Petkov:
On Wed, Aug 13, 2014 at 10:27:56AM +0200, Peter Zijlstra wrote:
And the thing is; we're all very busy so we tend to take the 'easy'
way out fo
On Thu, Sep 04, 2014 at 08:02:56PM +0200, Heiko Stübner wrote:
> Am Donnerstag, 4. September 2014, 10:40:24 schrieb Dmitry Torokhov:
> > Hi Chris,
> >
> > On Thu, Sep 04, 2014 at 09:12:38AM +0800, Chris Zhong wrote:
> > > + rk808_clkout->clk_data.clks = clk_table;
> > > + rk808_clkout->clk_data.cl
Make sure we actually see the output of validate_mm() and browse_rb()
before triggering a BUG(). pr_info isn't shown by default so the reason
for the BUG() isn't obvious.
Signed-off-by: Sasha Levin
---
mm/mmap.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
> From: Borislav Petkov [mailto:b...@alien8.de]
> > What I did claim is that it is going to be a far more user-friendly
> > stop gap than the "boot from rescue media" option.
>
> Ok, we have it now and we can use it if needed. All is good.
Quoted comment from commit 65cef1311d5d212fd3d48a43678536
On Thu, Sep 04, 2014 at 03:24:21PM +0800, Li Zefan wrote:
> Hi Guenter,
>
> Sorry for my late reply.
>
> On 2014/8/27 12:59, Guenter Roeck wrote:
> > On Tue, Aug 26, 2014 at 04:08:58PM -0700, Greg KH wrote:
> >> Li has agreed to continue to support the 3.4 stable kernel tree until
> >> September
Hi,
I keep triggering the following Oops with -rc3 when writing to the mass
storage gadget driver:
| # modprobe g_mass_storage stall=0 removable=1 file=/dev/sda
| [ 44.883554] Number of LUNs=8
| [ 44.886709] Mass Storage Function, version: 2009/09/11
| [ 44.892303] LUN: removable file: (no
This patchset adds support of Write-Through (WT) mapping on x86.
The study below shows that using WT mapping may be useful for
non-volatile memory.
http://www.hpl.hp.com/techreports/2012/HPL-2012-236.pdf
This patchset applies on top of the Juergen's patchset below,
which provides the basis of t
This patch sets WT to the PA4 slot in the PAT MSR when the processor
is not affected by the PAT errata. The upper 4 slots of the PAT MSR
are continued to be unused on the following Intel processors.
errata cpuid
--
Pentium 2, A52 family 0x6, m
Fix undefined behavior and compiler warning by replacing right
shift 32 with upper_32_bits macro
Signed-off-by: Scotty Bauer
---
kernel/sys.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sys.c b/kernel/sys.c
index ce81291..c78530b 100644
--- a/kernel/sys.c
+++ b/ke
This patch adds ioremap_wt() for creating WT mapping on x86.
It follows the same model as ioremap_wc() for multi-architecture
support. ARCH_HAS_IOREMAP_WT is defined in the x86 version of
io.h to indicate that ioremap_wt() is implemented on x86.
Signed-off-by: Toshi Kani
---
arch/x86/include/as
This patch changes reserve_memtype() to handle the WT cache mode.
When PAT is not enabled, it continues to set UC- to *new_type for
any non-WB request.
When a target range is RAM, reserve_ram_pages_type() fails for WT
for now. This function may not reserve a RAM range for WT since
reserve_ram_pag
This patch adds pgprot_writethrough() for setting WT to a given
pgprot_t.
Signed-off-by: Toshi Kani
---
arch/x86/include/asm/pgtable_types.h |3 +++
arch/x86/mm/pat.c| 10 ++
include/asm-generic/pgtable.h|4
3 files changed, 17 insertions(+)
di
This patch adds set_memory_wt(), set_memory_array_wt(), and
set_pages_array_wt() for setting range(s) of memory to WT.
Note that reserve_memtype() only supports WT for non-RAM ranges
at this point.
Signed-off-by: Toshi Kani
---
arch/x86/include/asm/cacheflush.h |6 +++
arch/x86/mm/pageattr.
On Thursday 04 September 2014 17:02:17 Lorenzo Pieralisi wrote:
> On Thu, Sep 04, 2014 at 03:05:53PM +0100, Arnd Bergmann wrote:
> > Interesting point: the generic implementation should probably not default
> > to reassigning all buses at all. We could have a (host controller specific,
> > but wit
Hi Michel,
Thank you for your feedback. I actually appology for the mistake.
However, the issue got already reported and a fix proposal was done at
the following location:
https://lists.01.org/pipermail/linux-nfc/2014-September/002918.html
Best Regards
Christophe
Le 04/09/2014 18:55, Michael
On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
> This patch adds set_memory_wt(), set_memory_array_wt(), and
> set_pages_array_wt() for setting range(s) of memory to WT.
>
Possibly dumb question: I thought that set_memory_xyz was only for
RAM. Is that incorrect?
--Andy
--
To unsubscribe fro
On Thu, 4 Sep 2014, Daniel Thompson wrote:
> This patch introduces a new default FIQ handler that is structured in a
> similar way to the existing ARM exception handler and result in the FIQ
> being handled by C code running on the SVC stack (despite this code run
> in the FIQ handler is subject t
On Thu, Sep 4, 2014 at 9:00 AM, Chris J Arges
wrote:
>
>
> On 09/04/2014 07:58 AM, Paolo Bonzini wrote:
>> Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
>> based, 2014-07-16) forgot to add tk->xtime_sec, thus breaking kvmclock on
>> hosts that have a reliable TSC. A
Dmitry,
On Thu, Sep 4, 2014 at 10:33 AM, Dmitry Torokhov
wrote:
> On Wed, Sep 03, 2014 at 09:18:42PM -0700, Doug Anderson wrote:
>> Chris,
>>
>> On Wed, Sep 3, 2014 at 6:12 PM, Chris Zhong wrote:
>> > Adding RTC driver for supporting RTC device present inside RK808 PMIC.
>> >
>> > Signed-off-by:
From: Fenghua Yu
The kernel parameter dis_ucode_ldr disables early loading microcode from
initrd. The parameter was introduced earlier by Borislave Petkov.
This patch adds the explanation for this parameter in
Documentation/kernel-parameters.txt for user convenience.
Signed-off-by: Fenghua Yu
Hi,
On Wed, Sep 3, 2014 at 6:12 PM, Chris Zhong wrote:
> - * Author: Chris Zhong
> - * Author: Zhang Qing
> + * Author: Chris Zhong
> + * Author: Zhang Qing
As Dmitry pointed out, you probably shouldn't have changed these
lines--they were good like they were.
-Doug
--
To unsubscribe from thi
On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
> On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
> > This patch adds set_memory_wt(), set_memory_array_wt(), and
> > set_pages_array_wt() for setting range(s) of memory to WT.
> >
>
> Possibly dumb question: I thought that set_memory_x
On 4 September 2014 14:54, Michael Brown wrote:
> On 04/09/14 11:48, Maarten Lankhorst wrote:
If not, Ard please go ahead with option #2 above. Overkill yes, but I've
done the single __attribute__() hacks in other projects and someone
(usually me) always eventually forgets to t
Il 04/09/2014 21:00, John Stultz ha scritto:
>
> Hey, thanks for reporting the issue and sending an initial patch (even
> if its not quite all sorted yet).
>
> Is the test you're using here available somewhere? Are there any
> special requirements to run it?
You need KVM on a machine with clocks
On 08/29/2014 11:02 AM, Borislav Petkov wrote:
> On Mon, Aug 11, 2014 at 10:18:12AM -0500, ttha...@opensource.altera.com wrote:
>> From: Thor Thayer
>>
>> This patch adds support for the CycloneV and ArriaV SDRAM controllers.
>> Correction and reporting of SBEs, Panic on DBEs.
>>
>> Signed-off-by:
On Thu, Sep 4, 2014 at 11:57 AM, Toshi Kani wrote:
> On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
>> On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
>> > This patch adds set_memory_wt(), set_memory_array_wt(), and
>> > set_pages_array_wt() for setting range(s) of memory to WT.
>>
Il 04/09/2014 20:16, Chris J Arges ha scritto:
>> +boot_ns = timespec_to_ns(&tk->total_sleep_time)
>> ++ tk->wall_to_monotonic.tv_sec * (u64)NSEC_PER_SEC
>> ++ tk->wall_to_monotonic.tv_nsec
>> ++ tk->xtime_sec * (u64)NSEC_PER_SEC;
So this means that the abov
On Thu, Sep 04, 2014 at 01:40:21PM -0500, Felipe Balbi wrote:
> Hi,
>
> I keep triggering the following Oops with -rc3 when writing to the mass
> storage gadget driver:
v3.17-rc3, correct?
I take it that the test passes on some earlier version?
On Thu, 4 Sep 2014, Oleg Nesterov wrote:
> On 09/04, Peter Zijlstra wrote:
> > On Wed, Sep 03, 2014 at 06:08:19PM +0200, Oleg Nesterov wrote:
> >
> > > And a stupid (really, I don't understand this code) question:
> > >
> > > /* for example, ksmd faulting in a user's mm */
> > > if (!p->mm)
> >
On Thu, Sep 4, 2014 at 1:33 PM, Alexander Holler wrote:
>>> Hmm, a sane and maintainable solution would use C++ with which people
>>> don't
>>> have to manually build lists or hashes for every structure like in the
>>> kernel (generic programming done right). So you won't find much kernel
>>> deve
On Thu, Sep 04, 2014 at 08:56:11PM +0200, RICARD Christophe wrote:
> However, the issue got already reported and a fix proposal was
> done at the following location:
Ah, sorry for list mismatch and thank you for the fix :-)
--
WBR, Michael Shigorin / http://altlinux.org
-- http://ope
Jaehoon,
On Wed, Sep 3, 2014 at 10:21 PM, Jaehoon Chung wrote:
> Hi Doug
>
> On 09/03/2014 08:37 AM, Doug Anderson wrote:
>> On dw_mmc there's a small race if you happen to get a card detect
>> interrupt at just the wrong time during probe. You may have enabled
>> the interrupt but host->slot[0]
On Wednesday, September 03, 2014 06:02:19 PM Brian Norris wrote:
> Hi,
>
> If I enable CONFIG_PM_DEBUG on a 3.14.y kernel, I can see the following
> results:
>
> # cat /sys/power/state
> freeze standby mem
> # cat /sys/power/pm_test
> [none] core processors platform devices freeze
On Thu, Sep 04, 2014 at 12:16:42PM -0700, Paul E. McKenney wrote:
> On Thu, Sep 04, 2014 at 01:40:21PM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > I keep triggering the following Oops with -rc3 when writing to the mass
> > storage gadget driver:
>
> v3.17-rc3, correct?
yup, as in subject ;-)
> I
On Thu, 2014-09-04 at 11:23 -0700, Vadim Bendebury wrote:
> This script is used by many other projects, and in some of them the
> requirement of at least 4 line long description for all Kconfig items
> is excessive. This patch adds a command line option to control the
> required minimum length.
>
On Thu, Sep 04, 2014 at 01:19:29PM -0500, Christoph Lameter wrote:
> On Thu, 4 Sep 2014, Paul E. McKenney wrote:
>
> > So in short, you don't see the potential for this use case actually
> > breaking anything, correct?
>
> In general its a performance impact but depending on how this_cpu_ops may
On Thursday, September 04, 2014 04:07:28 PM Viresh Kumar wrote:
> On 4 September 2014 15:33, Preeti U Murthy wrote:
> > I think Rafael's point was that since no driver that had implemented the
> > target_index callback was using it at the time that this patch was
> > proposed, it was be best to co
On 08/25/2014 11:29 AM, Stephen Warren wrote:
On 07/29/2014 10:21 AM, Stephen Warren wrote:
On 07/29/2014 08:25 AM, Thierry Reding wrote:
From: Thierry Reding
This will allow the Kconfig option to be shared among 32-bit and 64-bit
ARM.
This seems fine to me. I'd expect to apply it for 3.18,
On Thu, 2014-09-04 at 16:40 +0200, Frans Klaver wrote:
> I'll I fire up my eeepc and see what I can figure out. Should I take
> Pauls patch and see how it fits into this?
I haven't followed the conversation you're having with Greg, but I would
be grateful if you'd test _just_ my patch. Unless some
On Thu, 2014-09-04 at 12:14 -0700, Andy Lutomirski wrote:
> On Thu, Sep 4, 2014 at 11:57 AM, Toshi Kani wrote:
> > On Thu, 2014-09-04 at 11:57 -0700, Andy Lutomirski wrote:
> >> On Thu, Sep 4, 2014 at 11:35 AM, Toshi Kani wrote:
> >> > This patch adds set_memory_wt(), set_memory_array_wt(), and
>
On 09/04/2014 12:50 PM, One Thousand Gnomes wrote:
>> Besides updating the documentation, it may make sense to do something
>> arch-specific. Just bumping out storage on arches that don't need it
>> seems wasteful, as does generating bus locks on arches that don't need it.
>> Unfortunately, the cod
Il 04/09/2014 21:15, Paolo Bonzini ha scritto:
> Il 04/09/2014 20:16, Chris J Arges ha scritto:
>>> + boot_ns = timespec_to_ns(&tk->total_sleep_time)
>>> + + tk->wall_to_monotonic.tv_sec * (u64)NSEC_PER_SEC
>>> + + tk->wall_to_monotonic.tv_nsec
>>> + + tk->xtime_sec
* Nishanth Menon [140904 06:24]:
> Hi,
>
> The following series was inspired in part by
> http://marc.info/?l=linux-omap&m=140974309205295&w=2
> causing me to try and do an audit of pinctrl configurations on the platform.
>
> Further, failures on latest board updates in the automated farm also
Hi Mauro,
On Thu, 2014-09-04 at 12:36 -0300, Mauro Carvalho Chehab wrote:
> Em Thu, 22 May 2014 14:48:07 +0200
> Paul Bolle escreveu:
>
> > dib0900.c has always shipped with its own, manual, configuration
> > system. There a three problems with it.
> >
> > 1) macros that are defined, but not us
From: "Palik, Imre"
If the drbd backing device is a new device mapper device (e.g., a
dm-linear mapping of an existing block device that contains data), the
counters are initially 0 even though the device contains useful
data. This causes throttling until something accesses the drbd device
or the
401 - 500 of 751 matches
Mail list logo
