add support to identify physical device by flashing an LED
attached to it with ethtool -p cmd.
Signed-off-by: Luo bin
---
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 34
.../net/ethernet/huawei/hinic/hinic_hw_dev.c | 2 +
.../net/ethernet/huawei/hinic/hinic_hw_dev.h | 1 +
add support to get eeprom information from the plug-in module
with ethtool -m cmd.
Signed-off-by: Luo bin
---
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 69 ++
.../net/ethernet/huawei/hinic/hinic_hw_dev.h | 4 ++
.../net/ethernet/huawei/hinic/hinic_port.c| 72
add support to set TX/RX irq coalesce params with ethtool -C and
get these params with ethtool -c.
Signed-off-by: Luo bin
---
drivers/net/ethernet/huawei/hinic/hinic_dev.h | 8 +
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 234 ++
add support to set pause params with ethtool -A and get pause
params with ethtool -a. Also remove set_link_ksettings ops for VF
and enable pause by default.
Signed-off-by: Luo bin
---
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 86 ++-
add support to excute internal and external loopback test with
ethtool -t cmd.
Signed-off-by: Luo bin
---
drivers/net/ethernet/huawei/hinic/hinic_dev.h | 6 +
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 177 ++
.../net/ethernet/huawei/hinic/hinic_hw_dev.h | 3 +
> Signed-off-by: jiangying8582
Please use the real name for your contributions.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=719fdd32921fb7e3208db8832d32ae1c2d68900f#n431
Would you like to add the tag “Fixes” to the
нед, 28. јун 2020. у 14:06 Marc Zyngier је написао/ла:
>
> On 2020-06-28 12:25, Aleksandar Markovic wrote:
> > сре, 24. јун 2020. у 10:40 Marc Zyngier је написао/ла:
> >>
> >> On 2020-06-24 08:44, Tiezhu Yang wrote:
> >> > [git send-email failed due to too many commands,
> >> > so only cc the
On Sun, Jun 28, 2020 at 2:14 PM Maxim Levitsky wrote:
>
> Hi,
>
> I just did usual kernel update and now chromium crashes on startup.
> It happens both in a KVM's VM (with virtio-gpu if that matters) and natively
> with amdgpu driver.
> Most likely not GPU related although I initially suspected
Hi Sathy,
one minor comments below.
On 2020/6/5 5:50, sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> PCI_ERS_RESULT_NEED_RESET error status implies the device is
> requesting a slot reset and a notification about slot reset
> completion via
The 06/26/2020 13:00, David Miller wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> From: Horatiu Vultur
> Date: Fri, 26 Jun 2020 09:33:47 +0200
>
> > This patch series extends MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR.
> > To
Hi Jay,
I've tested the patches on my board, and they work well.
Thanks,
Yicong
On 2020/6/25 2:52, Jay Vosburgh wrote:
> Jay Vosburgh wrote:
>
>> sathyanarayanan.kuppusw...@linux.intel.com wrote:
>>
>> From: Kuppuswamy Sathyanarayanan
>>> Fatal (DPC) error recovery is currently broken for
There's patches in tip/sched/urgent for this...
On Sat, Jun 27, 2020 at 07:37:54PM -0700, Bart Van Assche wrote:
> On 2020-06-26 08:44, Alan Stern wrote:
> > On Fri, Jun 26, 2020 at 08:07:51AM -0700, Bart Van Assche wrote:
> >> As far as I know runtime power management support in the sd driver is
> >> working
> >> fine and is being used
Greeting
Please forgive me for stressing you with my predicaments and I sorry
to approach you through this media it is because it serves the fastest
means of communication. I came across your E-mail from my personal
search and I decided to contact you believing you will be honest to
fulfill my
On Sun, 2020-06-28 at 15:53 +0300, Amir Goldstein wrote:
> On Sun, Jun 28, 2020 at 2:14 PM Maxim Levitsky wrote:
> > Hi,
> >
> > I just did usual kernel update and now chromium crashes on startup.
> > It happens both in a KVM's VM (with virtio-gpu if that matters) and
> > natively with amdgpu
> when it returns an error code. Thus a pairing decrement is needed on
* I find it more appropriate to use the word “corresponding” here
(if you do still not like previous wording suggestions).
* Will it become helpful to add the tag “Fixes” to the commit message?
On Sun, 2020-06-28 at 16:14 +0300, Maxim Levitsky wrote:
> On Sun, 2020-06-28 at 15:53 +0300, Amir Goldstein wrote:
> > On Sun, Jun 28, 2020 at 2:14 PM Maxim Levitsky wrote:
> > > Hi,
> > >
> > > I just did usual kernel update and now chromium crashes on startup.
> > > It happens both in a KVM's
On Sat, Jun 27, 2020 at 10:39:20PM -0700, Linus Torvalds wrote:
> Ugh.
Heh, I was afraid of that..
> So how about the attached trivial two-liner? We solve the problem by
> simply marking ourselves TASK_RUNNING, which means that we won't be
> counted as an exclusive wakeup.
>
> Ok, so the "one"
On Sun, Jun 28, 2020 at 4:17 PM Maxim Levitsky wrote:
>
> On Sun, 2020-06-28 at 16:14 +0300, Maxim Levitsky wrote:
> > On Sun, 2020-06-28 at 15:53 +0300, Amir Goldstein wrote:
> > > On Sun, Jun 28, 2020 at 2:14 PM Maxim Levitsky
> > > wrote:
> > > > Hi,
> > > >
> > > > I just did usual kernel
On 6/26/20 11:12 PM, Stephen Rothwell wrote:
> Hi Jens,
>
> On Fri, 26 Jun 2020 20:25:31 -0600 Jens Axboe wrote:
>>
>> Right, but that's what git format-patch does when the line is long.
>
> I just tested, and "git format-patch" (for me) does *not* split those lines.
Huh, I could have sworn
Fixed a coding style issue.
Signed-off-by: B K Karthik
---
init/main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/init/main.c b/init/main.c
index 9127b240fd26..d8477fb95bec 100644
--- a/init/main.c
+++ b/init/main.c
@@ -385,11 +385,11 @@ static u32
I suggest to choose a more succinct patch subject.
> After the device is disconnected from the host side, the interface of
> the device is reset. If the userspace operates the device again,
> an error code should be returned.
Please use an imperative wording for the commit message.
The following sparse warnings are fixed:
net/bridge/br_mrp.c:106:18: warning: incorrect type in assignment (different
base types)
net/bridge/br_mrp.c:106:18:expected unsigned short [usertype]
net/bridge/br_mrp.c:106:18:got restricted __be16 [usertype]
net/bridge/br_mrp.c:281:23: warning:
Hi Wolfram,
You are right, +1 isn't required.
Checked your patch also on HW. It works OK.
Thank you,
Michael.
> -Original Message-
> From: Wolfram Sang
> Sent: Sunday, June 28, 2020 2:53 PM
> To: linux-...@vger.kernel.org
> Cc: linux-renesas-...@vger.kernel.org; Wolfram Sang
On 28/06/2020 16:45, Horatiu Vultur wrote:
> The following sparse warnings are fixed:
> net/bridge/br_mrp.c:106:18: warning: incorrect type in assignment (different
> base types)
> net/bridge/br_mrp.c:106:18:expected unsigned short [usertype]
> net/bridge/br_mrp.c:106:18:got restricted
The following are reported while using checkpatch.pl on
drivers/staging/fbtft/fbtft-bus.c
ERROR: space prohibited before that close parenthesis ')'
#65: FILE: drivers/staging/fbtft/fbtft-bus.c:65:
+define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8, )
ERROR: space prohibited before that close
Hi Linus,
please pull the x86/entry urgent pile which has accumulated since the
merge window. It is not the smallest but considering the almost complete
entry core rewrite, the amount of fixes to follow is somewhat higher
than usual, which is to be expected.
Thx.
---
The following changes since
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger crash:
Reported-and-tested-by: syzbot+08e3d39f3eb864321...@syzkaller.appspotmail.com
Tested on:
commit: 152c6a4d genetlink: get rid of family->attrbuf
git tree: https://github.com/congwang/linux.git
Hi Linus,
please pull three fixes from peterz suppressing KCOV instrumentation in
noinstr sections.
Thx.
---
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
uio_pdrv_genirq and uio_dmem_genirq interrupts are handled in
userspace. So the condition for the interrupt hasn't normally not been
cleared when top half returns. disable_irq_nosync is called in top half,
but since that normally is lazy the irq isn't actually disabled.
For level triggered
On Sun, Jun 28, 2020 at 03:43:10PM +0200, Markus Elfring wrote:
> I suggest to choose a more succinct patch subject.
>
>
> > After the device is disconnected from the host side, the interface of
> > the device is reset. If the userspace operates the device again,
> > an error code should be
Hi, Bernard:
Bernard Zhao 於 2020年6月16日 週二 下午2:51寫道:
>
> In function mtk_dsi_clk_hs_state, remove unnecessary conversion
> to bool return, this change is to make the code a bit readable.
Applied to mediatek-drm-fixes [1], thanks.
[1]
On Sun, Jun 28, 2020 at 5:20 PM H. Nikolaus Schaller wrote:
>
>
> > Am 28.06.2020 um 09:52 schrieb Masahiro Yamada :
> >
> > On Sun, Jun 28, 2020 at 3:17 PM H. Nikolaus Schaller
> > wrote:
> >>
> >> Hi,
> >>
> >>> Am 28.06.2020 um 07:51 schrieb Masahiro Yamada :
> >>>
> >>> On Thu, Jun 25, 2020
guoren 於 2020年6月27日 週六 上午12:29寫道:
>
> Hi Greentime,
>
> On 2020/6/23 9:28 下午, Greentime Hu wrote:
> > This patch implements and enables context tracking for riscv (which is a
> > prerequisite for CONFIG_NO_HZ_FULL support)
> >
> > It adds checking for previous state in the entry that all
dma-api
dma-api-howto
dma-attributes
dma-isa-lpc
The above 4 documents have been renamed and moved to
Documentation/core-api/, but there are still some old references
refer to the old files, this patch tries to correct them.
Fixes: 728c1471b544 ("docs: move DMA kAPI to Documentation/core-api")
Hi Linus,
please pull two urgent RCU, KCSAN-related fixes.
Thx.
---
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
Hi Linus,
please pull the x86/urgent pile which has nothing but clear fixes.
Thx.
---
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
On Sun, Jun 28, 2020 at 9:21 PM Mauro Carvalho Chehab
wrote:
>
> The Qt5 conversion broke support for debug info links.
>
> Restore the behaviour added by changeset
> ab45d190fd4a ("kconfig: create links in info window").
>
> Reported-by: Maxim Levitsky
> Signed-off-by: Mauro Carvalho Chehab
On Sun, Jun 28, 2020 at 5:40 PM Maxim Levitsky wrote:
>
> On Thu, 2020-06-25 at 16:52 +0200, Mauro Carvalho Chehab wrote:
> > The logic handling find on split mode is currently broken.
> > Fix it, making it work again as expected.
>
> I tested this patch and it works well.
> There is one really
On Sun, 2020-06-28 at 23:41 +0900, Masahiro Yamada wrote:
> On Sun, Jun 28, 2020 at 9:21 PM Mauro Carvalho Chehab
> wrote:
> > The Qt5 conversion broke support for debug info links.
> >
> > Restore the behaviour added by changeset
> > ab45d190fd4a ("kconfig: create links in info window").
> >
>
Fixes sparse warning:
Function parameter or member 'pbuflen' not described in 'packing'
Fixes: 554aae35007e ("lib: Add support for generic packing operations")
Signed-off-by: Vladimir Oltean
---
Hi David, since the original "packing" submission went in through your
tree, could you please take
On Sun, 28 Jun 2020 14:12:07 +0800
Guo Ren wrote:
> On Sun, Jun 28, 2020 at 10:59 AM Masami Hiramatsu wrote:
> >
> > On Sat, 27 Jun 2020 16:20:02 +
> > guo...@kernel.org wrote:
> >
> > > From: Guo Ren
> > >
> > > Unfortunately, the current code couldn't be compiled, because
> > >
On Sun, 2020-06-28 at 10:00 -0400, B K Karthik wrote:
> The following are reported while using checkpatch.pl on
> drivers/staging/fbtft/fbtft-bus.c
>
> ERROR: space prohibited before that close parenthesis ')'
> #65: FILE: drivers/staging/fbtft/fbtft-bus.c:65:
>
On Sun, Jun 28, 2020 at 11:48 PM Maxim Levitsky wrote:
>
> On Sun, 2020-06-28 at 23:41 +0900, Masahiro Yamada wrote:
> > On Sun, Jun 28, 2020 at 9:21 PM Mauro Carvalho Chehab
> > wrote:
> > > The Qt5 conversion broke support for debug info links.
> > >
> > > Restore the behaviour added by
From: Tom Rix
To use a dfl pci device, several dfl configs need to be selected.
This is tedious and error prone.
So automagically select the needed configs when FPGA_DFL_PCI
is selected.
Signed-off-by: Tom Rix
---
drivers/fpga/Kconfig | 36 +---
1 file
Hi Linus,
please pull the sched/urgent pile. I had to rebase it last-minute ontop
of -rc2 because it was based on a random merge commit after -rc2 and I
know you don't like pull requests based on random commits if there's not
a real reason for that.
Peter and I did try to look for a real reason
From: Bartosz Golaszewski
Memory allocated with kstrdup_const() must not be passed to regular
krealloc() as it is not aware of the possibility of the chunk residing
in .rodata. Since there are no potential users of krealloc_const()
at the moment, let's just update the doc to make it explicit.
These pins on the PocketBeagle P1 and P2 headers are connected to AM3358
balls with gpio lines, and these pins are not used for any other
peripherals by default. These GPIO lines are unclaimed and could be used
by userspace program through the gpiod ABI.
This patch adds a "default" state in the
On Sat, Dec 21, 2019 at 07:02:25AM -0700, Jens Axboe wrote:
> On 12/21/19 6:43 AM, Hillf Danton wrote:
> >
> > On Sat, 21 Dec 2019 00:05:07 -0800
> >> Hello,
> >>
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:7ddd09fc Add linux-next specific files for 20191220
> >> git tree:
Em Sun, 28 Jun 2020 17:48:08 +0300
Maxim Levitsky escreveu:
> On Sun, 2020-06-28 at 23:41 +0900, Masahiro Yamada wrote:
> > On Sun, Jun 28, 2020 at 9:21 PM Mauro Carvalho Chehab
> > wrote:
> > > The Qt5 conversion broke support for debug info links.
> > >
> > > Restore the behaviour added by
On Thu, Jun 11, 2020 at 6:29 PM Bob Liu wrote:
>
> Current code always set 'Unbound && max_active == 1' workqueues to ordered
> implicitly, while this may be not an expected behaviour for some use cases.
>
> E.g some scsi and iscsi workqueues(unbound && max_active = 1) want to be bind
> to
On Sun, Jun 28, 2020 at 10:52 PM Masami Hiramatsu wrote:
>
> On Sun, 28 Jun 2020 14:12:07 +0800
> Guo Ren wrote:
>
> > On Sun, Jun 28, 2020 at 10:59 AM Masami Hiramatsu
> > wrote:
> > >
> > > On Sat, 27 Jun 2020 16:20:02 +
> > > guo...@kernel.org wrote:
> > >
> > > > From: Guo Ren
> > > >
On 6/27/2020 2:40 AM, Furquan Shaikh wrote:
[CAUTION: External Email]
This change drops the override in `amd_gpio_irq_set_type()` that
ignores the IRQ trigger type settings from the caller. The device
driver (caller) is in a better position to identify the right trigger
type for the device
Hello RT-list!
I'm pleased to announce the 4.14.186-rt86 stable release.
Note: This update required dealing with a conflict in net/core/dev.c, where
devnet_rename_seq was moved from a seqence count to an RWSEWM and renamed
to devnet_rename_sem. If you encounter runtime issues that show
From: Guo Ren
Unfortunately, the current code couldn't be compiled:
CC arch/riscv/kernel/patch.o
In file included from ./include/linux/kernel.h:11,
from ./include/linux/list.h:9,
from ./include/linux/preempt.h:11,
from
Hi Paul,
在 2020/6/27 上午1:20, Paul Cercueil 写道:
Hi Zhou,
Le sam. 27 juin 2020 à 0:48, 周琰杰 (Zhou Yanjie)
a écrit :
Add new functions to "jz4780_otg_phy_ops" to enable or disable the
USB PHY in the Ingenic JZ4780 SoC.
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
The method struct pci_error_handlers::error_detected() is defined and
documented as taking an 'enum pci_channel_state' for the second
argument but most drivers use 'pci_channel_state_t' instead.
This 'pci_channel_state_t' is not a typedef for the enum but a typedef
for a bitwise type in order to
On Sun, Jun 28, 2020 at 12:18:10PM +0800, Xiang Zheng wrote:
> On 2020/6/26 7:24, Bjorn Helgaas wrote:
> > On Wed, Jun 24, 2020 at 06:23:09PM -0500, Bjorn Helgaas wrote:
> >> On Tue, Dec 10, 2019 at 11:15:27AM +0800, Xiang Zheng wrote:
> >>> 7ea7e98fd8d0 ("PCI: Block on access to temporarily
Hi Paul,
在 2020/6/27 上午1:36, Paul Cercueil 写道:
Hi Zhou,
Le sam. 27 juin 2020 à 0:48, 周琰杰 (Zhou Yanjie)
a écrit :
Add new functions to "x1000_otg_phy_ops" to calculat the rate of REFCLK,
which is needed by USB PHY in the Ingenic X1000 SoC.
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰
Em Sun, 28 Jun 2020 23:41:46 +0900
Masahiro Yamada escreveu:
> On Sun, Jun 28, 2020 at 9:21 PM Mauro Carvalho Chehab
> wrote:
> >
> > The Qt5 conversion broke support for debug info links.
> >
> > Restore the behaviour added by changeset
> > ab45d190fd4a ("kconfig: create links in info
Hi Steve,
On Fri, 26 Jun 2020 21:00:42 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Up until now, if an event is interrupted while it is recorded by an
> interrupt, and that interrupt records events, the time of those events will
> all be the same. This is because events
On Sun, 28 Jun 2020 16:07:37 +
guo...@kernel.org wrote:
> From: Guo Ren
>
> Unfortunately, the current code couldn't be compiled:
>
> CC arch/riscv/kernel/patch.o
> In file included from ./include/linux/kernel.h:11,
> from ./include/linux/list.h:9,
>
On Sun, Jun 28, 2020 at 01:17:59PM +0200, Markus Elfring wrote:
> > kmalloc(1024, GFP_HIGHUSER) can allocate memory normally,
> > kmalloc(64*1024, GFP_HIGHUSER) will cause a memory leak,
>
> Would you like to explain the influence of the selected allocation size
> in a different way?
Markus,
On Mon, 29 Jun 2020 01:23:23 +0900
Masami Hiramatsu wrote:
> >
> > Here's the design of this solution:
> >
> > All this is per cpu, and only needs to worry about nested events (not
> > parallel events).
> >
>
> This looks basically good to me, but I have some comments below.
> (just a
On 2020-06-28 13:48, Aleksandar Markovic wrote:
нед, 28. јун 2020. у 14:06 Marc Zyngier је написао/ла:
On 2020-06-28 12:25, Aleksandar Markovic wrote:
> сре, 24. јун 2020. у 10:40 Marc Zyngier је написао/ла:
>>
>> On 2020-06-24 08:44, Tiezhu Yang wrote:
>> > [git send-email failed due to too
On Thu, Jun 25, 2020 at 5:32 AM 'Sami Tolvanen' via Clang Built Linux
wrote:
>
> This patch series adds support for building x86_64 and arm64 kernels
> with Clang's Link Time Optimization (LTO).
>
> In addition to performance, the primary motivation for LTO is to allow
> Clang's Control-Flow
On Sun, Jun 28, 2020 at 7:05 AM Borislav Petkov wrote:
>
> please pull the x86/entry urgent pile which has accumulated since the
> merge window. It is not the smallest but considering the almost complete
> entry core rewrite, the amount of fixes to follow is somewhat higher
> than usual, which is
нед, 28. јун 2020. у 18:55 Marc Zyngier је написао/ла:
>
> On 2020-06-28 13:48, Aleksandar Markovic wrote:
> > нед, 28. јун 2020. у 14:06 Marc Zyngier је написао/ла:
> >>
> >> On 2020-06-28 12:25, Aleksandar Markovic wrote:
> >> > сре, 24. јун 2020. у 10:40 Marc Zyngier је написао/ла:
> >> >>
>
On Fri, Jun 26, 2020 at 8:41 PM Dan Williams wrote:
>
> On Fri, Jun 26, 2020 at 10:34 AM Rafael J. Wysocki wrote:
> >
> > Hi All,
> >
> > On Monday, June 22, 2020 3:50:42 PM CEST Rafael J. Wysocki wrote:
> > > Hi All,
> > >
> > > This series is to address the problem with RCU synchronization
On 2020-06-27 09:04, Christoph Hellwig wrote:
On Sat, Jun 27, 2020 at 01:00:19AM +0200, Daniel Borkmann wrote:
Given there is roughly a ~5 weeks window at max where this removal could
still be applied in the worst case, could we come up with a fix / proposal
first that moves this into the DMA
Add new functions to "jz4780_otg_phy_ops" to enable or disable the
USB PHY in the JZ4780 SoC.
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
1.Use "WARN()" instead "BUG()".
2.Move the reformat part ot the new patch.
3.Remove unnecessary
Reformat the code (add one level of indentation before the values),
to align the code in the macro definition section.
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v2:
New patch.
drivers/clk/ingenic/jz4780-cgu.c | 90
On Sun, Jun 28, 2020 at 09:57:00AM -0700, Linus Torvalds wrote:
> Tssk. This has an unnecessary merge "to resolve conflicts". I'd much
> rather have seen the pull without that.
Yeah, reportedly because "Linus renamed probe_kernel_read() and [peterz]
removed a call". I guess they did that for
Add functions for calculat the rate of REFCLK, which is needed by
USB PHY in Ingenic X1000 SoC.
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
1.Use "WARN()" instead "BUG()".
2.Remove unnecessary get_parent/set_parent functions.
v1->v2:
1.Use "WARN()" instead "BUG()".
2.Move the reformat part ot the new patch.
3.Remove unnecessary get_parent/set_parent functions.
周琰杰 (Zhou Yanjie) (3):
clk: JZ4780: Add functions for enable and disable USB PHY.
clk: JZ4780: Reformat the code to align it.
clk: X1000: Add support for
commit db37a34c563b ("block, bfq: get a ref to a group when adding it to a
service tree")
introduce leak forbfq_group and blkcg_gq objects because of get/put
imbalance. See trace balow:
-> blkg_alloc
-> bfq_pq_alloc
-> bfqg_get (+1)
->bfq_activate_bfqq
->bfq_activate_requeue_entity
On Fri, Jun 26, 2020 at 8:43 PM Dan Williams wrote:
>
> On Fri, Jun 26, 2020 at 7:22 AM Rafael J. Wysocki wrote:
> >
> > On Fri, Jun 26, 2020 at 2:06 AM Dan Williams
> > wrote:
> > >
> > > Quoting the documentation:
> > >
> > > Some persistent memory devices run a firmware locally on the
On 06/27/2020 10:12 PM, Rakesh Pillai wrote:
-Original Message-
From: Ben Greear
Sent: Saturday, June 27, 2020 8:58 PM
To: Rakesh Pillai ; ath...@lists.infradead.org
Cc: linux-wirel...@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath10k: Add history for
On Fri, Jun 26, 2020 at 06:14:55PM -0400, Steven Rostedt wrote:
> On Wed, 24 Jun 2020 20:59:13 -0700
> Alexei Starovoitov wrote:
>
> > > >
> > > > Nack.
>
> I nack your nack ;-)
ok. let's take it up to Linus to decide.
>
> > > > The message is bogus. It's used in production kernels.
> > > >
On Sun, 2020-06-28 at 17:25 +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Memory allocated with kstrdup_const() must not be passed to regular
> krealloc() as it is not aware of the possibility of the chunk residing
> in .rodata. Since there are no potential users of
--
Your attention to this news update.
The report / analysis received from our correspondence shows that you
have NOT received your PAYMENT, due to administrative injustice from
unpatriotic and uncivil payment officials. Following the resolution of
the U.S Department of State, you are mandated
On Sun, Jun 28, 2020 at 12:46:28PM +0900, Masahiro Yamada wrote:
> On Sun, Jun 28, 2020 at 6:21 AM Domenico Andreoli
> wrote:
> >
> > On Sat, Jun 27, 2020 at 09:02:52PM +0900, Masahiro Yamada wrote:
> > > On Sat, Jun 27, 2020 at 6:40 AM Domenico Andreoli
> > > wrote:
> > > > On Fri, Jun 26,
* Borislav Petkov wrote:
> On Sun, Jun 28, 2020 at 09:57:00AM -0700, Linus Torvalds wrote:
> > Tssk. This has an unnecessary merge "to resolve conflicts". I'd much
> > rather have seen the pull without that.
>
> Yeah, reportedly because "Linus renamed probe_kernel_read() and [peterz]
>
Commit f16861b12fa0 ("regulator: rename da903x to da903x-regulator") missed
to adjust the DIALOG SEMICONDUCTOR DRIVERS section in MAINTAINERS.
Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
warning: no file matchesF:drivers/regulator/da903x.c
The da903x-regulator.c
On Sun, Jun 28, 2020 at 7:37 PM Joe Perches wrote:
>
> On Sun, 2020-06-28 at 17:25 +0200, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > Memory allocated with kstrdup_const() must not be passed to regular
> > krealloc() as it is not aware of the possibility of the chunk
* Borislav Petkov wrote:
> Hi Linus,
>
> please pull the sched/urgent pile. I had to rebase it last-minute ontop
> of -rc2 because it was based on a random merge commit after -rc2 and I
> know you don't like pull requests based on random commits if there's not
> a real reason for that.
I
> I saw it with the mv64xxx (Allwinner) and omap (Beaglebone) drivers.
> From a quick look, it seems like quite a few others have the same
> problem.
Okay, well, to be fair, both drivers don't advertise
I2C_SMBUS_BLOCK_DATA. The client driver should check for that. Anyhow,
it makes sense to have
On Sun, 2020-06-28 at 20:06 +0200, Bartosz Golaszewski wrote:
> On Sun, Jun 28, 2020 at 7:37 PM Joe Perches wrote:
> > On Sun, 2020-06-28 at 17:25 +0200, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski
> > >
> > > Memory allocated with kstrdup_const() must not be passed to regular
>
On 23/06/2020 14:36, Pavel Machek wrote:
> Many SSDs are buggy, and will eventually corrupt themselves if you do enough
> sudden power loss experiments.
>
> HDDs don't like their power cut, either. You can hear the difference
> between normal power off and power cut...
I will change the patch
On 19/06/2020 00:31, Damien Le Moal wrote:
> On 2020/06/18 21:26, Simon Arlott wrote:
>> I haven't verified it, but the BIOS leaves the power off for several
>> seconds which should be long enough for the HDDs to spin down.
>>
>> I'm less concerned about those suddenly losing power but it would
Linus,
Please pull the latest efi/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
efi-urgent-2020-06-28
# HEAD: 2a55280a3675203496d302463b941834228b9875 efi/libstub: arm: Print CPU
boot mode and MMU state at boot
- Fix build regression on v4.8 and older
On Sat, 2020-06-27 at 06:32 -0700, t...@redhat.com wrote:
> From: Tom Rix
>
> clang static analysis flags several null function pointer problems.
>
> drivers/scsi/scsi_transport_spi.c:374:1: warning: Called function
> pointer is null (null dereference) [core.CallAndMessage]
>
The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
which is a typedef for an enum type defining 'NETDEV_TX_OK' but this
driver returns '0' instead of 'NETDEV_TX_OK'.
Fix this by returning ''NETDEV_TX_OK' instead of 0.
Signed-off-by: Luc Van Oostenryck
---
On 23/06/2020 21:42, Henrique de Moraes Holschuh wrote:
> [1] I have long lost the will and energy to pursue this, so *this* is a
> throw-away anecdote for anyone that cares: I reported here a few years
> ago that many models of *SATA* based SSDs from Crucial/Micron, Samsung
> and Intel were
I need to use "reboot=p" on my desktop because one of the PCIe devices
does not appear after a warm boot. This results in a very cold boot
because the BIOS turns the PSU off and on.
The scsi sd shutdown process does not send a stop command to disks
before the reboot happens (stop commands are
Linus,
Please pull the latest perf/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-2020-06-28
# HEAD: 16accae3d97f97d7f61c4ee5d0002bccdef59088 perf/x86/rapl: Fix RAPL
config variable bug
A single Kbuild dependency fix.
Signed-off-by: Ingo
Linus,
Please pull the latest timers/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-2020-06-28
# HEAD: f097eb38f71391ff2cf078788bad5a00eb3bd96a timekeeping: Fix kerneldoc
system_device_crosststamp & al
A single DocBook fix.
Thanks,
The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
which is a typedef for an enum type, but the implementation in this
driver returns an 'int'.
Fix this by returning 'netdev_tx_t' in this driver too and
usind 'NETDEV_TX_OK' instead of 0 accordingly.
Signed-off-by: Luc Van
On Sun, Jun 28, 2020 at 11:15 AM Ingo Molnar wrote:
>
> I based sched/urgent on a tested-working merge commit, not on a random
> interim commit - in this sense your rebase of 68f7b5cc835d was
> somewhat unnecessary.
>
> I believe avoiding random merge commits is mostly relevant in the
> merge
The pull request you sent on Sun, 28 Jun 2020 16:38:35 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/rcu_urgent_for_5.8_rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c141b30e9960e81455ad9c3658c079051eea7e2d
Thank you!
--
101 - 200 of 364 matches
Mail list logo