Current matching rules ensure that the voltage range of selected Source
Capability is entirely within the range defined in one of the Sink
Capabilities. This is reasonable but not practical because Sink may not
support wide range of voltage when sinking power while Source could
advertise its
From: Wanpeng Li
Reported by syzkaller:
CPU: 1 PID: 5962 Comm: syz-executor118 Not tainted 4.20.0-rc6+ #374
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:kvm_apic_hw_enabled arch/x86/kvm/lapic.h:169 [inline]
RIP:
In some scenario, we need to build initrd with kernel in a single image.
This can simplify system deployment process by downloading the whole system
once, such as in IC verification.
This patch adds support to upgrade ACPI tables from built-in initrd.
Cc: Joey Zheng
Signed-off-by: Shunyong Yang
Everyone:
This patch contains changes I made in order to add support for i.MX8MQ
to reset-imx7.c in order to enable support of PCIE IP block on i.MX8MQ
SoCs.
NOTE: This patch depens on CONFIG_ARCH_IMX8MQ introduced in [imx8mq]
Feedback is welcome!
Thanks,
Andrey Smirnov
Changes since [v2]
-
The driver now supports i.MX8MQ, so update bindings accordingly.
Cc: p.za...@pengutronix.de
Cc: Fabio Estevam
Cc: cphe...@gmail.com
Cc: l.st...@pengutronix.de
Cc: Leonard Crestez
Cc: "A.s. Dong"
Cc: Richard Zhu
Cc: Rob Herring
Cc: devicet...@vger.kernel.org
Cc: linux-...@nxp.com
Cc:
In order to enable supporting i.MX8MQ with this driver, convert it to
expect variant specific bits to be passed via driver data.
Cc: p.za...@pengutronix.de
Cc: Fabio Estevam
Cc: cphe...@gmail.com
Cc: l.st...@pengutronix.de
Cc: Leonard Crestez
Cc: "A.s. Dong"
Cc: Richard Zhu
Cc: Rob Herring
Add bits and pieces needed to support IP block variant found on
i.MX8MQ SoCs.
Cc: p.za...@pengutronix.de
Cc: Fabio Estevam
Cc: cphe...@gmail.com
Cc: l.st...@pengutronix.de
Cc: Leonard Crestez
Cc: "A.s. Dong"
Cc: Richard Zhu
Cc: Rob Herring
Cc: devicet...@vger.kernel.org
Cc: linux-...@nxp.com
User space tools which do automated task placement need information
about AVX-512 usage of tasks, because AVX-512 usage could cause core
turbo frequency drop and impact the running task on the sibling CPU.
The XSAVE hardware structure has bits that indicate when valid state
is present in
AVX-512 components use could cause core turbo frequency drop. So
it's useful to expose AVX-512 usage elapsed time as a heuristic hint
for the user space job scheduler to cluster the AVX-512 using tasks
together.
Example:
$ cat /proc/pid/status | grep AVX512_elapsed_ms
AVX512_elapsed_ms: 1020
Added AVX512_elapsed_ms in /proc//status. Report it
in Documentation/filesystems/proc.txt
Signed-off-by: Aubrey Li
Cc: Peter Zijlstra
Cc: Andi Kleen
Cc: Tim Chen
Cc: Dave Hansen
Cc: Arjan van de Ven
---
Documentation/filesystems/proc.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Sun, 16 Dec 2018, Rich Felker wrote:
> So in theory it's possible that there's a cpu model with fancy new
> core instructions but no fpu. In this case, you would need the
> capability to emulate or execute-out-of-line these instructions. But I
> have no idea if such cpu models actually exist.
Hi Sergei:
>-Original Message-
>From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
>Sent: Friday, December 14, 2018 7:18 PM
>To: Zengtao (B) ; ba...@kernel.org
>Cc: liangshengjun ; Greg Kroah-Hartman
>; linux-...@vger.kernel.org;
>linux-kernel@vger.kernel.org
>Subject: Re:
On 2018.12.11 03:50 Rafael J. Wysocki wrote:
...[snip]...
> With this version of the TEO governor I'm observing slight, but consistent
> performance improvements in some different benchmarks on a few different
> systems with respect to menu
Same here.
> and the corresponding power draw
Support pvpanic as a pci device in guest kernel.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 82 --
1 file changed, 80 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index f84ed30..b8d8dba
Return 0 for empty body register function normally.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index 3150dc2..f84ed30 100644
--- a/drivers/misc/pvpanic.c
+++
Add PCI dependency for pvpanic in Kconfig.
Signed-off-by: Peng Hao
---
drivers/misc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index f417b06..5ff8ca4 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@
Hi Thinh:
>-Original Message-
>From: Thinh Nguyen [mailto:thinh.ngu...@synopsys.com]
>Sent: Saturday, December 15, 2018 5:43 AM
>To: Felipe Balbi ; Zengtao (B)
>
>Cc: liangshengjun ; Greg Kroah-Hartman
>; linux-...@vger.kernel.org;
>linux-kernel@vger.kernel.org; Thinh Nguyen
>
>Subject:
staging:iio:adc: fix codestyle
Signed-off-by: Sergey Efimochkin
---
drivers/staging/iio/adc/ad7280a.c | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
b/drivers/staging/iio/adc/ad7280a.c
index 58420dcb406d..52e12d1201b3
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from net/core/dev.c:148:
net/core/dev.c: In function 'napi_gro_complete':
net/core/dev.c:5364:26: error: 'inet_gro_complete' undeclared (first use in
this function); did
Hi, thanks for your reply.
On Thu, Dec 13, 2018 at 03:51:32PM +0100, Christophe Leroy wrote:
> Hi Again,
>
> Le 13/12/2018 à 13:16, Christophe Leroy a écrit :
[...]
> > Can you tell/provide the .config and dts used ?
I'm using wii.dts and almost the wii_defconfig from my tree (save-
defconfig
On Thu, Dec 13, 2018 at 02:26:03PM +0100, Borislav Petkov wrote:
>On Wed, Dec 12, 2018 at 04:03:12PM +0800, Baoquan He wrote:
>> Surely, using the old simple_strtoull() is fine too, we can take its
>> replacement into TODO list.
>
>Yes, that would be nice.
Oops, I thought you agree with what
Christoph Hellwig writes:
> FYI, given that we are one week before the expected 4.20 release
> date and I haven't found the bug plaging Christians setups I think
> we need to defer most of this to the next merge window.
OK, sorry I couldn't help. I tried powering up my pasemi board last week
HELLO,
FIRSTLY I APOLOGIZE BECAUSE YOU DO NOT KNOW ME PERSONALLY, BUT I GOT YOUR EMAIL
FROM A WEB JOURNAL AND I WAS WONDERING IF WE COULD WORK TOGETHER BECAUSE I HAVE
A TRANSACTION FOR YOU ?
On Sun, Dec 16, 2018 at 11:17:04PM +, Long Li wrote:
> From: Long Li
>
> The current code attempts to pin memory using the largest possible wsize
> based on the currect SMB credits. This doesn't cause kernel oops but this is
> not optimal as we may pin more pages then actually needed.
>
>
Hi Amir,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.20-rc7 next-20181214]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
> On Dec 16, 2018, at 2:00 AM, Borislav Petkov wrote:
>
> On Sun, Dec 16, 2018 at 02:33:39AM +, Nadav Amit wrote:
>> In general, I think that from the start it was clear that the motivation for
>> the patch-set is not just performance and also better code. For example, I
>> see no reason to
On Sun, Dec 16, 2018 at 10:59:19AM -0800, Andy Lutomirski wrote:
> On Sun, Dec 16, 2018 at 10:13 AM Rich Felker wrote:
> >
> > On Sun, Dec 16, 2018 at 01:50:13PM +, Maciej W. Rozycki wrote:
> > > On Sat, 15 Dec 2018, Rich Felker wrote:
> > >
> > >
> > > It doesn't help that information about
Hi Hayashi-san
> > > > There's an ongoing thread between Morimoto-san and Tony Lindgren around
> > > > the graph card including this issue, there Morimoto-san proposed some
> > > > code which would let the reg property be optional. Device trees should
> > > > still be updated but that way we
Hi all,
So the little elves have been slowly working to get voice calls
working on droid 4 with the mainline kernel. And just in time for the
upcoming holidays, it might be possible to call friends and relatives.
I've pushed out an experimental branch containing serdev ts 27.010
UART
On Tue, Dec 04, 2018 at 02:01:07PM +0800, Shawn Guo wrote:
> Hi Kishon,
>
> On Tue, Dec 04, 2018 at 10:38:19AM +0530, Kishon Vijay Abraham I wrote:
> > Hi,
> >
> > On 27/11/18 3:37 PM, Shawn Guo wrote:
> > > It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which
> > > is usually
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/ipv6/ip6_output.c
between commit:
8203e2d844d3 ("net: clear skb->tstamp in forwarding paths")
from the net tree and commit:
f839a6c92504 ("net: Do not route unicast IP packets twice")
from the net-next tree.
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
between commit:
154e62abe9cd ("net/mlx5e: Properly initialize flow attributes for slow path
eswitch rule deletion")
from the net tree and commit:
e88afe759a49
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/crypto/chelsio/chtls/chtls_cm.c
between commit:
0c3a16be700e ("crypto/chelsio/chtls: send/recv window update")
from the net tree and commit:
02d805dc5fe3 ("cxgb4: use new fw interface to get the VIN and
Hi all,
Today's linux-next merge of the rdma tree got a conflict in:
include/linux/mlx5/mlx5_ifc.h
between commit:
663f146f2ecf ("net/mlx5: E-Switch, Fix fdb cap bits swap")
from the net tree and commit:
c74d90c11c05 ("net/mlx5: Fix offsets of ifc reserved fields")
from the rdma tree.
Well, that's more like it.
This is a *tiny* rc7, just how I like it. Maybe it's because everybody
is too busy prepping for the holidays, and maybe it's because we
simply are doing well. Regardless, it's been a quiet week, and I hope
the trend continues.
The patch looks pretty small too, although
On Sat, 2018-12-15 at 07:45 -0800, Guenter Roeck wrote:
> On 12/15/18 12:07 AM, Greg Kroah-Hartman wrote:
> > On Fri, Dec 14, 2018 at 06:10:29PM -0800, Guenter Roeck wrote:
> > > On 12/14/18 3:59 AM, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 4.4.168
On Sat, Oct 20, 2018 at 2:06 PM Hou Tao wrote:
>
> Now MTD emulated by UBI volumn doesn't allocate wbuf_verify in
> jffs2_ubivol_setup(), because UBI can do the verifcation itself,
> so when CONFIG_JFFS2_FS_WBUF_VERIFY is enabled and a MTD device
> emulated by UBI volumn is used, a Oops will
Hi Zhang,
Today's linux-next merge of the thermal tree got a conflict in:
drivers/thermal/Kconfig
between commit:
17815cc6622c ("treewide: surround Kconfig file paths with double quotes")
from the kbuild tree and commit:
3e8c4d31f8ed ("drivers: thermal: Move various drivers for intel
On 2018/12/16 10:50, Dmitry V. Levin wrote:
> According to the documentation in include/uapi/asm-generic/ioctl.h,
> _IOW means userspace is writing and kernel is reading, and
> _IOR means userspace is reading and kernel is writing.
>
> In case of these two ioctls, kernel is writing and userspace
Hi all,
Commit
5a0cb2ffce06 ("perf ordered_events: Add first_time() method")
is missing a Signed-off-by from its author.
Commits
a1dcb76e592a ("perf top: Move perf_top__reset_sample_counters() to after
counts display")
ffec48b73449 ("perf top: Display slow reader warning when droping
On 12/15/2018 04:55 AM, Christoph Hellwig wrote:
> The mail seems to be so oddly encoded so that git-am fails on it. Can
> you resend as plain text?
Hmmm... not sure what happened with that, but yeah, looking at the message
source shows something strange went on. Let me take a look and I'll try
.. along with the PRCI patches which are under review.
Will repost these such that the files that depend on the new clock
headers are at the end of this series. Then we can send those last two
patches after the clock merge in the merge window, assuming the PRCI
patches make it.
- Paul
On
Hi David,
niedz., 16 gru 2018 o 21:41 David Miller napisał(a):
>
> From: Marcin Wojtas
> Date: Tue, 11 Dec 2018 13:56:49 +0100
>
> > Recent changes in the mvneta driver reworked allocation
> > and handling of the ingress buffers to use entire pages.
> > Apart from that in SW BM scenario the HW
Hi all,
After merging the nfs-anna tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
/home/sfr/next/next/fs/nfs/nfsroot.c: In function 'root_nfs_data':
/home/sfr/next/next/fs/nfs/nfsroot.c:264:5: error: implicit declaration of
function 'fmtcheck'; did you mean
From: Long Li
The current code attempts to pin memory using the largest possible wsize
based on the currect SMB credits. This doesn't cause kernel oops but this is
not optimal as we may pin more pages then actually needed.
Fix this by only pinning what are needed for doing this write I/O.
The FAT32 File System Specification[1] states that:
If DIR_Name[0] == 0x00, then the directory entry is free, and there
are no allocated directory entries after this one.
The special 0 value, indicates to FAT file system driver code that
the rest of the entries in this directory
Convert all fallthrough comments to say "fall through", as well as
modify their placement to the point where the "break" would normally
be.
Cc: Bjorn Helgaas
Cc: Fabio Estevam
Cc: Chris Healy
Cc: Lucas Stach
Cc: Leonard Crestez
Cc: "A.s. Dong"
Cc: Richard Zhu
Cc: linux-...@nxp.com
Cc:
Lorenzo:
These are patches fixing things pointed out by Bjorn in [1] and [2] as
well as something I noticed while giving pci/next branch a try (#endif
placement). Hopefully this is at least somewhat helpful.
Thanks,
Andrey Smirnov
[1] lkml.kernel.org/r/20181214203828.gd20...@google.com
[2]
Fixup Kconfig, which lost SOC_IMX7D during merge as well as move
"endif" to its original placement to only imx6q_pcie_abort_handler()
when building for AArch64
Cc: Bjorn Helgaas
Cc: Fabio Estevam
Cc: Chris Healy
Cc: Lucas Stach
Cc: Leonard Crestez
Cc: "A.s. Dong"
Cc: Richard Zhu
Cc:
In order to avoid having potentially ever growing list of variants
that don't support methods implemented in imx6_pcie_reset_phy() and
imx6_setup_phy_mpll(), change logical checks in the to check for SoC's
that _do_ support what they implement. While at it, share the code via
a small helper
clcsock can be released while kernel_accept() references it in TCP
listen worker. Also, clcsock needs to wake up before released if TCP
fallback is used and the clcsock is blocked by accept. Add a lock to
safely release clcsock and call kernel_sock_shutdown() to wake up
clcsock from accept in
On Sun, Dec 16, 2018 at 01:43:54PM -0800, Amir Mahdi Ghorbanian wrote:
> Replaced udelay() by the preferred usleep_range() function.
>
> Signed-off-by: Amir Mahdi Ghorbanian
Nack, usleep_range isn't for atomic contexts like interrupt handlers.
> ---
> drivers/staging/nvec/nvec.c | 4 ++--
> 1
Hi Guenter,
After merging the hwmon-staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/hwmon/Kconfig:1298:warning: ignoring unsupported character '/'
drivers/hwmon/Kconfig:1299: syntax error
drivers/hwmon/Kconfig:1298:warning: ignoring unsupported character
From: Long Li
When pinning memory failed, we should return the correct error code and
rewind the SMB credits.
Reported-by: Murphy Zhou
Signed-off-by: Long Li
Cc: sta...@vger.kernel.org
Cc: Murphy Zhou
---
fs/cifs/file.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff
Hi,
On Fri, Dec 14, 2018 at 04:12:14PM +0100, Paweł Chmiel wrote:
> Document new optional voltage regulators, which can be used
> to power down/up touchscreen.
>
> Signed-off-by: Paweł Chmiel
> Reviewed-by: Rob Herring
Reviewed-by: Sebastian Reichel
-- Sebastian
> ---
> Changes from v1:
>
Hi Ezequiel,
On Sun, Dec 16, 2018 at 07:28:22PM -0300, Ezequiel Garcia wrote:
> On Sun, 16 Dec 2018 at 19:24, Paul Burton wrote:
> > This helps, but it only addresses one part of one of the 4 reasons I
> > listed as motivation for my revert. For example serial8250_do_shutdown()
> > also clearly
On Sun, 2018-12-16 at 13:43 -0800, Amir Mahdi Ghorbanian wrote:
> Replaced udelay() by the preferred usleep_range() function.
[]
> diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
[]
> @@ -626,7 +626,7 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
>
On Sun, 16 Dec 2018 at 19:24, Paul Burton wrote:
>
> Hi Ezequiel,
>
> On Sun, Dec 16, 2018 at 06:52:53PM -0300, Ezequiel Garcia wrote:
> > diff --git a/drivers/tty/serial/8250/8250_port.c
> > b/drivers/tty/serial/8250/8250_port.c
> > index c39482b96111..fac19cbc51d1 100644
> > ---
Hi Marek,
On Sun, Dec 16, 2018 at 11:01:18PM +0100, Marek Vasut wrote:
> >>> I did suggest an alternative approach which would rename
> >>> serial8250_clear_fifos() and split it into 2 variants - one that
> >>> disables FIFOs & one that does not, then use the latter in
> >>> __do_stop_tx_rs485():
Hi Ezequiel,
On Sun, Dec 16, 2018 at 06:52:53PM -0300, Ezequiel Garcia wrote:
> diff --git a/drivers/tty/serial/8250/8250_port.c
> b/drivers/tty/serial/8250/8250_port.c
> index c39482b96111..fac19cbc51d1 100644
> --- a/drivers/tty/serial/8250/8250_port.c
> +++
On Sun, Dec 16, 2018 at 10:45:23PM +0100, Marek Vasut wrote:
> >> I am unable to test it on such a short notice as I'm currently ill, so I
> >> cannot tell if your change breaks the OMAP3/AM335x boards or not. Given
> >> that there are very few CI20 boards in use, I'd like to ask you for some
> >>
On 12/16/2018 10:52 PM, Ezequiel Garcia wrote:
> On Sun, 16 Dec 2018 at 18:45, Marek Vasut wrote:
> [skips discussion]
>>
>>> Ultimately it's Greg's decision but it sounds like you're asking me to
>>> say it's OK to break the JZ4780 in a stable kernel with a patch that I
>>> think would be risky
On Sun, 2018-12-09 at 21:57 +, Nadav Amit wrote:
> This patch causes some sparse warnings. If you want to wait, I’ll send a
> patch to fix it. (No expected functional impact though).
Thanks for the note. I don't think that's enough of a reason to delay
this fix.
Ben.
>
> > On Dec 9, 2018,
On 12/16/2018 10:39 PM, Paul Burton wrote:
> Hi Marek,
Hi,
> On Sun, Dec 16, 2018 at 10:08:48PM +0100, Marek Vasut wrote:
>>> I did suggest an alternative approach which would rename
>>> serial8250_clear_fifos() and split it into 2 variants - one that
>>> disables FIFOs & one that does not, then
On Fri, Dec 14, 2018 at 04:43:21PM +0100, Jan Kara wrote:
> Hi!
>
> On Thu 13-12-18 08:46:41, Dave Chinner wrote:
> > On Wed, Dec 12, 2018 at 10:03:20AM -0500, Jerome Glisse wrote:
> > > On Mon, Dec 10, 2018 at 11:28:46AM +0100, Jan Kara wrote:
> > > > On Fri 07-12-18 21:24:46, Jerome Glisse
On Sun, Dec 16, 2018 at 02:55:05PM -0500, Konstantin Ryabitsev wrote:
> On Sun, Dec 16, 2018 at 09:21:35AM -1000, Joey Pabalinas wrote:
> > That was my first attempt, but the ducumentation for the public-inbox
> > format is sort of terrible,
>
> I'm surprised you think so, because it's basically
On Sun, 16 Dec 2018 at 18:45, Marek Vasut wrote:
[skips discussion]
>
> > Ultimately it's Greg's decision but it sounds like you're asking me to
> > say it's OK to break the JZ4780 in a stable kernel with a patch that I
> > think would be risky anyway, and I won't do that.
>
> I am saying this
On 12/16/2018 10:31 PM, Paul Burton wrote:
> Hi Marek,
Hi,
> On Sun, Dec 16, 2018 at 09:32:19PM +0100, Marek Vasut wrote:
>> I am unable to test it on such a short notice as I'm currently ill, so I
>> cannot tell if your change breaks the OMAP3/AM335x boards or not. Given
>> that there are very
[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On
29/12/2017 (Fri 13:18) Paul Gortmaker wrote:
> [Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.]
> On 29/12/2017 (Fri 10:47) Josh Poimboeuf wrote:
>
> > This seems to be related to a
Replaced udelay() by the preferred usleep_range() function.
Signed-off-by: Amir Mahdi Ghorbanian
---
drivers/staging/nvec/nvec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
index 08027a3..6f35f92 100644
---
On Mon, 2018-12-10 at 00:24 +0100, Vitaly Kuznetsov wrote:
> Ben Hutchings writes:
>
> > 3.16.62-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Vitaly Kuznetsov
> >
> > commit 2d408c0d4574b01b9ed45e02516888bf925e11a9 upstream.
Hi Marek,
On Sun, Dec 16, 2018 at 10:08:48PM +0100, Marek Vasut wrote:
> > I did suggest an alternative approach which would rename
> > serial8250_clear_fifos() and split it into 2 variants - one that
> > disables FIFOs & one that does not, then use the latter in
> > __do_stop_tx_rs485():
> >
>
On Mon, 2018-12-10 at 12:36 -0800, Guenter Roeck wrote:
> On Mon, Dec 10, 2018 at 07:06:41PM +, Ben Hutchings wrote:
> > On Mon, 2018-12-10 at 08:54 -0800, Guenter Roeck wrote:
> > > On Sun, Dec 09, 2018 at 09:50:32PM +, Ben Hutchings wrote:
> > > > This is the start of the stable review
Hi Marek,
On Sun, Dec 16, 2018 at 09:32:19PM +0100, Marek Vasut wrote:
> I am unable to test it on such a short notice as I'm currently ill, so I
> cannot tell if your change breaks the OMAP3/AM335x boards or not. Given
> that there are very few CI20 boards in use, I'd like to ask you for some
>
:
https://github.com/0day-ci/linux/commits/Peng-Hao/misc-pvpanic-return-0-for-empty-body-register-function/20181216-140504
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master
On 12/16/2018 09:10 PM, Paul Burton wrote:
> Commit f6aa5beb45be ("serial: 8250: Fix clearing FIFOs in RS485 mode
> again") makes a change to FIFO clearing code which its commit message
> suggests was intended to be specific to use with RS485 mode, however:
>
> 1) The change made does not just
From: Marcin Wojtas
Date: Tue, 11 Dec 2018 13:56:49 +0100
> Recent changes in the mvneta driver reworked allocation
> and handling of the ingress buffers to use entire pages.
> Apart from that in SW BM scenario the HW must be informed
> via PRXDQS about the biggest possible incoming buffer
>
On 12/16/2018 09:10 PM, Paul Burton wrote:
> Commit f6aa5beb45be ("serial: 8250: Fix clearing FIFOs in RS485 mode
> again") makes a change to FIFO clearing code which its commit message
> suggests was intended to be specific to use with RS485 mode, however:
>
> 1) The change made does not just
On Mon, Dec 17, 2018 at 03:22:39AM +0800, kbuild test robot wrote:
> Hi Chao,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.20-rc6 next-20181214]
> [if your patch is applied to the wrong git tree, please drop us
Hi Sowjanya,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on ulf.hansson-mmc/next]
[also build test ERROR on v4.20-rc6 next-20181214]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Commit f6aa5beb45be ("serial: 8250: Fix clearing FIFOs in RS485 mode
again") makes a change to FIFO clearing code which its commit message
suggests was intended to be specific to use with RS485 mode, however:
1) The change made does not just affect __do_stop_tx_rs485(), it also
affects other
From: Peng Li
Date: Sat, 15 Dec 2018 11:53:19 +0800
> This patchset introduces some code improvements and fixes
> for the identified problems in the HNS driver.
>
> Every patch is independent.
Series applied, thank you.
On Sun, Dec 16, 2018 at 2:19 PM David Miller wrote:
>
> From: Paolo Abeni
> Date: Sun, 16 Dec 2018 19:55:40 +0100
>
> > Again, I messed it! I'm really sorry to waste everybody's time.
> > I was unable to give proper coverage with different configs. I tested
> > vs.:
> >
> > CONFIG_IPV6=ymn
> >
Sure. Published v3 with lower case chars. Fixed in both relevant patches.
On Sat, Dec 15, 2018 at 9:10 PM OGAWA Hirofumi
wrote:
>
> Carmeli Tamir writes:
>
> > This patch introduces 3 new inline functions - IS_FAT12, IS_FAT16 and
> > IS_FAT32, and replaces every occurrence in the code in which
This patch introduces 3 new inline functions - is_fat12, is_fat16 and
is_fat32, and replaces every occurrence in the code in which the FS
variant (whether this is FAT12, FAT16 or FAT32) was previously checked
using msdos_sb_info->fat_bits.
Signed-off-by: Carmeli Tamir
---
fs/fat/cache.c | 2
Along the FAT FS code, the FAT variant (whether this is FAT12, FAT16 or FAT32)
is
determined by checking the fat_bits field of struct msdos_sb_info.
This is somewhat error prone as it forces the usage of magics (12, 16, 32)
multiple times in the code.
This series replaces the places in which the
MAX_FAT is useless in msdos_fs.h, since it uses the MSDOS_SB function
that is defined in fat.h. So really, this macro can be only called
from code that already includes fat.h.
Hence, this patch moves it to fat.h, right after MSDOS_SB is defined.
I also changed it to an inline function in order to
The comment edited in this patch was the only reference to the
FAT_FIRST_ENT macro, which is not used anymore. Moreover, the
commented line of code does not compile with the current code.
Since the FAT_FIRST_ENT macro checks the FAT variant in a way that the
patch series changes, I removed it,
On Sat, Dec 15, 2018 at 11:43:08AM -0800, David Miller wrote:
> From: Jason Wang
> Date: Fri, 14 Dec 2018 12:29:54 +0800
>
> >
> > On 2018/12/14 上午4:12, Michael S. Tsirkin wrote:
> >> On Thu, Dec 13, 2018 at 06:10:19PM +0800, Jason Wang wrote:
> >>> Hi:
> >>>
> >>> This series tries to access
On Sun, Dec 16, 2018 at 09:21:35AM -1000, Joey Pabalinas wrote:
> That was my first attempt, but the ducumentation for the public-inbox
> format is sort of terrible,
I'm surprised you think so, because it's basically a simple file called
"m" that is updated on each commit and contains the body
On Sun, Dec 16, 2018 at 02:46:49PM -0500, Konstantin Ryabitsev wrote:
> On Sun, Dec 16, 2018 at 09:06:39AM -1000, Joey Pabalinas wrote:
> > I spent a lot of time trying to find an LKML archive in Maildir format
> > that I could use for local searches with nutmuch or something, but all
> > the
On Thu, Dec 13, 2018 at 08:23:55PM +, Fabrizio Castro wrote:
> RZ/G2E USB 3.0 implementation is like the one found on R-Car E3,
> therefore add the same quirk.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Fri, Dec 14, 2018 at 10:25 PM David Miller wrote:
>
> From: Arnd Bergmann
> Date: Mon, 10 Dec 2018 22:17:20 +0100
>
> > @@ -635,8 +636,9 @@ static int threadfunc(void *data)
> > int i, step, err = 0, insert_retries = 0;
> > struct thread_data *tdata = data;
> >
> > - up(_sem);
On Thu, Dec 13, 2018 at 08:22:18PM +, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) SoC bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
This is one of only two files that initialize a semaphore to a negative
value. We don't really need the two semaphores here at all, but can do
the same thing in more conventional and more effient way, by using a
single waitqueue and an atomic thread counter.
This gets us a little bit closer to
On Sun, Dec 16, 2018 at 09:06:39AM -1000, Joey Pabalinas wrote:
> I spent a lot of time trying to find an LKML archive in Maildir format
> that I could use for local searches with nutmuch or something, but all
> the links I was able to find were all dead.
>
> I ended up just compiling one myself
On Sun, 16 Dec 2018, Andy Lutomirski wrote:
> > I think it suffices to emulate what compilers generate in delay slots,
> > which should be fairly minimal and stable. At the very least we could
> > enumerate everything GCC and LLVM already emit there, and get them to
> > upstream a policy of not
On Fri, Dec 14, 2018 at 1:53 PM Waiman Long wrote:
>
> This patchset addresses 2 issues found in the dentry code and adds a
> new nr_dentry_negative per-cpu counter to track the total number of
> negative dentries in all the LRU lists.
The series looks sane to me. I'm assuming I'll get it either
On Sat, Dec 15, 2018 at 11:46:11AM -0800, David Miller wrote:
> From: Pavel Tikhomirov
> Date: Thu, 13 Dec 2018 17:53:50 +0300
>
> > We've failed to copy and process vhost_iotlb_msg so let userspace at
> > least know about it. For instance before these patch the code below runs
> > without any
On Tue, Dec 11, 2018 at 08:18:08AM -0600, Bjorn Helgaas wrote:
> Hi Michael,
>
> Please run "git log --oneline drivers/pci/setup-bus.c" and follow
> the usual style.
>
> On Mon, Dec 10, 2018 at 09:18:40PM -0500, Michael S. Tsirkin wrote:
> > commit 1f82de10d6 ("PCI/x86: don't assume prefetchable
101 - 200 of 348 matches
Mail list logo
