On Mon, 2015-09-07 at 22:04 +0800, Bamvor Jian Zhang wrote:
> selftests: exec: simpification the Makefile
Please give us a better subject, ie something like:
selftests/exec: Revert to default emit rule
> With the previous patch, the installation method change from install
> to rsync. There is
On Tue, Sep 8, 2015 at 7:45 AM, Sedat Dilek wrote:
> On Tue, Sep 8, 2015 at 12:30 AM, Sedat Dilek wrote:
>> On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek wrote:
>>> On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds
>>> wrote:
On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote:
>
>
On Mon, 2015-09-07 at 22:04 +0800, Bamvor Jian Zhang wrote:
> The command of install could not handle the special files in exec
> testcases, change the default rule to rsync to fix this.
> The result of installation is unchanged after this commit.
>
> Suggested-by: Michael Ellerman
>
perf_event_create_kernel_counter is used to enable perf events in kernel
without buffer for logging its events. This patch add new fucntion which
enable perf events with ring buffer. Intel PT logger uses this to enable
Intel PT and some associated events with its log buffer.
Signed-off-by: Takao
When panic occurs, Intel PT logging is stopped to prevent it from
overwrite its log buffer. The registers of Intel PT are saved in the
memory on panic, they are needed for debugger to find the last position
where Intel PT wrote data.
Signed-off-by: Takao Indoh
---
arch/x86/kernel/crash.c |9
Hi all,
These patch series provide logging feature for Intel Processor Trace
(Intel PT).
Intel PT is a new feature of Intel CPU "Broadwell", it captures
information about program execution flow. Here is a article about Intel
PT.
https://software.intel.com/en-us/blogs/2013/09/18/processor-tracing
This patch provides Intel PT logging feature. When system boots with a
parameter "intel_pt_log", log buffers for Intel PT are allocated and
logging starts, then processor flow information is written in the log
buffer by hardware like flight recorder. This is very helpful to
investigate a cause of
This patch adds function to find struct trace_event by event name like
"sched_switch" , and return its type so that Intel PT logger can enable
the trace event in kernel. Intel PT logger needs this because it needs
sched_switch tracing to collect side-band data.
Signed-off-by: Takao Indoh
---
On Mon, 2015-09-07 at 22:04 +0800, Bamvor Jian Zhang wrote:
> selftests: mqueue: simpification the Makefile
This should be:
selftests/mqueue: Simplify the Makefile
And please write a change log, even for simple commits like this.
You can say something like:
Use make's implict rule for
On Tue, Sep 8, 2015 at 12:30 AM, Sedat Dilek wrote:
> On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek wrote:
>> On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds
>> wrote:
>>> On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote:
That does not work.
>>>
>>> .. because you didn't do what I
On Mon, 2015-09-07 at 22:04 +0800, Bamvor Jian Zhang wrote:
> change from = to += in order to pass the proper headers and librareis
Please start your changelogs with a Capital letter, they are supposed to be
proper English sentences.
> (popt.h and libpopt.so) in order to build successful in
On Mon, 2015-09-07 at 22:04 +0800, Bamvor Jian Zhang wrote:
> Check it before compiling to avoid the failure of building and
> installation.
I asked you not to do this.
http://lkml.kernel.org/r/1440991580.5735.4.ca...@ellerman.id.au
Can you tell me why you ignored my comments?
cheers
--
To
On Mon, 2015-09-07 at 22:04 +0800, Bamvor Jian Zhang wrote:
> commit "2bf9e0a locking/static_keys: Provide a selftest" rename
^
d
> jump_label directory to static_keys.
On 9/8/15 1:28 PM, Byungchul Park wrote:
On Tue, Sep 08, 2015 at 11:46:01AM +0800, Wanpeng Li wrote:
On 9/7/15 10:02 PM, Peter Zijlstra wrote:
Please always Cc at least the person who wrote the lines you modify.
On Mon, Sep 07, 2015 at 05:45:20PM +0800, Wanpeng Li wrote:
The sleeper task
On Tue, Sep 08, 2015 at 05:23:59AM +0200, Stephan Mueller wrote:
> Am Dienstag, 16. Juni 2015, 11:46:46 schrieb Boris Brezillon:
>
> Hi Herbert,
>
> >The crypto drivers are supposed to update the IV passed to the crypto
> >request before calling the completion callback.
> >Test for the IV value
On Tue, Sep 08, 2015 at 11:46:01AM +0800, Wanpeng Li wrote:
> On 9/7/15 10:02 PM, Peter Zijlstra wrote:
> >Please always Cc at least the person who wrote the lines you modify.
> >
> >On Mon, Sep 07, 2015 at 05:45:20PM +0800, Wanpeng Li wrote:
> >>The sleeper task will be normalized when moved from
Hi all,
Please do not add material for v4.4 until after v4.3-rc1 is out.
Changes since 20150903:
I used the h8300 tree from next-20150828 since the current tree has been
rebased onto something very old :-(
The parisc-hd tree gained a conflict against Linus' tree.
The v4l-dvb tree gained a
Hi Auhur,
Could you please help to apply the test patch
against the latest mainstream linux kernel?
Thanks!
Gerry
On 2015/9/7 14:26, Arthur Marsh wrote:
>
>
> Jiang Liu wrote on 07/09/15 12:36:
>> On 2015/9/7 4:31, Arthur Marsh wrote:
>>> Arthur Marsh wrote on 06/09/15 21:07:
On (09/08/15 13:50), Minchan Kim wrote:
> For exmaple, disksize, max_comp_streams are changed only if
> it is successful.
> If your logic were right approach, we should change
> max_comp_streams for *stupid* script although it doesn't check
define stupid.
is echo 210 >
On 08-09-15, 13:48, Krzysztof Kozlowski wrote:
> Somehow my mind stuck on solving Exynos4x12 cpufreq issues.
>
> Right, it should go through Rafael's, probably except DTS patch (4/4)
> because it depends on previous DTS changes. These changes are still in
> arm-soc, not in Linus' tree [0].
On Tue, 08 Sep 2015 02:30:07 +0200,
Kim, Milo wrote:
>
> Hi Takashi,
>
> On 9/7/2015 11:19 PM, Jacek Anaszewski wrote:
> > Hi Takashi,
> >
> > Thanks for chasing this.
> > Milo, could you express your opinion?
> >
> > On 09/07/2015 02:25 PM, Takashi Iwai wrote:
> >> The commit [b67893206fc0:
On (09/08/15 13:50), Minchan Kim wrote:
[..]
> And it's straightforward/consistent to change the thing's state
> only if is successful.
>
what for? I provided several good reasons not to do this, because
it makes life easier for users. we added this check in Jun 25, 2015
while this functionality
On 09/07/2015 10:40 AM, Michael Ellerman wrote:
On Fri, 2015-09-04 at 17:51 -0300, Arnaldo Carvalho de Melo wrote:
Em Tue, Sep 01, 2015 at 12:18:47PM +0530, Hemant Kumar escreveu:
Should I try to process the 5 together, applying thest two first?
Yes, this patchset needs to be applied
On 8 September 2015 at 14:04, Stephen Rothwell wrote:
> Hi Dave,
>
> On Tue, 8 Sep 2015 13:01:21 +1000 Dave Airlie wrote:
>>
>> Is this to be a regular thing? because I know I'd prefer to merge
>> fixes than wait for -rc1 to be an accurate copy of linux-next.
>
> It happens when I can (almost)
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/net/ieee802154/at86rf230.c: In function 'at86rf230_stats_show':
drivers/net/ieee802154/at86rf230.c:1650:6: error: void value not ignored as it
ought to be
ret = seq_printf(file,
On Tue, Sep 08, 2015 at 10:58:31AM +0900, Sergey Senozhatsky wrote:
> On (09/08/15 10:33), Sergey Senozhatsky wrote:
> > > I don't understand your concern. To me, this patch makes sense to me.
> > > Could you explain your point clearly, again?
> >
> > OK. suppose someone landed a typo in a 'zram
On 08.09.2015 13:20, Viresh Kumar wrote:
> On 08-09-15, 12:56, Krzysztof Kozlowski wrote:
>> There were no comments from your side for this patchset nor for previous
>> Marek's fix. After mentioned change and Bart's re-spin, do you plan to
>> grab this patchset and send it for current v4.3 cycle?
Op 08-09-15 om 01:42 schreef Stephen Rothwell:
> Hi all,
>
> On Thu, 3 Sep 2015 10:49:19 +1000 Stephen Rothwell
> wrote:
>> After merging the drm-misc tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c: In function
>>
On 08-09-15, 12:56, Krzysztof Kozlowski wrote:
> There were no comments from your side for this patchset nor for previous
> Marek's fix. After mentioned change and Bart's re-spin, do you plan to
> grab this patchset and send it for current v4.3 cycle?
Why do you think it should go via Kukjin's
On Mon, 2015-09-07 at 16:01 +, Mathieu Desnoyers wrote:
> - On Sep 3, 2015, at 11:36 PM, Michael Ellerman m...@ellerman.id.au wrote:
> > On Thu, 2015-09-03 at 15:47 +, Mathieu Desnoyers wrote:
> >>
> >> My personal experience is that make headers_install does not necessarily
> >>
Hi Dave,
On Tue, 8 Sep 2015 13:01:21 +1000 Dave Airlie wrote:
>
> Is this to be a regular thing? because I know I'd prefer to merge
> fixes than wait for -rc1 to be an accurate copy of linux-next.
It happens when I can (almost) keep up with Linus' merge rate (often I
can't). It is not an issue
On Mon, 2015-09-07 at 16:24 +0200, Christophe Leroy wrote:
> memcpy() uses instruction dcbz to speed up copy by not wasting time
> loading cache line with data that will be overwritten.
> Some platform like mpc52xx do no have cache active at startup and
> can therefore not use memcpy(). Allthough
On 08.09.2015 11:46, Viresh Kumar wrote:
> On 07-09-15, 17:41, Bartlomiej Zolnierkiewicz wrote:
>> Hi,
>>
>> This patch series adds suspend frequency support (using opp-v2
>> bindings and suspend-opp functionality) to cpufreq-dt driver and
>> then adds suspend opp for Exynos4412 based boards.
>>
On 9/7/15 10:02 PM, Peter Zijlstra wrote:
Please always Cc at least the person who wrote the lines you modify.
On Mon, Sep 07, 2015 at 05:45:20PM +0800, Wanpeng Li wrote:
The sleeper task will be normalized when moved from fair_sched_class, in
order that vruntime will be adjusted either the
Am Dienstag, 16. Juni 2015, 11:46:46 schrieb Boris Brezillon:
Hi Herbert,
>The crypto drivers are supposed to update the IV passed to the crypto
>request before calling the completion callback.
>Test for the IV value before considering the test as successful.
May I ask whether there is anything
On Fri, Aug 28, 2015 at 11:31 AM, Sean Fu wrote:
> On Thu, Aug 27, 2015 at 4:32 PM, Sean Fu wrote:
>> On Thu, Aug 27, 2015 at 10:32 AM, Steven Rostedt wrote:
>>> On Thu, 27 Aug 2015 08:17:29 +0800
>>> Sean Fu wrote:
strace execute result:
write(3, "1\2\0", 3)= -1
On 8 September 2015 at 12:03, Stephen Rothwell wrote:
> Hi Linus,
>
> On Fri, 4 Sep 2015 23:40:53 +0100 (IST) Dave Airlie wrote:
>>
>> This is the main pull request for the drm for 4.3. Nouveau is probably the
>> biggest
>> amount of changes in here, since it missed 4.2. Highlights below, along
On Mon, Sep 07, 2015 at 07:29:42PM +1000, Michael Ellerman wrote:
> On Mon, 2015-24-08 at 11:20:25 UTC, Kevin Hao wrote:
> > This function is only used by get_vtb(). They are almost the same
> > except the reading from the real register. Move the mfspr() to
> > get_vtb() and kill the function
Date: Mon, 7 Sep 2015 19:27:01 -0700
(Please Cc me when replying; I'm not subscribed)
Hi. Perf currently has trouble reading separate debug-info files when trying to
look up symbols in a 'perf report'. According to the gdb documentation:
The arch-specific IOREMAP_MAX_ORDER is introduced in
commit: ff0daca([ARM] Add section support to ioremap) and
commit: a069c89 ([ARM] 3705/1: add supersection support to ioremap()).
But supersections and sections mappings are only used in !SMP && !LPAE case.
Otherwise, mapping is created using the
On 07-09-15, 17:41, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> This patch series adds suspend frequency support (using opp-v2
> bindings and suspend-opp functionality) to cpufreq-dt driver and
> then adds suspend opp for Exynos4412 based boards.
>
> This patch series fixes suspend/resume support
On 07-09-15, 17:41, Bartlomiej Zolnierkiewicz wrote:
> +#ifdef CONFIG_PM
> + .suspend = cpufreq_generic_suspend,
> +#endif
I don't think there is any need of the #ifdef here.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 08-09-15, 07:41, Viresh Kumar wrote:
> > > next_sampling = jiffies + usecs_to_jiffies(new_rate);
> > > appointed_at = dbs_info->cdbs.dwork.timer.expires;
> >
> > For that to work we always need to do stuff for policy->cpus in sync.
> > Do we?
>
> Hmm, we are not in 100%
hello wanpeng,
On Mon, Sep 07, 2015 at 05:45:20PM +0800, Wanpeng Li wrote:
> The sleeper task will be normalized when moved from fair_sched_class, in
> order that vruntime will be adjusted either the task is running or sleeping
> when moved back. The nomalization in switch_to_fair for sleep
On 08-09-15, 03:33, Rafael J. Wysocki wrote:
> > + /* Make sure the work is not canceled on policy->cpus */
>
> I'm not sure what scenario can lead to that. Care to explain?
CPUFREQ_GOV_STOP event called for the policy and so all its works
are in canceled state.
> > + if
Hi Paolo, Stephen,
On 9/8/15 9:35 AM, Stephen Rothwell wrote:
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'grow_halt_poll_ns':
Hi Linus,
On Fri, 4 Sep 2015 23:40:53 +0100 (IST) Dave Airlie wrote:
>
> This is the main pull request for the drm for 4.3. Nouveau is probably the
> biggest
> amount of changes in here, since it missed 4.2. Highlights below, along with
> the usual
> bunch of fixes. There are a few minor
On Tue, 8 Sep 2015, Russell King - ARM Linux wrote:
> On Mon, Sep 07, 2015 at 03:40:36PM -0400, Nicolas Pitre wrote:
> > On Mon, 7 Sep 2015, Arnd Bergmann wrote:
> >
> > > On Thursday 03 September 2015 21:24:00 Nicolas Pitre wrote:
> > > > If 768MB targets were common place then it could be
On 08-09-15, 03:15, Rafael J. Wysocki wrote:
> On Monday, July 27, 2015 05:58:09 PM Viresh Kumar wrote:
> > __gov_queue_work() isn't required anymore and can be merged with
> > gov_queue_work(). Do it.
> >
> > Signed-off-by: Viresh Kumar
>
> Quite frankly I don't see the point.
But isn't that
On 08-09-15, 03:11, Rafael J. Wysocki wrote:
> There really are two cases, either you pass a CPU or gov_queue_work() has to
> walk policy->cpus.
Right (At least for now, we are doing just that.)
> Doing it the way you did hides that IMO.
Maybe. But I see it otherwise. Adding special meaning to
Hi Linus,
On Mon, 07 Sep 2015 16:59:04 -0400 Trond Myklebust
wrote:
>
> The following changes since commit 74d33293e467df61de1b1d8b2fbe29e550dec33b:
>
> Linux 4.2-rc5 (2015-08-02 18:34:55 -0700)
>
> are available in the git repository at:
>
>
On (09/08/15 10:33), Sergey Senozhatsky wrote:
> > I don't understand your concern. To me, this patch makes sense to me.
> > Could you explain your point clearly, again?
>
> OK. suppose someone landed a typo in a 'zram device management' script
>
> echo llzo > /sys/block/zram0/comp_algorithm
>
On Sun, Sep 06, 2015 at 03:47:37PM +0800, Wangnan (F) wrote:
> Hi Namhyung,
Hi,
I'm off until Wednesday. I'll be able to take a look at it on
Thursday.
Thanks,
Namhyung
>
> Thanks for this patchset.
>
> Could you plase have a look at patch 5/27 and 6/27 in my newest pull
> request?
> These
Hi Javi,
On Mon, Sep 7, 2015 at 9:19 PM, Javi Merino wrote:
> Relax the thermal governor requirements of sustainable_power and at
> least two trip points so that it can be bound to any thermal zone.
> Its behavior won't be optimal, it would be the best possible with the
> data provided.
I
Jungseok,
On 09/08/2015 01:34 AM, Jungseok Lee wrote:
On Sep 8, 2015, at 1:06 AM, James Morse wrote:
On 07/09/15 16:48, Jungseok Lee wrote:
On Sep 7, 2015, at 11:36 PM, James Morse wrote:
Hi James,
Having to handle interrupts on top of an existing kernel stack means the
kernel stack must
The shadow which correspond 16 bytes may span 2 or 3 bytes. If shadow
only take 2 bytes, we can return in "if (likely(!last_byte)) ...", but
it calculates wrong, so fix it.
Signed-off-by: Xishi Qiu
---
mm/kasan/kasan.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git
Conservative governor has its own 'enable' field to check if
conservative governor is used for a CPU or not
This can be checked by policy->governor with 'cpufreq_gov_conservative'
and so this field can be dropped.
Because its not guaranteed that dbs_info->cdbs.shared will a valid
pointer for all
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'grow_halt_poll_ns':
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1931:2: error: implicit
declaration of function
On 08-09-15, 02:17, Rafael J. Wysocki wrote:
> > static inline unsigned int get_freq_target(struct cs_dbs_tuners *cs_tuners,
> >struct cpufreq_policy *policy)
> > {
> > @@ -119,12 +132,14 @@ static int dbs_cpufreq_notifier(struct notifier_block
> > *nb,
On Tue, Sep 08, 2015 at 10:20:38AM +0900, Sergey Senozhatsky wrote:
> On (09/08/15 10:07), Minchan Kim wrote:
> [..]
> > > + int ret;
> >
> > For the clarification, I want to call it as 'error' instead of ret.
> >
> > >
> > > backend = find_backend(compress);
> > > if (!backend)
> > > @@
On (09/08/15 10:14), Minchan Kim wrote:
[..]
> > NACK.
> >
> > This is intentional. We haven't returned 'invalid compression algorithm'
> > error from comp_algorithm_store() historically, so someone's script can
> > simply ignore it. However, the script will fail to init the device and
> > user
On (09/08/15 10:07), Minchan Kim wrote:
[..]
> > + int ret;
>
> For the clarification, I want to call it as 'error' instead of ret.
>
> >
> > backend = find_backend(compress);
> > if (!backend)
> > @@ -347,10 +348,10 @@ struct zcomp *zcomp_create(const char *compress, int
> >
Two examples for barriers in wake_up() and co. in memory-barriers.txt
are misleading, along with their explanations:
1. The example which wanted to explain the write barrier in
wake_up() and co. [spotted by Oleg Nesterov ]
2. The example which wanted to explain that the write
Hey Sergey,
On Tue, Sep 08, 2015 at 08:56:35AM +0900, Sergey Senozhatsky wrote:
> On (09/07/15 21:48), Luis Henriques wrote:
> > Validate the new compression algorithm before copying it into the zram
> > 'compressor' field, keeping the old one if it's invalid.
> >
>
> NACK.
>
> This is
> -Original Message-
> From: linux-input-ow...@vger.kernel.org
> [mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Rafael J. Wysocki
> Sent: 08 September, 2015 0:20
> To: Tirdea, Irina
> Cc: Alan Stern; linux...@vger.kernel.org; linux-in...@vger.kernel.org;
>
> -Original Message-
> From: Srinivas Pandruvada [mailto:srinivas.pandruv...@linux.intel.com]
> Sent: 31 August, 2015 22:39
> To: Jonathan Cameron; Markus Pargmann; Tirdea, Irina
> Cc: Lars-Peter Clausen; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org; ker...@pengutronix.de
>
On Monday, July 27, 2015 05:58:11 PM Viresh Kumar wrote:
> Currently update_sampling_rate() runs over each online CPU and
> cancels/queues work on it. Its very inefficient for the case where a
> single policy manages multiple CPUs, as they can be processed together.
>
> Also drop the unnecessary
Hello,
First of all, Thanks for catching a bug and review, Guys.
Below there are just some cleanup.
If you guys think it's better, please respin.
On Mon, Sep 07, 2015 at 03:13:10PM +0100, Luis Henriques wrote:
> zcomp_create() verifies the success of zcomp_strm_{multi,siggle}_create()
> through
On Monday, July 27, 2015 05:58:09 PM Viresh Kumar wrote:
> __gov_queue_work() isn't required anymore and can be merged with
> gov_queue_work(). Do it.
>
> Signed-off-by: Viresh Kumar
Quite frankly I don't see the point.
I'd even remove the inline from its definition and let the compiler decide
On Monday, July 27, 2015 05:58:08 PM Viresh Kumar wrote:
> The sampling rate is updated with a call to update_sampling_rate(), and
> we process CPUs one by one here. While the work is canceled on per-cpu
> basis, it is getting queued (by mistake) for all policy->cpus.
>
> This would result in
On 08.09.2015 00:41, Bartlomiej Zolnierkiewicz wrote:
> Mark 800MHz OPP as a suspend opp for Exynos4412 based
> boards so effectively cpufreq-dt driver behavior w.r.t.
> suspend frequency matches what the old exynos-cpufreq
> driver has been doing.
>
> This patch fixes suspend/resume support on
Hi Takashi,
On 9/7/2015 11:19 PM, Jacek Anaszewski wrote:
Hi Takashi,
Thanks for chasing this.
Milo, could you express your opinion?
On 09/07/2015 02:25 PM, Takashi Iwai wrote:
The commit [b67893206fc0: leds:lp55xx: fix firmware loading error]
tries to address the firmware file handling with
Hi Oleg,
On Mon, Sep 07, 2015 at 07:06:52PM +0200, Oleg Nesterov wrote:
> Sorry for delay,
>
> On 09/02, Boqun Feng wrote:
> >
> > On Tue, Sep 01, 2015 at 06:39:23PM +0200, Oleg Nesterov wrote:
> > > On 09/01, Boqun Feng wrote:
> > > >
> > > > On Tue, Sep 01, 2015 at 11:59:23AM +0200, Oleg
On Mon, Sep 07, 2015 at 03:40:36PM -0400, Nicolas Pitre wrote:
> On Mon, 7 Sep 2015, Arnd Bergmann wrote:
>
> > On Thursday 03 September 2015 21:24:00 Nicolas Pitre wrote:
> > > If 768MB targets were common place then it could be worth changing the
> > > default vmalloc size to accommodate this
On (09/07/15 15:13), Luis Henriques wrote:
> zcomp_create() verifies the success of zcomp_strm_{multi,siggle}_create()
> through comp->stream, which can potentially be pointing to memory that was
> freed if these functions returned an error.
>
> Fixes: beca3ec71fe5 ("zram: add multi stream
On (09/07/15 21:48), Luis Henriques wrote:
> Validate the new compression algorithm before copying it into the zram
> 'compressor' field, keeping the old one if it's invalid.
>
NACK.
This is intentional. We haven't returned 'invalid compression algorithm'
error from comp_algorithm_store()
On Monday, July 27, 2015 05:58:07 PM Viresh Kumar wrote:
> Conservative governor has its own 'enable' field to check if
> conservative governor is used for a CPU or not
>
> This can be checked by policy->governor with 'cpufreq_gov_conservative'
> and so this field can be dropped.
>
> Because its
On 9/6/2015 8:50 PM, Frank Rowand wrote:
> On 9/6/2015 7:16 PM, Frank Rowand wrote:
>> On 9/6/2015 1:46 PM, Rob Herring wrote:
>>> On Fri, Sep 4, 2015 at 8:14 PM, Frank Rowand wrote:
On 9/4/2015 12:12 PM, David Daney wrote:
> From: David Daney
>
> It is perfectly legitimate for
Hi all,
On Thu, 3 Sep 2015 10:49:19 +1000 Stephen Rothwell
wrote:
>
> After merging the drm-misc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c: In function
> 'mdp5_plane_cleanup_fb':
>
Hi Linus,
On Wed, 29 Jul 2015 19:12:56 +0200 Andrea Arcangeli wrote:
>
> On Tue, Jul 28, 2015 at 04:00:15PM +1000, Stephen Rothwell wrote:
> > -359 i386userfaultfd sys_userfaultfd
> > ++374 i386userfaultfd sys_userfaultfd
>
> Do I understand
Hi Mauro,
Today's linux-next merge of the v4l-dvb tree got a conflict in:
mm/Makefile
between commit:
c1a4de99fada ("userfaultfd: mcopy_atomic|mfill_zeropage:
UFFDIO_COPY|UFFDIO_ZEROPAGE preparation")
from Linus' tree and commit:
8025e5ddf9c1 ("[media] mm: Provide new
On Monday, July 27, 2015 05:58:06 PM Viresh Kumar wrote:
> Its better to use __func__ to print functions name instead of writing
> the name in the print statement. This also has the advantage that a
> change in function's name doesn't force us to change the print message
> as well.
>
>
Hi all,
Today's linux-next merge of the parisc-hd tree got a conflict in:
arch/parisc/kernel/irq.c
between commit:
d2109a12198e ("parisc/irq: Use access helper irq_data_get_affinity_mask()")
from Linus' tree and commit:
b15e2f939727 ("parisc: Filter out spurious interrupts in PA-RISC
I have been getting those warnings across a range of guest
kernels in my development virtual machines. The host is a
3.13 Ubuntu kernel. The latest guest on which I reproduced
this is a 4.2 kernel (akpm's tree).
[ 126.902240] clocksource: timekeeping watchdog: Marking clocksource 'tsc' as
Remove sparse warning "symbol 'sptlrpc_plain_init' was not declared"
by including ptlrpc_internal.h, which includes sptlrpc_plain_init.
Signed-off-by: Anders Fridlund
---
drivers/staging/lustre/lustre/ptlrpc/sec_plain.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Add add Device tree bindings for registers
which are not covered by hwmon ABI and are required to
configure specific HW.
---
Changed in v3:
- Fixed vendor prefix
- Added short registers description,
full registers description is available at
On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek wrote:
> On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds
> wrote:
>> On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote:
>>>
>>> That does not work.
>>
>> .. because you didn't do what I told you to do.
>>
>>> I copied a gcc-compiled percpu.o OR
I have been getting those warnings across a range of guest
kernels in my development virtual machines. The host is a
3.13 Ubuntu kernel. The latest guest on which I reproduced
this is a 4.2 kernel (akpm's tree).
[ 126.902240] clocksource: timekeeping watchdog: Marking clocksource 'tsc' as
On Mon, Sep 7, 2015 at 12:30 PM, Maciej W. Rozycki wrote:
> On Mon, 7 Sep 2015, Andy Lutomirski wrote:
>
>> > These are all implementation-specific details, including the INT1
>> > instruction, which is why I am not at all surprised that they are omitted
>> > from architecture manuals.
>>
>>
The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have a built-in
Silicon Motion USB UVC WebCam. Enable support for the USB Video Class
driver and its needed media Kconfig symbols so the camera is supported.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/configs/exynos_defconfig |
Hi All,
After the Energy Aware Scheduling and Power Management microconference
at the LPC I and Morten prepared a summary of it for the LPC readout session.
There was not enough time to present the whole of it, though, so I promised
to send it out, but then got distracted by urgent stuff and
Hi Sergei,
On Tue, 2015-09-08 at 00:24 +0300, Sergei Shtylyov wrote:
> On 09/07/2015 11:50 PM, Alexey Brodkin wrote:
>
> > Current implementation via IS_ERR(phydev) may make no sense because
> > of_phy_attach() returns NULL on failure instead of error value.
>
> Not of_phy_connect()?
I
On 09/07/2015 11:50 PM, Alexey Brodkin wrote:
Current implementation via IS_ERR(phydev) may make no sense because
of_phy_attach() returns NULL on failure instead of error value.
Not of_phy_connect()?
Still for checking result of phy_connect() IS_ERR() is useful.
To address both
On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds
wrote:
> On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote:
>>
>> That does not work.
>
> .. because you didn't do what I told you to do.
>
>> I copied a gcc-compiled percpu.o OR deleted/renamed percpu.o and
>> re-invoked make - this starts a
On Wednesday, August 12, 2015 11:49:19 AM Chen Yu wrote:
> In current code, if system is using performance policy, user can
> modify the max_perf_pct to any values lower than 100:
>
> $ grep . /sys/devices/system/cpu/intel_pstate/m*_perf_pct
> /sys/devices/system/cpu/intel_pstate/max_perf_pct:100
On Monday, September 07, 2015 10:55:43 AM Daniel Wagner wrote:
> On 09/05/2015 04:11 AM, Rafael J. Wysocki wrote:
> > On Friday, September 04, 2015 03:34:55 PM Daniel Wagner wrote:
> >> Instead encode the FREEZE state via the CPU state we allow the
> >> interesting subsystems (MCE, microcode) to
Hi Sergei,
On Mon, 2015-09-07 at 23:53 +0300, Sergei Shtylyov wrote:
> On 09/07/2015 11:50 PM, Alexey Brodkin wrote:
>
> > Current implementation via IS_ERR(phydev) may make no sense because
> > of_phy_attach() returns NULL on failure instead of error value.
> >
> > Still for checking result of
On Monday, September 07, 2015 11:11:19 AM Jiang Liu wrote:
> On 2015/9/4 22:16, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Fri, Sep 4, 2015 at 9:20 AM, Jiang Liu wrote:
> >> On 2015/9/4 4:08, Rafael J. Wysocki wrote:
> >>> Hi Tejun,
> >>>
> >>> On Thu, Sep 3, 2015 at 6:19 PM, Tejun Heo wrote:
On Friday, September 04, 2015 06:06:48 PM Marc Zyngier wrote:
> IRQ controllers and timers are the two types of device the kernel
> requires before being able to use the device driver model.
>
> ACPI so far lacks a proper probing infrastructure similar to the one
> we have with DT, where we're
On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote:
>
> That does not work.
.. because you didn't do what I told you to do.
> I copied a gcc-compiled percpu.o OR deleted/renamed percpu.o and
> re-invoked make - this starts a complete new build from scratch.
Right. Because you changed the
1 - 100 of 1136 matches
Mail list logo
