On Mon, 2014-04-28 at 16:34 +0300, Ivan T. Ivanov wrote:
> From: Tim Bird
>
> Select the secondary PHY using the TCSR register, if phy-num=1
> in the DTS (or phy_number is set in the platform data). The
> SOC has 2 PHYs which can be used with the OTG port, and this
> code allows configuring the
On Fri, 2014-05-02 at 20:54 -0500, Andy Gross wrote:
> This patch corrects the error check on the call to pm_runtime_get_sync.
>
> Signed-off-by: Andy Gross
Reviewed-by: Ivan T. Ivanov
> ---
> drivers/i2c/busses/i2c-qup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --gi
On 05/02/2014 09:32 PM, Linus Torvalds wrote:
> On Fri, May 2, 2014 at 4:53 PM, Andy Lutomirski wrote:
>> On my box, this saves about 100ns on each interrupt and trap that
>> happens while running in kernel space. This speeds up my kernel_pf
>> microbenchmark by about 17%.
>
> Btw, would you min
This patch adds support for checking soc compatibility based on
compatibility match. It will help us in removing soc_is_exynos4
and soc_is_exynos5 function usage and definition.
CC: Russell King
CC: Heiko Stuebner
CC: Thomas Abraham
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/exynos.
This patch series attempts to get rid of soc_is_exynos macros
and eventually with the help of this series we can probably get
rid of CONFIG_SOC_EXYNOS in near future.
Each Exynos SoC has ChipID block which can give information about
SoC's product Id and revision number. Currently we have si
Exynos SoCs have Chipid IP, for identification of product IDs
and SoC revistions. Till now we are using static macros
such as soc_is_exynos and #ifdefs for run time identification
of SoCs and their revisions. This is leading to add new Kconfig,
soc_is_exynos definitions each time new SoC su
This patch removed "plat/cpu.h" inclusion from hotplug.c as it
is not required.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/hotplug.c |2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/mach-exynos/hotplug.c b/arch/arm/mach-exynos/hotplug.c
index 0243ef3..5e19601 100644
---
Folks, please pull the following patch from Dave that fixes some bugs in
the EFI earlyprintk code when using ",keep".
The following changes since commit 47514c996fac5e6f13ef3a4c5e23f1c5cffabb7b:
efi: Pass correct file handle to efi_file_{read,close} (2014-04-10 21:20:03
+0100)
are available i
On Sat, 2014-05-03 at 10:29 +0800, Andrew Cooks wrote:
> Hi Alex
>
> On Fri, May 2, 2014 at 12:27 AM, Alex Williamson
> wrote:
> > The existing quirk for these devices doesn't really solve the problem,
> > re-implement it using the DMA alias iterator. We'll come back later
> > and remove the exi
It is only a typo issue, the related commit:
"1fbc4c4 drivers/rtc/rtc-puv3.c: use dev_dbg() instead of pr_debug()"
The related error (for unicore32 with allmodconfig):
CC [M] drivers/rtc/rtc-puv3.o
drivers/rtc/rtc-puv3.c: In function ‘puv3_rtc_setalarm’:
drivers/rtc/rtc-puv3.c:143: er
It is only a typo issue, the related commit:
"1fbc4c4 drivers/rtc/rtc-puv3.c: use dev_dbg() instead of pr_debug()"
The related error (unicore32 with allmodconfig):
CC [M] drivers/rtc/rtc-puv3.o
drivers/rtc/rtc-puv3.c: In function ‘puv3_rtc_setpie’:
drivers/rtc/rtc-puv3.c:74: error: im
Fix 2 typo issues for commit "1fbc4c4 drivers/rtc/rtc-puv3.c: use
dev_dbg() instead of pr_debug()".
Signed-off-by: Chen Gang
---
drivers/rtc/rtc-puv3.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Fri, May 2, 2014 at 4:53 PM, Andy Lutomirski wrote:
> On my box, this saves about 100ns on each interrupt and trap that
> happens while running in kernel space. This speeds up my kernel_pf
> microbenchmark by about 17%.
Btw, would you mind _trying_ to do a similar trick for the "return to
use
Hello dear,
My name is Miss Adena, I'm very glad when i come across your profile today
while searching for a partnership which interest me to write to you, I will
like to build a good relationship with you because i see you as a one with a
good heart .I want you to understand that a Good friend
On Fri, May 02, 2014 at 06:22:43PM -0700, Maxime Ripard wrote:
> Hi Guenter,
>
> On Thu, May 01, 2014 at 08:41:29AM -0700, Guenter Roeck wrote:
> > Some hardware implements reboot through its watchdog hardware,
> > for example by triggering a watchdog timeout. Platform specific
> > code starts to
On Fri, May 02, 2014 at 11:40:22PM +0100, Al Viro wrote:
> On Fri, May 02, 2014 at 02:18:43PM -0700, Linus Torvalds wrote:
> > On Fri, May 2, 2014 at 2:08 PM, Miklos Szeredi wrote:
> > > There's more of the "delete from shrink list not owned by us" in select
> > > parent.
> > > Proposed patch app
On 05/02/2014 04:53 PM, Andy Lutomirski wrote:
> On my box, this saves about 100ns on each interrupt and trap that
> happens while running in kernel space. This speeds up my kernel_pf
> microbenchmark by about 17%.
>
> Signed-off-by: Andy Lutomirski
I'd really like to see a workload which would
We use usb ehci to connect with modem and run stress test on ehci
remote wake. Sometimes usb disconnect. We add more debug ftrace
(Kernel version: 3.10) and list the key log to show how problem
happened.
-0 [000] d.h2 26879.385095: ehci_irq: irq status 1008c PPCE FLR PCD
-0 [000] d.h2 2687
Noi oferim credite la rata dobânzii de 3% pentru toate scop. Ne e-mail dacă
sunteți interesat.
We offer loans at 3% interest rate for all purpose. Email us if you are
interested.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@v
Linus,
This is a small fix where the trigger code used the wrong
rcu_dereference(). It required rcu_dereference_sched() instead of
the normal rcu_dereference(). It produces a nasty RCU lockdep splat
due to the incorrect rcu notation.
Please pull the latest trace-fixes-v3.15-rc3 tree, which can b
On Fri, 2 May 2014, Vince Weaver wrote:
> I've been fuzzing without your additional patch for 6 hours and all looks
> (almost) good. I can add in your patch and let it fuzz overnight.
and I applied the additional patch, installed the kernel, hit reboot, and
the following happened (this was caus
On Fri, May 02, 2014 at 06:27:56PM -0700, Sterling Huxley wrote:
^^
Better luck next year, and you might want to start preparing a posting a month
earlier than this time around - you are 31 days late.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Fri, 2 May 2014, Thomas Gleixner wrote:
> > OK the proper patch has been running the quick reproducer for a bit
> > without triggering the issue, I'll let it run a bit more and then upgrade
> > to full fuzzing.
>
> If you do that, please add the patch below.
I've been fuzzing without your a
Hi Pankaj,
On 03.05.2014 03:52, Pankaj Dubey wrote:
Hi,
Gentle ping.
Tomasz, Kukjin will you please have a look on this series.
Sure. I have added this series to my queue and should be able to find
some time to review it after the weekend.
Best regards,
Tomasz
--
To unsubscribe from this
This patch corrects the error check on the call to pm_runtime_get_sync.
Signed-off-by: Andy Gross
---
drivers/i2c/busses/i2c-qup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-qup.c b/drivers/i2c/busses/i2c-qup.c
index 1b4cf14..2a5efb5 100644
--- a/d
On Fri, May 02, 2014 at 11:09:18PM +0200, Geert Uytterhoeven wrote:
> On Fri, May 2, 2014 at 7:14 PM, Mark Brown wrote:
> > Ugh. It would seem better to have these functions stubbed out. But
> As long as we have include/asm-generic/dma-mapping-broken.h,
> it'll be like this...
Yeah, I'm not s
Hi,
Gentle ping.
Tomasz, Kukjin will you please have a look on this series.
Thanks,
Pankaj Dubey
On 04/30/2014 02:17 PM, Pankaj Dubey wrote:
This patch series, does some minor cleanup of exynos machine files.
It also modifies Exynos Power Management Unit (PMU) related code for
converting it
An Immune System for Linux
An Operating System does not know the origins of a program. If requested,
the OS will run any program, every program, all programs. This was
good in the old days when the logistics of distributing a program were
expensive, time consuming, and labor i
Hi Guenter,
On Thu, May 01, 2014 at 08:41:29AM -0700, Guenter Roeck wrote:
> Some hardware implements reboot through its watchdog hardware,
> for example by triggering a watchdog timeout. Platform specific
> code starts to spread into watchdog drivers, typically by setting
> pointers to a callback
When 'console=hvc0' is specified to the kernel parameter in x86 KVM guest,
hvc console is setup within a kthread. However, that will cause SEGV
and the boot will fail when the driver is builtin to the kernel,
because currently hvc_console_setup() is annotated with '__init'. This
patch removes '__in
Need generic definition for readl_relaxed(), like other architectures
have done. Or can not pass compiling with allmodconfig, the related
error:
CC [M] drivers/message/fusion/mptbase.o
drivers/message/fusion/mptbase.c: In function ‘mpt_send_handshake_request’:
drivers/message/fusion/mptba
Thank Sergei for reviewing.
I think
On Sat, May 3, 2014 at 12:18 AM, Sergei Shtylyov
wrote:
>> +
>> + if (pkt_dev->clone_skb && is_vlan_dev(odev)) {
>> + nskb = skb_clone(pkt_dev->skb, GFP_ATOMIC);
>> + ret = -ENOMEM;
>> + if (nskb)
>> +
http://horde-update.yolasite.com/
Thanks.
--
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 at http://www.tux.org/lkml/
Hi. Viresh Kumar
Your reply is so fast like Usain Bolt.
> So, create three flags:
> OPP_TABLE_ORDER_ASCENDING 0
> OPP_TABLE_ORDER_DESCENDING1
> OPP_TABLE_ORDER_ORIGINAL 2 (And use this for your case.)
-> Actually, I want to use OPP_TABLE_ORDER_DESCENDING.
On Fri, May 2, 2014 at 4:51 PM, Andy Lutomirski wrote:
> On my box, this saves about 100ns on each interrupt and trap that
> happens while running in kernel space. This speeds up my kernel_pf
> microbenchmark by about 17%.
Acked-by: Linus Torvalds
Now it just needs lots of testing to make sure
Hello, Peter,
The following commit seems to have been dropped on the floor.
Given that you haven't complained, I feel the need to ask you
if you still need it. ;-)
If you do need it, I will push it into 3.16.
Thanx, Paul
-
On my box, this saves about 100ns on each interrupt and trap that
happens while running in kernel space. This speeds up my kernel_pf
microbenchmark by about 17%.
Signed-off-by: Andy Lutomirski
---
Changes from v1:
- Comment fix *facepalm*
Changes from the RFC:
- Much better comments
- Rewri
On my box, this saves about 100ns on each interrupt and trap that
happens while running in kernel space. This speeds up my kernel_pf
microbenchmark by about 17%.
Signed-off-by: Andy Lutomirski
---
Changes from the RFC:
- Much better comments
- Rewritten to use popq_cfi directly instead of RES
On Fri, 2014-05-02 at 17:04 +0200, Denys Vlasenko wrote:
> Before this patch, instructions such as div, mul,
> shifts with count in CL, cmpxchg are mishandled.
I just noticed that this sounds rather worse than it is. It would be
more precise to say, "Before this patch, the rip-relative addressing
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-3.15-rc4
to receive ACPI, power management and PNP fixes for v3.15-rc4
with top-most commit de3afce5336af3214374de6df360f9eb010a9a36
Merge branches 'acpi-ec' and 'acpi-processor'
on top o
While in that area, I noticed that the soft limit tree updaters don't
actually use the memcg argument anymore...
---
From: Johannes Weiner
Subject: [patch] mm: memcontrol: remove unnecessary memcg argument from soft
limit functions
Signed-off-by: Johannes Weiner
---
mm/memcontrol.c | 34 +
On Fri, May 02, 2014 at 03:05:16PM -0700, Andrew Morton wrote:
> On Thu, 1 May 2014 08:54:50 -0400 Johannes Weiner wrote:
>
> > On Mon, Apr 28, 2014 at 05:04:26PM +0200, Michal Hocko wrote:
> > > On Tue 22-04-14 11:59:23, Michal Hocko wrote:
> > > > On Sat 19-04-14 07:01:43, Jianyu Zhan wrote:
>
On Fri, May 02, 2014 at 01:59:29PM -0700, Tomas Pop wrote:
> Hi Guenter, thanks for comments! I will include them in third version,
> but I have still few questions...
>
> On Don, 2014-05-01 at 19:06 -0700, Guenter Roeck wrote:
> > On 05/01/2014 04:05 PM, Tomas Pop wrote:
> > > One more time this
On Fri, May 02, 2014 at 11:40:22PM +0100, Al Viro wrote:
> On Fri, May 02, 2014 at 02:18:43PM -0700, Linus Torvalds wrote:
> > On Fri, May 2, 2014 at 2:08 PM, Miklos Szeredi wrote:
> > > There's more of the "delete from shrink list not owned by us" in select
> > > parent.
> > > Proposed patch app
On Fri, 2 May 2014 15:09:14 -0700 John Stultz wrote:
> Recently, Jiri pointed out a potential deadlock when calling printk
> while holding the timekeeping seqlock.
>
> Annoyingly, the seqlock lockdep enablement doesn't catch this, as
> printk disables lockdep.
>
> When looking for possible sol
When 'console=hvc0' is specified to the kernel parameter in x86 KVM guest,
hvc console is setup within a kthread. However, that will cause SEGV
and the boot will fail when the driver is builtin to the kernel,
because currently hvc_console_setup() is annotated with '__init'. This
patch removes '__in
On Fri, Apr 25, 2014 at 8:42 PM, Jin, Yao wrote:
> On 2014/4/26 11:04, Jin, Yao wrote:
(...)
> I think we still need a small modification on pinctrl-baytrail.c, that
> is moving gpiochip_add forward, otherwise the to_irq method is not set.
>
> diff --git a/drivers/pinctrl/pinctrl-baytrail.c
> b/dr
On Fri 02-05-14 14:22:20, Andrew Morton wrote:
> From: Will Deacon
> Subject: printk: print initial logbuf contents before re-enabling interrupts
>
> When running on a hideously slow system (~10Mhz FPGA) with a bunch of
> debug printk invocations on the timer interrupt path, we end up filling
> t
Hi Rob,
On 05/02/2014 09:58 AM, Rob Herring wrote:
> On Wed, Apr 30, 2014 at 7:34 PM, Suman Anna wrote:
>> This patch adds the generic common bindings used to represent
>> a hwlock device and use/request locks in a device-tree build.
>>
>> All the platform-specific hwlock driver implementations n
On Fri, Apr 25, 2014 at 1:41 PM, Andy Gross wrote:
> Fix copy/paste error in pinctrl_pin_desc for pin 0.
>
> Signed-off-by: Andy Gross
Pretty obvious.
Patch applied!
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to maj
Found using smatch:
drivers/iio/industrialio-event.c:327 iio_device_add_event() error: buffer
overflow 'iio_ev_info_text' 3 <= 7
It was probably never hit because the mask_* members of the event_spec struct
are filled by using the BIT() macro with values from the iio_event_info enum
that also serv
Found using smatch:
drivers/iio/industrialio-core.c:719 iio_device_add_info_mask_type() error:
buffer overflow 'iio_chan_info_postfix' 17 <= 63
It was probably never hit because the info_mask_* members are filled by using
the BIT() macro with values from the iio_chan_info_enum enum that also serve
On Fri, May 02, 2014 at 02:18:43PM -0700, Linus Torvalds wrote:
> On Fri, May 2, 2014 at 2:08 PM, Miklos Szeredi wrote:
> > There's more of the "delete from shrink list not owned by us" in select
> > parent.
> > Proposed patch appended.
>
> Ahh. Clearly this needs more work before I pull.
*nod*
Hi Mel,
Vlastimil Babka suggested I should try this patch to work around a different
issue I'm seeing, and noticed that it doesn't build because:
On 05/01/2014 04:44 AM, Mel Gorman wrote:
> +void set_pageblock_flags_mask(struct page *page,
> + unsigned long flags,
> +
On Mon, 07 Apr 2014 14:24:45 +0930 Rusty Russell wrote:
> Subject: param: hand arguments after -- straight to init
>
> The kernel passes any args it doesn't need through to init, except it
> assumes anything containing '.' belongs to the kernel (for a module).
> This change means all users can c
On Fri, May 02, 2014 at 11:08:13PM +0200, Miklos Szeredi wrote:
> There's more of the "delete from shrink list not owned by us" in select
> parent.
> Proposed patch appended.
While it certainly looks like dentry_lru_del() should die, I really wonder if
"let's pretend that dentry isn't there if it
On Fri, Apr 25, 2014 at 9:31 AM, Timur Tabi wrote:
> Rafael J. Wysocki wrote:
>>
>> I would be interested in understanding what exactly the flow is in that
>> situation, so care to educate me? What does the driver do to trigger
>> this and what exactly does happen in response to that?
>
>
> I onl
A release candidate Git v2.0.0-rc2 is now available for testing
at the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following public repositories all have a copy of the 'v2.0.0-rc2'
tag and the 'master' branch that the tag points at:
ur
On Fri, Apr 25, 2014 at 8:24 AM, Stephen Warren wrote:
> On 04/24/2014 12:22 PM, Thierry Reding wrote:
> ...
>> The downside of not allowing the gpiod API to support the -gpio suffix
>> is that we'll never be able to convert drivers that use such a binding
>> and will forever have a hodgepodge of
On Fri, Apr 25, 2014 at 8:10 AM, Thierry Reding
wrote:
> From: Thierry Reding
>
> Add the GPIO-related device-managed functions to the list of functions
> in Documentation/driver-model/devres.txt.
>
> Signed-off-by: Thierry Reding
Patch applied.
Yours,
Linus Walleij
--
To unsubscribe from thi
On Fri, Apr 25, 2014 at 7:54 AM, Thierry Reding
wrote:
> From: Thierry Reding
>
> The function is called gpiod_get(), not gpio_get(). Fix the kernel-doc
> comment to match the name.
>
> Signed-off-by: Thierry Reding
Patch applied.
Yours,
Linus Walleij
--
To unsubscribe from this list: send th
On Tue, Feb 11, 2014 at 9:10 AM, Pawel Moll wrote:
> This patch adds a trival sched clock source using free
> running, 24MHz clocked counter present in the ARM Ltd.
> Versatile Express platform's System Registers block.
>
> This code replaces the call in the VE machine code.
>
> Cc: Daniel Lezcan
A commit in akpm's tree (printk: remove separate printk_sched
buffers...), removed the printk_sched irqsave/restore lines
since it was safe for current users. Since we may be expanding
usage of printk_sched(), re-add the irqsave/restore logic
to make the functionality more generally safe.
Cc: Jan
Recently, Jiri pointed out a potential deadlock when calling printk
while holding the timekeeping seqlock.
Annoyingly, the seqlock lockdep enablement doesn't catch this, as
printk disables lockdep.
When looking for possible solutions, one idea was to use a local buffer
and defer the printk to lat
Jiri Bohac pointed out that there are rare but potential deadlock
possibilities when calling printk while holding the timekeeping
seqlock.
This is due to printk() triggering console sem wakeup, which can
cause scheduling code to trigger hrtimers which may try to read
the time.
Specifically, as Ji
Two of the three prink_deferred uses are really printk_once style
uses, so add a printk_once_deferred macro to simplify those call
sites.
Cc: Jan Kara
Cc: Peter Zijlstra
Cc: Jiri Bohac
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Andrew Morton
Cc: Steven Rostedt
Signed-off-by: John Stultz
---
After learning we'll need some sort of deferred printk functionality
in the timekeeping core, Peter suggested we rename the printk_sched
function so it can be reused by needed subsystems.
This only changes the function name and name of the associated buffer.
No logic changes.
Cc: Jan Kara
Cc: Pe
On Thu, 1 May 2014 08:54:50 -0400 Johannes Weiner wrote:
> On Mon, Apr 28, 2014 at 05:04:26PM +0200, Michal Hocko wrote:
> > On Tue 22-04-14 11:59:23, Michal Hocko wrote:
> > > On Sat 19-04-14 07:01:43, Jianyu Zhan wrote:
> > > > introduce helper mem_cgroup_zoneinfo_zone(). This will make
> > > >
On Fri, May 02, 2014 at 06:49:30PM +0200, Michal Hocko wrote:
> On Fri 02-05-14 11:58:05, Johannes Weiner wrote:
> > On Fri, May 02, 2014 at 11:36:28AM +0200, Michal Hocko wrote:
> > > On Wed 30-04-14 18:55:50, Johannes Weiner wrote:
> > > > On Mon, Apr 28, 2014 at 02:26:42PM +0200, Michal Hocko wr
Hi Linus,
This was the pending bug fix I mentioned in my previous pull request.
Normally this would go through Greg's tree seeing that it is a
drivercore change, but devicetree exposes the problem. I've discussed
with Greg and he okayed me asking you to pull directly.
Cheers,
g.
The following ch
On 05/02/2014 02:42 PM, Andy Lutomirski wrote:
>
> Hah -- I think I just faked both of you out :)
>
> I don't think this has anything to do with the error code, and I think
> that the errorentry code already does more or less that: it pushes -1.
>
> The real issue here is probably the magic 16-b
From: Stéphane Graber
Date: Wed, 30 Apr 2014 11:25:43 -0400
> This switches a few remaining capable(CAP_NET_ADMIN) to ns_capable so
> that root in a user namespace may set tc rules inside that namespace.
>
> Signed-off-by: Stéphane Graber
> Acked-by: Serge E. Hallyn
Applied to net-next, thank
On Fri, May 2, 2014 at 2:37 PM, H. Peter Anvin wrote:
> On 05/02/2014 02:07 PM, Linus Torvalds wrote:
>> On Fri, May 2, 2014 at 2:04 PM, Andy Lutomirski wrote:
>>>
>>> Because otherwise I'd have to keep track of whether it's a zeroentry
>>> or an errorentry. I can't stuff the offset in a registe
On 05/02/2014 02:07 PM, Linus Torvalds wrote:
> On Fri, May 2, 2014 at 2:04 PM, Andy Lutomirski wrote:
>>
>> Because otherwise I'd have to keep track of whether it's a zeroentry
>> or an errorentry. I can't stuff the offset in a register without even
>> more stack hackery, since there are no avai
On Fri, May 02, 2014 at 11:26:24PM +0200, Thomas Gleixner wrote:
> Russell reported, that irqtime_account_idle_ticks() takes ages due to:
>
>for (i = 0; i < ticks; i++)
>irqtime_account_process_tick(current, 0, rq);
>
> It's sad, that this code was written way _AFTER_ the
On Fri, 2 May 2014, Linus Torvalds wrote:
> On Fri, May 2, 2014 at 1:30 PM, Thomas Gleixner wrote:
> >
> > So what about manipulating the stack so that the popf does not enable
> > interrupts and do an explicit sti to get the benefit of the
> > one-instruction shadow ?
>
> That's what I already
Russell reported, that irqtime_account_idle_ticks() takes ages due to:
for (i = 0; i < ticks; i++)
irqtime_account_process_tick(current, 0, rq);
It's sad, that this code was written way _AFTER_ the NOHZ idle
functionality was available. I charge myself guitly for not paying
> > /*
> > + * Guide to the rw_semaphore's count field for common values.
> > + * (32 bit case illustrated, similar for 64 bit)
>
> The values below are x86-specific; the actual defines are arch-dependent.
> Do other archs use different values?
This is also the value used also for generic case
On Fri, May 2, 2014 at 2:08 PM, Miklos Szeredi wrote:
> There's more of the "delete from shrink list not owned by us" in select
> parent.
> Proposed patch appended.
Ahh. Clearly this needs more work before I pull.
Linus
--
To unsubscribe from this list: send the line "unsubscribe l
Hi Mark,
On Fri, May 2, 2014 at 7:14 PM, Mark Brown wrote:
> On Fri, May 02, 2014 at 06:29:34AM +0200, Geert Uytterhoeven wrote:
>> If NO_DMA=y:
>>
>> drivers/built-in.o: In function `spi_map_buf':
>> spi.c:(.text+0x21bc60): undefined reference to `dma_map_sg'
>> drivers/built-in.o: In function `
To silence the warning
cpufreq_cpu0: failed to get cpu0 regulator: -19
from the cpufreq driver regarding a missing regulator,
add a fixed regulator to the DT.
Zynq does not support voltage scaling and the CPU rail should always be
supplied with 1 V, hence it is added in the SOC-level dtsi.
There's more of the "delete from shrink list not owned by us" in select parent.
Proposed patch appended.
And I'm not sure what umount_collect() is supposed to do. Can other shrinkers
still be active at that point? That would present other problems, no?
Also somewhat related is the question: how
On Fri, May 2, 2014 at 2:04 PM, Andy Lutomirski wrote:
>
> Because otherwise I'd have to keep track of whether it's a zeroentry
> or an errorentry. I can't stuff the offset in a register without even
> more stack hackery, since there are no available registers there. I
> could split the whole th
On Thu, May 1, 2014 at 7:34 AM, Al Viro wrote:
>
> OK, fixed and pushed (both branches).
Al, can you send a real pull request (the "both branches" part in
particular makes me worry about which one you think is right), because
I suspect by now we just need to get this wider testing.
On Fri, May 2, 2014 at 2:01 PM, Linus Torvalds
wrote:
> On Fri, May 2, 2014 at 1:30 PM, Thomas Gleixner wrote:
>>
>> So what about manipulating the stack so that the popf does not enable
>> interrupts and do an explicit sti to get the benefit of the
>> one-instruction shadow ?
>
> That's what I a
On Fri, May 02, 2014 at 11:00:04AM +0200, Szeredi Miklos wrote:
> The bug is private, but I'll ask if I can repost it. The first thing
> is a a warning from the D_FLAG_VERIFY() in d_shrink_del() from
> shrink_dentry_list(). They added printks that show that the dentry
> has DCACHE_DENTRY_KILLED.
On Fri, May 2, 2014 at 1:30 PM, Thomas Gleixner wrote:
>
> So what about manipulating the stack so that the popf does not enable
> interrupts and do an explicit sti to get the benefit of the
> one-instruction shadow ?
That's what I already suggested in the original "I don't think popf
works" emai
Quoting Richard Guy Briggs (r...@redhat.com):
> On 14/05/02, Serge E. Hallyn wrote:
> > Quoting Richard Guy Briggs (r...@redhat.com):
> > > I saw no replies to my questions when I replied a year after Aris'
> > > posting, so
> > > I don't know if it was ignored or got lost in stale threads:
> > >
Hi Guenter, thanks for comments! I will include them in third version,
but I have still few questions...
On Don, 2014-05-01 at 19:06 -0700, Guenter Roeck wrote:
> On 05/01/2014 04:05 PM, Tomas Pop wrote:
> > One more time this patch sent with correct settings of my email client
> > - I'm sorry for
Quoting Richard Guy Briggs (r...@redhat.com):
> On 14/05/02, Serge E. Hallyn wrote:
> > Quoting Richard Guy Briggs (r...@redhat.com):
> >
> > Most of this looks reasonable, but I'm curious about something,
> >
> > > +/**
> > > + * ns_serial - compute a serial number for the namespace
> > > + *
>
On Fri, 2 May 2014, Vince Weaver wrote:
> On Fri, 2 May 2014, Thomas Gleixner wrote:
>
> > Hmm, and where comes the WARN_ON in _free_event() from? That's not in
> > Peters last patch.
>
> ahh, you're right :( My fault. I gave the new patch and the previous
> patch similar names and applied th
On Fri, 2 May 2014 16:23:43 -0400
Dan Streetman wrote:
> lib/plist.c uses pr_debug() in its test function, which is compiled
> and run only when CONFIG_DEBUG_PI_LIST in set; however pr_debug()
> is compiled out unless -DDEBUG is set for the file.
>
> Update lib/Makefile to add -DDEBUG to CFLAGS
Signed-off-by: Greg DeAngelis
---
drivers/staging/bcm/Transmit.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/bcm/Transmit.c b/drivers/staging/bcm/Transmit.c
index 2ed4836..4976746 100644
--- a/drivers/staging/bcm/Transmit.c
+++ b/driv
On 02/05/14 19:28, Hartley Sweeten wrote:
On Friday, May 02, 2014 9:50 AM, Ian Abbott wrote:
On 2014-05-02 15:57, Brilliantov Kirill Vladimirovich wrote:
Signed-off-by: Brilliantov Kirill Vladimirovich
---
drivers/staging/comedi/drivers/ni_stc.h | 2 +-
1 file changed, 1 insertion(+), 1 d
On Fri, 2 May 2014, Linus Torvalds wrote:
> On Fri, May 2, 2014 at 12:31 PM, Linus Torvalds
> wrote:
> >
> > Also, are you *really* sure that "popf" has the same one-instruction
> > interrupt shadow that "sti" has? Because I'm not at all sure that is
> > true, and it's not documented as far as I
On Fri, 2 May 2014, Mel Gorman wrote:
> > The page locks I'm referring to is the lock_page() in __unmap_and_move()
> > that gets called for sync compaction after the migrate_pages() iteration
> > makes a few passes and unsuccessfully grabs it. This becomes a forced
> > migration since __unmap_
On 05/02/2014 01:15 PM, Andy Lutomirski wrote:
> This just moves code around.
>
> Signed-off-by: Andy Lutomirski
One more thing: please explain *why* here.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel
lib/plist.c uses pr_debug() in its test function, which is compiled
and run only when CONFIG_DEBUG_PI_LIST in set; however pr_debug()
is compiled out unless -DDEBUG is set for the file.
Update lib/Makefile to add -DDEBUG to CFLAGS_plist.o if
CONFIG_DEBUG_PI_LIST is set, so that the pr_debug() outp
On Fri, 2 May 2014 12:31:42 -0700
Linus Torvalds wrote:
>
> And NMI not being re-enabled might just be a real advantage. Adding
> Steven to the cc to make him aware of this patch.
>
There's not much of an advantage for NMIs, as they seldom page fault.
We may get some due to vmalloc'd areas, but
From: Grygorii Strashko
Date: Wed, 30 Apr 2014 15:23:32 +0300
> Introduce a resource managed devm_mdiobus_alloc[_size]()/devm_mdiobus_free()
> to automatically clean up MDIO bus alocations made by MDIO drivers,
> thus leading to simplified MDIO drivers code.
>
> Clean up Davinci MDIO driver and
1 - 100 of 601 matches
Mail list logo
