Jason A. Donenfeld wrote:
>
> Siphash needs a random secret key, yes. The point is that the hash
> function remains secure so long as the secret key is kept secret.
> Other functions can't make the same guarantee, and so nervous periodic
> key rotation is necessary, but in most cases nothing is d
On 12/15/2016 06:15 AM, Michael S. Tsirkin wrote:
> That's the default now, no need for makefiles to set it.
>
> Signed-off-by: Michael S. Tsirkin
> ---
[...]
> drivers/net/can/Makefile | 1 -
For drivers/net/can/Makefile:
Acked-by: Marc Kleine-Budde
regards,
On Wednesday, December 14, 2016 11:07 PM Michal Hocko wrote:
> From: Michal Hocko
>
> Tetsuo Handa has pointed out that 0a0337e0d1d1 ("mm, oom: rework oom
> detection") has subtly changed semantic for costly high order requests
> with __GFP_NOFAIL and withtout __GFP_REPEAT and those can fail rig
On Thu, Dec 15, 2016 at 12:57:29AM +0100, Alexandre Belloni wrote:
> The license test has been mangled at some point then copy pasted across
> multiple files. Restore it to what it should be.
> Note that this is not intended as a license change.
>
> Cc: Dong Aisheng
> Cc: Eric Nelson
> Cc: Gary
On Tue, 13 Dec 2016 09:03:19 -0700
Shuah Khan wrote:
> On 12/13/2016 08:25 AM, Steven Rostedt wrote:
> > On Tue, 13 Dec 2016 07:06:18 -0700
> > Shuah Khan wrote:
> >
> >> On 12/12/2016 08:23 PM, Masami Hiramatsu wrote:
> >>> Ping?
> >>>
> >>> On Fri, 25 Nov 2016 21:58:48 +0900
> >>> Masami Hira
On 12/08/2016 03:26 PM, Rafael J. Wysocki wrote:
On Thursday, December 08, 2016 10:55:59 AM Jani Nikula wrote:
On Thu, 08 Dec 2016, "Rafael J. Wysocki" wrote:
On Wednesday, December 07, 2016 10:35:07 AM Jani Nikula wrote:
On Wed, 07 Dec 2016, "Rafael J. Wysocki" wrote:
On Monday, December 0
There's a new C: entry for IRC or similar chat, so add the OFTC #mm channel.
While at it, add more F: entries for least the more prominent include/ files
related to mm.
Signed-off-by: Vlastimil Babka
---
MAINTAINERS | 16
1 file changed, 16 insertions(+)
diff --git a/MAINTAINER
On 12/14/2016 11:32 PM, Laurent Pinchart wrote:
> Hi Peter,
>
> On Thursday 01 Sep 2016 14:22:54 Peter Ujfalusi wrote:
>> Hi,
>>
>> The following series will convert the omapdrm stack to use the generic
>> videmode instead of the private omap_video_timings struct for the panel
>> information.
>>
在 2016/12/15 15:24, Jia He 写道:
nsm_use_hostnames is a module parameter and it will be exported to sysctl
procfs. This is to let user sometimes change it from userspace. But the
minimal unit for sysctl procfs read/write it sizeof(int).
^^^is^^^
In big en
On Wed, Dec 14, 2016 at 11:52 PM, Jiri Olsa wrote:
> On Wed, Dec 14, 2016 at 11:26:49PM -0800, Stephane Eranian wrote:
>> On Wed, Dec 14, 2016 at 9:55 AM, Peter Zijlstra wrote:
>> >
>> > Just spotted this again, ping?
>> >
>> Ok, on what processor running what command, so I can try and reproduce?
On Thu, 15 Dec 2016 13:15:34 +0530
Kirti Wankhede wrote:
> On 12/15/2016 1:09 AM, Alex Williamson wrote:
> > This sample driver was originally under Documentation/ and was moved
> > to samples, but build support was never adjusted for the new location.
> >
> > Signed-off-by: Alex Williamson
> >
在 2016/12/15 15:24, Jia He 写道:
This is to let bool variable could be correctly displayed in
big/little endian sysctl procfs. sizeof(bool) is arch dependent,
proc_dobool should work in all arches.
Suggested-by: Pan Xinhui
Signed-off-by: Jia He
---
include/linux/sysctl.h | 2 ++
kernel/sysct
On Dec 15 2016 or thereabouts, Andy Shevchenko wrote:
> There is a possibility that lock will be left acquired.
> Consolidate error path under out_free_unlock label.
>
> Reported-by: kbuild test robot
> Cc: Benjamin Tissoires
> Signed-off-by: Andy Shevchenko
With Darren's remarks, the patch is
On Thu, 15 Dec 2016 12:05:35 +0530
Kirti Wankhede wrote:
> On 12/14/2016 2:28 AM, Alex Williamson wrote:
> > As part of the mdev support, type1 now gets a task reference per
> > vfio_dma and uses that to get an mm reference for the task while
> > working on accounting. That's the correct thing t
On Thu, 2016-12-15 at 15:57 +0800, Herbert Xu wrote:
> Jason A. Donenfeld wrote:
> >
> > Siphash needs a random secret key, yes. The point is that the hash
> > function remains secure so long as the secret key is kept secret.
> > Other functions can't make the same guarantee, and so nervous
> > p
On 12/14/2016 07:11 PM, Michal Hocko wrote:
On Wed 14-12-16 18:28:38, Vlastimil Babka wrote:
On 12/14/2016 03:53 PM, Michal Hocko wrote:
From: Michal Hocko
Higher order requests oom debugging is currently quite hard. We do have
some compaction points which can tell us how the compaction is op
(Adding Luis because he has been working on request_firmware() lately)
Pali Rohár writes:
>> > So no, there is no argument against... request_firmware() in
>> > fallback mode with userspace helper is by design blocking and
>> > waiting for userspace. But waiting for some change in DTS in
>> > ke
Hi Alexandre,
On mer., déc. 14 2016, Alexandre Belloni
wrote:
> The dual GPLv2/X11 license the text that is used
> is missing a few characters.
As for the other series could you squash all this series in a single
patch and fix the commit log (s/test/text/) ?
Thanks,
Gregory
>
>
> Alexand
From: GaoShengWu
Line 28 of kthread.c violates chapter 3 of CodingStyle - put the opening
brace last on the line, and put the closing brace first.
Signed-off-by: GaoShengWu
---
checkpatch.pl complained as the following:
ERROR: open brace '{' following struct go on the same line
#28: FILE: ker
On Thu, 2016-12-15 at 01:04 +0100, Alexandre Belloni wrote:
> The license test has been mangled at some point then copy pasted
> across
> multiple files. Restore it to what it should be.
> Note that this is not intended as a license change.
>
> Cc: Marcel Ziswiler
> Signed-off-by: Alexandre Bello
On 15.12.2016 00:29, Jason A. Donenfeld wrote:
> Hi Hannes,
>
> On Wed, Dec 14, 2016 at 11:03 PM, Hannes Frederic Sowa
> wrote:
>> I fear that the alignment requirement will be a source of bugs on 32 bit
>> machines, where you cannot even simply take a well aligned struct on a
>> stack and put it
On 14/12/16 23:36, Laurent Pinchart wrote:
>> I guess a first step is Peter Ujfalusi's series:
>> https://lkml.org/lkml/2016/9/1/267
>
> Peter, do you plan to respin that patch series ?
That series has been merged already.
Tomi
signature.asc
Description: OpenPGP digital signature
On Wed, Dec 14, 2016 at 11:26:49PM -0800, Stephane Eranian wrote:
> On Wed, Dec 14, 2016 at 9:55 AM, Peter Zijlstra wrote:
> >
> > Just spotted this again, ping?
> >
> Ok, on what processor running what command, so I can try and reproduce?
For me its more of a correctness issue, i've not actually
On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> usleep_range() is intended for delays in the 10us to 10ms range that need
> good precision. a useleep_range(1, will effectively be no more than an
> imprecise udelay with some added cache disruption as it will fire more or
> less immediately - use ud
It's also way easier to read using atomic_inc_not_zero..
Reviewed-by: Christoph Hellwig
Not sure you're sending this to the right maintainers, though. You
probably want to include Greg.
On Wed, Dec 14, 2016 at 11:17:46PM -0800, Dan Williams wrote:
> For warnings that should only ever trigger during development and
> testing replace WARN statements with lockdep_assert_held. The lockdep
> pattern is prevalent, and these paths are are well covered by libnvdimm
> + dax unit tests.
>
On Wed, Dec 14, 2016 at 10:59:59PM -0800, Dan Williams wrote:
> Johannes points out that the warning in alloc_dax_region() seems to
> imply that multiple devices might claim a dax region. In fact it's a
> warning to driver developers that the dax core wants to own the
> driver_data pointer for the
Looks fine:
Reviewed-by: Christoph Hellwig
(but I agree with the bracing nitpick from Gavin)
On 12/15/16 17:45, Christoph Hellwig wrote:
> On Thu, Dec 15, 2016 at 10:33:47AM +0900, Damien Le Moal wrote:
>> For a regular block device, I agree. But in Stephan case, I think that
>> the check really needs to be against the physical block size, with the
>> added condition that the bdev is a D
On Thu, 15 Dec 2016, Jani Nikula wrote:
> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
>> usleep_range() is intended for delays in the 10us to 10ms range that need
>> good precision. a useleep_range(1, will effectively be no more than an
>> imprecise udelay with some added cache disruption as it
On Thu, Dec 15, 2016 at 10:47:57AM +0200, Jani Nikula wrote:
> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> > usleep_range() is intended for delays in the 10us to 10ms range that need
> > good precision. a useleep_range(1, will effectively be no more than an
> > imprecise udelay with some added
On Thu, Dec 15, 2016 at 10:33:47AM +0900, Damien Le Moal wrote:
> For a regular block device, I agree. But in Stephan case, I think that
> the check really needs to be against the physical block size, with the
> added condition that the bdev is a DASD device (similarly to the zone
> alignment check
Hello.
On 15/12/16 06:15, Michael S. Tsirkin wrote:
__bitwise__ used to mean "yes, please enable sparse checks
unconditionally", but now that we dropped __CHECK_ENDIAN__
__bitwise is exactly the same.
There aren't many users, replace it by __bitwise everywhere.
Signed-off-by: Michael S. Tsirkin
n 14/12/16 23:12, Philippe Reynes wrote:
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> Signed-off-by: Philippe Reynes
Thanks Philippe. We'll get some testing done on this.
Bert.
On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> Even on fast systems a 2 microsecond delay is most likely more efficient
> as a busy-wait loop. The overhead of a hrtimer does not seem warranted -
> change this to a udelay(2).
Similar concerns as in [1]. We don't need the accuracy of udelay() here
Hi Bibby,
On Wed, Dec 14, 2016 at 1:14 PM, Bibby Hsieh wrote:
>
> MT8173 overlay can support UYVY and YUYV format,
> we add the format in DRM driver.
>
> Signed-off-by: Bibby Hsieh
> ---
> drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 6 ++
> drivers/gpu/drm/mediatek/mtk_drm_plane.c | 2 ++
>
On Thu, 2016-12-15 at 00:57 +0100, Alexandre Belloni wrote:
> The license test has been mangled at some point then copy pasted
> across
> multiple files. Restore it to what it should be.
> Note that this is not intended as a license change.
>
> Cc: Geert Uytterhoeven
> Cc: Marcel Ziswiler
> Cc:
On Dez 15 2016, Minchan Kim wrote:
> You mean program itself access the address(ie, 0xb740) is hang
> while access the address from the debugger is OK?
Yes.
> Can you reproduce it easily?
100%
> Did you test it in real machine or qemu on x86?
Both real and kvm.
> Could you show me h
On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote:
> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> > Even on fast systems a 2 microsecond delay is most likely more efficient
> > as a busy-wait loop. The overhead of a hrtimer does not seem warranted -
> > change this to a udelay(2).
>
On Thu, Dec 15, 2016 at 10:25:19AM +0100, Daniel Vetter wrote:
> On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote:
> > On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> > > Even on fast systems a 2 microsecond delay is most likely more efficient
> > > as a busy-wait loop. The overhead of
On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote:
> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> > Even on fast systems a 2 microsecond delay is most likely more efficient
> > as a busy-wait loop. The overhead of a hrtimer does not seem warranted -
> > change this to a udelay(2).
>
If the ac-detect gpio does not support interrupts, provide a fallback
to poll the gpio at a configurable interval.
Signed-off-by: Peter Rosin
---
v2 -> v3 changes:
- use device_property_read_u32 instead of of_property_read_u32
v1 -> v2 changes:
- use poll-interval instead of ti,poll-interval-ms
This patch fixes the bug of devfreq_add_device(). The devfreq device must
have the default governor. If find_devfreq_governor() returns error,
devfreq_add_device() fail to add the devfreq instance.
Fixes: 1b5c1be2c88e ("PM / devfreq: map devfreq drivers to governor using name")
Cc: sta...@vger.ker
This patch fixes the wrong return value. If devfreq driver requires the wrong
and non-available governor, it is fail. So, this patch returns the error
insead of -EPROBE_DEFER.
Fixes: 403e0689d2a9 ("PM / devfreq: exynos: Add support of bus frequency of
sub-blocks using passive
This patch just removes '.' character from the sysfs name of devfreq-event
device as following. Usually, the subsystem uses the similiar naming style
such as {framework name}{Number}.
- old : /sys/class/devfreq-event/event.X
- new : /sys/class/devfreq-event/eventX
Signed-off-by: Chanwoo Choi
---
This patches update the devfreq and devfreq-event device. I add the summary
of each patch as following.
- Patch1 is documented for bus frequency scaling of Exynos5433's VDD_INT.
The related-to patches[1] were merged by Exynos SoC maintainer.
- Patch2 uses the regmap interface instead of raw_read
This patch just adds the simple log to show the PPMU device's registration
during the kernel booting.
Cc: Kukjin Kim
Cc: Krzysztof Kozlowski
Cc: Javier Martinez Canillas
Cc: linux-samsung-...@vger.kernel.org
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/event/exynos-ppmu.c | 5 -
1 file
This patch modifies the device name as devfreq[X] for sysfs by using the
'devfreq'
prefix word instead of separate device name. On user-space aspect, user would
find the some devfreq drvier with 'devfreq[X]' pattern. So, this patch modify
the
device name as following:
- /sys/class/devfreq/[non-st
Hi Luis,
Thanks for the patch.
On 12/13/2016 04:08 AM, Luis R. Rodriguez wrote:
We need to ensure that when driver developers use the custom firmware
fallback mechanism it was not a copy and paste bug. These use cases on
upstream drivers are rare, we only have 2 upstream users and its for
reall
The macro is to be used similarly as WARN_ON as:
if (WARN_ON_RATELIMIT(condition, state))
do_something();
One would expect only 'condition' to affect the 'if', but
WARN_ON_RATELIMIT does internally only:
WARN_ON((condition) && __ratelimit(state))
So the 'if' is affected by the ratelim
This patch just fixes the checkpatch warnings.
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/devfreq.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 47206a21bb90..8e5938c9c7d6 100644
--- a/drivers/d
This patch uses the regmap interface to read and write the registers for exynos
PPMU device instead of the legacy memory map functions.
Cc: Kukjin Kim
Cc: Krzysztof Kozlowski
Cc: Javier Martinez Canillas
Cc: linux-samsung-...@vger.kernel.org
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/eve
On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> On Thu, Dec 15, 2016 at 10:47:57AM +0200, Jani Nikula wrote:
>> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
>> > usleep_range() is intended for delays in the 10us to 10ms range that need
>> > good precision. a useleep_range(1, will effectively be
Em Wed, 14 Dec 2016 17:18:57 -0800
Greg Kroah-Hartman escreveu:
> On Wed, Dec 14, 2016 at 04:38:32PM -0800, Linus Torvalds wrote:
> > On Wed, Dec 14, 2016 at 11:18 AM, Jaegeuk Kim wrote:
> > >
> > > BTW, I just downloaded mainline, and tried to build a debian package but
> > > failed due to mi
On Wed, 14 Dec 2016, Roland Scheidegger wrote:
> Am 14.12.2016 um 22:40 schrieb Thomas Gleixner:
> > And the whole mess stems from the fact that the deadline is not as one
> > would expect simply compared against the sum of the counter and the adjust
> > MSR.
> Why would it be compared against the
This patch adds the detailed corrleation between sub-blocks and VDD_INT power
line for Exynos5433. VDD_INT provided the power source to INT (Internal) block.
Cc: Rob Herring
Cc: devicet...@vger.kernel.org
Signed-off-by: Chanwoo Choi
---
Documentation/devicetree/bindings/devfreq/exynos-bus.txt |
This patch shows the real clock rate after calling clk_set_rate()
to debug it.
Cc: Kukjin Kim
Cc: Krzysztof Kozlowski
Cc: Javier Martinez Canillas
Cc: linux-samsung-...@vger.kernel.org
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/exynos-bus.c | 8
1 file changed, 4 insertions(+),
Add myself to the DEVFREQ entry as reviewer, I've been helping reviewing
and tesing the devfreq support patches for the couple of years. Also,
I'm going to contribute the improvement for devfreq subsystem. It would
be easier for me for review if I'm cc'ed for patches.
Cc: MyungJoo Ham
Cc: Kyungmi
On 12/14/2016 03:30 PM, Sean Paul wrote:
On Wed, Dec 14, 2016 at 12:03 AM, Archit Taneja wrote:
Hi,
On 12/12/2016 08:28 PM, Sean Paul wrote:
On Fri, Dec 9, 2016 at 9:49 PM, Caesar Wang wrote:
Look likes, the BOE panel FW didn't ack the DPCD600 signal from the host
device, that will caus
On Thu, 15 Dec 2016, Gavin Shan wrote:
> > static int get_nodes_in_cpumask(const struct cpumask *mask, nodemask_t
> > *nodemsk)
> > {
> >-int n, nodes;
> >+int n, nodes = 0;
> >
> > /* Calculate the number of nodes in the supplied affinity mask */
> >-for (n = 0, nodes = 0; n < num
This patches fix the bug of devfreq_add_device() when governor name is wrong
and the wrong return value of probe() function for exynos_bus.c driver.
And I've been helping reviewing and tesing the devfreq support patches
for the couple of years. Also, I'm going to contribute the improvement
for dev
Hi,
On 14/12/2016 20:39, Alex Williamson wrote:
> This sample driver was originally under Documentation/ and was moved
> to samples, but build support was never adjusted for the new location.
>
> Signed-off-by: Alex Williamson
> ---
> samples/Kconfig|7 +++
> samples/Makefil
Hi!
> The driver uses a private lock for synchronization of the xmit function and
> the xmit completion handler, but since the NETIF_F_LLTX flag is not set,
> the xmit function is also called with the xmit_lock held.
>
> On the other hand the completion handler uses the reverse locking order by
>
On 12/15/2016 1:42 PM, Alex Williamson wrote:
> On Thu, 15 Dec 2016 13:15:34 +0530
> Kirti Wankhede wrote:
>
>> On 12/15/2016 1:09 AM, Alex Williamson wrote:
>>> This sample driver was originally under Documentation/ and was moved
>>> to samples, but build support was never adjusted for the new
xtensa supports DMA API debug and contiguous DMA, mark it as such.
Signed-off-by: Max Filippov
---
Documentation/features/io/dma-api-debug/arch-support.txt | 2 +-
Documentation/features/io/dma-contiguous/arch-support.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Do
On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote:
>> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
>> > Even on fast systems a 2 microsecond delay is most likely more efficient
>> > as a busy-wait loop. The overhead of a hrtimer does not
Dear all,
Please ignore this patches.
I sent the patches[1][2] again.
[1] https://lkml.org/lkml/2016/12/15/119
[2] https://lkml.org/lkml/2016/12/15/122
--
Regards,
Chanwoo Choi
On 2016년 11월 24일 14:01, Chanwoo Choi wrote:
> This patches modify the devfreq and devfreq-event framework for improvi
QCA BAM also support command descriptor which allows the SW to
create descriptors of type command which does not generate any
data transmissions but configures registers in the peripheral.
In command descriptor the 32bit address point to the start of
the command block which holds the command elemen
The current DMA APIs only support SGL or data in generic format.
The QCA BAM DMA engine data cannot be mapped with already
available APIs due to following reasons.
1. The QCA BAM DMA engine uses custom flags which cannot be
mapped with generic DMA engine flags.
2. Some peripheral driver like QC
The default SG does not have flag field but the BAM requires
flags to be passed for each SG. Since SG is linux generic and
other subsystem drivers also use this SG, so we cannot add flag
field in default SG. Now, this patch adds BAM SG and its mapping
operations. This BAM SG contains generic SG and
These patches mainly adds the support for QCA BAM command
descriptor and per SG flags which are required for implementing
BAM DMA support for some QCA peripherals like QPIC NAND/LCD.
The BAM command descriptors perform all register reads and writes
while data descriptors do data transfer. The QPIC
arch/blackfin/mm/sram-alloc.c does not use any miscdevice so the
inclusion of linux/miscdevice.h is unnecessary.
This patch remove this inclusion.
Signed-off-by: Corentin Labbe
---
arch/blackfin/mm/sram-alloc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/blackfin/mm/sram-alloc.c b/ar
BAM custom mapping mainly adds per SG BAM specific flag support
which cannot be implemented with generic SG mapping function.
For each SG, it checks for dma_flags and set the same in
bam_async_desc.
Signed-off-by: Abhishek Sahu
---
drivers/dma/qcom/bam_dma.c | 92 ++
The QCA BAM DMA descriptor has other flags which cannot be
mapped with generic DMA engine flags. This patch creates a
new header file for BAM driver and moves the BAM flags
to this file. Some other BAM specific mapping functions will
be added in this file which can be used by different QCA
peripher
bfin_crc.h driver does not use any miscdevice, so this patch remove this
unnecessary inclusion.
Signed-off-by: Corentin Labbe
---
drivers/crypto/bfin_crc.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/bfin_crc.h b/drivers/crypto/bfin_crc.h
index 75cef4d..786ef74 100644
--- a
bfin_crc.c print some u32 as unsigned long ans so gcc complains
about it.
This patch remove the long print qualifier.
Signed-off-by: Corentin Labbe
---
drivers/crypto/bfin_crc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/crypto/bfin_crc.c b/drivers/crypto/b
On 12/15/2016 01:46 AM, Andrei Vagin wrote:
> On Sun, Dec 11, 2016 at 12:54:56PM +0100, Michael Kerrisk (man-pages) wrote:
>> [was: [PATCH 0/4 v3] Add an interface to discover relationships
>> between namespaces]
>>
>> Hello Andrei
>>
>> See below for my attempt to document the following.
>
> Hi M
Ping.
On 11/03/2016, 07:32 PM, Jiri Slaby wrote:
> With this reproducer:
> struct sockaddr_alg alg = {
> .salg_family = 0x26,
> .salg_type = "hash",
> .salg_feat = 0xf,
> .salg_mask = 0x5,
> .salg_name = "digest_null",
> };
> int sock, sock2;
On 12/15/2016 10:45 AM, Pavel Machek wrote:
Giuseppe, is there documentation available for the chip? Driver says
Documentation available at:
http://www.stlinux.com
but that page does not work for me...
Hi Pavel, yes the page has been removed but all the relevant and
updated driver
On Thu, Dec 15, 2016 at 11:52:34AM +0200, Jani Nikula wrote:
> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote:
> >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
> >> > Even on fast systems a 2 microsecond delay is most likely more ef
From: Behalf Of Jason A. Donenfeld
> Sent: 14 December 2016 18:46
...
> + ret = *chaining = siphash24((u8 *)&combined, offsetof(typeof(combined),
> end),
If you make the first argument 'const void *' you won't need the cast
on every call.
I'd also suggest making the key u64[2].
Davi
From: Michal Hocko
Tetsuo has been stressing OOM killer path with many parallel allocation
requests when he has noticed that it is not all that hard to swamp
kernel logs with warn_alloc messages caused by allocation stalls. Even
though the allocation stall message is triggered only once in 10s th
pm_qos.h does not use any miscdevice, so this patch
remove this unnecessary inclusion.
Signed-off-by: Corentin Labbe
---
include/linux/pm_qos.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/pm_qos.h b/include/linux/pm_qos.h
index 0f65d36..d4d3479 100644
--- a/include/linux/pm_
Michael Kerrisk (man-pages) wrote:
> >│Is 'keyring' allowed to be 0? Reading the source, it │
> >│appears so. In this case, by default, the key is │
> >│assigned to the session keyring. But, the │
> >│KEYCTL_SET_REQKEY_KEYRING also seems to have
On Thu, Dec 15, 2016 at 01:09:20AM +0100, Pali Rohár wrote:
> If cmdline is not in DT, but /chosen exists, then function
> early_init_dt_scan_chosen() use cmdline from CONFIG_CMDLINE.
Ah, yes. Looks to me then as if the bug exists there, and not in arch
code then. early_init_dt_scan_chosen() co
On Thu, 15 Dec 2016, Ville Syrjälä wrote:
> On Thu, Dec 15, 2016 at 11:52:34AM +0200, Jani Nikula wrote:
>> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
>> > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote:
>> >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote:
>> >> > Even on fast sys
From: Linus Torvalds
> Sent: 15 December 2016 00:11
> On Wed, Dec 14, 2016 at 3:34 PM, Jason A. Donenfeld wrote:
> >
> > Or does your reasonable dislike of "word" still allow for the use of
> > dword and qword, so that the current function names of:
>
> dword really is confusing to people.
>
> If
On Thu 15-12-16 15:54:37, Hillf Danton wrote:
> On Wednesday, December 14, 2016 11:07 PM Michal Hocko wrote:
[...]
> > /* Avoid allocations with no watermarks from looping endlessly */
> > - if (test_thread_flag(TIF_MEMDIE) && !(gfp_mask & __GFP_NOFAIL))
> > + if (test_thread_flag(TIF_MEMD
Hi Sebastien,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.9]
[cannot apply to next-20161215]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Sebastien-Bourdelin/of
On 14/12/2016 18:47, Mason wrote:
> On 14/12/2016 18:08, Thomas Gleixner wrote:
>
>> On Wed, 14 Dec 2016, Mason wrote:
>>
>>> I'm seeing Linux v4.9 crash (dereferencing NULL) when I try to online
>>> the secondary core, after putting it offline.
>>
>> Does the patch below fix the issue?
>>
>> Tha
Olaf Hering writes:
> KY,
>
> if a hyperv VM crashes alot of work must be done to prepare the
> environment for the kdump kernel. This approach is different compared to
> all the other VM types, or baremetal. Since the just crashed kernel is
> per definition unreliable all that work should be don
On Thu, Dec 15, Olaf Hering wrote:
> On Thu, Dec 15, Vitaly Kuznetsov wrote:
>
> > I see a number of minor but at least one major issue against such move:
> > At least for some Hyper-V versions (2012R2 for example)
> > CHANNELMSG_UNLOAD_RESPONSE is delivered to the CPU which initially sent
> > C
On Thu, Dec 15, Vitaly Kuznetsov wrote:
> I see a number of minor but at least one major issue against such move:
> At least for some Hyper-V versions (2012R2 for example)
> CHANNELMSG_UNLOAD_RESPONSE is delivered to the CPU which initially sent
> CHANNELMSG_REQUESTOFFERS and on kdump we may not
On 14.12.2016 23:37, Alexandre Belloni wrote:
The license test has been mangled at some point then copy pasted across
multiple files. Restore it to what it should be.
Note that this is not intended as a license change.
Cc: Arnaud Ebalard
Cc: Boris Brezillon
Cc: Ezequiel Garcia
Cc: Paul Bolle
On Thu 2016-12-15 11:08:36, Giuseppe CAVALLARO wrote:
> On 12/15/2016 10:45 AM, Pavel Machek wrote:
> >Giuseppe, is there documentation available for the chip? Driver says
> >
> > Documentation available at:
> > http://www.stlinux.com
> >
> >but that page does not work for me...
>
> Hi P
On 12/14/2016 12:11 PM, Bhumika Goyal wrote:
> Check for v4l2_subdev_ops structures that are only passed as an
> argument to the function v4l2_subdev_init. This argument is of type
> const, so v4l2_subdev_ops structures having this property can also be
> declared const.
> Signed-off-by: Bhumika G
I and Sergey would like to volunteer as printk code maintainers.
It is a code that everyone is using, various people fix bugs or
even add features but there is nobody really interested into
maintaining it.
I and Sergey have put a lot of effort into understanding the code
and related problems. We a
On 15/12/2016 04:36, Mike Galbraith wrote:
> Grumpy master.today, w. tune for maximum bloat PREEMPT config.
I'll queue a revert of 0b9f6c4615c993d2b552e0d2bd1ade49b56e5beb.
Paolo
> [ 101.898909] ===
> [ 101.898910] [ INFO: suspicious RCU usage. ]
> [ 101.898912]
Olaf Hering writes:
> On Thu, Dec 15, Vitaly Kuznetsov wrote:
>
>> I see a number of minor but at least one major issue against such move:
>> At least for some Hyper-V versions (2012R2 for example)
>> CHANNELMSG_UNLOAD_RESPONSE is delivered to the CPU which initially sent
>> CHANNELMSG_REQUESTOF
Olaf Hering writes:
> On Thu, Dec 15, Olaf Hering wrote:
>
>> On Thu, Dec 15, Vitaly Kuznetsov wrote:
>>
>> > I see a number of minor but at least one major issue against such move:
>> > At least for some Hyper-V versions (2012R2 for example)
>> > CHANNELMSG_UNLOAD_RESPONSE is delivered to the C
1 - 100 of 753 matches
Mail list logo
