Hi Robin,
On Fri, Dec 7, 2018 at 2:54 PM Vivek Gautam wrote:
>
> Hi Robin,
>
> On Tue, Dec 4, 2018 at 8:51 PM Robin Murphy wrote:
> >
> > On 04/12/2018 11:01, Vivek Gautam wrote:
> > > Qualcomm SoCs have an additional level of cache called as
> > > System cache, aka. Last level cache (LLC).
Hi Linus,
please pull s390 fixes and features for 4.21
The following changes since commit 94f371cb73944b410a269d570d6946c042f2ddd0:
Merge tag 'acpi-4.20-rc5' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2018-11-29
15:54:12 -0800)
are available in the git repository at:
On Mon, Dec 31, 2018 at 07:11:27PM +, Mark Brown wrote:
> On Fri, Dec 28, 2018 at 10:05:33AM +0200, Matti Vaittinen wrote:
>
> > Last night - just when I was about to get some sleep - it stroke me. I
> > think the correct thing to do would be leaving the irq_set_type to NULL
> > for those IRQ
On 12/24/18 4:48 PM, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:6a1d293238c1 Add linux-next specific files for 20181224
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=149a2add40
> kernel config:
On Tue, Jan 1, 2019 at 11:43 PM kbuild test robot wrote:
>
> Hi Sinan,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 28e8c4bc8eb483c22d977e147a0b98fc63efadf7
> commit:
On Sun, Dec 30, 2018 at 5:29 PM Julia Lawall wrote:
>
> Delete tab aligning a statement with the right hand side of a
> preceding assignment rather than the left hand side.
>
> Found with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
Thanks, Julia.
Acked-by: Jack Wang
>
> ---
>
On Thu, Dec 13, 2018 at 9:20 AM Tomasz Figa wrote:
>
> On Fri, Dec 7, 2018 at 6:25 PM Vivek Gautam
> wrote:
> >
> > Hi Robin,
> >
> > On Tue, Dec 4, 2018 at 8:51 PM Robin Murphy wrote:
> > >
> > > On 04/12/2018 11:01, Vivek Gautam wrote:
> > > > Qualcomm SoCs have an additional level of cache
It is a sample for pstore_rom, using general ram rather than block device.
According to pstore_rom, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
pstore_rom is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
Why should we need pstore_rom?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a
Why should we need pstore_rom?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a sample for block device logger in driver
MTD (drivers/mtd/mtdoops.c).
2. Do not any equipment have
On 12/20/2018 7:05 PM, Srinivas Ramana wrote:
If the default_affinity is managed/initialized by a system and
all the cpus present in irq_default_affinity are hotplugged out
we may end up passing a cpumask of 0 to irq_do_set_affinity().
Fix this by falling back to cpu_online_mask in case the
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org
> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Xiubo Li
> Sent: Wednesday, January 02, 2019 2:37 PM
> To: liujian (CE)
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH]
On Tue, Jan 1, 2019 at 11:59 AM Yong Wu wrote:
>
> The register VLD_PA_RNG(0x118) was forgot to backup while adding 4GB
> mode support for mt2712. this patch add it.
>
> Fixes: 30e2fccf9512 ("iommu/mediatek: Enlarge the validate PA range
> for 4GB mode")
> Signed-off-by: Yong Wu
> ---
>
On Fri, Dec 21, 2018 at 9:43 PM Marc Gonzalez wrote:
>
> The private copy of readl_poll_timeout is no longer needed.
> Use the implementation in iopoll.h instead.
>
> Signed-off-by: Marc Gonzalez
> ---
> drivers/phy/qualcomm/phy-qcom-ufs-i.h | 19 +--
> 1 file changed, 1
On 29. 12. 18, 13:48, Valentin Vidic wrote:
> Give a better descriptions of what WAKEUP_CHARS represents.
>
> Signed-off-by: Valentin Vidic
I am not a native speaker, but this is much better than the current text.
Acked-by: Jiri Slaby
BTW this text is copy from/to all the other WAKEUP_CHARS
On Mon, Dec 31, 2018 at 4:46 PM Mike Rapoport wrote:
>
> On Fri, Dec 28, 2018 at 11:00:02AM +0800, Pingfan Liu wrote:
> > Customer reported a bug on a high end server with many pcie devices, where
> > kernel bootup with crashkernel=384M, and kaslr is enabled. Even
> > though we still see much
On Mon, Dec 31, 2018 at 4:40 PM Mike Rapoport wrote:
>
> On Fri, Dec 28, 2018 at 11:00:01AM +0800, Pingfan Liu wrote:
> > The bottom-up allocation style is introduced to cope with movable_node,
> > where the limit inferior of allocation starts from kernel's end, due to
> > lack of knowledge of
There are two new Realtek Ethernet devices which are re-branded r8168h.
Add the IDs to to support them.
Signed-off-by: Kai-Heng Feng
---
drivers/net/ethernet/realtek/r8169.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/ethernet/realtek/r8169.c
On Tue, Jan 1, 2019 at 11:58 AM Yong Wu wrote:
>
> Both mt8173 and mt8183 don't have this vld_pa_rng(valid physical address
> range) register while mt2712 have. Move it into the plat_data.
>
> Signed-off-by: Yong Wu
> ---
> drivers/iommu/mtk_iommu.c | 3 ++-
> drivers/iommu/mtk_iommu.h | 1 +
>
On Tue, Jan 1, 2019 at 11:58 AM Yong Wu wrote:
>
> In mt8173 and mt8183, 0x48 is REG_MMU_STANDARD_AXI_MODE while
> it is extended to REG_MMU_CTRL which contains _STANDARD_AXI_MODE in
> the other SoCs. I move this property to plat_data since both mt8173
> and mt8183 use this property.
>
> It is a
On 2019/1/3 0:26, liujian wrote:
Fixes: 57c5f4df0a5a ("uio: fix crash after the device is unregistered")
Signed-off-by: liujian
---
drivers/uio/uio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 5c10fc7..bde7d7a 100644
---
On 02.01.2019 00:36, Andrew Lunn wrote:
>>> Is there a .ndo_change_mtu callback, which does not assign a new mtu itself?
>>>
>> So far all drivers have to do it themselves. But IMO this is more a
>> workaround
>> for the core not doing it. It's something the core should do.
>> Now we can remove
Fixes: 57c5f4df0a5a ("uio: fix crash after the device is unregistered")
Signed-off-by: liujian
---
drivers/uio/uio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 5c10fc7..bde7d7a 100644
--- a/drivers/uio/uio.c
+++
On Tue, Jan 1, 2019 at 11:58 AM Yong Wu wrote:
>
> The protect memory setting is a little different in the different SoCs.
> In the register REG_MMU_CTRL_REG(0x110), the TF_PROT(translation fault
> protect) shift bit is normally 4 while it shift 5 bits only in the
> mt8173. This patch delete the
Add PCIe Root Port support for Stratix 10 device and also update
device tree binding documentation.
v2 -> v3:
-
- Rename Stratix10 to Stratix 10.
- Change bool s10_flag to enum version.
v1 -> v2:
-
- Add define S10_TLP_FMTTYPE_* macros.
- Remove initialize structure members to
Add PCIe Root Port support for Stratix 10 device.
Main differences:
- HIP interface to access Root Port configuration register.
- TLP programming flow:
- One REG0 register
- Don't need to check alignment
Signed-off-by: Ley Foon Tan
---
drivers/pci/controller/Kconfig |2 +-
Add support for altr,pcie-root-port-2.0.
Signed-off-by: Ley Foon Tan
---
.../devicetree/bindings/pci/altera-pcie.txt|4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/altera-pcie.txt
If all the components associated to a component master is not added
to the component framework due to the HW capability or Kconfig
selection, component_match will be NULL at
component_master_add_with_match().
To avoid this, component_match_alloc() is added to the framework,
to allcoate the struct
On Tue, Jan 1, 2019 at 11:58 AM Yong Wu wrote:
>
> The larb-id may be remapped in the smi-common, this means the
> larb-id reported in the mtk_iommu_isr isn't the real larb-id,
>
> Take mt8183 as a example:
>M4U
> |
>
On 23-12-18, 09:57, Julia Lawall wrote:
> Drop LIST_HEAD where the variable it declares is never used.
>
> tmp_list has been declared since the introduction of the driver
> and has never been used. The two declarations of list were
> introduced with the containing functions but were also not
On 23-12-18, 09:57, Julia Lawall wrote:
> Drop LIST_HEAD where the variable it declares is never used.
>
> The variable has not been used since the function was introduced
> in 740aa95703c5 ("dmaengine: pl330: Split device_control").
>
> The semantic patch that fixes this problem is as follows:
On 23-12-18, 09:57, Julia Lawall wrote:
> Drop LIST_HEAD where the variable it declares has never been
> used.
>
> The semantic patch that fixes this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@
> identifier x;
> @@
> - LIST_HEAD(x);
> ... when != x
> //
Applied, thanks
On 23-12-18, 09:57, Julia Lawall wrote:
> Drop LIST_HEAD where the variable it declares is never used.
>
> Commit ab703f818ac3 ("dmaengine: dw: lazy allocation of dma
> descriptors") removed the uses, but not the declaration.
>
> The semantic patch that fixes this problem is as follows:
>
On 23-12-18, 09:57, Julia Lawall wrote:
> Drop LIST_HEAD where the variable it declares is never used.
>
> The declarations were introduced with the file, but the declared
> variables were not used.
>
> The semantic patch that fixes this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
>
From: Honghui Zhang
drivers/pci/pcie-mediatek.c:720:13-16: WARNING: Suspicious code. resource_size
is maybe missing with mem
Generated by: scripts/coccinelle/api/resource_size.cocci
Signed-off-by: Honghui Zhang
---
drivers/pci/controller/pcie-mediatek.c | 4 +---
1 file changed, 1
Hi all,
On Mon, Dec 10, 2018 at 9:15 AM Nicolas Boichat wrote:
>
> This is a follow-up to the discussion in [1], [2].
>
> IOMMUs using ARMv7 short-descriptor format require page tables
> (level 1 and 2) to be allocated within the first 4GB of RAM, even
> on 64-bit systems.
>
> For L1 tables that
Hi all,
Please do not add any material destined for the next merge window to
your linux-next included trees until after -rc1 has been released.
Changes since 20181224:
The vfs tree gained conflicts against Linus' and the ext3 trees. It also
gained a build failure for which I added a work
Before device_register, if something goes wrong, we need to manually
free idev.
In the error handling path, after device_unregister, idev maybe have been
released, we should not use it anymore.
Signed-off-by: liujian
---
drivers/uio/uio.c | 25 +++--
1 file changed, 19
Hi Linus,
The following changes since commit f5d582777bcb1c7ff19a5a2343f66ea01de401c6:
Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid (2018-12-10
11:04:41 -0800)
are available in the Git repository at:
On Fri, 28 Dec 2018 at 00:31, Ard Biesheuvel wrote:
>
> Similar to how OP-TEE is exposed as a pseudo device under /firmware/optee
> on DT systems, permit OP-TEE presence to be exposed via a device object
> in the ACPI namespace. This makes it possible to model the OP-TEE interface
> as a platform
On Wednesday, January 2, 2019 5:56:10 AM IST Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 11 Dec 2018 10:13:22 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the f2fs tree got a conflict in:
> >
> > fs/f2fs/dir.c
> >
> > between commit:
> >
> > 848a010287e6 ("f2fs:
Hi Rui, Eduardo,
Wish you very happy new year and Thank you very much for your response.
Regards,
Srinath.
On Tue, Jan 1, 2019 at 9:37 PM Eduardo Valentin wrote:
>
> On Tue, Jan 01, 2019 at 10:04:39PM +0800, Zhang Rui wrote:
> > On 一, 2018-12-31 at 14:15 -0800, Florian Fainelli wrote:
> > >
>
On Tue, 1 Jan 2019, Vineeth Pillai wrote:
> Thanks a lot for the fixes and detailed explanation Hugh! I shall fold all
> the changes from you and Huang in the next iteration.
>
> Thanks for all the suggestions and comments as well. I am looking into all
> those and will include all the changes
syzbot has found a reproducer for the following crash on:
HEAD commit:28e8c4bc8eb4 Merge tag 'rtc-4.21' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1745f5bf40
kernel config:
Hi Al,
After merging the vfs tree, today's linux-next build (x86_64 allnoconfig)
failed like this:
fs/fs_context.c: In function 'logfc':
fs/fs_context.c:400:3: error: implicit declaration of function 'vprintk_emit';
did you mean 'dev_printk_emit'? [-Werror=implicit-function-declaration]
Small pull request this time around with only two commits; some missing
prototype warning fix and a syzkaller fix when a 9p server advertises a
too small msize.
The commit date is close-ish because I reworded a commit message to
add a Cc to stable for the msize fix recently, but the patchs
On Wed, Jan 2, 2019 at 1:54 AM Paul E. McKenney wrote:
>
> On Tue, Jan 01, 2019 at 10:03:20PM +0800, Junchang Wang wrote:
> > Torture types "rcu_bh" and "sched" were removed in commit "c770c82a23".
> > The name of torture type "rcu_busted" was changed to "busted" in commit
> > "b3c983142d". Two
On Thu 06 Dec 01:39 PST 2018, Srinivas Kandagatla wrote:
> Regmap would use device name to create debugfs entries. If the device
> has multiple regmaps it is recommended to use name field in regmap_config.
> Fix this by providing name to the regmap configs correctly.
>
> Without this patch we
If there is no shutdown callback, our board will report pcie UNF errors
after restarting. This patch add shutdown callback for hinic.
Signed-off-by: Xue Chaojing
---
drivers/net/ethernet/huawei/hinic/hinic_main.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
On 2018/12/31 下午5:51, Jesper Dangaard Brouer wrote:
Hi MST and Jason,
Could you please take a look at this? This bug is caused by a thread
resizing the tun-queue (via tun_queue_resize -> ptr_ring_resize_multiple).
And error happens in tun_net_xmit -> ptr_ring_produce. My guess is bug
On 2018/12/31 上午2:48, Michael S. Tsirkin wrote:
On Thu, Dec 27, 2018 at 06:04:53PM +0800, Jason Wang wrote:
On 2018/12/26 下午11:22, Michael S. Tsirkin wrote:
On Thu, Dec 06, 2018 at 04:17:36PM +0800, Jason Wang wrote:
On 2018/12/6 上午6:54, Michael S. Tsirkin wrote:
When use_napi is set,
On 2018/12/31 上午2:45, Michael S. Tsirkin wrote:
On Thu, Dec 27, 2018 at 06:00:36PM +0800, Jason Wang wrote:
On 2018/12/26 下午11:19, Michael S. Tsirkin wrote:
On Thu, Dec 06, 2018 at 04:17:36PM +0800, Jason Wang wrote:
On 2018/12/6 上午6:54, Michael S. Tsirkin wrote:
When use_napi is set,
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 8e143b90e4d45cca3dc53760d3cfab988bc74571
commit: 031337ace2d1c22a447da6390716fe92592cdd6e PCI: mediatek: Add loadable
kernel module support
date: 3 months ago
coccinelle warnings: (new ones prefixed by
Hi Joe,
On Tue, Jan 01, 2019 at 08:56:49AM -0800, Joe Perches wrote:
> On Tue, 2019-01-01 at 08:56 +0530, Manivannan Sadhasivam wrote:
> > Hi Joe,
>
> Hi Manivannan.
>
> > On Mon, Dec 31, 2018 at 11:12:18AM -0800, Joe Perches wrote:
> > > On Tue, 2019-01-01 at 00:25 +0530, Manivannan Sadhasivam
1. add uart APDMA controller device node
2. add uart 0/1/2/3/4/5 DMA function
Signed-off-by: Long Cheng
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 50 +
1 file changed, 50 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
In DMA engine framework, add 8250 uart dma to support MediaTek uart.
If MediaTek uart enabled(SERIAL_8250_MT6577), and want to improve
the performance, can enable the function.
Signed-off-by: Long Cheng
---
drivers/dma/mediatek/8250_mtk_dma.c | 652 +++
In Mediatek SOCs, the uart can support DMA function.
Base on DMA engine formwork, we add the DMA code to support uart. And put the
code under drivers/dma.
This series contains document bindings, Kconfig to control the function enable
or not,
device tree including interrupt and dma device node,
Hi all,
On Mon, 26 Nov 2018 15:39:25 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> arch/x86/kernel/cpu/resctrl/rdtgroup.c
>
> between commit:
>
> 16ec1a5d58ea ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context")
> (where the file is
On Mon, 2018-12-31 at 09:17 -0600, Bjorn Helgaas wrote:
> Run "git log --oneline --follow drivers/pci/controller/pcie-altera.c"
> and
> make your subject line match in style, phrasing, and capitalization.
>
> Hint:
>
> pci: altera: Add Stratix10 PCIe support
> ef75369a5b9a PCI:
On Mon, 2018-12-31 at 09:17 -0600, Bjorn Helgaas wrote:
> Run "git log --oneline --follow drivers/pci/controller/pcie-altera.c"
> and
> make your subject line match in style, phrasing, and capitalization.
>
> Hint:
>
> pci: altera: Add Stratix10 PCIe support
> ef75369a5b9a PCI:
On 12/31/18 12:27 AM, Tariq Toukan wrote:
>
>
> On 1/27/2018 2:41 PM, jianchao.wang wrote:
>> Hi Tariq
>>
>> Thanks for your kindly response.
>> That's really appreciated.
>>
>> On 01/25/2018 05:54 PM, Tariq Toukan wrote:
>>>
>>>
>>> On 25/01/2018 8:25 AM, jianchao.wang wrote:
Hi Eric
Let's say you had an old knife shack. Called Knife Shack InC. (you
ain't incorporated, you just call it that, looks nice on the sign). On
an old dusty road, telephone pole bout ready to fall down next typhoon
hit. Behind yo knoif shack there is quite a body of water, now it's
murky, but it is
The failure happened when I tried to send up to 96DPs per an interval
for SSP ISOC transations by libusb, this is used to verify SSP ISOC
function of USB3 GEN2 controller, so update it as 96DPs.
(refer usb3.1r1.0 section 8.12.6 Isochronous Transactions)
Signed-off-by: Chunfeng Yun
---
v2: update
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
kernel/cgroup/cgroup-v1.c
between commit:
3fc9c12d27b4 ("cgroup: Add named hierarchy disabling to cgroup_no_v1 boot
param")
from Linus' tree and commit:
b3678086951a ("kernfs, sysfs, cgroup, intel_rdt: Support
On Mon, 2018-12-31 at 10:15 -0600, Bjorn Helgaas wrote:
> On Mon, Dec 31, 2018 at 04:24:51PM +0800, Ley Foon Tan wrote:
> >
> > Add PCIe Root Port support for Stratix10 device and also update
> "Stratix10" is a big step better than "StratixXX" because a web
> search
> for the latter finds
On Fri, Dec 21, 2018 at 04:33:38AM +, Richard Zhu wrote:
> The MSI Enable bit in the MSI Capability (PCIe r4.0, sec 7.7.1.2)
> controls whether a Function can request service using MSI.
>
> i.MX6 Root Ports implement the MSI Capability and may use MSI to
> request service for events like PME,
Hi Al,
Today's linux-next merge of the vfs tree got conflicts in:
kernel/cgroup/cgroup.c
between commit:
e250d91d6575 ("cgroup: fix parsing empty mount option string")
from Linus' tree and commit:
b3678086951a ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context")
from the vfs tree.
On 2019/1/1 7:42, Nadav Amit wrote:
A recent enhancement intentionally fails the kernel build if the
compiler does not support retpolines and CONFIG_RETPOLINE is set.
However, the patch that introduced it did not change RETPOLINE macro
references into CONFIG_RETPOLINE ones. As a result,
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit bea5b158ff0da9c7246ff391f754f5f38e34577a
Author: Rob Herring
AuthorDate: Thu Aug 11 10:20:58 2016 -0500
Commit: Greg
Hi Steven,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 8e143b90e4d45cca3dc53760d3cfab988bc74571
commit: cec8d0e7f06e08b981e9d61bef267c8c36d536f5 sh: ftrace: Use
ftrace_graph_get_ret_stack() instead of
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
fs/Makefile
between commit:
d44170a7ba48 ("fs: common implementation of file type")
from the ext3 tree and commits:
fe43eec04841 ("vfs: Introduce fs_context, switch vfs_kern_mount() to it.")
82685adaccb3 ("vfs: Add
Hi Yu
As I understand it you are asking about the case where the two PCIe End Points
(EPs) are connected below the same PCIe switch that is connected via it's
Upstream Port (UPS) to a Root Port (RP) that is part of a Root Complex (RC).
Do I understand this correctly?
The ECR Eric mentioned
On 1/1/19 1:31 PM, Michael Straube wrote:
I've tested your patch and it solved the issue. No freezes and dmesg looks good.
I noticed that try_then_request_module() is also used in rtw_wep_encrypt() and
rtw_wep_decrypt(). I guess that also could cause problems?
Yes, I believe it would if
It is a sample for pstore_rom, using general ram rather than block device.
According to pstore_rom, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
It was unrelated to my USB issue. It happened again after I rebooted
within 4 hours of uptime.
This time there were 2 traces, one right after the other and included
another line number.
*
Jan 01 17:47:54 computername plasmashell[1048]: qt.qpa.xcb:
QXcbConnection: XCB error: 2 (BadValue),
Why should we need pstore_rom?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a sample for block device logger in driver
MTD (drivers/mtd/mtdoops.c).
2. Do not any equipment have
pstore_rom is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
Why should we need pstore_rom?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a
On Tue, Jan 01, 2019 at 02:53:07PM +0530, Aneesh Kumar K.V wrote:
> Fengguang Wu writes:
>
> > From: Yao Yuan
> >
> > Signed-off-by: Yao Yuan
> > Signed-off-by: Fengguang Wu
> > ---
> > arch/x86/kvm/mmu.c | 12 +++-
> > 1 file changed, 11 insertions(+), 1 deletion(-)
> >
> > ---
On Tue, Jan 01, 2019 at 03:32:50PM -0800, Linus Torvalds wrote:
> On Tue, Jan 1, 2019 at 3:16 PM Eduardo Valentin wrote:
> >
> > > It doesn't even build cleanly.
> > >
> >
> > Do you still have have a copy of the build error?
>
> A plain "make allmodconfig" shows a warning.
I see. I am afraid I
Patch sent by mistake. The commit message should be:
"Docs/kernel-api.rst: Remove blk-tag.c reference"
Thanks,
On Tue, Jan 01, 2019 at 10:40:14PM -0200, Marcos Paulo de Souza wrote:
> After 7ca01926463a, legacy rq tagging was removed, so block/blk-tag.c
> does not exists anymore. When generating
Am 31.12.18 um 23:56 schrieb Andreas Färber:
> Am 31.12.18 um 18:50 schrieb Mark Brown:
>> On Sun, Dec 30, 2018 at 11:55:46AM +0100, Andreas Färber wrote:
>>> Given that observed symptoms were CPU stalls, workqueue hangs and RCU
>>> problems, requiring a power-cycle to recover, I wonder whether we
After 7ca01926463a, legacy rq tagging was removed, so block/blk-tag.c
does not exists anymore. When generating pdfdocs, sphinx complains about
this missing file:
Error: Cannot open file ./block/blk-tag.c
Error: Cannot open file ./block/blk-tag.c
Error: Cannot open file ./block/blk-tag.c
Error:
Hi all,
On Fri, 7 Dec 2018 11:53:40 +1100 Stephen Rothwell
wrote:
>
> Hi all,
>
> Today's linux-next merge of the jc_docs tree got a conflict in:
>
> Documentation/filesystems/index.rst
>
> between commit:
>
> 1b71a6809f96 ("fs-verity: add a documentation file")
>
> from the fscrypt
The pull request you sent on Tue, 1 Jan 2019 07:20:41 +0900:
> git://github.com/openrisc/linux.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fbea8c7c793397cdf4ba53a32f99b656467b7c7f
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sun, 30 Dec 2018 10:51:31 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/
> tags/kgdb-4.21-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fcf010449ebe1db0cb68b2c6410972a782f2bd14
Thank you!
--
The pull request you sent on Mon, 31 Dec 2018 17:36:58 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
> tags/iommu-updates-v4.21
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8e143b90e4d45cca3dc53760d3cfab988bc74571
Thank you!
--
The pull request you sent on Mon, 31 Dec 2018 20:21:36 +0530:
> git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-4.21-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/78e8696c234ab637c4dd516cabeac344d84ec10b
Thank you!
--
Deet-doot-dot, I am a
Hi all,
On Tue, 11 Dec 2018 10:13:22 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the f2fs tree got a conflict in:
>
> fs/f2fs/dir.c
>
> between commit:
>
> 848a010287e6 ("f2fs: use IS_ENCRYPTED() to check encryption status")
>
> from the fscrypt tree and commit:
>
>
On Tue, Jan 1, 2019 at 5:30 PM Jan Vlietland wrote:
>
> Hi Ilia, many thanks for answering my mail.
>
> Tonight I tried to see what happens if I generate a xorg.conf file and place
> it in /etc/X11/xorg.conf, as described here:
>
1015331
You cannot revoke the GPL license, having no attached interest is
meaningless.
It is not meaningless, it is essential.
For you to have an attached interest, you must secure it.
And you must secure it from the property owner.
The GPL is a commercial distribution license.
It is
he compares lending a physical object to licensing intellectual
property
Why are you still LARPing as a laywer?
1015334
The foundation of this law IS in property law.
Copyright is alienable in all ways that property is (see: US Copyright
statute).
That is where you get the ability to
Hi Sinan,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 28e8c4bc8eb483c22d977e147a0b98fc63efadf7
commit: 5d32a66541c4683456507481a0944ed2985e75c7 PCI/ACPI: Allow ACPI to be
built without CONFIG_PCI set
date: 13
> > Is there a .ndo_change_mtu callback, which does not assign a new mtu itself?
> >
> So far all drivers have to do it themselves. But IMO this is more a workaround
> for the core not doing it. It's something the core should do.
> Now we can remove this from drivers.
Hi Heiner
I think somebody
On Tue, Jan 1, 2019 at 3:16 PM Eduardo Valentin wrote:
>
> > It doesn't even build cleanly.
> >
>
> Do you still have have a copy of the build error?
A plain "make allmodconfig" shows a warning.
And I refuse to add new warnings.
Linus
Thanks for your response :).
Please Spread the word regarding the copyright-holders rights (remeber:
the
Linux kernel programmers did not sign over their copyrights, one of the
reasons Linux grew so quickly amongst developers where GNU very slowly
(The FSF will only include code where the
On Tue, Jan 01, 2019 at 03:18:51PM +0530, Murali Krishna Policharla wrote:
> Hi Andrew,
>Currently net/dsa/slave.c does not have
> ndo_change_mtu function. But shortly I will be submitting a separate
> patch outside this fix that has ndo_change_mtu function support
On Tue, Jan 01, 2019 at 01:35:36PM -0800, Linus Torvalds wrote:
> On Tue, Jan 1, 2019 at 8:05 AM Eduardo Valentin wrote:
> >
> > Please consider pulling from
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
> > linus
>
> No.
>
> I pulled and immediately
Funny, the pro-CoC developers claim any discussion is off-topic on the
linux developer lists.
The licensing of linux-kernel is completely on topic, since there may
be linux-copyright-holders reading this list.
They have been told they have no rights, that they transferred them
away.
This is
If you lend (license) your lawnmower to BrucePerens, and receive nothing
in return, and BrucePerens hires someone else to draw a star on your
lawnmower, BrucePerens believes he can keep your lawnmower forever
because he "relied" on your lease and , even though he paid you nothing
and you never
I have a very profitable business proposal for you
1 - 100 of 209 matches
Mail list logo
