On 08/02/2019 17:08, Nicolas Dichtel wrote:
> Le 08/02/2019 à 15:43, Nikolay Aleksandrov a écrit :
>> On 08/02/2019 16:18, Nicolas Dichtel wrote:
>>> Le 08/02/2019 à 05:11, Callum Sinclair a écrit :
Currently the only way to clear the mfc cache was to delete the entries
>>> mfc stands for
On Fri, Feb 08, 2019 at 03:41:55PM -0500, Nitesh Narayan Lal wrote:
> >> I am also planning to try Michael's suggestion of using MAX_ORDER - 1.
> >> However I am still thinking about a workload which I can use to test its
> >> effectiveness.
> > You might want to look at doing something like
Hi Dmitry,
Thank you for the update.
On 2/8/19 8:57 AM, Dmitry Torokhov wrote:
Updating LED state requires access to regmap and therefore we may sleep,
so we could not do that directly form set_brightness() method.
Historically we used private work to adjust the brightness, but with the
On Fri, Feb 08, 2019 at 09:58:47AM -0800, Alexander Duyck wrote:
> On Thu, Feb 7, 2019 at 12:50 PM Nitesh Narayan Lal wrote:
> >
> >
> > On 2/7/19 12:43 PM, Alexander Duyck wrote:
> > > On Tue, Feb 5, 2019 at 3:21 PM Michael S. Tsirkin wrote:
> > >> On Tue, Feb 05, 2019 at 04:54:03PM -0500,
On Wed, Feb 6, 2019 at 1:52 PM Mike Rapoport wrote:
>
> On Mon, Feb 04, 2019 at 10:32:39PM +0200, Oded Gabbay wrote:
> > Hello,
> > This is v3 of the Habana Labs kernel driver patch-set. It contains minor
> > fixes
> > according to reviews done on v2. In addition, it is rebased on v5.0-rc5.
> >
On Thu, Feb 7, 2019 at 8:24 AM Casey Schaufler wrote:
> I added Kees to the CC list. Kees, what to you think about
> ignoring security= if lsm= is specified? I'm ambivalent.
This was one of many earlier suggestions, and the consensus seemed to
be "don't mix security= and lsm=". Why would anyone
On Fri, 2019-02-08 at 16:05 -0500, Nitesh Narayan Lal wrote:
> On 2/7/19 1:44 PM, Alexander Duyck wrote:
> > On Thu, 2019-02-07 at 13:21 -0500, Luiz Capitulino wrote:
> > > On Mon, 04 Feb 2019 10:15:52 -0800
> > > Alexander Duyck wrote:
> > >
> > > > From: Alexander Duyck
> > > >
> > > > Add
On Thu, Feb 07, 2019 at 09:37:27PM -0800, Andrew Morton wrote:
> On Thu, 7 Feb 2019 11:27:50 +0100 Jan Kara wrote:
>
> > On Fri 01-02-19 09:19:04, Dave Chinner wrote:
> > > Maybe for memcgs, but that's exactly the oppose of what we want to
> > > do for global caches (e.g. filesystem metadata
On Fri, Feb 8, 2019 at 2:16 PM Greg KH wrote:
>
> On Mon, Feb 04, 2019 at 10:32:53PM +0200, Oded Gabbay wrote:
> > +int __init hl_debugfs_init(void)
> > +{
> > + hl_debug_root = debugfs_create_dir("habanalabs", NULL);
> > + if (IS_ERR_OR_NULL(hl_debug_root)) {
> > +
f the underlying changes.
> would be candidates, which were merged in 5.0.
>
> I have reverted the first two, see how that works out.
>
> --
> Sander
>
Heiner
>
>>> --
>>> Sander
>>>
>> Heiner
>>
>>>
>>> [ 6466.554866] kern
On 1/18/19 10:00 AM, Jarkko Sakkinen wrote:
On Fri, Jan 11, 2019 at 08:28:00PM +, Safford, David (GE Global Research)
wrote:
You might mention that this is an important feature, as on at least some
systems, ppi function 23 is the only way to enable/disable PCR banks.
I have tested this
On Fri, Feb 08, 2019 at 12:10:28PM +0100, Jan Kara wrote:
> On Fri 08-02-19 15:43:02, Dave Chinner wrote:
> > On Thu, Feb 07, 2019 at 04:55:37PM +, Christopher Lameter wrote:
> > > One approach that may be a clean way to solve this:
> > > 3. Filesystems that allow bypass of the page cache
--
Greetings and how are you doing?
I want you to be my partner in the transfer of the sum of Twenty Three
Million Six hundred thousand
dollars discovered in my department in a Bank here in West Africa and I
will give you more details on this when I get your reply but be rest
assured that I
On Fri, Feb 8, 2019 at 2:14 PM Greg KH wrote:
>
> On Mon, Feb 04, 2019 at 10:32:48PM +0200, Oded Gabbay wrote:
> > This patch add the sysfs and hwmon entries that are exposed by the driver.
> >
> > Goya has several sensors, from various categories such as temperature,
> > voltage, current, etc.
On Fri, Feb 08, 2019 at 08:12:47PM +0200, Mike Rapoport wrote:
> On Fri, Feb 08, 2019 at 01:02:51AM -0500, Michael S. Tsirkin wrote:
> > Now that we have MAP_SHARED, MAP_PRIVATE and MAP_SHARED_VALIDATE on all
> > architectures, it probably makes sense to de-duplicate these
> > and put them into a
On 2/8/19 3:46 PM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 03:32:32PM -0500, Stefan Berger wrote:
tpm_del_char_device also needs the start/stop!
Done and updated the commit message to have all the call sites:
* tpm_chip_register()
* tpm_class_shutdown()
*
On Fri, 2019-02-08 at 14:54 -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> security/integrity/ima/ima_template_lib.c:85:10: warning: this statement
Le 08/02/2019 16:51, Daniel Vetter a écrit :
> On Thu, Feb 07, 2019 at 10:44:10AM +0100, Neil Armstrong wrote:
>> Hi,
>>
>> On 14/01/2019 17:36, Ayan Halder wrote:
>>> On Thu, Jan 10, 2019 at 03:57:09AM +0800, Randy Li wrote:
P010 is a planar 4:2:0 YUV with interleaved UV plane, 10 bits
If monitor pages are not allocated to a channel, the channel does not
have a valid monitor id or valid monitor page data. In these cases, some
of the "_show" functions display incorrect data. The "_show" functions
that display monitor page data access and display data that is beyond
the bounds of
On 2/7/19 1:44 PM, Alexander Duyck wrote:
> On Thu, 2019-02-07 at 13:21 -0500, Luiz Capitulino wrote:
>> On Mon, 04 Feb 2019 10:15:52 -0800
>> Alexander Duyck wrote:
>>
>>> From: Alexander Duyck
>>>
>>> Add guest support for providing free memory hints to the KVM hypervisor for
>>> freed pages
Change the monitor_pages index in server_monitor_pending_show() to '0'.
'0' is the correct monitor_pages index for the server. A comment for the
monitor_pages field in the vmbus_connection struct definition indicates
that the 1st page is for parent->child notifications. In addition, the
On Fri, Jan 18, 2019 at 01:03:46PM -0800, Matthias Kaehlcke wrote:
> Hi Marcel,
>
> On Fri, Jan 18, 2019 at 09:57:14AM +0100, Marcel Holtmann wrote:
> > Hi Balakrishna,
> >
> > >>> On 2019-01-15 06:50, Matthias Kaehlcke wrote:
> > >>> > On Mon, Jan 14, 2019 at 09:21:25PM +0530, Balakrishna
Some of the monitor id and monitor page data sysfs files display
incorrect data. This patchset provides the following changes:
1) Change the monitor_pages index in server_monitor_pending_show() to
'0', which is the correct index for the server.
2) If monitor pages are not allocated to a channel,
On 2/8/19 2:21 PM, David Miller wrote:
> From: "Gustavo A. R. Silva"
> Date: Fri, 8 Feb 2019 13:58:38 -0600
>
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> Warning level 3 was used: -Wimplicit-fallthrough=3
>>
>> This
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
security/integrity/ima/ima_template_lib.c:85:10: warning: this statement may
fall through [-Wimplicit-fallthrough=]
re merged in 5.0.
I have reverted the first two, see how that works out.
--
Sander
>> --
>> Sander
>>
> Heiner
>
>>
>> [ 6466.554866] kernel BUG at lib/dynamic_queue_limits.c:27!
>> [ 6466.571425] invalid opcode: [#1] SMP NOPTI
>> [ 6466.585890] CPU: 3
On Fri, Feb 8, 2019 at 3:11 AM Jan Kara wrote:
>
> On Fri 08-02-19 15:43:02, Dave Chinner wrote:
> > On Thu, Feb 07, 2019 at 04:55:37PM +, Christopher Lameter wrote:
> > > One approach that may be a clean way to solve this:
> > > 3. Filesystems that allow bypass of the page cache (like XFS /
On Fri, Feb 08, 2019 at 03:32:32PM -0500, Stefan Berger wrote:
> On 2/8/19 3:23 PM, Jarkko Sakkinen wrote:
> > On Fri, Feb 08, 2019 at 02:27:31PM -0500, Stefan Berger wrote:
> > > On 2/8/19 2:17 PM, Jarkko Sakkinen wrote:
> > > >*/
> > > > if (rc > 0) {
> > > > dev_warn(>dev,
> > > >
On Fri, Feb 08, 2019 at 08:10:24PM +0100, Borislav Petkov wrote:
> On Fri, Feb 08, 2019 at 11:02:48AM -0800, Guenter Roeck wrote:
> > Hi,
> >
> > On Fri, Feb 01, 2019 at 03:01:11AM -0800, tip-bot for Chao Fan wrote:
> > > Commit-ID: 3a63f70bf4c3a17f5d9c9bf3bc3288a23bdfefce
> > > Gitweb:
> >
On 2/8/19 2:32 AM, Mike Rapoport wrote:
On Thu, Feb 07, 2019 at 11:56:48PM -0800, john.hubb...@gmail.com wrote:
From: John Hubbard
[...]
+/**
+ * put_user_page() - release a gup-pinned page
+ * @page:pointer to page to be released
+ *
+ * Pages that were pinned via
Warn when any SPDX-License-Identifier: tag is not created
on the proper line number.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 8
1 file changed, 8 insertions(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 216480ae29d1..d0001fd1112d 100755
---
On 2/8/19 12:58 PM, Alexander Duyck wrote:
> On Thu, Feb 7, 2019 at 12:50 PM Nitesh Narayan Lal wrote:
>>
>> On 2/7/19 12:43 PM, Alexander Duyck wrote:
>>> On Tue, Feb 5, 2019 at 3:21 PM Michael S. Tsirkin wrote:
On Tue, Feb 05, 2019 at 04:54:03PM -0500, Nitesh Narayan Lal wrote:
> On
On Fri, Feb 08, 2019 at 10:23:53PM +0200, Jarkko Sakkinen wrote:
> On Fri, Feb 08, 2019 at 02:27:31PM -0500, Stefan Berger wrote:
> > On 2/8/19 2:17 PM, Jarkko Sakkinen wrote:
> > >
> > > */
> > > if (rc > 0) {
> > > dev_warn(>dev,
> > >"%s: send(): invalid value %d\n", __func__,
> -Original Message-
> From: Jeff King
> Sent: February 8, 2019 14:32
> To: Randall S. Becker
> Cc: 'Junio C Hamano' ; g...@vger.kernel.org; 'Linux
> Kernel' ; git-packag...@googlegroups.com
> Subject: Re: [Breakage] Git v2.21.0-rc0 - t5318 (NonStop)
>
> On Fri, Feb 08, 2019 at
On 2/8/19 3:23 PM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 02:27:31PM -0500, Stefan Berger wrote:
On 2/8/19 2:17 PM, Jarkko Sakkinen wrote:
*/
if (rc > 0) {
dev_warn(>dev,
"%s: send(): invalid value %d\n", __func__, rc);
rc = 0;
}
Should be fairly
Instead of doing this compile-time check in some slightly arbitrary
user of struct filename, put it next to the definition.
Signed-off-by: Rasmus Villemoes
---
v2: added, mostly as an example of use of static_assert(), to check
that the compiler actually groks it. Feel free to NAK it as useless
On 02/08/2019 02:50 PM, Linus Torvalds wrote:
> On Thu, Feb 7, 2019 at 11:08 AM Waiman Long wrote:
>> This patchset revamps the current rwsem-xadd implementation to make
>> it saner and easier to work with. This patchset removes all the
>> architecture specific assembly code and uses generic C
On Fri, Feb 08, 2019 at 03:11:29PM -0500, Todd Zullinger wrote:
> It made me wonder how I had missed it in my own testing.
> This one requires SHELL_PATH to be bash, while I only set
> TEST_SHELL_PATH to bash for the improved -x tracing in the
> fedora builds.
Note that you don't need Bash to use
BUILD_BUG_ON() is a little annoying, since it cannot be used outside
function scope. So one cannot put assertions about the sizeof() a
struct next to the struct definition, but has to hide that in some
more or less arbitrary function.
Since gcc 4.6 (which is now also the required minimum), there
At the time of d0484193 (lib/vsprintf.c: expand field_width to 24
bits), there was no compiletime_assert/BUILD_BUG/ variant that
could be used outside function scope. Now we have static_assert(), so
move the assertion next to the definition instead of hiding it in some
arbitrary function.
On Fri, Feb 08, 2019 at 02:27:31PM -0500, Stefan Berger wrote:
> On 2/8/19 2:17 PM, Jarkko Sakkinen wrote:
> >
> > */
> > if (rc > 0) {
> > dev_warn(>dev,
> > "%s: send(): invalid value %d\n", __func__, rc);
> > rc = 0;
> > }
> >
> > Should be fairly safe play now.
>
>
From: "Gustavo A. R. Silva"
Date: Fri, 8 Feb 2019 13:58:38 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
>
Hi Ezequiel,
On Wed, Feb 06, 2019 at 07:59:43PM -0300, Ezequiel Garcia wrote:
> > + csi->isp_clk = devm_clk_get(>dev, "isp");
> > + if (IS_ERR(csi->isp_clk)) {
> > + dev_err(>dev, "Couldn't get our ISP clock\n");
> > + return PTR_ERR(csi->isp_clk);
> > +
From: "J. Bruce Fields"
A client's actions shouldn't revoke its own delegations, even if those
same actions (rename, link, etc.) would conflict if they came from a
different client.
Since nfsd has the necessary information to determine both who is
performing the action and who holds the
From: "J. Bruce Fields"
Signed-off-by: J. Bruce Fields
---
include/linux/sunrpc/svc.h | 1 +
net/sunrpc/svc.c | 23 ++-
2 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/include/linux/sunrpc/svc.h b/include/linux/sunrpc/svc.h
index
From: "J. Bruce Fields"
These patches allow NFSv4 clients holding delegations to keep them when
the operation that would break a delegation comes from the same client.
To do that, we somehow need to pass the identity of the
delegation-breaker down through the VFS.
This series uses the tgid, a
From: "J. Bruce Fields"
This will also simplify a following patch that allows multiple
kthreadd's.
Signed-off-by: J. Bruce Fields
---
init/init_task.c | 3 +++
kernel/fork.c| 4
kernel/kthread.c | 3 +--
3 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/init/init_task.c
From: "J. Bruce Fields"
No change in behavior, just trivial refactoring.
Signed-off-by: J. Bruce Fields
---
net/sunrpc/svc.c | 62 +---
1 file changed, 37 insertions(+), 25 deletions(-)
diff --git a/net/sunrpc/svc.c b/net/sunrpc/svc.c
index
From: "J. Bruce Fields"
Allow subsystems to run their own kthreadd's.
I'm experimenting with this to allow nfsd to put its threads into its
own thread group to make it easy for the vfs to tell when nfsd is
breaking one of its own leases.
Signed-off-by: J. Bruce Fields
---
SZEDER Gábor wrote:
> On Fri, Feb 08, 2019 at 05:48:27AM -0500, Randall S. Becker wrote:
>> We have a few new breakages on the NonStop port in 2.21.0-rc0. The first is
>> in t5403, as below:
[...]
>> The post-checkout hook is:
>> #!/usr/local/bin/bash
>> echo "$@" >$GIT_DIR/post-checkout.args
>>
From: "J. Bruce Fields"
Trivial refactoring, no change in behavior.
Not really necessary, a separate function for the inner loop just seems
a little nicer to me.
Signed-off-by: J. Bruce Fields
---
kernel/kthread.c | 33 +++--
1 file changed, 19 insertions(+), 14
From: "J. Bruce Fields"
This is so knfsd can add CLONE_THREAD.
Signed-off-by: J. Bruce Fields
---
include/linux/kthread.h | 3 ++-
kernel/kthread.c| 11 +++
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/include/linux/kthread.h b/include/linux/kthread.h
index
Hi,
A few comments inline.
On a general note I agree with others that this code would benefit
from more comments.
On Wed, Jan 30, 2019 at 05:18:09PM +0800, Hsin-Hsiung Wang wrote:
> This adds support for the MediaTek MT6358 PMIC. This is a
> multifunction device with the following sub modules:
Hi Tom,
On Fri, Feb 08, 2019 at 04:30:39PM +0800, Tom Li wrote:
> Hello, Greg, Ralf, Paul, James, Alexandre and Huacai
>
> Many years ago when I was still in the middle scheool, I got a Loongson
> Yeeloong laptop to explore the world of non-x86 world, as Geert Uytterhoeven
> once said, there's
On Mon, 4 Feb 2019 16:29:31 -0800
Frank Rowand wrote:
> On 2/2/19 12:56 PM, Matthew Wilcox wrote:
> > On Fri, Feb 01, 2019 at 02:04:16PM -0800, frowand.l...@gmail.com wrote:
> >>Include documentation for each *function* in *source*.
> >> - If no *function* if specified, the documentaion
On Fri, Feb 08, 2019 at 09:54:57AM -0800, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> Implement a x86 specific version of perf_get_page_size(), which do full
> page-table walk of a given virtual address to retrieve page size.
> For x86, disabling IRQs over the walk is sufficient to
> Jeremy Linton hat am 25. Januar 2019 um 19:06
> geschrieben:
>
>
> Arm64 machines should be displaying a human readable
> vulnerability status to speculative execution attacks in
> /sys/devices/system/cpu/vulnerabilities
>
> This series enables that behavior by providing the expected
>
> On Feb 8, 2019, at 3:13 AM, Greg Kroah-Hartman
> wrote:
>
> On Wed, Feb 06, 2019 at 03:57:02PM -0800, Nadav Amit wrote:
>> From: Xavier Deguillard
>>
>> Currently, the balloon driver would fail to run if memory is greater
>> than 16TB of vRAM. Previous patches have already converted the
On Fri, 08 Feb 2019 14:40:28 +1100
Michael Ellerman wrote:
> > - I don't think this should be a top-level directory full of docs; the top
> > level is already rather overpopulated. At worst, we should create an
> > arch/ directory for architecture-specific docs.
>
> We currently have
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enabling
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
From: "Gustavo A. R. Silva"
Date: Fri, 8 Feb 2019 13:16:47 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
>
From: "Gustavo A. R. Silva"
Date: Fri, 8 Feb 2019 13:14:12 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
>
On Tue, Feb 05, 2019 at 03:06:56PM -0600, Alexandru Gagniuc wrote:
> According to PCIe 3.0, the presence detect state is a logical OR of
> in-band and out-of-band presence. With this, we'd expect the presence
> state to always be asserted when the link comes up.
Do you have a PCIe 4.0 spec? I
From: "Gustavo A. R. Silva"
Date: Fri, 8 Feb 2019 13:09:06 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
>
From: "Gustavo A. R. Silva"
Date: Fri, 8 Feb 2019 13:07:29 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
>
From: "Gustavo A. R. Silva"
Date: Fri, 8 Feb 2019 12:53:56 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Notice that, in this particular case, the fall-through annotation
> is placed at the beginning of the code
On Fri, Feb 8, 2019 at 2:06 PM Greg KH wrote:
>
> On Mon, Feb 04, 2019 at 10:32:44PM +0200, Oded Gabbay wrote:
> > +int hl_cb_ioctl(struct hl_fpriv *hpriv, void *data)
> > +{
> > + union hl_cb_args *args = data;
> > + struct hl_device *hdev = hpriv->hdev;
> > + u64 handle;
> > +
On Wed, Jan 30, 2019 at 01:46:47PM +0100, Jiri Slaby wrote:
> There are functions in relocate_kernel which are not annotated. This
> makes automatic annotations rather hard. So annotate all the functions
> now.
>
> Note that these are not C-like functions, so we do not use FUNC, but
> CODE
Remove KMS cleanup task from documentation solved by patchset
https://patchwork.freedesktop.org/series/54310/
Signed-off-by: Shayenne Moura
---
Documentation/gpu/todo.rst | 4
1 file changed, 4 deletions(-)
diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
index
From: "Gustavo A. R. Silva"
Date: Fri, 8 Feb 2019 12:37:33 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
>
On Thu, Feb 7, 2019 at 11:08 AM Waiman Long wrote:
>
> This patchset revamps the current rwsem-xadd implementation to make
> it saner and easier to work with. This patchset removes all the
> architecture specific assembly code and uses generic C code for all
> architectures. This eases
On Fri, 8 Feb 2019 13:35:39 -0200
Shayenne Moura wrote:
> Remove KMS cleanup task from documentation solved by patchset
> https://patchwork.freedesktop.org/series/54310/
>
> Signed-off-by: Shayenne Moura
This seems like a worthy change, but Documentation/gpu is managed by the
DRM maintainers.
I just sent out a fixed version. Thanks!
On Fri, Feb 8, 2019 at 10:18 AM Enric Balletbo Serra
wrote:
>
> Hi Nick,
> Missatge de Nick Crews del dia dv., 8 de febr.
> 2019 a les 2:24:
> >
> > Add a debugfs attribute that allows sending raw commands to the EC.
> > This is useful for development
The pull request you sent on Fri, 8 Feb 2019 09:39:21 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> tags/char-misc-5.0-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/680905431b9de8c7224b15b76b1826a1481cfeaf
Thank you!
--
The pull request you sent on Thu, 7 Feb 2019 23:25:17 -0800:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.0-fixes-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bd5ff862ec7855cc7a110891443e7dc6deeb6b84
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 08 Feb 2019 02:42:09 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net master
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/27b4ad621e887ce8e5eb508a0103f13d30f6b38a
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 8 Feb 2019 09:38:35 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> tags/staging-5.0-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e464f50c057a1fbefae6c6078f9bd5511f84f199
Thank you!
--
On Tue, Oct 30, 2018 at 5:22 PM David Engraf wrote:
>
> Unpacking an external initrd may fail e.g. not enough memory. This leads
> to an incomplete rootfs because some files might be extracted already.
> Fixed by cleaning the rootfs so the kernel is not using an incomplete
> rootfs.
This breaks
The pull request you sent on Fri, 8 Feb 2019 09:37:47 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-5.0-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/00a159a0007b91fbce2a93e2666951c760ce6811
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 8 Feb 2019 09:38:08 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-5.0-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e22a15d1c4b36877934ab360aace41ddf8a6577c
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 8 Feb 2019 11:05:22 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-02-08
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/adcbc921d3dff0bf1657d4d31beee68f92f51538
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 8 Feb 2019 09:39:04 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
> tags/driver-core-5.0-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8c8e62cc983938a554d39497b5600b842f8a7965
Thank you!
--
[+cc Marc, Thomas]
On Fri, Feb 08, 2019 at 09:54:38AM -0700, Logan Gunthorpe wrote:
> The double underscore types are meant for compatibility in userspace
> headers which does not apply here. Therefore, change to use the
> standard no-underscore types.
>
> The origin of the double underscore
Hi Marek,
* Marek Szyprowski [2019-02-08 13:36]:
On 21/01/19 16:02, Jochen Sprickerhof wrote:
[..]
I'm not sure why this it only works with the driver compiled into the
kernel nor why it needs a hard reset or why it was the line was dropped
when the patch was accepted. Would be great to get
This Embedded Controller has an internal RTC that is exposed
as a standard RTC class driver with read/write functionality.
The driver is added to the drivers/rtc/ so that the maintainer of that
directory will be able to comment on this change, as that maintainer is
the expert on this system. In
Add a debugfs attribute that allows sending raw commands to the EC.
This is useful for development and debug but should not be enabled
in a production environment.
To test:
Get the EC firmware build date
First send the request command
> echo 00 f0 38 00 03 00 > raw
Then read the result.
This EC is an incompatible variant of the typical Chrome OS embedded
controller. It uses the same low-level communication and a similar
protocol with some significant differences. The EC firmware does
not support the same mailbox commands so it is not registered as a
cros_ec device type. This
There is a new chromebook that contains a different Embedded Controller
(codename Wilco) than the rest of the chromebook series. Thus the kernel
requires a different driver than the already existing and generalized
cros_ec_* drivers. The core of the communication with the EC
is implemented in
In order to allow this code to be re-used, remove the dependency
on the rest of the cros_ec code from the cros_ec_lpc_mec functions.
Instead of using a hardcoded register base address of 0x800 have
this be passed in to cros_ec_lpc_mec_init(). The existing cros_ec
use case now passes in the 0x800
Disclaimer:
I cannot test this driver as I do not have any h/w.
This RFC patch is not intended as a ready-made solution,
but to provoke discussion.
Problem 1:
lm8323_pwm_work() could still run after the device has been removed, which
would result in a use-after-free.
Problem 2:
The
Recursive mutex lock/unlock is not permitted. Remove.
Signed-off-by: Sven Van Asbroeck
---
drivers/input/keyboard/lm8323.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/input/keyboard/lm8323.c b/drivers/input/keyboard/lm8323.c
index ea4ed1750eb5..4363c60f7845 100644
---
On Fri, Feb 08, 2019 at 02:26:17PM -0500, Randall S. Becker wrote:
> > > For this, we could use truncate -s count file instead of dd to get a
> > > fixed size file of nulls. This would remove the need for /dev/zero in
> > > t5318 (the patch below probably will wrap badly in my mailer so I can
> >
Johannes Sixt writes:
> If the data does not have to be a sequence of zero bytes, the
> alternatives are:
>
> * `test-genrandom seed-string $size` for a sequence of reproducible
> "random" bytes
>
> * `printf "%0*d" $size 0` for a sequence of '0' characters.
>
> In t5318, the zero bytes do
The ycbcr2rgb and inverse rgb2ycbcr matrices define the BT.601 encoding
coefficients, so rename them to indicate that. And add some comments
to make clear these are BT.601 coefficients encoding between YUV limited
range and RGB full range. The ic_csc_rgb2rgb matrix is just an identity
matrix, so
Pass v4l2 encoding enum to the ipu_ic task init functions, and add
support for the BT.709 encoding and inverse encoding matrices.
Reported-by: Tim Harvey
Signed-off-by: Steve Longerbeam
---
Changes in v2:
- only return "Unsupported YCbCr encoding" error if inf != outf,
since if inf == outf,
The IC now supports BT.709 Y'CbCr encoding, in addition to existing BT.601
encoding, so allow both, for pipelines that route through the IC.
Reported-by: Tim Harvey
Signed-off-by: Steve Longerbeam
---
Changes in v2:
- move ic_route check above default colorimetry checks, and fill default
Simplify the selection of the Y'CbCr encoding matrices in init_csc().
A side-effect of this change is that init_csc() now allows YUV->YUV
using the identity matrix, intead of returning error.
Signed-off-by: Steve Longerbeam
---
drivers/gpu/ipu-v3/ipu-ic.c | 12
1 file changed, 4
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enabling
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
On 2/8/19 2:17 PM, Jarkko Sakkinen wrote:
*/
if (rc > 0) {
dev_warn(>dev,
"%s: send(): invalid value %d\n", __func__, rc);
rc = 0;
}
Should be fairly safe play now.
Unfortuantely it isn't. You seemed to have lost the
EXPORT_SYMBOL_GPL(tpm_chip_start/stop)
On February 8, 2019 14:15, Jeff King wrote:
> On Fri, Feb 08, 2019 at 01:47:04PM -0500, Randall S. Becker wrote:
>
> > > Though I suspect we may be able to just find a solution that works
> > > everywhere, without having two different implementations. If we know
> > > we need $count bytes for dd,
201 - 300 of 1100 matches
Mail list logo
