Introduce quirks and module parameters. 3 quirks are added:
1. Fixes reporting brightness keys twice since it's already handled by
acpi-video.
2. Some models need a short delay when setting battery thresholds to
prevent a race condition when two processes read/write. (will be used later)
3.
Move from WMI driver to platform driver. This move is necessary since
the driver is no longer a hotkeys driver only. Platform driver makes it
easier for users to access sysfs attributes under (i.e.
/sys/devices/platform/huawei-wmi) compared to wmi driver.
Use WMI device UID, AMW0 has a UID of
Changes in v2:
* Use battery charge control API.
This patch series introduce changes to huawei-wmi driver that includes:
* Move to platform driver
* Implement driver quirks and parameters
* Implement WMI management interface
* Add micmute LED support through WMI
* Add battery charging protection
Christoph,
> On Wed, Sep 18, 2019 at 11:08:07AM -0600, Keith Busch wrote:
>> And yes, that bouncing is really nasty, but it's really only needed for
>> PRP, so maybe let's just not ignore that transfer mode and support
>> extended metadata iff the controller supports SGLs. We just need a
>>
The copyright notices as I got them said "GPLv2 or later", which I
screwed up when putting in the SPDX tags. Fix them to match the
license I got the code under.
Signed-off-by: Valdis Kletnieks
---
diff --git a/drivers/staging/exfat/Makefile b/drivers/staging/exfat/Makefile
index
Add usage message on how to exit the virtualenv after documentation
work is done.
Signed-off-by: Shuah Khan
---
Changes since v1:
Changed the message based on Mauro's review comments.
scripts/sphinx-pre-install | 8
1 file changed, 8 insertions(+)
diff --git
On Wed, Sep 18, 2019 at 03:08:41PM +0800, Yunfeng Ye wrote:
>
>
>On 2019/9/18 14:51, Wei Yang wrote:
>> On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote:
>>> Currently, when memblock_find_in_range_node() fail on the exact node, it
>>> will use %NUMA_NO_NODE to find memblock from other
On Wed, Sep 18, 2019 at 5:22 PM Linus Torvalds
wrote:
>
> Commit messages need to explain the commit. The same is even more true
> of merges!
Side note: that wasn't actually the only problem with that merge.
The other problem was that neither of the merge bases made any sense
what-so-ever.
On Mon, Sep 16, 2019 at 4:09 AM David Howells wrote:
>
> Here's a set of patches for AFS. The first three are trivial, deleting
> unused symbols and rolling out a wrapper function.
Pulled.
However, I was close to unpulling it again. It has a merge commit with
this merge message:
Merge
The pull request you sent on Sun, 15 Sep 2019 21:42:58 -0700:
> git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fscrypt-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/734d1ed83e1f9b7bafb650033fb87c657858cf5b
Thank you!
--
Deet-doot-dot, I am a
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3 next-20190918]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base
Before creating a new devfreq device devfreq_add_device() checks
if there is already a devfreq dev associated with the requesting
device (parent). If that's the case the function rejects to create
another devfreq dev for that parent and logs an error. The error
message is very unspecific, make it
Em Fri, Jul 19, 2019 at 10:58:37AM +0530, Ravi Bangoria escreveu:
>
> LGTM. For the series,
>
> Reviewed-By: Ravi Bangoria
Thanks, applied.
- Arnaldo
On Wed, Sep 18, 2019 at 2:17 PM Ahmed S. Darwish wrote:
>
> Since Linux v3.17, getrandom(2) has been created as a new and more
> secure interface for pseudorandom data requests. It attempted to
> solve three problems, as compared to /dev/urandom:
I don't think your patch is really _wrong_, but
On Tue, Sep 17, 2019 at 9:23 PM Nathan Chancellor
wrote:
>
> After commit 62974fc389b3 ("libnvdimm: Enable unit test infrastructure
> compile checks"), clang warns:
>
> In file included from
> ../drivers/nvdimm/../../tools/testing/nvdimm/test/iomap.c:15:
>
Em Tue, Sep 17, 2019 at 01:12:46PM +0530, Mukesh Ojha escreveu:
>
> On 9/11/2019 8:51 PM, Colin King wrote:
> > From: Colin Ian King
> >
> > There is a spelling mistake in a TEST_ASSERT_VAL message. Fix it.
> >
> > Signed-off-by: Colin Ian King
>
> Reviewed-by: Mukesh Ojha
Thanks, applied.
Em Wed, Sep 11, 2019 at 09:44:20AM +0530, Ravi Bangoria escreveu:
>
>
> On 9/4/19 3:17 PM, Srikar Dronamraju wrote:
> > There are some problems in perf stat when using a combination of repeat and
> > interval options. This series tries to fix them.
>
> For the series:
>
> Tested-by: Ravi
Existing intel_cht_int33fe ACPI pseudo-device driver assumes that
hardware has Type-C connector and register related devices described as
I2C connections in the _CRS resource.
There is at least one hardware (Lenovo Yoga Book YB1-91L/F) with Micro-B
USB connector exists. It has INT33FE device in
Patch to support INT33FE ACPI pseudo-device on hardware with USB Micro-B
connector.
v4:
- Micro-B variant: Don't print error to the kernel log if i2c_acpi_new_device()
has returned -EPROBE_DEFER.
v3:
- Rename TypeB variant to Micro-B (we have only one such device for now and it
has Micro-B
On Wed, 18 Sep 2019 18:44:36 +0200
Greg Kurz wrote:
> On Wed, 11 Sep 2019 21:52:35 +0200
> Thomas Huth wrote:
>
> > After the kfree()s haven been removed in the previous
> > commit 9798f4ea71ea ("fix rollback when kvmppc_xive_create fails"),
> > the code can be simplified even more to simply
Define a weak function in COND_SYSCALL instead of a weak alias to
sys_ni_syscall, which has an incompatible type. This fixes indirect
call mismatches with Control-Flow Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
---
arch/x86/include/asm/syscall_wrapper.h | 21 -
1
Use the correct function type for sys_ni_syscall in system
call tables to fix indirect call mismatches with Control-Flow
Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
---
arch/x86/entry/syscall_32.c| 8 +++-
arch/x86/entry/syscall_64.c| 14 ++
Although a syscall defined using SYSCALL_DEFINE0 doesn't accept
parameters, use the correct function type to avoid type mismatches
with Control-Flow Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
Acked-by: Andy Lutomirski
---
arch/x86/include/asm/syscall_wrapper.h | 23
Use COMPAT_SYSCALL_DEFINE0 to define (rt_)sigreturn syscalls to
replace sys32_sigreturn and sys32_rt_sigreturn. This fixes indirect
call mismatches with Control-Flow Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
---
arch/x86/entry/syscalls/syscall_32.tbl | 4 ++--
From: Andy Lutomirski
x86 has special handling for COMPAT_SYSCALL_DEFINEx, but there was
no override for COMPAT_SYSCALL_DEFINE0. Wire it up so that we can
use it for rt_sigreturn.
Signed-off-by: Andy Lutomirski
Signed-off-by: Sami Tolvanen
---
arch/x86/include/asm/syscall_wrapper.h | 32
This patch set changes x86 syscall wrappers and related functions to
use function types that match sys_call_ptr_t. This fixes indirect call
mismatches with Control-Flow Integrity (CFI) checking.
Changes since v1:
- Use SYSCALL_DEFINE0 for __x64_sys_ni_syscall.
- Include Andy's
On Thu, Sep 19, 2019 at 05:11:28AM +0800, Gao Xiang wrote:
> Hi Christoph,
>
> On Wed, Sep 18, 2019 at 11:24:12AM -0700, Christoph Hellwig wrote:
> > Just as a note of record: I don't think either file system move
> > is a good idea. erofs still needs a lot of work, especially in
> >
On 2019-09-18 13:13, Rob Herring wrote:
On Wed, Sep 18, 2019 at 1:47 PM Raghavendra Rao Ananta
wrote:
On some embedded systems, the '/memory' dt-property gets updated
by the bootloader (for example, the DDR configuration) and then
gets passed onto the kernel. The device drivers may have to
Welp, looks like I didn't test debug configs properly.
Allow me 1-2 days to work on fixing it for v2.
Thanks in advance.
On Thu, Sep 19, 2019 at 6:31 AM kbuild test robot wrote:
>
> Hi Park,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
>
Thanks Rob and Alyssa.
+Douglas Anderson +Dominik Behr who may be interested (if not already aware)
On Sat, Sep 14, 2019 at 2:17 AM Alyssa Rosenzweig
wrote:
>
> > > > The binding we use with out-of-tree Mali drivers includes more
> > > > clocks, I assume this would be required eventually if we
On Thu, Sep 19, 2019 at 4:41 AM Tim Chen wrote:
>
> On 9/17/19 6:33 PM, Aubrey Li wrote:
> > On Sun, Sep 15, 2019 at 10:14 PM Aaron Lu
> > wrote:
>
> >>
> >> And I have pushed Tim's branch to:
> >> https://github.com/aaronlu/linux coresched-v3-v5.1.5-test-tim
> >>
> >> Mine:
> >>
On Wed, Sep 18, 2019 at 01:26:39PM -0700, Linus Torvalds wrote:
> Of course, even then people will say "I don't trust the platform". But
> at some point you just say "you have trust issues" and move on.
It's where our extreme configurability can hurt. Sometimes we'd rather
avoid providing some of
On Wed, Sep 18, 2019 at 11:33:32PM +0300, Yauhen Kharuzhy wrote:
> On Wed, Sep 18, 2019 at 10:12:43PM +0200, Hans de Goede wrote:
> > Hi,
> >
> > On 18-09-2019 13:42, Yauhen Kharuzhy wrote:
> > > On Wed, Sep 18, 2019 at 11:20:21AM +0200, Hans de Goede wrote:
> > > > Hi,
> > > >
> > > > On
Hi all,
Changes since 20190917:
The sound-current tree gained a build failure for which I reverted a
commit.
The driver-core tree gained a merge failure which I fixed up.
Non-merge commits (relative to Linus' tree): 8551
7914 files changed, 621805 insertions(+), 224850 deletions(-)
On Thu, Sep 19, 2019 at 12:00 AM wrote:
>
> > -Original Message-
> > From: Rafael J. Wysocki
> > Sent: Wednesday, September 18, 2019 4:57 PM
> > To: Limonciello, Mario
> > Cc: kbu...@kernel.org; ax...@fb.com; h...@lst.de; s...@grimberg.me; linux-
> > n...@lists.infradead.org;
> -Original Message-
> From: Rafael J. Wysocki
> Sent: Wednesday, September 18, 2019 4:57 PM
> To: Limonciello, Mario
> Cc: kbu...@kernel.org; ax...@fb.com; h...@lst.de; s...@grimberg.me; linux-
> n...@lists.infradead.org; linux-kernel@vger.kernel.org; Hong, Ryan; Wang,
> Crag;
-Chen/mfd-mt6360-add-pmic-mt6360-driver/20190918-181850
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 7.4.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
On Wednesday, September 18, 2019 11:43:28 PM CEST mario.limoncie...@dell.com
wrote:
> > -Original Message-
> > From: Rafael J. Wysocki
> > Sent: Wednesday, September 18, 2019 4:31 PM
> > To: Limonciello, Mario
> > Cc: Keith Busch; Jens Axboe; Christoph Hellwig; Sagi Grimberg; linux-
> >
On Wed, Sep 18, 2019 at 12:03:17PM -0700, Linus Torvalds wrote:
> On Wed, Sep 18, 2019 at 11:53 AM Greg KH wrote:
> > On Wed, Sep 18, 2019 at 06:09:52PM +0100, Mark Brown wrote:
> > > After merging the driver-core tree, today's linux-next build
> > > for arm64 allmodconfig failed like this:
> >
On Tue, Sep 17, 2019 at 09:21:49PM -0700, Nathan Chancellor wrote:
> After commit 62974fc389b3 ("libnvdimm: Enable unit test infrastructure
> compile checks"), clang warns:
>
> In file included from
> ../drivers/nvdimm/../../tools/testing/nvdimm/test/iomap.c:15:
>
Assuming that the Kbuild bot doesn't get mad about the format string
now, LGTM. Thanks Daniel!
Reviewed-by: Nick Crews
On Wed, Sep 18, 2019 at 2:43 PM Daniel Campello wrote:
>
> This change introduces a new debugfs file 'test_event' that when written
> to causes the EC to generate a test
> -Original Message-
> From: Rafael J. Wysocki
> Sent: Wednesday, September 18, 2019 4:31 PM
> To: Limonciello, Mario
> Cc: Keith Busch; Jens Axboe; Christoph Hellwig; Sagi Grimberg; linux-
> n...@lists.infradead.org; LKML; Hong, Ryan; Wang, Crag; s...@google.com;
> Dominguez, Jared;
On Wed, Sep 18, 2019 at 4:05 AM Ivan Khoronzhuk
wrote:
>
> On Tue, Sep 17, 2019 at 10:19:22PM -0700, Andrii Nakryiko wrote:
> >On Mon, Sep 16, 2019 at 4:00 AM Ivan Khoronzhuk
> > wrote:
> >>
> >> In case of LDFLAGS and EXTRA_CC/CXX flags there is no way to pass them
> >> correctly to build
On Wednesday, September 18, 2019 11:31:19 PM CEST Rafael J. Wysocki wrote:
> On Thursday, September 12, 2019 1:42:33 AM CEST Mario Limonciello wrote:
> > The action of saving the PCI state will cause numerous PCI configuration
> > space reads which depending upon the vendor implementation may
Hi Park,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3 next-20190917]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Park,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3 next-20190917]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Thursday, September 12, 2019 1:42:33 AM CEST Mario Limonciello wrote:
> The action of saving the PCI state will cause numerous PCI configuration
> space reads which depending upon the vendor implementation may cause
> the drive to exit the deepest NVMe state.
>
> In these cases ASPM will
On Wed, Sep 18, 2019 at 3:35 AM Ivan Khoronzhuk
wrote:
>
> On Tue, Sep 17, 2019 at 04:42:07PM -0700, Andrii Nakryiko wrote:
> >On Mon, Sep 16, 2019 at 3:59 AM Ivan Khoronzhuk
> > wrote:
> >>
> >> While compile natively, the hosts cflags and ldflags are equal to ones
> >> used from HOSTCFLAGS and
Hi Dan,
I think Greg's guidance clarified everything nicely -
we will avoid sub-dirs in favour of prefixes
to *intensity and *max_intensity.
Before you will send an update I have some improvement
ideas regarding the remnants after the previous approach,
where single color intensity update
On Wednesday, September 18, 2019 6:52:31 PM CEST mario.limoncie...@dell.com
wrote:
> > -Original Message-
> > From: Rafael J. Wysocki
> > Sent: Tuesday, September 17, 2019 4:36 PM
> > To: Keith Busch
> > Cc: Limonciello, Mario; Jens Axboe; Christoph Hellwig; Sagi Grimberg; linux-
> >
On 9/4/19 6:44 PM, Julien Desfossez wrote:
> +
> +static void coresched_idle_worker_fini(struct rq *rq)
> +{
> + if (rq->core_idle_task) {
> + kthread_stop(rq->core_idle_task);
> + rq->core_idle_task = NULL;
> + }
During testing, I have found access of
On 9/18/19 1:04 PM, Halil Pasic wrote:
On Fri, 13 Sep 2019 17:26:52 -0400
Tony Krowiak wrote:
+static void vfio_ap_mdev_get_crycb_matrix(struct ap_matrix_mdev *matrix_mdev)
+{
+ unsigned long apid, apqi;
+ unsigned long masksz = BITS_TO_LONGS(AP_DEVICES) *
+
On Wed, Sep 18, 2019 at 3:12 AM Ivan Khoronzhuk
wrote:
>
> On Tue, Sep 17, 2019 at 04:19:40PM -0700, Andrii Nakryiko wrote:
> >On Mon, Sep 16, 2019 at 3:58 AM Ivan Khoronzhuk
> > wrote:
> >>
> >> The makefile.target is added only and will be used in
> >
> >typo: Makefile
> >
> >>
From: Ira Weiny
Signed-off-by: Ira Weiny
---
include/linux/nd.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/nd.h b/include/linux/nd.h
index f778f962d1b6..55c735997805 100644
--- a/include/linux/nd.h
+++ b/include/linux/nd.h
@@ -147,7 +147,7 @@ static
On Wed, Sep 18, 2019 at 04:06:38PM -0400, vincent.cheng...@renesas.com wrote:
> From: Vincent Cheng
>
> The IDT ClockMatrix (TM) family includes integrated devices that provide
> eight PLL channels. Each PLL channel can be independently configured as a
> frequency synthesizer, jitter
Since Linux v3.17, getrandom(2) has been created as a new and more
secure interface for pseudorandom data requests. It attempted to
solve three problems, as compared to /dev/urandom:
1. the need to access filesystem paths, which can fail, e.g. under a
chroot
2. the need to open a file
Hi,
This is an RFC, and it obviously needs much more testing beside the
"it boots" smoke test I've just did.
Interestingly though, on my current system, the triggered WARN()
**reliably** makes the system get un-stuck... I know this is a very
crude heuristic, but I would personally prefer it to
On 9/10/19 7:27 AM, Julien Desfossez wrote:
> On 29-Aug-2019 04:38:21 PM, Peter Zijlstra wrote:
>> On Thu, Aug 29, 2019 at 10:30:51AM -0400, Phil Auld wrote:
>>> I think, though, that you were basically agreeing with me that the current
>>> core scheduler does not close the holes, or am I reading
Hi Christoph,
On Wed, Sep 18, 2019 at 11:24:12AM -0700, Christoph Hellwig wrote:
> Just as a note of record: I don't think either file system move
> is a good idea. erofs still needs a lot of work, especially in
> interacting with the mm code like abusing page->mapping.
I know what you mean,
Hi,
On 18-09-2019 17:27, Yauhen Kharuzhy wrote:
Existing intel_cht_int33fe ACPI pseudo-device driver assumes that
hardware has Type-C connector and register related devices described as
I2C connections in the _CRS resource.
There is at least one hardware (Lenovo Yoga Book YB1-91L/F) with
On 9/18/19 5:33 AM, Eugeniu Rosca wrote:
Hi Shuah,
On Tue, Sep 17, 2019 at 08:40:22PM +0200, Eugeniu Rosca wrote:
From: "George G. Davis"
The newly added optional file argument does not validate if the
file is indeed a watchdog, e.g.:
./watchdog-test -f /dev/zero
Watchdog Ticking Away!
> On Sep 12, 2019, at 21:10, Andy Lutomirski wrote:
>
> I also think that, before this series can have my ack, it needs an actual gdb
> maintainer to chime in, publicly, and state that they have thought about and
> tested the ABI changes and that gdb still works on patched kernels with and
From: Randy Dunlap
Fix typos in drivers/ntb/hw/idt/Kconfig.
Use consistent spelling and capitalization.
Fixes: bf2a952d31d2 ("NTB: Add IDT 89HPESxNTx PCIe-switches support")
Signed-off-by: Randy Dunlap
Cc: Jon Mason
Cc: Dave Jiang
Cc: Allen Hubbe
Cc: Serge Semin
Cc:
On Wed, Sep 18, 2019 at 01:17:13PM -0500, Larry Finger wrote:
> The external module is vboxdrv, which is part of VirtualBox. The setting of
> pages to be executable appears to have been added in kernel 2.4.20.
>
> I am now testing with the former calls to set_pages_x() and set_pages_nx()
>
On 09/18/2019 08:07 PM, Greg KH wrote:
On Wed, Sep 18, 2019 at 12:03:17PM -0700, Linus Torvalds wrote:
On Wed, Sep 18, 2019 at 11:53 AM Greg KH wrote:
On Wed, Sep 18, 2019 at 06:09:52PM +0100, Mark Brown wrote:
After merging the driver-core tree, today's linux-next build
for arm64
On 9/18/19 12:55 PM, Arnd Bergmann wrote:
The ionic driver started using dymamic_hex_dump(), but
that is not always defined:
drivers/net/ethernet/pensando/ionic/ionic_main.c:229:2: error: implicit
declaration of function 'dynamic_hex_dump'
[-Werror,-Wimplicit-function-declaration]
Add a
On Wed, Sep 18, 2019 at 08:50:10PM +0200, Greg KH wrote:
> > exfat is just a random old code drop from Samsung hastily picked up,
> > and also duplicating the fat16/32 functionality, and without
> > consultation of the developes of that who are trying to work through
> > their process of
On Thu, 19 Sep 2019 05:31:21 +0900, Ju Hyung Park said:
> We should probably ask Valdis on what happened there.
>
> Even the old exFAT v1.2.24 from Galaxy S7 is using "either version 2
> of the License, or (at your option) any later version".
> You can go check it yourself by searching "G930F"
On 9/18/19 12:57 PM, Arnd Bergmann wrote:
The debugfs function was apparently changed from returning an error code
to a void return, but the return code left in place, causing a warning
from clang:
drivers/net/ethernet/pensando/ionic/ionic_debugfs.c:60:37: error: expression
result unused
The pull request you sent on Mon, 16 Sep 2019 06:50:40 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
> tags/filelock-v5.4-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d013cc800a2a41b0496f99a11f3cff724cf65941
Thank you!
--
This change introduces a new debugfs file 'test_event' that when written
to causes the EC to generate a test event.
Signed-off-by: Daniel Campello
---
Changes for v2:
- Cleaned up and added comments.
- Renamed and updated function signature from write_to_mailbox to
send_ec_cmd.
Changes
On Wed, 18 Sep 2019 at 23:34, Navid Emamdoost wrote:
>
> In sja1105_static_config_upload, in two cases memory is leaked: when
> static_config_buf_prepare_for_upload fails and when sja1105_inhibit_tx
> fails. In both cases config_buf should be released.
>
> Fixes: 8aa9ebccae87 ("net: dsa:
On 9/17/19 6:33 PM, Aubrey Li wrote:
> On Sun, Sep 15, 2019 at 10:14 PM Aaron Lu wrote:
>>
>> And I have pushed Tim's branch to:
>> https://github.com/aaronlu/linux coresched-v3-v5.1.5-test-tim
>>
>> Mine:
>> https://github.com/aaronlu/linux coresched-v3-v5.1.5-test-core_vruntime
Aubrey,
Hi Arnd,
On 18/09/2019 20:59, Arnd Bergmann wrote:
> The css_task_iter interfaces are defined conditionally and
> cause build failures when used in other configurations:
>
> kernel/sched/core.c:1081:23: error: variable has incomplete type 'struct
> css_task_iter'
> kernel/sched/core.c:1084:2:
Hmm. This adds that NET_TC_SKB_EXT config thing, and makes it "default y".
Why?
It's also done in a crazy way:
+ depends on NET_CLS_ACT
+ default y if NET_CLS_ACT
yeah, that's some screwed-up thinking right there. First it depends on
another config variable, and then it defaults to
In sja1105_static_config_upload, in two cases memory is leaked: when
static_config_buf_prepare_for_upload fails and when sja1105_inhibit_tx
fails. In both cases config_buf should be released.
Fixes: 8aa9ebccae87 ("net: dsa: Introduce driver for NXP SJA1105 5-port
L2 switch")
Fixes: 1a4c69406cc1
On Wed, Sep 18, 2019 at 10:12:43PM +0200, Hans de Goede wrote:
> Hi,
>
> On 18-09-2019 13:42, Yauhen Kharuzhy wrote:
> > On Wed, Sep 18, 2019 at 11:20:21AM +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 17-09-2019 21:45, Yauhen Kharuzhy wrote:
> > > > Existing intel_cht_int33fe ACPI
On Thu, Sep 19, 2019 at 5:26 AM Greg KH wrote:
> That differs from the original exfat code, so something is odd here. I
> need some sort of clarification from Samsung as to when they changed the
> license in order to be able to relicense these files.
We should probably ask Valdis on what
On Wed, Sep 18, 2019 at 08:16:42AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Sep 17, 2019 at 06:03:53PM -0700, Gregory Nowak wrote:
> > On Tue, Sep 17, 2019 at 10:01:18AM +0200, Greg Kroah-Hartman wrote:
> > > On Mon, Sep 16, 2019 at 03:38:48PM -0700, Gregory Nowak wrote:
> > > > On Mon, Sep 16,
From: Vincent Cheng
The IDT ClockMatrix (TM) family includes integrated devices that provide
eight PLL channels. Each PLL channel can be independently configured as a
frequency synthesizer, jitter attenuator, digitally controlled
oscillator (DCO), or a digital phase lock loop (DPLL). Typically
From: Vincent Cheng
Add device tree binding doc for the IDT ClockMatrix PTP clock driver.
Signed-off-by: Vincent Cheng
---
Documentation/devicetree/bindings/ptp/ptp-idtcm.txt | 15 +++
1 file changed, 15 insertions(+)
create mode 100644
The pull request you sent on Tue, 17 Sep 2019 02:41:01 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mount-base
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e170eb27715fc9253ae031297d0638a3ef51b5da
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Tue, 17 Sep 2019 02:37:41 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.dcache
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b30d87cf969e1711f1f621b6b61efb145ee6c6d9
Thank you!
--
Deet-doot-dot, I am a bot.
On Wed, Sep 18, 2019 at 1:15 PM Alexander E. Patrakov
wrote:
>
> No, this is not the solution, if we take seriously not only getrandom
> hangs, but also urandom warnings. In some setups (root on LUKS is one of
> them) they happen early in the initramfs. Therefore "restoring" entropy
> from the
On Thu, Sep 19, 2019 at 05:22:03AM +0900, Ju Hyung Park wrote:
> Hi Greg,
>
> On Thu, Sep 19, 2019 at 5:12 AM Greg KH wrote:
> > That's a lot of rewriting :(
> >
> > How about at least keeping the file names the same to make it easier to
> > see what happened here?
> >
> > Then send a follow-on
On Wed, 11 Sep 2019 21:52:35 +0200
Thomas Huth wrote:
> After the kfree()s haven been removed in the previous
> commit 9798f4ea71ea ("fix rollback when kvmppc_xive_create fails"),
> the code can be simplified even more to simply always "return ret"
> now.
>
> Signed-off-by: Thomas Huth
> ---
On Wed, Sep 18, 2019 at 8:13 AM Jinshan Xiong wrote:
>
> The problem with the current approach is that it would be difficult to filter
> cgroup, especially the cgroup in question has descendents, and also it would
> spawn new descendents after BPF program is installed. it's hard to filter it
>
The ARM netx platform got removed in 5.3, so this driver
is now useless.
Reported-by: Uwe Kleine-König
Cc: Sascha Hauer
Signed-off-by: Arnd Bergmann
---
This fell through the cracks somewhere, I meant to send it as a separate
patch for net-next in v5.4, but only sent it as part of a series
Hi Greg,
On Thu, Sep 19, 2019 at 5:12 AM Greg KH wrote:
> That's a lot of rewriting :(
>
> How about at least keeping the file names the same to make it easier to
> see what happened here?
>
> Then send a follow-on patch that just does the rename?
That's still not quite useful tbh, lemme bring
On Wed, Sep 18, 2019 at 05:23:09PM +0200, Ondřej Jirman wrote:
> Hi,
>
> On Wed, Sep 18, 2019 at 04:17:34PM +0200, Maxime Ripard wrote:
> > Hi,
> >
> > On Sun, Sep 15, 2019 at 12:03:37AM +0200, meg...@megous.com wrote:
> > > From: Ondrej Jirman
> > >
> > > There are various issues that this
Hi Allen,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3 next-20190917]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Wed, Sep 18, 2019 at 03:09:06PM -0500, Rob Herring wrote:
> On Wed, Sep 18, 2019 at 3:47 AM Uwe Kleine-König
> wrote:
> >
> > Before commit e42ee61017f5 ("of: Let of_for_each_phandle fallback to
> > non-negative cell_count") the iterator functions calling
> > of_for_each_phandle assumed a cell
19.09.2019 00:56, Eric W. Biederman пишет:
The cheap solution appears to be copying a random seed from a previous
boot, and I think that will take care of many many cases, and has
already been implemented. Which reduces this to a system first
boot issue.
No, this is not the solution, if we
On Wed, Sep 18, 2019 at 12:56 PM Eric W. Biederman
wrote:
>
> The cheap solution appears to be copying a random seed from a previous
> boot, and I think that will take care of many many cases, and has
> already been implemented. Which reduces this to a system first
> boot issue.
Not really.
On Thu, Sep 19, 2019 at 04:59:20AM +0900, Park Ju Hyung wrote:
> --- a/drivers/staging/exfat/exfat.h
> +++ b/drivers/staging/exfat/exfat.h
> @@ -1,4 +1,4 @@
> -/* SPDX-License-Identifier: GPL-2.0 */
> +// SPDX-License-Identifier: GPL-2.0-or-later
You just changed the license of this file. Are
On Wed, Sep 18, 2019 at 1:47 PM Raghavendra Rao Ananta
wrote:
>
> On some embedded systems, the '/memory' dt-property gets updated
> by the bootloader (for example, the DDR configuration) and then
> gets passed onto the kernel. The device drivers may have to read
> the properties at runtime to
Hi,
On 18-09-2019 13:42, Yauhen Kharuzhy wrote:
On Wed, Sep 18, 2019 at 11:20:21AM +0200, Hans de Goede wrote:
Hi,
On 17-09-2019 21:45, Yauhen Kharuzhy wrote:
Existing intel_cht_int33fe ACPI pseudo-device driver assumes that
hardware has TypeC connector and register related devices described
From: Markus Elfring
Date: Wed, 18 Sep 2019 22:00:14 +0200
Simplify this function implementation by using a known wrapper function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/tty/serial/8250/8250_bcm2835aux.c | 8 +---
1 file
On Thu, Sep 19, 2019 at 04:59:20AM +0900, Park Ju Hyung wrote:
> The new sdFAT driver base brings many improvements to the table.
> Quoting Namjae Jeon:
>
> ==
> 1. sdfat has been refactored to improve compatibility, readability
de53fd7aedb1 has just been merged into Linus' mainline tree for
eventual inclusion in 5.4. This should be pushed into there, and not
wait till 5.5.
Both I and Ben Segall have already +1'd this in previous threads.
Sorry for introducing the warnings.
Dave.
On Wed, Sep 18, 2019 at 2:02 PM Qian
101 - 200 of 1030 matches
Mail list logo
