On Thu, 18 Jul 2019, Waiman Long wrote:
> The memcg_cache_params structure is only embedded into the kmem_cache
> of slab and slub allocators as defined in slab_def.h and slub_def.h
> and used internally by mm code. There is no needed to expose it in
> a public header. So move it from
Hi "George,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.2 next-20190719]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Arnd,
On Sat, Jul 20, 2019 at 10:55 PM Arnd Bergmann wrote:
>
> On Sat, Jul 20, 2019 at 5:26 AM Masahiro Yamada
> wrote:
> >
> > masahiro@grover:~/ref/linux$ git grep netxbig_led_platform_data
> > drivers/leds/leds-netxbig.c: struct
> > netxbig_led_platform_data
The following changes since commit 02e5ad973883c36c0868b301b8357d9c455bb91c:
perf_event_get(): don't bother with fget_raw() (2019-06-26 20:43:53 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you to fetch changes up
Linus,
Please pull a couple of DT binding fixes for 5.3-rc.
Rob
The following changes since commit abdfd52a295fb5731ab07b5c9013e2e39f4d1cbe:
Merge tag 'armsoc-defconfig' of
git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc (2019-07-19
17:27:27 -0700)
are available in the Git repository
On Sat, 20 Jul 2019 16:32:32 +0900
Masami Hiramatsu wrote:
> Hi James,
>
> On Fri, 19 Jul 2019 09:42:05 +0100
> James Morse wrote:
>
> > Hi,
> >
> > On 7/18/19 3:31 PM, Masami Hiramatsu wrote:
> > > On Thu, 18 Jul 2019 10:20:23 +0100
> > > Mark Rutland wrote:
> > >
> > >> On Wed, Jul 17,
Please pull the following changes since commit
ae9b728c8dc0a9939d89f84e8603258ca2a0df22:
Merge tag '4.3-rc-smb3-fixes' of
git://git.samba.org/sfrench/cifs-2.6 (2019-07-18 11:11:51 -0700)
are available in the Git repository at:
git://git.samba.org/sfrench/cifs-2.6.git tags/5.3-smb3-fixes
From: Colin Ian King
Fix spelling mistake in kernel warning message and replace
printk with with pr_warn.
Signed-off-by: Colin Ian King
---
drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
Hello Linus,
Here are the NTB changes for v5.3. The big change is adding the virtual
MSI interface for NTB (reviewed and acked by Bjorn). Also, there are
some bug fixes. Please consider pulling them.
Thanks,
Jon
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
On Sat, 2019-07-20 at 22:42 +0200, Takashi Iwai wrote:
> On Fri, 19 Jul 2019 20:07:46 +0200,
> Takashi Iwai wrote:
> > On Fri, 19 Jul 2019 18:36:53 +0200,
> > Luciano Coelho wrote:
> > > Adding Dor.
> > >
> > > Hi Takashi,
> > >
> > > Do you have full logs of the crash? We can't see much from
On Fri, 19 Jul 2019 20:07:46 +0200,
Takashi Iwai wrote:
>
> On Fri, 19 Jul 2019 18:36:53 +0200,
> Luciano Coelho wrote:
> >
> > Adding Dor.
> >
> > Hi Takashi,
> >
> > Do you have full logs of the crash? We can't see much from the log
> > snippet pasted in the bug report.
>
> OK, I'll ask
On Sat, Jul 20, 2019 at 9:34 PM Florian Weimer wrote:
> * Arnd Bergmann:
> > On Sat, Jul 20, 2019 at 8:10 PM Florian Weimer wrote:
> > As far as I can tell, nobody thought it would be a problem to move it
> > from asm/sockios.h to linux/sockios.h, as the general rule is that one
> > should use
Allocation for priv->pFirmware may fail, so a null check is necessary.
priv->pFirmware is accessed at line 2743. I added the check and made
appropriate changes to propagate the errno to the caller.
Signed-off-by: Navid Emamdoost
---
drivers/staging/rtl8192u/r8192U_core.c | 13 +++--
1
On 19/07/2019 19:04:21+, Trent Piepho wrote:
> On Fri, 2019-07-19 at 02:57 +, Anson Huang wrote:
> >
> > > I do worry that handling the irq before the rtc device is registered
> > > could still
> > > result in a crash. From what I saw, the irq path in snvs only uses
> > > driver state
On Sat, Jul 20, 2019 at 8:03 PM Bartosz Golaszewski
wrote:
> I'll apply it to my local tree and send it for v5.3-rc2.
OK! Do you see it as bug fix so it should go in the rcs?
It pretty much needs to be a regression to go in there,
because this stub stuff blew up in my face before :/
Thanks,
The pull request you sent on Sat, 20 Jul 2019 22:10:36 +0300:
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f1a3b43cc1f50c6ee5ba582f2025db3dea891208
Thank you!
--
Deet-doot-dot, I am a bot.
* Arnd Bergmann:
> On Sat, Jul 20, 2019 at 8:10 PM Florian Weimer wrote:
>>
>> * Sergei Trofimovich:
>>
>> > Should #include always be included by user app?
>> > Or should glibc tweak it's definition of '#include '
>> > to make it available on both old and new version of linux headers?
>>
>>
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get:
- Apple SPI keyboard and trackpad driver for newer Macs
- ALPS driver will ignore trackpoint-only devices to give chance
On Sat, Jul 20, 2019 at 8:10 PM Florian Weimer wrote:
>
> * Sergei Trofimovich:
>
> > Should #include always be included by user app?
> > Or should glibc tweak it's definition of '#include '
> > to make it available on both old and new version of linux headers?
>
> What is the reason for
The pull request you sent on Sat, 20 Jul 2019 11:31:01 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.3-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/168c79971b4a7be7011e73bf488b740a8e1135c8
Thank you!
--
The pull request you sent on Sat, 20 Jul 2019 12:50:00 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> core-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e6023adc5c6af79ac8ac5b17939f58091fa0d870
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Sat, 20 Jul 2019 13:43:07 +0200:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/07ab9d5bc53d7fe84047be1d403566123ab9cfaa
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 20 Jul 2019 12:50:00 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> perf-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/46f5c0cc3af0ecb76224a91d2997d74e35ff7821
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Sat, 20 Jul 2019 12:50:00 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4b01f5a4c9c4f0c502875c1fb31dcd5d0df86475
Thank you!
--
Deet-doot-dot, I am
The pull request you sent on Sat, 20 Jul 2019 08:33:21 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f65420df914a85e33b2c8b1cab310858b2abb7c0
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 20 Jul 2019 12:50:00 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> sched-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/70e6e1b971e46f5c1c2d72217ba62401a2edc22b
Thank you!
--
Deet-doot-dot,
The pull request you sent on Sat, 20 Jul 2019 04:02:18 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.dcache2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/18253e034d2aeee140f82fc9fe89c4bce5c81799
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 20 Jul 2019 12:50:00 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c6dd78fcb8eefa15dd861889e0f59d301cb5230c
Thank you!
--
Deet-doot-dot, I am
* Sergei Trofimovich:
> Should #include always be included by user app?
> Or should glibc tweak it's definition of '#include '
> to make it available on both old and new version of linux headers?
What is the reason for dropping SIOCGSTAMP from ?
If we know that, it will be much easier to
wt., 16 lip 2019 o 23:46 Linus Walleij napisał(a):
>
> On Tue, Jul 9, 2019 at 4:20 PM Bartosz Golaszewski wrote:
> > wt., 9 lip 2019 o 15:30 Linus Walleij napisał(a):
>
> > > I was thinking something like this in the stubs:
> > >
> > > gpiod_get[_index]() {
> > > return POISON;
> > > }
> >
Code is same if translate is true/false in case invalid packet is
received.So remove else part.
Issue identified with coccicheck
Signed-off-by: Hariprasad Kelam
---
drivers/net/wireless/ray_cs.c | 29 -
1 file changed, 8 insertions(+), 21 deletions(-)
diff --git
On Fri, Jul 19, 2019 at 08:59:02PM +, Matt Sickler wrote:
> >From: Bharath Vedartham
> >Changes since v2
> >- Added back PageResevered check as suggested by John Hubbard.
> >
> >The PageReserved check needs a closer look and is not worth messing
> >around with for now.
> >
> >Matt,
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d ("mm:
introduce put_user_page*(), placeholder versions").
Cc: Ira Weiny
Cc: John
On Fri, Jul 19, 2019 at 02:28:39PM -0700, John Hubbard wrote:
> On 7/19/19 1:02 PM, Bharath Vedartham wrote:
> > There have been issues with coordination of various subsystems using
> > get_user_pages. These issues are better described in [1].
> >
> > An implementation of tracking get_user_pages
Commit
https://github.com/torvalds/linux/commit/0768e17073dc527ccd18ed5f96ce85f9985e9115
("net: socket: implement 64-bit timestamps") caused a bit of userspace breakage
for existing programs:
- firefox: https://bugs.gentoo.org/689808
- qemu:
On 20.07.2019 16:22, Thomas Voegtle wrote:
> On Sat, 20 Jul 2019, Heiner Kallweit wrote:
>
>> On 19.07.2019 23:12, Thomas Voegtle wrote:
>>> On Fri, 19 Jul 2019, Heiner Kallweit wrote:
>>>
On 18.07.2019 20:50, Thomas Voegtle wrote:
>
> Hello,
>
> I'm having network problems
$(basename ...) trims the last suffix. Using it is more intuitive in
my opinion.
This pattern rule makes %.asn1.c and %.asn1.h at the same time.
Previously, the short log showed only either of them, depending on
the target file in question.
To clarify that two files are being generated by the
We generally expect bison to create not only a C file, but also a
header, which will be included from the lexer.
Currently, Kbuild generates them in separate rules. So, for instance,
when building Kconfig, you will notice bison is invoked twice:
HOSTCC scripts/kconfig/conf.o
HOSTCC
Flex and bison are used for kconfig, dtc, genksyms, all of which are
host programs. I never imagine the kernel embeds a parser or a lexer.
Move the flex and bison rules to scripts/Makefile.host. This file is
included only when hostprogs-y etc. is present in the Makefile in the
directory. So,
Hi Masahiro,
On Sat, 2019-07-20 at 11:40 +0900, Masahiro Yamada wrote:
> On Sat, Jul 20, 2019 at 4:28 AM Eugeniy Paltsev
> wrote:
> > As of today we are able to pass custom flags to dtc compiler but not
> > to dtc preprocessor.
> > This ability is required for including some board-specific
the subject is unsuitable? i mean the prefix should be fs/ramfs rather
than knfsd?
2019-05-22 3:25 GMT+12:00, Haodong Wong :
> Refer to tmpfs, use inode number and generation number
> to construct the filehandle for nfs-export
would you like to describe what is happening without this patch?
I have updated the patches with the requested changes and sent a v3.
Best,
Maximilian
Hi Andra,
Just realized one minor issue:
On Fri, Jul 19, 2019 at 9:14 AM andradanciu1997
wrote:
> + {
> + clock-frequency = <10>;
> + pinctrl-names = "default";
> + pinctrl-0 = <_i2c1>;
> + status = "okay";
> +
> + pmic: pmic@4b {
> + reg =
Hello
This is just a report for someone who hit the same problem.
When setting 1 to sysfs debug_force_rr_cpu can trigger the
following LOCKDEP WARNING.
Reproducer:
# ssh localhost // to use pty
# echo 1 > /sys/module/workqueue/parameters/debug_force_rr_cpu
This problem is similar to the
Do not use the surfacepro3_button driver on newer Microsoft Surface
models, only use it on the Surface Pro 3 and 4. Newer models (5th, 6th
and possibly future generations) use the same device as the Surface Pro
4 to represent their volume and power buttons (MSHW0040), but their
actual
This series adds support for power and volume buttons on 5th and 6th
generation Microsoft Surface devices. Specifically, it adds support for
the power-button on the Surface Laptop 1 and Laptop 2, as well as
support for power- and (on-device) volume-buttons on the Surface Pro 5
(2017), Pro 6, and
Power and volume button support for 5th and 6th generation Microsoft
Surface devices via soc_button_array.
Note that these devices use the same MSHW0040 device as on the Surface
Pro 4, however the implementation is different (GPIOs vs. ACPI
notifications). Thus some checking is required to ensure
On 7/20/19 4:41 AM, Luis Henriques wrote:
> "Linus Torvalds" writes:
>
>> On Fri, Jul 19, 2019 at 12:32 PM Waiman Long wrote:
>>> This patch shouldn't change the behavior of the rwsem code. The code
>>> only access data within the rw_semaphore structures. I don't know why it
>>> will cause a
Users can call ref_module func in their modules to construct
relationships with other modules. However, the holders
'/sys/module//holders' of the target module donot include
the users` module. So lsmod command misses detailed info of 'Used by'.
When load module, the process is given as follows,
On 2019/07/20 21:49, Andy Lutomirski wrote:
> On Fri, Jul 19, 2019 at 8:59 PM Eiichi Tsukata wrote:
>>
...
>>
>>
>>
>> debug() // dr6: 0x4ff0, user_mode: 1
>> TRACE_IRQS_OFF
>> arch_stack_user_walk()
>> debug() // dr6: 0x4ff1 == 0x4ff0 | 0x0ff1 ... (*)
>>
On Sat, 20 Jul 2019, Heiner Kallweit wrote:
On 19.07.2019 23:12, Thomas Voegtle wrote:
On Fri, 19 Jul 2019, Heiner Kallweit wrote:
On 18.07.2019 20:50, Thomas Voegtle wrote:
Hello,
I'm having network problems with the commits on r8169 since v5.2. There are
ping packet loss, sometimes
On Thu, Jul 18, 2019 at 4:01 PM Zhiyong Tao wrote:
>
> This patch support efuse calibration in auxadc driver
>
> Signed-off-by: Zhiyong Tao
> Signed-off-by: jg_poxu
> ---
> drivers/iio/adc/mt6577_auxadc.c | 71
> +
> 1 file changed, 71 insertions(+)
>
>
Good Day
I am Mr.sallm Salif,, a regional managing director (CORIS BANK
INTERNATIONAL) Ouagadougou Burkina Faso, in my department we have
US$9,500. million united state dollars, to transfer into your
account as a dormant fund.If you are interested to use this fund to
help the orphans around
On Fri, Jul 19, 2019 at 11:54 AM Nadav Amit wrote:
>
> > On Jul 19, 2019, at 11:48 AM, Dave Hansen wrote:
> >
> > On 7/19/19 11:43 AM, Nadav Amit wrote:
> >> Andy said that for the lazy tlb optimizations there might soon be more
> >> shared state. If you prefer, I can move is_lazy outside of
On Sat, Jul 20, 2019 at 5:26 AM Masahiro Yamada
wrote:
>
> masahiro@grover:~/ref/linux$ git grep netxbig_led_platform_data
> drivers/leds/leds-netxbig.c: struct
> netxbig_led_platform_data *pdata,
> drivers/leds/leds-netxbig.c: struct
>
On 7/19/19 1:29 AM, Vignesh Raghavendra wrote:
> On x86_64, when CONFIG_OF is not disabled:
>
> WARNING: unmet direct dependencies detected for MUX_MMIO
> Depends on [n]: MULTIPLEXER [=y] && (OF [=n] || COMPILE_TEST [=n])
> Selected by [y]:
> - HBMC_AM654 [=y] && MTD [=y] && MTD_HYPERBUS
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
up to: 6879298bd067: x86/entry/64: Prevent clobbering of saved CR2 value
A set of x86 specific fixes and updates:
- The CR2 corruption fixes
Linus,
please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
up to: e0c5c5e308ee: Merge tag 'perf-core-for-mingo-5.3-20190715' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent
Linus,
please pull the latest smp-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
smp-urgent-for-linus
up to: 19dbdcb8039c: smp: Warn on function calls from softirq context
Add warnings to the smp function calls so callers from wrong contexts get
Linus,
please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
up to: b68b9907069a: objtool: Support conditional retpolines
This update contains:
- A collection of objtool fixes which address recent
Linus,
please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
up to: a50a3f4b6a31: sched/rt, Kconfig: Introduce CONFIG_PREEMPT_RT
The real-time preemption patch set exists for almost 15 years now and
On Fri, Jul 19, 2019 at 8:59 PM Eiichi Tsukata wrote:
>
>
> On 2019/07/19 5:27, Andy Lutomirski wrote:
> > Hi all-
> >
> > I suspect that a bunch of the bugs you're all finding boil down to:
> >
> > - Nested debug exceptions could corrupt the outer exception's DR6.
> > - Nested debug exceptions
Hi Ming!
>> Christoph Hellwig (8):
>> scsi: megaraid_sas: set an unlimited max_segment_size
>> scsi: mpt3sas: set an unlimited max_segment_size for SAS 3.0 HBAs
>> scsi: IB/srp: set virt_boundary_mask in the scsi host
>> scsi: IB/iser: set virt_boundary_mask in the scsi
Commit-ID: 6879298bd0673840cadd1fb36d7225485504ceb4
Gitweb: https://git.kernel.org/tip/6879298bd0673840cadd1fb36d7225485504ceb4
Author: Thomas Gleixner
AuthorDate: Sat, 20 Jul 2019 10:56:41 +0200
Committer: Thomas Gleixner
CommitDate: Sat, 20 Jul 2019 14:28:41 +0200
x86/entry/64:
On Fri, Jul 19, 2019 at 10:32:55PM -0400, George G. Davis wrote:
> When an unhandled data or prefetch abort occurs, the die() string
> is empty resulting in backtrace messages similar to the following:
>
> Internal error: : 1 [#1] PREEMPT SMP ARM
>
> Replace the null string with the name
Add a header include guard just in case.
Signed-off-by: Masahiro Yamada
---
include/linux/platform_data/pinctrl-single.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/linux/platform_data/pinctrl-single.h
b/include/linux/platform_data/pinctrl-single.h
index
Linus,
The following changes since commit 964a4eacef67503a1154f7e0a75f52fbdce52022:
Merge tag 'dlm-5.3' of
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm (2019-07-12
17:37:53 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git
于 2019年7月20日 GMT+08:00 下午6:13:18, Maxime Ripard 写到:
>On Sat, Jul 13, 2019 at 11:46:33AM +0800, Icenowy Zheng wrote:
>> The Lichee Zero Plus is a core board made by Sipeed, with a microUSB
>> connector on it, TF slot or WSON8 SD chip, optional eMMC or SPI
>Flash.
>> It has a gold finger
On Fri, Jul 19, 2019 at 04:02:15PM +0200, Vincent Guittot wrote:
> On Fri, 19 Jul 2019 at 14:54, Peter Zijlstra wrote:
> >
> > On Fri, Jul 19, 2019 at 09:58:23AM +0200, Vincent Guittot wrote:
> > > -void fix_small_imbalance(struct lb_env *env, struct sd_lb_stats *sds)
> > Maybe strip this out
On Sat, Jul 20, 2019 at 10:56:41AM +0200, Thomas Gleixner wrote:
> The recent fix for CR2 corruption introduced a new way to reliably corrupt
> the saved CR2 value.
>
> CR2 is saved early in the entry code in RDX, which is the third argument to
> the fault handling functions. But it missed that
On Sat, Jul 20, 2019 at 09:41:05AM +0100, Luis Henriques wrote:
> [ 39.801179]
> ==
> [ 39.801973] BUG: KASAN: use-after-free in rwsem_down_write_slowpath
> (/home/miguel/kernel/linux/kernel/locking/rwsem.c:669
>
On Sat, 20 Jul 2019 at 11:54, Thomas Gleixner wrote:
>
> On Sat, 20 Jul 2019, Mike Lothian wrote:
> > Here is my config
> >
> > https://github.com/FireBurn/KernelStuff/blob/9b7e96581598d50b266f9df258e7de764949147a/dot_config_tip
> >
>
> Builds perfectly fine.
Sorry top posted from my phone
Are
On Sat, 20 Jul 2019, Mike Lothian wrote:
> Here is my config
>
> https://github.com/FireBurn/KernelStuff/blob/9b7e96581598d50b266f9df258e7de764949147a/dot_config_tip
>
Builds perfectly fine.
These include guards are broken.
Match the #if !define() and #define lines so that they work correctly.
Signed-off-by: Masahiro Yamada
---
include/trace/events/dma_fence.h | 2 +-
include/trace/events/napi.h | 4 ++--
include/trace/events/qdisc.h | 4 ++--
On Sat, 20 Jul 2019 at 10:34, Thomas Gleixner wrote:
>
> On Sat, 20 Jul 2019, Mike Lothian wrote:
> > On Wed, 17 Jul 2019 at 08:57, Thomas Gleixner wrote:
> > I've done a bit more digging, I had a second machine that was building
> > Linus's tree just fine with ld.gold
> >
> > I tried forcing
On Sat, Jul 13, 2019 at 11:46:33AM +0800, Icenowy Zheng wrote:
> The Lichee Zero Plus is a core board made by Sipeed, with a microUSB
> connector on it, TF slot or WSON8 SD chip, optional eMMC or SPI Flash.
> It has a gold finger connector for expansion, and UART is available from
> reserved pins
On Sat, Jul 13, 2019 at 11:46:34AM +0800, Icenowy Zheng wrote:
> Lichee zero plus is a core board made by Sipeed, which includes on-board
> TF slot or SMT SD NAND, and optional SPI NOR or eMMC, a UART debug
> header, a microUSB slot and a gold finger connector for expansion. It
> can use either
On Fri, Jul 19, 2019 at 09:58:53PM +0200, Pavel Machek wrote:
> Hi!
>
> Something went wrong in this mail:
>
> On Thu 2019-07-18 12:01:44, Greg Kroah-Hartman wrote:
> > From: Thomas Gleixner t...@linutronix.de
> >
>
> normally there should be <> around the email address. And they are in
> the
syzbot has bisected this bug to:
commit 7f466032dc9e5a61217f22ea34b2df932786bbfc
Author: Jason Wang
Date: Fri May 24 08:12:18 2019 +
vhost: access vq metadata through kernel virtual address
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=149a8a2060
start commit:
于 2019年7月20日 GMT+08:00 下午5:48:14, Maxime Ripard 写到:
>On Sat, Jul 13, 2019 at 11:46:32AM +0800, Icenowy Zheng wrote:
>> The Allwinner S3/S3L/V3 SoCs all share the same die with the V3s SoC,
>> but with more GPIO wired out of the package.
>>
>> Add DTSI files for these SoCs. The DTSI file for V3
On Sat, Jul 13, 2019 at 11:46:32AM +0800, Icenowy Zheng wrote:
> The Allwinner S3/S3L/V3 SoCs all share the same die with the V3s SoC,
> but with more GPIO wired out of the package.
>
> Add DTSI files for these SoCs. The DTSI file for V3 just replaces the
> pinctrl compatible string, and the
On Sat, Jul 13, 2019 at 11:46:31AM +0800, Icenowy Zheng wrote:
> + [CLK_MMC1] = _clk.common.hw,
> + [CLK_MMC1_SAMPLE] = _sample_clk.common.hw,
> + [CLK_MMC1_OUTPUT] = _output_clk.common.hw,
> + [CLK_MMC2] =
Luis Henriques writes:
> Luis Henriques writes:
>
>> "Linus Torvalds" writes:
>>
>>> On Fri, Jul 19, 2019 at 12:32 PM Waiman Long wrote:
This patch shouldn't change the behavior of the rwsem code. The code
only access data within the rw_semaphore structures. I don't know why it
于 2019年7月20日 GMT+08:00 下午5:44:49, Maxime Ripard 写到:
>On Sat, Jul 13, 2019 at 11:46:30AM +0800, Icenowy Zheng wrote:
>> The MMC2 clock slices are currently not defined in V3s CCU driver,
>which
>> makes MMC2 not working.
>>
>> Fix this issue.
>>
>> Fixes: d0f11d14b0bc ("clk: sunxi-ng: add
On Sat, Jul 13, 2019 at 11:46:30AM +0800, Icenowy Zheng wrote:
> The MMC2 clock slices are currently not defined in V3s CCU driver, which
> makes MMC2 not working.
>
> Fix this issue.
>
> Fixes: d0f11d14b0bc ("clk: sunxi-ng: add support for V3s CCU")
> Signed-off-by: Icenowy Zheng
> ---
> New
On Sat, Jul 13, 2019 at 11:46:29AM +0800, Icenowy Zheng wrote:
> Despite Allwinner V3 and V3s shares the same die, one peripheral (I2S)
> is only available on V3, and thus the clocks is not declared for V3s
> CCU.
>
> Add a V3 CCU compatible string to the binding to prepare for a CCU
> driver that
On Sat, Jul 13, 2019 at 11:46:28AM +0800, Icenowy Zheng wrote:
> The user manual of V3/V3s/S3 declares a PLL_DDR1, however it's forgot
> when developing the V3s CCU driver.
>
> Add back the missing PLL_DDR1.
>
> Fixes: d0f11d14b0bc ("clk: sunxi-ng: add support for V3s CCU")
> Signed-off-by:
On Sat, 20 Jul 2019, Mike Lothian wrote:
> On Wed, 17 Jul 2019 at 08:57, Thomas Gleixner wrote:
> I've done a bit more digging, I had a second machine that was building
> Linus's tree just fine with ld.gold
>
> I tried forcing ld.bfd on the problem machine and got this:
>
> ld.bfd:
Luis Henriques writes:
> "Linus Torvalds" writes:
>
>> On Fri, Jul 19, 2019 at 12:32 PM Waiman Long wrote:
>>>
>>> This patch shouldn't change the behavior of the rwsem code. The code
>>> only access data within the rw_semaphore structures. I don't know why it
>>> will cause a KASAN error. I
Commit-ID: 19dbdcb8039cff16669a05136a29180778d16d0a
Gitweb: https://git.kernel.org/tip/19dbdcb8039cff16669a05136a29180778d16d0a
Author: Peter Zijlstra
AuthorDate: Thu, 18 Jul 2019 11:20:09 +0200
Committer: Thomas Gleixner
CommitDate: Sat, 20 Jul 2019 11:27:16 +0200
smp: Warn on
On Sat, Jul 13, 2019 at 11:46:27AM +0800, Icenowy Zheng wrote:
> Introduce the GPIO pins that is only available on V3 (not on V3s) to the
> V3s pinctrl driver.
>
> Signed-off-by: Icenowy Zheng
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
On 19.07.2019 23:12, Thomas Voegtle wrote:
> On Fri, 19 Jul 2019, Heiner Kallweit wrote:
>
>> On 18.07.2019 20:50, Thomas Voegtle wrote:
>>>
>>> Hello,
>>>
>>> I'm having network problems with the commits on r8169 since v5.2. There are
>>> ping packet loss, sometimes 100%, sometimes 50%. In the
On Wed, 17 Jul 2019 at 08:57, Thomas Gleixner wrote:
>
> On Wed, 17 Jul 2019, Masahiro Yamada wrote:
> > On Wed, Jul 17, 2019 at 4:47 AM Thomas Gleixner wrote:
> > > So instead of dealing with attempts to duct tape gold support without
> > > understanding the root cause and without support from
On 19.07.2019 23:12, Thomas Voegtle wrote:
> On Fri, 19 Jul 2019, Heiner Kallweit wrote:
>
>> On 18.07.2019 20:50, Thomas Voegtle wrote:
>>>
>>> Hello,
>>>
>>> I'm having network problems with the commits on r8169 since v5.2. There are
>>> ping packet loss, sometimes 100%, sometimes 50%. In the
The recent fix for CR2 corruption introduced a new way to reliably corrupt
the saved CR2 value.
CR2 is saved early in the entry code in RDX, which is the third argument to
the fault handling functions. But it missed that between saving and
invoking the fault handler enter_from_user_mode() can be
On Sat, 20 Jul 2019, Thomas Gleixner wrote:
> On Sat, 20 Jul 2019, Thomas Gleixner wrote:
> > On Fri, 19 Jul 2019, Sean Christopherson wrote:
> > > [0.680477] Run /sbin/init as init process
> > > [0.682116] init[1]: segfault at 2926a7ef ip 7f98a49d9c30 sp
> > > 7fffd83e6af0 error
"Linus Torvalds" writes:
> On Fri, Jul 19, 2019 at 12:32 PM Waiman Long wrote:
>>
>> This patch shouldn't change the behavior of the rwsem code. The code
>> only access data within the rw_semaphore structures. I don't know why it
>> will cause a KASAN error. I will have to reproduce it and
Hi,
On Thu, Jul 18, 2019 at 12:15:09PM +0100, Jan Kotas wrote:
> This patch adds support for CSI2TX v2.1 version of the controller.
>
> Signed-off-by: Jan Kotas
> ---
> drivers/media/platform/cadence/cdns-csi2tx.c | 142
> +--
> 1 file changed, 112 insertions(+), 30
65;5603;1c
On Thu, Jul 18, 2019 at 12:15:08PM +0100, Jan Kotas wrote:
> This patch adds line checks for CSI2TX, to prevent
> clock lane being used as a data lane.
>
> Signed-off-by: Jan Kotas
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
On Thu, Jul 18, 2019 at 12:15:07PM +0100, Jan Kotas wrote:
> This patch adds a DT bindings documentation for
> Cadence CSI2TX v2.1 controller.
>
> Signed-off-by: Jan Kotas
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
1 - 100 of 121 matches
Mail list logo
