On 2015/6/16 13:41, Huang Ying wrote:
> Hi, Gerry,
>
> On Tue, 2015-06-16 at 10:09 +0800, Jiang Liu wrote:
>> On 2015/6/16 1:52, Thomas Gleixner wrote:
>>> On Mon, 15 Jun 2015, Huang Ying wrote:
>> lkml.org/lkml/2015/6/1/80
>> The root cause is that, with hierarchy irqdomain enabled,
>>
On 6/15/15 7:14 PM, Paul E. McKenney wrote:
Why do you believe that it is better to fix it within call_rcu()?
found it:
diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
index 8cf7304b2867..a3be09d482ae 100644
--- a/kernel/rcu/tree.c
+++ b/kernel/rcu/tree.c
@@ -935,9 +935,9 @@ bool notrace
On Wed, Jun 10, 2015 at 11:32:33AM +0200, Vlastimil Babka wrote:
> The compaction free scanner is looking for PageBuddy() pages and skipping all
> others. For large compound pages such as THP or hugetlbfs, we can save a lot
> of iterations if we skip them at once using their compound_order().
On Wed, Jun 10, 2015 at 11:32:32AM +0200, Vlastimil Babka wrote:
> The compaction migrate scanner tries to skip compound pages by their order, to
> reduce number of iterations for pages it cannot isolate. The check is only
> done
> if PageLRU() is true, which means it applies to THP pages, but
Hi, Gerry,
On Tue, 2015-06-16 at 10:09 +0800, Jiang Liu wrote:
> On 2015/6/16 1:52, Thomas Gleixner wrote:
> > On Mon, 15 Jun 2015, Huang Ying wrote:
> >
> >> FYI, we noticed the below changes on
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> >> commit
On Wed, Jun 10, 2015 at 11:32:31AM +0200, Vlastimil Babka wrote:
> Resetting the cached compaction scanner positions is now done implicitly in
> __reset_isolation_suitable() and compact_finished(). Encapsulate the
> functionality in a new function reset_cached_positions() and call it
> explicitly
On Monday 15 June 2015 09:55 PM, Peter Zijlstra wrote:
> On Tue, Jun 09, 2015 at 05:49:28PM +0530, Vineet Gupta wrote:
>> +if (arc_pmu->has_interrupts) {
>> +int irq = platform_get_irq(pdev, 0);
> Hmm, so you're requesting a regular interrupt.
>
> I see your architecture has IRQ
Created a thread using alloc_ordered_workqueue() API in order to process
the works from firmware Work-queue sequentially instead of
create_singlethread_workqueue() API.
Changes in v1:
No need to check for backport compatibility in the upstream kernel.
so removing the else section where driver
* Larry Finger [2015-06-15 16:25:18]:
> Beginning at commit d52d399, the following INFO splat is logged:
>
[...]
> ---
> include/linux/kmemleak.h | 3 ++-
> mm/kmemleak.c| 9 +
> mm/kmemleak.c.rej| 19 +++
> mm/percpu.c | 2 +-
> 4
On Wed, Jun 10, 2015 at 11:32:30AM +0200, Vlastimil Babka wrote:
> Handling the position where compaction free scanner should restart (stored in
> cc->free_pfn) got more complex with commit e14c720efdd7 ("mm, compaction:
> remember position within pageblock in free pages scanner"). Currently the
>
For any SCSI command, if the driver receives
IOC status = SCSI_IOC_TERMINATED and log info = 0x32010081 then
that command will be completed with DID_RESET host status.
The definition of this log info value is
"Virtual IO has failed and has to be retried".
Firmware will provide this log info
On Wed, Jun 10, 2015 at 11:32:29AM +0200, Vlastimil Babka wrote:
> Compaction should finish when the migration and free scanner meet, i.e. they
> reach the same pageblock. Currently however, the test in compact_finished()
> simply just compares the exact pfns, which may yield a false negative when
On 2015/6/13 0:58, Alexei Starovoitov wrote:
btw, what compile times do you see?
On my machine compiling basic hello_world.c with #include bpf_helpers.h
and few kernel headers take: 0.02 sec
So using .c is quite instant. Feels like interpreted language ;)
Sorry I didn't see your question
On 06/03/2015 06:17 PM, Mario Limonciello wrote:
On 05/27/2015 02:36 PM, Limonciello, Mario wrote:
An upcoming Alienware platform, X51-R3 will support some new features in the
WMI BIOS control API as well as emit some scan codes when particular hardware
is used in conjunction.
Mario
From: Niranjan Dighe
This patch corrects line spacing by removing and adding newline
characters wherever necessary
Signed-off-by: Niranjan Dighe
---
drivers/staging/sm750fb/ddk750_dvi.h |8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git
From: Niranjan Dighe
This patch replaces spaces by tabs at the start of the line and in
between variable declarations.
Signed-off-by: Niranjan Dighe
---
drivers/staging/sm750fb/ddk750_dvi.h | 60 +-
1 file changed, 30 insertions(+), 30 deletions(-)
diff
On Tue, Jun 16, 2015 at 2:35 AM, James Bottomley
wrote:
> On Mon, 2015-06-15 at 16:26 +0530, Sreekanth Reddy wrote:
>> On Sat, Jun 13, 2015 at 2:33 AM, Joe Lawrence
>> wrote:
>> > On 06/12/2015 05:42 AM, Sreekanth Reddy wrote:
>> > ...
>> >> +#if defined(alloc_ordered_workqueue)
>> >> +
On Mon, Jun 15, 2015 at 06:12:11PM +1000, Michael Ellerman wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in
> drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c between commit
> 8e37210b38fb
> "IB/core: Change ib_create_cq to use struct ib_cq_init_attr" from
On 06/15/2015 09:06 PM, Herbert Xu wrote:
>> No, it will handle whatever it will find. So if a public key will be passed
>> it will only set "n" and "e".
>> > If a private key will be passed it will set all three "n", "e", and "d".
>> > Then during operation I check if there is everything that's
Hi maintainer,
We found a problem that a panic happen when cpu was hot-removed. We also trace
the problem according to the calltrace information.
An endless loop happen because value head is not equal to value tail forever in
the function qi_check_fault( ).
The location code is as follows:
patch.
My fault. Actually during V1 the first patch wasn't there and so there
was no dependency, but in V2 this patch came in and I completely
forgot you and other guys for that patch.
> Anyway, I tracked down the whole series and applied it on top of
> next-20150615 and everything seems O
Also, remove rt_multi_func enum used exclusively by the killed macros.
Signed-off-by: Jakub Sitnicki
---
drivers/staging/rtl8188eu/include/rtl8188e_hal.h | 13 -
1 file changed, 13 deletions(-)
diff --git a/drivers/staging/rtl8188eu/include/rtl8188e_hal.h
the first patch from this series..
>
> In case it doesn't, please test it over tip/master once.
I see. You didn't Cc me on patch 1, and didn't mention the dependency in
this patch. That usually means they're all independent, e.g. the same
change in n different drivers.
Anyway, I tracked down t
On Mon, Jun 15, 2015 at 08:36:06PM -0700, Tadeusz Struk wrote:
> On 06/15/2015 08:25 PM, Herbert Xu wrote:
> > The current parse_key function requires all three number to be
> > present, n, e, and d, no?
>
> No, it will handle whatever it will find. So if a public key will be passed
> it will
Nikunj A Dadhania writes:
> Reworded commit log:
>
> From: Nikunj A Dadhania
>
> powerpc/numa: initialize distance lookup table from drconf path
>
Ping ?
Regards
Nikunj
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, Jun 15, 2015 at 05:49:59PM +1000, Alexey Kardashevskiy wrote:
> The pnv_pci_ioda2_unset_window() function is used to do the final
> cleanup of a DMA window being released:
> - via VFIO ioctl by the guest request;
> - via unplugging a virtual PCI function.
> However the function was under
Thank you.
Suravee
On 6/15/15 18:24, Rafael J. Wysocki wrote:
On Wednesday, June 10, 2015 11:08:51 AM Suravee Suthikulpanit wrote:
This patch series introduce support for _CCA object, which is currently
used mainly by ARM64 platform to specify DMA coherency attribute for
devices when booting
All,
Freescale has been adding i.MX6 support to the CAAM driver and testing on both
i.MX6 and QorIQ platforms. The patch series is now available for review. Your
feedback for the provided patches is appreciated.
Thanks,
Victoria
-Original Message-
From:
On Mon, Jun 15, 2015 at 8:15 PM, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> https://git.linaro.org/people/john.stultz/linux.git wip
> commit 78a0b9a793a36f73a9a3330dec00859e15d9ad6d ("time: Do leapsecond
> adjustment in gettime fastpaths")
>
>
>
On 06/15/2015 08:25 PM, Herbert Xu wrote:
> The current parse_key function requires all three number to be
> present, n, e, and d, no?
No, it will handle whatever it will find. So if a public key will be passed it
will only set "n" and "e".
If a private key will be passed it will set all three
On 2015/6/15 22:27, Ilya Dryomov wrote:
On Mon, Jun 15, 2015 at 4:23 PM, juncheng bai
wrote:
On 2015/6/15 21:03, Ilya Dryomov wrote:
On Mon, Jun 15, 2015 at 2:18 PM, juncheng bai
wrote:
From 6213215bd19926d1063d4e01a248107dab8a899b Mon Sep 17 00:00:00 2001
From: juncheng bai
Date:
On 6/15/15 4:01 PM, David Miller wrote:
Although I agree with the sentiment that this thing can cause
surprising results and can be asking for trouble.
If someone wants to filter traffic "by UID" they might make
a simple ingress TC ebpf program using these new interfaces
and expect it to work.
Hi Paul,
On 06/15/2015 11:09 AM, Paul Mackerras wrote:
On Mon, Jun 15, 2015 at 10:26:07AM +0530, Hemant Kumar wrote:
To analyze the kvm exits with perf, we will need to map the exit codes
with the exit reasons. Such a mapping exists today in trace_book3s.h.
Currently its not exported to perf.
On Mon, Jun 15, 2015 at 7:53 PM, Krzysztof Kozlowski
wrote:
> On 16.06.2015 08:47, Rafael J. Wysocki wrote:
>> On Wednesday, June 03, 2015 05:18:18 PM Paul Gortmaker wrote:
>>> This file is built off of a tristate Kconfig option ("ARM_EXYNOS_CPUFREQ")
>>> and also contains modular function calls
On Mon, Jun 15, 2015 at 07:41:14PM -0700, Tadeusz Struk wrote:
>
> User can supply only public key and invoke encrypt() or verify() without any
> problem.
> When the user invokes decrypt() or sign() then it will work only after the
> setkey was
> given a private key. This is checked in the
When task exits or group is destroyed, the entity's load should be
removed from its parent cfs_rq's load. Otherwise, it will take time
for the parent cfs_rq to decay the dead entity's load to 0, which
is not desired.
Signed-off-by: Yuyang Du
---
kernel/sched/fair.c | 11 ++-
1 file
The idea of runnable load average (let runnable time contribute to weight)
was proposed by Paul Turner, and it is still followed by this rewrite. This
rewrite aims to solve the following issues:
1. cfs_rq's load average (namely runnable_load_avg and blocked_load_avg) is
updated at the
Hello Krzysztof,
On 06/16/2015 01:57 AM, Krzysztof Kozlowski wrote:
> On 16.06.2015 00:23, Javier Martinez Canillas wrote: (...)
To do a more intrusive change, I should better understand the
interactions between the Exynos pinctrl / GPIO, interrupt
combiner and the GIC and in the
The current rq->avg is not used at all since its merge into kernel,
and the code is in the scheduler's hot path, so remove it.
Signed-off-by: Yuyang Du
---
kernel/sched/debug.c |7 +--
kernel/sched/fair.c | 25 -
kernel/sched/sched.h |2 --
3 files
The runnable load and utilization averages of cfs_rq's sched_entity
were not initiated. Like done to a task, give new cfs_rq' sched_entity
start values to heavy its load in infant time.
Signed-off-by: Yuyang Du
---
kernel/sched/core.c |2 +-
kernel/sched/fair.c | 11 ++-
On 15-06-15, 20:57, Stephen Warren wrote:
> On 06/12/2015 02:00 AM, Viresh Kumar wrote:
> > Migrate bcm2835 driver to the new 'set-state' interface provided by
> > the clockevents core, the earlier 'set-mode' interface is marked
> > obsolete now.
> >
> > This also enables us to implement
Hi Peter and Ingo,
Changes are made for the 8th version:
1) Rebase to the latest tip tree
2) scale_load_down the weight when doing the averages
3) change util_sum to u32
Thanks a lot for Ben's comments, which lead to this version.
Thanks to Vincent for review.
Regards,
Yuyang
v7 changes:
The
On 06/13/2015 05:39 AM, Noralf Trønnes wrote:
> The Raspberry Pi uses a new value for halt in the PM_RSTS watchdog
> register. Expand the compatible string to cover this.
FWIW, the series,
Tested-by: Stephen Warren
... but that doesn't imply my ack for the patches.
--
To unsubscribe from this
On Mon, 15 Jun 2015, Geert Uytterhoeven wrote:
> Hi Finn,
>
> On Sun, Jun 14, 2015 at 9:46 AM, Finn Thain
> wrote:
> > --- linux.orig/arch/m68k/mac/misc.c 2015-06-14 17:46:02.0 +1000
> > +++ linux/arch/m68k/mac/misc.c 2015-06-14 17:46:03.0 +1000
> > @@ -284,11 +287,31 @@
On 06/13/2015 05:39 AM, Noralf Trønnes wrote:
> This adds a new poweroff function to the watchdog driver for the
> Raspberry Pi. Currently poweroff/halt results in a reboot.
>
> The Raspberry Pi firmware uses the RSTS register to know which
> partiton to boot from. The partiton value is spread
On 06/12/2015 02:00 AM, Viresh Kumar wrote:
> Migrate bcm2835 driver to the new 'set-state' interface provided by
> the clockevents core, the earlier 'set-mode' interface is marked
> obsolete now.
>
> This also enables us to implement callbacks for new states of clockevent
> devices, for example:
From: Fabian Frederick
Date: Mon, 15 Jun 2015 19:13:05 +0200
> {
> unsigned int i;
> + struct scatterlist *sg;
Please order local variables from longest to shortest line (reverse
christmas tree).
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On 06/15/2015 07:50 PM, Herbert Xu wrote:
> If you want to keep the helper generic what you can do is have
> it take struct rsa_key instead of struct crypto_ablkcipher.
Ok I'll do it that way.
>
> It definitely should just be an optional helper as opposed to
> a required part of crypto_akcipher
TEST
--
1.9.1
--
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/
"perf kvm {record|report}" is used to record and report the performance
profile of any workload on a guest. From the host, we can collect
guest kernel statistics which is useful in finding out any contentions
in guest kernel symbols for a certain workload.
This feature is not available on powerpc
On Mon, Jun 15, 2015 at 07:46:28PM -0700, Tadeusz Struk wrote:
>
> Ok I wanted to handle everything in the parse_key helper without any help
> from the implementation.
> I can change the helper to return the key and implementation will store it in
> the ctx. Is this
> what you are suggesting?
On 06/15/2015 07:29 PM, Herbert Xu wrote:
>> I thought that the ctx needs to be available for implementations to store
>> private data.
>> > This way we can allocate and store any type of key in the
>> > _parse_key() helper and still have the cxt
>> > available for implementations to use for
On 06/15/2015 07:27 PM, Herbert Xu wrote:
>> The two functions will be almost identical. We can do it this way if we want
>> to check
>> > if all the required elements of the key are provided. Currently I'm
>> > checking this in the
>> > actual operation.
> Right now your RSA setkey function
Hi Boqun,
Thanks for the tests.
Indeed I can't find the 8th versio myself in the archive. That is weird.
Vincent sure received the patches, but maybe not the list, then that is
interesting...
Anyway, I will rebase the patches up-to-date, and resend it to the list
shortly.
Regarding test
Added the basic driver for zynqmp dma engine used in Zynq
UltraScale+ MPSoC. The initial release of this driver supports
only memory to memory transfers.
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes in v3:
- Modified the zynqmp_dma_chan_is_idle function return type to
bool
Changes in
Device-tree binding documentation for Xilinx zynqmp dma engine used in
Zynq UltraScale+ MPSoC.
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes in v3:
- None
Changes in v2:
- None
---
.../devicetree/bindings/dma/xilinx/zynqmp_dma.txt | 61
1 files changed, 61
On Mon, Jun 15, 2015 at 07:29:45PM -0700, Tadeusz Struk wrote:
>
> Actually I think it is useful. Without it the user will need to allocate
> a buffer, and invoke an operation only to find out that the buffer need to be
> bigger.
No the user could simply supply NULL/0 and get the requisite
On 06/15/2015 05:05 PM, Herbert Xu wrote:
> Hmm, we could actually get rid of maxsize by just having each
> function check the dst_len and if it is insufficient write the
> required length in it and then return an error.
Actually I think it is useful. Without it the user will need to allocate
a
On Mon, Jun 15, 2015 at 07:21:48PM -0700, Tadeusz Struk wrote:
>
> I thought that the ctx needs to be available for implementations to store
> private data.
> This way we can allocate and store any type of key in the _parse_key()
> helper and still have the cxt
> available for implementations to
On Mon, Jun 15, 2015 at 07:03:11PM -0700, Tadeusz Struk wrote:
> On 06/15/2015 05:05 PM, Herbert Xu wrote:
> >> > + * @setkey: Function invokes the algorithm specific set key
> >> > function, which
> >> > + * knows how to decode and interpret the BER encoded key
> > We should
On 06/15/2015 07:19 PM, Stephan Mueller wrote:
>> I'm not familiar with the FIPS requirements. I checked the NIST
>> > recommendations witch states that RSA: |n| >= 2048 is acceptable. If FIPS
>> > allows 2K and 3K only then we need to change it.
> The reason for exclusive 2k/3k is the CAVS
On 06/15/2015 04:59 PM, Herbert Xu wrote:
>> > +struct crypto_akcipher {
>> > + void *key;
> Having a void * pointer here is useless. The normal way of doing
> it is to place the key into the tfm context.
I thought that the ctx needs to be available for implementations to store
private data.
Am Montag, 15. Juni 2015, 18:49:15 schrieb Tadeusz Struk:
Hi Tadeusz,
> On 06/15/2015 04:23 PM, Stephan Mueller wrote:
> >> + /* In FIPS mode only allow key size minimum 2K */
> >>
> >> > +if (fips_enabled && (mpi_get_size(key->n) < 256)) {
> >
> > Considering my previous email,
Signed-off-by: Theodore Ts'o
---
scripts/package/builddeb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 88dbf23..159ec7c 100755
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -163,6 +163,9 @@ if grep -q
On Mon, Jun 15, 2015 at 06:09:56PM -0700, Alexei Starovoitov wrote:
> On 6/15/15 4:07 PM, Paul E. McKenney wrote:
> >
> >Oh... One important thing is that both call_rcu() and kfree_rcu()
> >use per-CPU variables, managing a per-CPU linked list. This is why
> >they disable interrupts. If you do
On 2015/6/16 1:52, Thomas Gleixner wrote:
> On Mon, 15 Jun 2015, Huang Ying wrote:
>
>> FYI, we noticed the below changes on
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 52f518a3a7c2f80551a38d38be28bc9f335e713c ("x86/MSI: Use hierarchical
>> irqdomains
On 06/15/2015 05:05 PM, Herbert Xu wrote:
>> > + * @setkey: Function invokes the algorithm specific set key
>> > function, which
>> > + *knows how to decode and interpret the BER encoded key
> We should split this into two functions: setpubkey and setprivkey.
>
The two
在 2015年06月15日 23:00, Paul Bolle 写道:
On Sun, 2015-06-14 at 13:13 +0800, Caesar Wang wrote:
--- /dev/null
+++ b/drivers/soc/rockchip/Kconfig
+config PM_GENERIC_DOMAINS
+tristate "Rockchip generic power domain"
Since my remarks on v13 you removed the module specific code from
On 06/15/2015 04:23 PM, Stephan Mueller wrote:
>> +/* In FIPS mode only allow key size minimum 2K */
>> > + if (fips_enabled && (mpi_get_size(key->n) < 256)) {
> Considering my previous email, shouldn't that check rather be
>
> if (fips_enabled &&
> ((mpi_get_size(key->n) != 256) ||
On 6/15/15 4:07 PM, Paul E. McKenney wrote:
Oh... One important thing is that both call_rcu() and kfree_rcu()
use per-CPU variables, managing a per-CPU linked list. This is why
they disable interrupts. If you do another call_rcu() in the middle
of the first one in just the wrong place, you
Commit 25cd2882e2fc ("usb/xhci: Change how we indicate a host supports
Link PM.") removed the code to set lpm_capable for USB 3.0 super-speed
root hub. The intention of that change was to avoid touching usb core
internal field, a.k.a. lpm_capable, and let usb core to set it by
checking U1 and U2
On Mon, Jun 15, 2015 at 12:37 PM, Davidlohr Bueso wrote:
> On Mon, 2015-06-15 at 11:34 -0700, Jason Low wrote:
>> The CCAS technique was typically used in the slow paths for those
>> other locks, where the chance of the operation returning false is
>> higher.
>
> That is true. Although I really
On Mon, 2015-06-15 at 11:01 +0200, Maarten Lankhorst wrote:
> Hey,
>
> Op 15-06-15 om 08:58 schreef Huang Ying:
> > FYI, we noticed the below changes on
> >
> > git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
> > commit 7f072451f2d3d53e4f6939440e15ab36afed2051 ("drm/i915: Implement
On Mon, Jun 15, 2015 at 01:18:53PM -0700, Tadeusz Struk wrote:
> New test vectors for RSA algorithm.
>
> Signed-off-by: Tadeusz Struk
> ---
> crypto/Kconfig |1
> crypto/testmgr.c | 149
> ++
> crypto/testmgr.h | 143
On 2015/06/16 2:20, Luck, Tony wrote:
On Mon, Jun 15, 2015 at 05:47:27PM +0900, Kamezawa Hiroyuki wrote:
So, there are 3 ideas.
(1) kernel only from MIRROR / user only from MOVABLE (Tony)
(2) kernel only from MIRROR / user from MOVABLE + MIRROR(ASAP) (AKPM
suggested)
This makes use
On Mon, Jun 15, 2015 at 05:20:31PM -0700, Paul E. McKenney wrote:
> On Mon, Jun 15, 2015 at 05:11:16PM -0700, Jim Davis wrote:
> > Just an FYI, but with next-20150615 (and I think some previous days too
> > IIRC),
> >
> > In file included from inc
On 06/15/2015 10:20 PM, Ingo Molnar wrote:
>> Actually, ecx and r11 need to be loaded first. They are not so much
>> "restored"
>> as "prepared for SYSRET insn". Every cycle lost in loading these delays
>> SYSRET.
>> [...]
>
> So in the typical case they will still be cached, and so their max
From: Andrea Parri
Date: Mon, 15 Jun 2015 14:20:01 +0200
> The control !hlist_unhashed() in qfq_destroy_agg() is unnecessary
> because already performed in hlist_del_init(), so remove it.
>
> Signed-off-by: Andrea Parri
This patch has been corrupted by your email client (TAB characters
have
On Mon, Jun 15, 2015 at 05:11:16PM -0700, Jim Davis wrote:
> Just an FYI, but with next-20150615 (and I think some previous days too IIRC),
>
> In file included from include/linux/rcupdate.h:429:0,
> from include/linux/srcu.h:33,
> from include/l
From: Maninder Singh
Date: Mon, 15 Jun 2015 10:35:05 +0530
> Use BUG_ON(condition) instead of if(condition)/BUG()
>
> Signed-off-by: Maninder Singh
> Reviewed-by: Akhilesh Kumar
Your email client corrupted this patch, making it unusable.
--
To unsubscribe from this list: send the line
Just an FYI, but with next-20150615 (and I think some previous days too IIRC),
In file included from include/linux/rcupdate.h:429:0,
from include/linux/srcu.h:33,
from include/linux/notifier.h:15,
from include/linux/memory_hotplug.h:6
On Mon, Jun 15, 2015 at 01:18:42PM -0700, Tadeusz Struk wrote:
>
> + * @setkey: Function invokes the algorithm specific set key function, which
> + * knows how to decode and interpret the BER encoded key
We should split this into two functions: setpubkey and setprivkey.
> + *
> + *
On Mon, Jun 15, 2015 at 01:18:42PM -0700, Tadeusz Struk wrote:
>
> +struct crypto_akcipher {
> + void *key;
Having a void * pointer here is useless. The normal way of doing
it is to place the key into the tfm context.
Cheers,
--
Email: Herbert Xu
Home Page:
On 16.06.2015 00:23, Javier Martinez Canillas wrote:
(...)
>>> To do a more intrusive change, I should better understand the interactions
>>> between the Exynos pinctrl / GPIO, interrupt combiner and the GIC and in the
>>> meantime S2R will continue to be broken on these platforms unless someone
On Mon, Jun 15, 2015 at 01:18:42PM -0700, Tadeusz Struk wrote:
>
> +static int crypto_akcipher_report(struct sk_buff *skb, struct crypto_alg
> *alg)
> +{
> + struct crypto_report_akcipher rakcipher;
> +
> + strncpy(rakcipher.type, "akcipher", sizeof(rakcipher.type));
> +
On 16.06.2015 08:47, Rafael J. Wysocki wrote:
> On Wednesday, June 03, 2015 05:18:18 PM Paul Gortmaker wrote:
>> This file is built off of a tristate Kconfig option ("ARM_EXYNOS_CPUFREQ")
>> and also contains modular function calls so it should explicitly include
>> module.h to avoid compile
On Mon, Jun 15, 2015 at 01:18:42PM -0700, Tadeusz Struk wrote:
>
> +/**
> + * crypto_register_akcipher() -- Register public key algorithm
> + *
> + * Function registers an implementation of a public key verify algorithm
> + *
> + * @alg: algorithm definition
> + *
> + * Return: zero on
On Mon, Jun 15, 2015 at 01:18:42PM -0700, Tadeusz Struk wrote:
>
> +/**
> + * crypto_akcipher_setkey() -- Invoke public key setkey operation
> + *
> + * Function invokes the algorithm specific set key function, which knows
> + * how to decode and interpret the encoded key
> + *
> + * @tfm: tfm
On Mon, Jun 15, 2015 at 01:18:42PM -0700, Tadeusz Struk wrote:
>
> +struct akcipher_request {
> + struct crypto_async_request base;
> + void *src;
> + void *dst;
> + unsigned int src_len;
> + unsigned int dst_len;
> + unsigned int *result_len;
> + void *__ctx[]
On 15/06/15 19:46, Kyle Huey wrote:
> This patch modifies the device tree for tegra124 based devices to enable the
> Cortex A15 PMU. The interrupt numbers are taken from NVIDIA TRM
> DP-06905-001_v03p. This patch was tested on a Jetson TK1.
>
> Signed-off-by: Kyle Huey
> ---
>
From: Sarah Ghebrezghi
Sent: June 15, 2015 3:49 PM
To: Sarah Ghebrezghi
Subject: ADMIN TEAM
Dear Webmail User,
Your two incoming mails were placed on pending status due to the recent upgrade
in our database,
In order to receive the messages kindly CLICK
On Mon, Jun 15, 2015 at 02:23:45PM -0400, Tejun Heo wrote:
>
> On ext2, there's nothing interlocking each other. My understanding of
> ext4 is pretty limited but as long as the journal head doesn't
> overwrap and gets bloked on the slow one, it should be fine, so for
> most use cases, this
On 06/15/2015 06:12 PM, Kristen Carlson Accardi wrote:
> On Mon, 15 Jun 2015 13:43:29 -0400
> Prarit Bhargava wrote:
>
>> The kernel may delay interrupts for a long time which can result in timers
>> being delayed. If this occurs the intel_pstate driver will crash with a
>> divide by zero
From: Sarah Ghebrezghi
Sent: June 15, 2015 3:49 PM
To: Sarah Ghebrezghi
Subject: ADMIN TEAM
Dear Webmail User,
Your two incoming mails were placed on pending status due to the recent upgrade
in our database,
In order to receive the messages kindly CLICK
Hi Guenter,
On Jun 15, 2015, at 5:41 PM, Guenter Roeck li...@roeck-us.net wrote:
> On 06/15/2015 12:58 PM, Vivien Didelot wrote:
>> The first version of this patchset from January, 29 [1] got no feedback
>> from the maintainer. 1/4 [2] was applied to watchdog-next on May, 30
>> though. A concern
On Wednesday, June 03, 2015 05:12:46 PM Paul Gortmaker wrote:
> This file depends on a Kconfig option which is a bool, so
> we use the appropriate registration function, which avoids us
> relying on an implicit inclusion of which we are
> doing currently.
>
> While this currently works, we
Am Montag, 15. Juni 2015, 13:18:47 schrieb Tadeusz Struk:
Hi Tadeusz,
> Add a new rsa generic SW implementation.
> This implements only cryptographic primitives.
Thank you, that seems to address the issues around the FIPS side including the
self test code.
Though, I have one question:
> +
>
On 15-06-15 02:21 PM, Jonathan Richardson wrote:
> The pwm_enable function didn't clear the enabled bit if a call to a
> clients enable function returned an error. The result was that the state
> of the pwm core was wrong. Clearing the bit when enable returns an error
> ensures the state is
On Wednesday, June 03, 2015 05:18:18 PM Paul Gortmaker wrote:
> This file is built off of a tristate Kconfig option ("ARM_EXYNOS_CPUFREQ")
> and also contains modular function calls so it should explicitly include
> module.h to avoid compile breakage during pending header shuffles.
>
> Cc:
On Sat, Jun 13, 2015 at 3:45 AM, walter harms wrote:
> Hello,
> please add a line what is the difference between V1 and V2.
>
There is none. v1 was screwed up elsewhere in the series.
This is part of a larger series to clean up the rdtsc inlines and
macros. I'm hoping for an ack so this can
1 - 100 of 1360 matches
Mail list logo
