On Sun, Jul 9, 2017 at 10:08 PM, Cong Wang wrote:
> netlink_sendskb() is problematic, it releases sock refcnt
> silently which could cause troubles we can call it multiple
> times. info->notify_sock is a good example where we
> setup once and use it to send netlink skb's for many times.
> It shoul
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sergei Shtylyov
commit 5f4c8cafe1148f8a91287072815df8f0b66f0e5c upstream.
All R8A7794 manuals I have here (0.50 and 1.10) agree that the PFC driver
has ATAG0# and ATAWR0# signals in IPSR12 swap
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Salido
commit 6265539776a0810b7ce6398c27866ddb9c6bd154 upstream.
The driver_override implementation is susceptible to race condition when
different threads are reading vs storing a diffe
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Yan, Zheng
commit b50c2de51e611da90cf3cf04c058f7e9bbe79e93 upstream.
The dirfragtree is lazily updated, it's not always accurate. Infinite
loops happens in following circumstance.
- client sen
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Stephan Mueller
commit b61929c654f2e725644935737c4c1ea9c741e2f8 upstream.
Initialise ctr_completion variable before use.
Cc:
Signed-off-by: Harsh Jain
Signed-off-by: Stephan Mueller
Signed
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 629e014bb8349fcf7c1e4df19a842652ece1c945 upstream.
Currently we just stash anything we got into file->f_flags, and the
report it in fcntl(F_GETFD). This patch just cle
This is the start of the stable review cycle for the 4.9.37 release.
There are 41 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Jul 12 17:10:36 UTC 2017.
Anything receive
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sabrina Dubroca
commit 9e52b32567126fe146f198971364f68d3bc5233f upstream.
Always try to parse an address, since kstrtoul() will safely fail when
given a symbol as input. If that fails (which wi
On 10 July 2017 at 16:52, Marc Zyngier wrote:
> Ard and myself have just spent quite some time lately trying to pin
> down an issue in the DMA code which was taking the form of a PCIe USB3
> controller issuing a DMA access at some bizarre address, and being
> caught red-handed by the IOMMU.
>
> Af
Hi Alan,
On 07/08/2017 06:21 PM, Alan Stern wrote:
Pardon me for barging in, but I found this whole interchange extremely
confusing...
On Sat, 8 Jul 2017, Ingo Molnar wrote:
* Paul E. McKenney wrote:
On Sat, Jul 08, 2017 at 10:35:43AM +0200, Ingo Molnar wrote:
* Manfred Spraul wrote:
H
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 80f18379a7c350c011d30332658aa15fe49a8fa5 upstream.
Add a central define for all valid open flags, and use it in the uniqueness
check.
Signed-off-by: Christoph Hellwig
On 07/10/2017 09:22 AM, Vlastimil Babka wrote:
> On 07/09/2017 09:32 AM, Anshuman Khandual wrote:
>> On 07/07/2017 11:39 PM, Mike Kravetz wrote:
>>> On 07/07/2017 10:45 AM, Kirill A. Shutemov wrote:
On Fri, Jul 07, 2017 at 10:29:52AM -0700, Mike Kravetz wrote:
> On 07/07/2017 03:23 AM, Kir
This is the start of the stable review cycle for the 4.11.10 release.
There are 36 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Jul 12 17:10:29 UTC 2017.
Anything receiv
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit 04fb365c453e14ff9e8a28f1c46050d920a27a4a upstream.
%p will leak kernel pointers, so let's not expose the information on
dmesg and instead use %pK. %pK will only show the ac
On Mon, Jul 10, 2017 at 5:47 AM, Corey Minyard wrote:
>
> https://github.com/cminyard/linux-ipmi.git tags/for-linus-4.13
Hmm.
This is signed using a completely new key.
That part is fine: the new key is 4k bits instead of the old 1k key.
But the new key is signed by absolutely nothing - not
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Abeni
commit 236222d39347e0e486010f10c1493e83dbbdfba8 upstream.
According to the Intel datasheet, the REP MOVSB instruction
exposes a pretty heavy setup cost (50 ticks), which hurts
shor
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Jeremie Rapin
commit fd90f73a9925f248d696bde1cfc836d9fda5570d upstream.
Added the USB serial device ID for the CEL ZigBee EM3588
radio stick.
Signed-off-by: Jeremie Rapin
Acked-by: Johan Hov
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Juergen Gross
commit 1a3fc2c402810bf336882e695abd1678dbc8d279 upstream.
There has been a report about a deadlock in the xenbus driver:
[ 247.979498] =
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Yan, Zheng
commit b50c2de51e611da90cf3cf04c058f7e9bbe79e93 upstream.
The dirfragtree is lazily updated, it's not always accurate. Infinite
loops happens in following circumstance.
- client se
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Jarkko Sakkinen
commit 13b47cfcfc60495cde216eef4c01040d76174cbe upstream.
While cleaning up sysfs callback that prints EK we discovered a kernel
memory leak. This commit fixes the issue by zer
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Pismenny
commit 5ecce4c9b17bed4dc9cb58bfb10447307569b77b upstream.
The ib_uverbs_create_ah() ind ib_uverbs_modify_qp() calls receive
the port number from user input as part of its attrib
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Gruenbacher
commit 961ae1d83d055a4b9ebbfb4cc8ca62ec1a7a3b74 upstream.
Before commit 88ffbf3e03 "GFS2: Use resizable hash table for glocks",
glocks were freed via call_rcu to allow read
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Josh Zimmerman
commit d1bd4a792d3961a04e6154118816b00167aad91a upstream.
If a TPM2 loses power without a TPM2_Shutdown command being issued (a
"disorderly reboot"), it may lose some state that
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Jiahau Chang
commit dec08194ffeccfa1cf085906b53d301930eae18f upstream.
For AMD Promontory xHCI host, although you can disable USB 2.0 ports in
BIOS settings, those ports will be enabled anyway
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
commit 664b7c4728821767e0228ee161bab87db2be58f1 upstream.
Andre Przywara noticed that we can get the
following warning with -EPROBE_DEFER:
"WARNING: CPU: 1 PID: 89 at drivers/b
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Sergei Shtylyov
commit da7a692fbbab07f4e9798b5b52798f6e3256dd8f upstream.
The R8A7791 PFC driver was apparently based on the preliminary revisions
of the user's manual, which omitted the H
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 629e014bb8349fcf7c1e4df19a842652ece1c945 upstream.
Currently we just stash anything we got into file->f_flags, and the
report it in fcntl(F_GETFD). This patch just cl
On Mon, Jul 10, 2017 at 06:42:06PM +0200, Peter Zijlstra wrote:
> On Mon, Jul 10, 2017 at 07:46:09AM -0700, Andi Kleen wrote:
> > > So how much of the gain is simply due to skipping NOHZ? Mike used to
> > > carry a patch that would throttle NOHZ. And that is a _far_ smaller and
> > > simpler patch
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Sergei Shtylyov
commit 5f4c8cafe1148f8a91287072815df8f0b66f0e5c upstream.
All R8A7794 manuals I have here (0.50 and 1.10) agree that the PFC driver
has ATAG0# and ATAWR0# signals in IPSR12 swa
On 07/10/17 09:08, Rob Herring wrote:
> On Fri, Jul 7, 2017 at 7:28 PM, wrote:
>> From: Frank Rowand
>>
>> Correct existing node name detection when overlay node name has
>> a unit-address.
>>
>> Expected test result is overlay will update the nodes and properties
>> for /testcase-data-2/fairway
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit 4324b6084f45b9faebda8d6563d8625d22b4b5df upstream.
Fix typos in hscif2_clk_b_mux[] and hscif4_ctrl_mux[].
Fixes: a56069c46c102710 ("pinctrl: sh-pfc: r8a7795: Add HSC
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Sergei Shtylyov
commit 58439280f84e6b39fd7d61f25ab30489c1aaf0a9 upstream.
PINMUX_IPSR_MSEL() macro invocation for the TX2 signal has apparently wrong
1st argument -- most probably a result of
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Herrenschmidt
commit 7cf916bd639bd26db7214f2205bccdb4b9306256 upstream.
The current definition is wrong. This breaks my upcoming
Aspeed virtual hub driver.
Signed-off-by: Benjamin He
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 80f18379a7c350c011d30332658aa15fe49a8fa5 upstream.
Add a central define for all valid open flags, and use it in the uniqueness
check.
Signed-off-by: Christoph Hellwig
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Grzeschik
commit b3b51417d0af63fb9a06662dc292200aed9ea53f upstream.
The usbip stack dynamically allocates the transfer_buffer and
setup_packet of each urb that got generated by the tcp
4.11-stable review patch. If anyone has any objections, please let me know.
--
From: Juri Lelli
commit f70b281b59a871545362a494d99a644153fbbaac upstream.
The sysfs cpu_capacity entry for each CPU has nothing to do with
PROC_FS, nor it's in /proc/sys path.
Remove such ifdef.
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit ff801b716effd652f420204eddb36f6e4a716819 upstream.
Stephen reported the following build warning in UP:
kernel/sched/fair.c:2657:9: warning: 'struct sched_domain' declar
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Abeni
commit 236222d39347e0e486010f10c1493e83dbbdfba8 upstream.
According to the Intel datasheet, the REP MOVSB instruction
exposes a pretty heavy setup cost (50 ticks), which hurts
shor
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Rik van Riel
commit 7d894e6e34a5cdd12309c7e4a3f830277ad4b7bf upstream.
Then 'this_cpu' and 'prev_cpu' are in the same socket, select_idle_sibling()
will do its thing regardless of the return v
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Stephan Mueller
commit b61929c654f2e725644935737c4c1ea9c741e2f8 upstream.
Initialise ctr_completion variable before use.
Cc:
Signed-off-by: Harsh Jain
Signed-off-by: Stephan Mueller
Signed
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Rik van Riel
commit 815abf5af45f04f759f12f3172afd15226fd7f71 upstream.
The effective_load() function was only used by the NUMA balancing
code, and not by the regular load balancing code. Now t
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Rik van Riel
commit 3fed382b46baac83703130fe4cd3d9147f427fb9 upstream.
Since select_idle_sibling() can place a task anywhere on a socket,
comparing loads between individual CPU cores makes no
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 1ad3aaf3fcd206628a19a9b9e0922b95e2d4 upstream.
Hackbench recently suffered a bunch of pain, first by commit:
4c77b18cf8b7 ("sched/fair: Make select_idle_cpu() more
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit c743f0a5c50f2fcbc628526279cfa24f3dabe182 upstream.
More users for for_each_cpu_wrap() have appeared. Promote the construct
to generic cpumask interface.
The implementati
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Herrenschmidt
commit 7cf916bd639bd26db7214f2205bccdb4b9306256 upstream.
The current definition is wrong. This breaks my upcoming
Aspeed virtual hub driver.
Signed-off-by: Benjamin He
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Vlastimil Babka
commit 8655d5497735b288f8a9b458bd22e7d1bf95bb61 upstream.
A customer has reported a soft-lockup when running an intensive
memory stress test, where the trace on multiple CPU's
On 07/10/2017 06:41 AM, Michal Hocko wrote:
> On Mon 10-07-17 17:02:11, Anshuman Khandual wrote:
>> In the header file, just specify the dependency of MREMAP_FIXED
>> on MREMAP_MAYMOVE and make it explicit for the user space.
>
> I really fail to see a point of this patch. The depency belongs to t
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jeremie Rapin
commit fd90f73a9925f248d696bde1cfc836d9fda5570d upstream.
Added the USB serial device ID for the CEL ZigBee EM3588
radio stick.
Signed-off-by: Jeremie Rapin
Acked-by: Johan Hov
On 2017-07-10 14:09, Mark Brown wrote:
> On Sun, Jul 09, 2017 at 12:48:10AM +0300, Andy Shevchenko wrote:
>> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote:
>
>>> Tested on the IOT2000 where the second SPI bus is connected to an
>>> Arduino-compatible connector and multiplexed between SPI, GPI
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit 04fb365c453e14ff9e8a28f1c46050d920a27a4a upstream.
%p will leak kernel pointers, so let's not expose the information on
dmesg and instead use %pK. %pK will only show the ac
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit e271b2c909a22a2c13b2d5f77f2ce0091b74540c upstream.
Make sure to release any OF device-node reference taken when creating
the USB device.
Note that we currently do not hold
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jarkko Sakkinen
commit 13b47cfcfc60495cde216eef4c01040d76174cbe upstream.
While cleaning up sysfs callback that prints EK we discovered a kernel
memory leak. This commit fixes the issue by zer
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Josh Zimmerman
commit f77af15165847406b15d8f70c382c4cb15846b2a upstream.
The TPM class has some common shutdown code that must be executed for
all drivers. This adds some needed functionality
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Gruenbacher
commit 961ae1d83d055a4b9ebbfb4cc8ca62ec1a7a3b74 upstream.
Before commit 88ffbf3e03 "GFS2: Use resizable hash table for glocks",
glocks were freed via call_rcu to allow read
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jiahau Chang
commit dec08194ffeccfa1cf085906b53d301930eae18f upstream.
For AMD Promontory xHCI host, although you can disable USB 2.0 ports in
BIOS settings, those ports will be enabled anyway
Hi Alan,
On Thu, Jul 6, 2017 at 11:47 AM, Alan Tull wrote:
> fpga-mgr has three methods for programming FPGAs, depending on
> whether the image is in a scatter gather list, a contiguous
> buffer, or a firmware file. This makes it difficult to write
> upper layers as the caller has to assume wheth
Hi Masama,
Thank you for looking into this.
You are right, I don't see the issue when my trace_clock = x86-tsc.
I tried with other clocks and apparently, I only see this when my
clock is either perf or global.
You mentioned this happens when "it adjusts timestamp", so does that
mean this is an ex
On 07/08/2017 05:08 AM, Thomas Gleixner wrote:
> On Fri, 7 Jul 2017, Doug Berger wrote:
>
>> The irq_gc_mask_disable_reg_and_ack() function name implies that it
>> provides the combined functions of irq_gc_mask_disable_reg() and
>> irq_gc_ack(). However, the implementation does not actually do
>>
On Fri, Jul 07, 2017 at 11:30:41AM +0200, Thierry Reding wrote:
> On Fri, Jul 07, 2017 at 08:42:32AM +0100, Jon Hunter wrote:
> >
> > On 07/07/17 07:27, Gustavo A. R. Silva wrote:
> > > Check return value from call to of_match_device()
> > > in order to prevent a NULL pointer dereference.
> > >
>
On Mon, Jul 10, 2017 at 10:51:02AM +0200, Arnd Bergmann wrote:
> We cannot build the new ftide010 code without also building the faraday
> sata bridge driver:
>
> drivers/ata/pata_ftide010.o: In function `pata_ftide010_probe':
> pata_ftide010.c:(.text+0x2b8): undefined reference to `gemini_sata_br
On Mon, Jul 10, 2017 at 09:33:13AM -0500, Rob Herring wrote:
> On Thu, Jul 06, 2017 at 05:43:23PM -0700, Brian Norris wrote:
> > www.firmware.org doesn't resolve for me. I found these equivalent URLs
> > by taking the redirects from the previous (openfirmware.org) URLs, as
> > seen before commit f5
On 07/10/2017 12:12 PM, Linus Torvalds wrote:
On Mon, Jul 10, 2017 at 5:47 AM, Corey Minyard wrote:
https://github.com/cminyard/linux-ipmi.git tags/for-linus-4.13
Hmm.
This is signed using a completely new key.
That part is fine: the new key is 4k bits instead of the old 1k key.
But the
From: Colin Ian King
Don't populate array startup_lookup on the stack but instead make
it static. Makes the object code smaller.
Before:
textdata bss dec hex filename
217545440 128 273226aba drivers/iio/adc/at91_adc.o
After:
textdata bss dec
On Mon 10-07-17 12:54:21, Jerome Glisse wrote:
> On Mon, Jul 10, 2017 at 06:36:52PM +0200, Michal Hocko wrote:
> > On Mon 10-07-17 12:25:42, Jerome Glisse wrote:
> > [...]
> > > Bottom line is that we can always free and uncharge device memory
> > > page just like any regular page.
> >
> > OK, thi
On 07/07/2017 09:07, Balbir Singh wrote:
> On Fri, 2017-06-16 at 19:52 +0200, Laurent Dufour wrote:
>> From: Peter Zijlstra
>>
>> One of the side effects of speculating on faults (without holding
>> mmap_sem) is that we can race with free_pgtables() and therefore we
>> cannot assume the page-table
On 2017-07-07 23:14, Joel Fernandes wrote:
Hi Vikram,
On Thu, Jul 6, 2017 at 11:44 PM, Vikram Mulukutla
wrote:
On 2017-07-04 10:34, Patrick Bellasi wrote:
Currently the utilization of the FAIR class is collected before
locking
the policy. Although that should not be a big issue for most cas
On Mon, 2017-07-10 at 18:17 +0300, Andy Shevchenko wrote:
> On Mon, Jul 10, 2017 at 5:37 PM, Abdul Haleem
> wrote:
> > On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote:
> >> On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem
> >> wrote:
> >> > next-20170705 fails to build on powerpc with below
On Fri, Jul 07, 2017 at 06:42:27PM +0200, Sebastian Reichel wrote:
> snd-soc-cq93vc-objs := cq93vc.o
> +snd-soc-cpcap-objs := cpcap.o
Please keep Kconfig and Makefile lexically sorted.
> +static int cpcap_audio_write(struct cpcap_audio *cpcap,
> + u16 reg, u16 mask, u16
This time signed with the right key...
The following changes since commit 13e0988140374123bead1dd27c287354cb95108e:
docs: complete bumping minimal GNU Make version to 3.81 (2017-05-06
18:49:09 -0700)
are available in the git repository at:
https://github.com/cminyard/linux-ipmi.git tags
On Fri, Jul 07, 2017 at 08:50:40AM +0200, Thomas Gleixner wrote:
> Aside of that, are you really serious about serializing the world and
> everything on a single global mutex?
It would be nice to not do that, but there are challenges. At
any instant someone else might run:
# rmdir /sys/fs/resctrl
Hi,
This is a call for presentations for the Tracing Summit which will be
held in Prague, Czech Republic, on October 27th, 2017, at the Hilton
Prague. This event is co-located with the Open Source Summit Europe
2017.
The Tracing Summit is organized by the Linux Foundation Diagnostic and
Monitorin
On Mon, Jul 10, 2017 at 10:45 AM, Corey Minyard wrote:
>
> Dang it. I generated a new key to replace the old key, waiting to have it
> signed an such, and it defaulted to the new key. I'll do a v2 with the
> right key. Sorry.
I would have been perfectly happy with the new key if you just signe
On Mon, Jul 10, 2017 at 9:14 AM, Alexandru Moise
<00moses.alexande...@gmail.com> wrote:
> On Mon, Jul 10, 2017 at 08:52:46AM +0200, Daniel Vetter wrote:
>> On Sat, Jul 08, 2017 at 11:43:52PM +0200, Alexandru Moise wrote:
>> > If the DRM core fails to init for whatever reason, ensure that
>> > no dr
On Mon, Jul 10, 2017 at 8:44 AM, Maxime Ripard
wrote:
> On Sun, Jul 09, 2017 at 11:11:07PM +0800, Chen-Yu Tsai wrote:
>> On Sun, Jul 9, 2017 at 3:59 PM, Jonathan Liu wrote:
>> > The drm_driver lastclose callback is called when the last userspace
>> > DRM client has closed. Call drm_fbdev_cma_rest
On 7/8/2017 4:24 AM, Ingo Molnar wrote:
* Tom Lendacky wrote:
This patch series provides support for AMD's new Secure Memory Encryption (SME)
feature.
I'm wondering, what's the typical performance hit to DRAM access latency when
SME
is enabled?
It's about an extra 10 cycles of DRAM lat
This thing is definitely not cc'd to the right people:
On Sun, Jul 9, 2017 at 10:08 PM, Cong Wang wrote:
>
> Cc: Linus Torvalds
> Cc: Andrew Morton
> Cc: Manfred Spraul
> Signed-off-by: Cong Wang
Unlike your previous patch, this seems to be more of a generic netlink
interface issue, so you s
On Mon, Jul 10, 2017 at 07:48:58PM +0200, Michal Hocko wrote:
> On Mon 10-07-17 12:54:21, Jerome Glisse wrote:
> > On Mon, Jul 10, 2017 at 06:36:52PM +0200, Michal Hocko wrote:
> > > On Mon 10-07-17 12:25:42, Jerome Glisse wrote:
> > > [...]
> > > > Bottom line is that we can always free and unchar
On Mon, Jul 10, 2017 at 10:07:40AM -0500, Christopher Bostic wrote:
>
>
> On 7/8/17 9:59 AM, Guenter Roeck wrote:
> >On Thu, Jul 06, 2017 at 07:48:59PM -0500, Christopher Bostic wrote:
> >>Describe device tree optional properties:
> >>
> >> * aspeed,reset-type = "cpu|soc|system|none"
> >>
On Mon 10-07-17 18:27:51, Michal Hocko wrote:
> On Mon 10-07-17 09:12:11, Kees Cook wrote:
[...]
> > >> do_execveat_common() ->
> > >> exec_binprm() ->
> > >> search_binary_handler() ->
> > >> fmt->load_binary (load_elf_binary()) ->
> > >> setup_new_exec() ->
> > >> arch_pick_mmap_layout() ->
> > >
On Mon, Jul 10, 2017 at 12:36 PM, Moritz Fischer
wrote:
Hi Moritz,
Thanks for looking at this stuff.
>>
>> +struct fpga_image_info *fpga_image_info_alloc(struct device *dev)
>> +{
>> + struct fpga_image_info *info;
>> +
>> + info = devm_kzalloc(dev, sizeof(*info), GFP_KERNEL);
>> +
On Mon, Jul 10, 2017 at 8:59 AM, Michal Hocko wrote:
>
> We will always need some gap inforcement.
Considering the Java issue, that's rather questionable.
We really can't be breaking libreoffice. That's like a big classic
no-no - it affects normal users that simply cannot be expected to work
aro
On Mon, 2017-07-10 at 20:16 +0200, Michal Hocko wrote:
> OK, I misread the code. 32b applications on 64b systems do top down
> by
> default and only if they override this by ADDR_COMPAT_LAYOUT
> personality. For some reason I thought that 32b userspace goes a
> different path and makes sure that t
From: Colin Ian King
Don't populate const arrays on the stack but instead make them static.
Makes the object code smaller and saves nearly 550 bytes.
Before:
textdata bss dec hex filename
3638 752 043901126 smiapp-quirk.o
After:
textdata bss
Fields of hfa384x_commsquality were used as __le16 but defined as u16.
Type is changed to __le16.
Signed-off-by: Vitali Liaukovich
---
drivers/staging/wlan-ng/hfa384x.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/wlan-ng/hfa384x.h
b/drivers/staging/
On Fri, Jun 30, 2017 at 11:08:15PM +0530, Aravind Thokala wrote:
> Hello Mark,
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion
From: Arnd Bergmann
Date: Mon, 10 Jul 2017 11:37:51 +0200
> The new IPSec offload code introduced a build error:
>
> drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_rxtx.o: In function
> `mlx5e_ipsec_build_inverse_table':
> ipsec_rxtx.c:(.text+0x556): undefined reference
>
> Another pat
From: "Edward A. James"
This series adds an algorithm for an I2C master physically located on an FSI
slave device. The I2C master has multiple ports, each of which may be connected
to an I2C slave. Access to the I2C master registers is achieved over FSI bus.
Due to the multi-port nature of the I
From: "Edward A. James"
Add and initialize I2C adapters for each port on the FSI-attached I2C
master. Ports for each master are defined in the devicetree.
Signed-off-by: Edward A. James
---
drivers/i2c/busses/i2c-fsi.c | 91
1 file changed, 91 inser
From: "Edward A. James"
Document the bindings.
Signed-off-by: Edward A. James
---
Documentation/devicetree/bindings/i2c/i2c-fsi.txt | 40 +++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-fsi.txt
diff --git a/Documentation/d
From: "Edward A. James"
Since there are many ports per master, each with it's own adapter and
chardev, we need some locking to prevent transfers from changing the\
master state while other transfers are in progress.
Signed-off-by: Edward A. James
---
drivers/i2c/busses/i2c-fsi.c | 43 +
On Mon 10-07-17 11:24:55, Linus Torvalds wrote:
> On Mon, Jul 10, 2017 at 8:59 AM, Michal Hocko wrote:
> >
> > We will always need some gap inforcement.
>
> Considering the Java issue, that's rather questionable.
>
> We really can't be breaking libreoffice. That's like a big classic
> no-no - it
From: "Edward A. James"
Bus recovery should reset the engine and force clock the bus 9 times
to recover most situations.
Signed-off-by: Edward A. James
---
drivers/i2c/busses/i2c-fsi.c | 75
1 file changed, 75 insertions(+)
diff --git a/drivers/i2c
From: "Edward A. James"
Add register definitions for FSI-attached I2C master and functions to
access those registers over FSI. Add an FSI driver so that our I2C bus
is probed up during an FSI scan.
Signed-off-by: Edward A. James
---
drivers/i2c/busses/Kconfig | 11 ++
drivers/i2c/busses/Mak
From: "Edward A. James"
Execute I2C transfers from the FSI-attached I2C master. Use polling
instead of interrupts as we have no hardware IRQ over FSI.
Signed-off-by: Edward A. James
---
drivers/i2c/busses/i2c-fsi.c | 197 ++-
1 file changed, 195 insertio
The patch
ASoC: rt5663: add in missing loop counter to avoid infinite loop
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 h
The patch
spi/bcm63xx-hspi: Fix checkpatch warnings
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus du
The patch
spi/ath79: Fix checkpatch warnings
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
th
The patch
regulator: cpcap: Fix standby mode
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
On 07/10/2017 04:44 PM, Gleb Fotengauer-Malinovskiy wrote:
> This ioctl actually writes to parameter too.
Maybe rephrase that to:
The kernel does not only read struct kvm_s390_cmma_log for
KVM_S390_GET_CMMA_BITS,
it also writes back a return value making this _IOWR instead of _IOW.
> Fixes: 403
The patch
regulator: cpcap: Add OF mode mapping
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
501 - 600 of 848 matches
Mail list logo
