On Tue, Apr 10, 2018 at 12:38:46PM -0700, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add documentation to describe Xilinx ZynqMP clock driver
> bindings.
>
> Signed-off-by: Rajan Vaja
> Signed-off-by: Jolly Shah
> ---
> .../firmware/xilinx/xlnx,zynqmp-firmware.txt | 53 ++
> incl
On Mon, 16 Apr 2018, Sasha Levin wrote:
> I agree that as an enterprise distro taking everything from -stable
> isn't the best idea. Ideally you'd want to be close to the first
> extreme you've mentioned and only take commits if customers are asking
> you to do so.
>
> I think that the rule we're
On Mon, 16 Apr 2018 13:17:24 -0700
Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 1:02 PM, Steven Rostedt wrote:
> >
> > But this is going way off topic to what we were discussing. The
> > discussion is about what gets backported. Is automating the process
> > going to make stable better? Or is
On Mon, 16 Apr 2018 20:49:12 +
Bart Van Assche wrote:
> Which tools process these strings? Has it been verified whether or not
> the tools that process these strings still work fine with this patch
> applied?
Ideally, tools shouldn't process trace event strings, but I'm sure some
do. :-/
Ge
Hello
Greeetings to you please did you get my previous email regarding my
investment proposal last week friday ?
MS.Zeliha ömer faruk
zeliha.omer.fa...@gmail.com
From: Randy Dunlap
Fix build errors when INFINIBAND_USER_ACCESS=m and MLX5_INFINIBAND=y.
The build error occurs when the mlx5 driver code attempts to use
USER_ACCESS interfaces, which are built as a loadable module.
Fixes these build errors:
drivers/infiniband/hw/mlx5/main.o: In function `popul
On Mon, 2018-04-16 at 21:10 +, Bean Huo (beanhuo) wrote:
> Hi, Bart
>
> > mi...@redhad.com; linux-bl...@vger.kernel.org; raja...@google.com
> > Subject: [EXT] Re: [RESEND PATCH v1 1/2] trace: events: scsi: Add tag in
> > SCSI
> > trace events
> >
> > On Mon, 2018-04-16 at 14:31 +, Bean H
On Mon, Apr 16, 2018 at 10:43:28PM +0200, Jiri Kosina wrote:
>On Mon, 16 Apr 2018, Sasha Levin wrote:
>
>> So I think that Linus's claim that users come first applies here as
>> well. If there's a user that cares about a particular feature being
>> broken, then we go ahead and fix his bug rather th
Hi, Bart
>mi...@redhad.com; linux-bl...@vger.kernel.org; raja...@google.com
>Subject: [EXT] Re: [RESEND PATCH v1 1/2] trace: events: scsi: Add tag in SCSI
>trace events
>
>On Mon, 2018-04-16 at 14:31 +, Bean Huo (beanhuo) wrote:
>> TP_printk("host_no=%u channel=%u id=%u lun=%u data_sgl=%u
On Mon, Apr 16, 2018 at 11:11 PM, Michal Hocko wrote:
> On Mon 16-04-18 22:17:40, Jann Horn wrote:
>> On Mon, Apr 16, 2018 at 9:57 PM, Michal Hocko wrote:
>> > On Mon 16-04-18 21:30:09, Jann Horn wrote:
>> >> On Mon, Apr 16, 2018 at 9:18 PM, Michal Hocko wrote:
>> > [...]
>> >> > Yes, reasonably
> From: Jan Kara
> Sent: Monday, April 16, 2018 07:41
> ...
> How easily can you hit this? Are you able to run debug kernels / inspect
> crash dumps when the issue occurs? Also testing with the latest mainline
> kernel (4.16) would be welcome whether this isn't just an issue with the
> backport of
On Mon 16-04-18 22:17:40, Jann Horn wrote:
> On Mon, Apr 16, 2018 at 9:57 PM, Michal Hocko wrote:
> > On Mon 16-04-18 21:30:09, Jann Horn wrote:
> >> On Mon, Apr 16, 2018 at 9:18 PM, Michal Hocko wrote:
> > [...]
> >> > Yes, reasonably well written application will not have this problem.
> >> > T
On Sun, Mar 25, 2018 at 12:24:58AM +0100, Alban Bedel wrote:
> Config data for drivers, like MAC addresses, is often stored in MTD.
> Add a binding that define how such data storage can be represented in
> device tree.
>
> Signed-off-by: Alban Bedel
> ---
> Changelog:
> v2: * Added a "Required pr
On Mon, 16 Apr 2018, Sasha Levin wrote:
> So if a user is operating a nuclear power plant, and has 2 leds: green
> one that says "All OK!" and a red one saying "NUCLEAR MELTDOWN!", and
> once in a blue moon a race condition is causing the red one to go on and
> cause panic in the little provinc
On Sun, Mar 25, 2018 at 12:24:57AM +0100, Alban Bedel wrote:
> Having the cells as subnodes of the provider device without any
> compatible property might clash with other bindings. To avoid this
> problem update the binding to have all the cells in a 'nvmem-cells'
> subnode with a 'nvmem-cells' co
On Mon, 16 Apr 2018, Vlastimil Babka wrote:
> On 04/16/2018 09:36 PM, Mikulas Patocka wrote:
>
> >>> I need to increase it just for dm-bufio slabs.
> >>
> >> If you do this then others will want the same...
> >
> > If others need it, they can turn on the flag SLAB_MINIMIZE_WASTE too.
>
> I th
- On Apr 16, 2018, at 3:26 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Mon, Apr 16, 2018 at 12:21 PM, Mathieu Desnoyers
> wrote:
>>
>> And I try very hard to avoid being told I'm the one breaking
>> user-space. ;-)
>
> You *can't* be breaking user space. User space doesn't
On Fri, Apr 13, 2018 at 07:50:34PM -0700, David Collins wrote:
> Introduce bindings for RPMh regulator devices found on some
> Qualcomm Technlogies, Inc. SoCs. These devices allow a given
> processor within the SoC to make PMIC regulator requests which
> are aggregated within the RPMh hardware blo
Moving perf tools CoreSight support to the SPDX identifier.
Signed-off-by: Mathieu Poirier
---
tools/include/linux/coresight-pmu.h | 13 +
tools/perf/arch/arm/util/auxtrace.c | 13 +
tools/perf/arch/arm/util/cs-etm.c | 13 +---
This patchset introduces memcg variant memory allocation functions. The
caller can explicitly pass the memcg to charge for kmem allocations.
Currently the kernel, for __GFP_ACCOUNT memory allocation requests,
extract the memcg of the current task to charge for the kmem allocation.
This patch series
Hi Linus,
please pull a trivial one-line build fix for the parisc architecture from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-4.17-3
* Fix build error because of missing binfmt_elf32.o file which is still
mentioned in the Makefile.
Thanks,
Helge
---
A lot of memory can be consumed by the events generated for the huge or
unlimited queues if there is either no or slow listener. This can cause
system level memory pressure or OOMs. So, it's better to account the
fsnotify kmem caches to the memcg of the listener.
There are seven fsnotify kmem ca
Introduce the memcg variant for kmalloc[_node] and
kmem_cache_alloc[_node]. For kmem_cache_alloc, the kernel switches the
root kmem cache with the memcg specific kmem cache for __GFP_ACCOUNT
allocations to charge those allocations to the memcg. However, the memcg
to charge is extracted from the c
Moving all kernel side CoreSight framework and drivers to SPDX identifier.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-cpu-debug.c | 14 +-
drivers/hwtracing/coresight/coresight-dynamic-replicator.c | 10 +-
drivers/hwtracing/coresight/co
On 2018-04-16 10:14, Evan Green wrote:
On Fri, Apr 13, 2018 at 4:08 PM wrote:
On 2018-04-12 15:02, Evan Green wrote:
> Hi Rishabh,
>
> On Tue, Apr 10, 2018 at 1:09 PM Rishabh Bhatnagar
>
> wrote:
>
>> LLCC (Last Level Cache Controller) provides additional cache memory
>> in the system. LLCC i
On Mon, 2018-04-16 at 14:33 +, Bean Huo (beanhuo) wrote:
> [ ... ]
> - TP_printk("%d,%d %s (%s) %llu + %u [%d]",
> + TP_printk("%d,%d %s (%s) %llu + %u tag=%d [%d]",
> [ ... ]
> - TP_printk("%d,%d %s (%s) %llu + %u [%d]",
> + TP_printk("%d,%d %s (%s) %llu + %u tag=%d [%d]",
> [
On Mon, 2018-04-16 at 14:31 +, Bean Huo (beanhuo) wrote:
> TP_printk("host_no=%u channel=%u id=%u lun=%u data_sgl=%u prot_sgl=%u" \
> - " prot_op=%s cmnd=(%s %s raw=%s)",
> + " prot_op=%s tag=%d cmnd=(%s %s raw=%s)",
>
> [ ... ]
> TP_printk("host_no=%u c
On Sat, Apr 14, 2018 at 08:06:40AM +0530, Taniya Das wrote:
> Add RPMh clock device bindings for Qualcomm Technology Inc's SoCs. These
> devices would be used for communicating resource state requests to control
> the clocks managed by RPMh.
>
> Signed-off-by: Amit Nischal
> Signed-off-by: Taniya
On Thu, Apr 12, 2018 at 8:02 PM, Kees Cook wrote:
> On Thu, Apr 12, 2018 at 3:47 PM, Kees Cook wrote:
>> After fixing up some build issues in the middle of the 4.16 cycle, I
>> get an unhelpful bisect result of commit 0a4b6e2f80aa ("Merge branch
>> 'for-4.16/block'"). Instead of letting the test
On Mon, 16 Apr 2018, Sasha Levin wrote:
> So I think that Linus's claim that users come first applies here as
> well. If there's a user that cares about a particular feature being
> broken, then we go ahead and fix his bug rather then ignoring him.
So one extreme is fixing -stable *iff* users act
On Mon, 2018-04-16 at 20:27 +, Bean Huo (beanhuo) wrote:
> By the way, these patches are not to add new feature, they are just to
> add print tag along with the other exist printed request parameters.
Are you aware that there are two tag fields in struct request, namely "tag"
and "internal_tag
On Fri, Apr 13, 2018 at 10:21:22PM +0530, Manu Gautam wrote:
> Existing documentation has lot of incorrect information as it
> was originally added for a driver that no longer exists.
>
> Signed-off-by: Manu Gautam
> ---
> .../devicetree/bindings/usb/qcom,dwc3.txt | 78
> ++
On Mon, Apr 16, 2018 at 10:17:17PM +0200, Jiri Kosina wrote:
>On Mon, 16 Apr 2018, Sasha Levin wrote:
>
>> So if a user is operating a nuclear power plant, and has 2 leds: green
>> one that says "All OK!" and a red one saying "NUCLEAR MELTDOWN!", and
>> once in a blue moon a race condition is causi
On Sun, 15 Apr 2018 20:36:56 +0300
Mike Rapoport wrote:
> I didn't mean we should keep it as unorganized jumble of stuff and I agree
> that splitting the documentation by audience is better because developers
> are already know how to find it :)
>
> I just thought that putting the doc into the p
On Mon, Apr 16, 2018 at 12:25 PM, Eric Anholt wrote:
> The GPU subsystem node was a workaround to have a central device to
> bind V3D and display to. Following the lead of 246774d17fc0
> ("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove
> the subsystem node usage and just creat
On Mon, 16 Apr 2018, Linus Torvalds wrote:
> The ones who should matter most for that discussion is the distros,
> since they are the actual users of stable (as well as the people doing
> the work, of course - ie Sasha and Greg and the rest of the stable
> gang).
>
> And I suspect that they actua
>>> This patch is not acceptable because it adds support for tag tracing
>>> to the legacy block layer only. Any patch that adds a new feature to
>>> the legacy block layer must also add it to blk-mq.
>>>
>> To be honest, I don't understand your point, can you give me more
>explanation?
>
>The lega
On Thu, Mar 29, 2018 at 10:28:23AM +0100, Matt Redfearn wrote:
> @@ -260,6 +260,11 @@
> jr ra
> andiv1, a2, STORMASK
This patch looks good, well spotted!
But whats that v1 write about? Any ideas? Seems to go back to the git
epoch, and $3 isn't in the clobber l
On Mon, Apr 16, 2018 at 9:57 PM, Michal Hocko wrote:
> On Mon 16-04-18 21:30:09, Jann Horn wrote:
>> On Mon, Apr 16, 2018 at 9:18 PM, Michal Hocko wrote:
> [...]
>> > Yes, reasonably well written application will not have this problem.
>> > That, however, requires an external synchronization and
On Mon, Apr 16, 2018 at 1:02 PM, Steven Rostedt wrote:
>
> But this is going way off topic to what we were discussing. The
> discussion is about what gets backported. Is automating the process
> going to make stable better? Or is it likely to add more regressions.
>
> Sasha's response has been tha
On 04/13, Chao Yu wrote:
> On 2018/4/13 12:05, Jaegeuk Kim wrote:
> > On 04/13, Chao Yu wrote:
> >> On 2018/4/13 9:04, Jaegeuk Kim wrote:
> >>> On 04/10, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2018/4/8 16:13, Chao Yu wrote:
> > f2fs doesn't allow abuse on atomic write class interfac
On Mon, 16 Apr 2018 17:45:01 +0200
Thymo van Beers wrote:
> Some lines used spaces instead of tabs at line start.
> This can cause mangled lines in editors due to inconsistency.
>
> Replace spaces for tabs where appropriate.
Seems like a fine idea. The patch doesn't apply, though; can you plea
On Fri, Apr 13, 2018 at 01:36:48PM -0300, Hernán Gonzalez wrote:
Commit msg?
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Hernán Gonzalez
> ---
> .../devicetree/bindings/staging/iio/cdc/ad7746.txt | 34
> ++
> 1 file changed, 34 i
On Thu, 12 Apr 2018 16:44:10 -0400
Konstantin Ryabitsev wrote:
> Small tweaks to the Maintainer PGP guide:
>
> - Use --quick-addkey command that is compatible between GnuPG-2.2 and
>GnuPG-2.1 (which many people still have)
> - Add a note about the Nitrokey program
> - Warn that some devic
On Fri, Apr 13, 2018 at 09:51:12AM +0100, Phil Edworthy wrote:
> The DesignWare GPIO IP can be configured for either 1 interrupt or 1
> per GPIO in port A, but the driver currently only supports 1 interrupt.
> See the DesignWare DW_apb_gpio Databook description of the
> 'GPIO_INTR_IO' parameter.
>
Johan,
On Fri, Apr 13, 2018 at 05:15:05PM +0200, Johan Hovold wrote:
> To be able to use DSPS-based controllers with device-tree descriptions
> of the USB topology, we need to associate the glue device's device-tree
> node with the child controller device.
>
> Note that this can also be used to e
On Mon, 16 Apr 2018 12:55:46 -0700
Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 12:38 PM, Steven Rostedt wrote:
> >
> > But I don't see in the git history that this was ever reverted. My reply
> > saying that "I hope it wasn't reverted", was a response for it being
> > reverted in stable, not
On Mon, Apr 16, 2018 at 07:34:29PM +, Yann Collet wrote:
> Hi Singh
>
> I don't have any strong opinion on this topic.
>
> You made your case clear:
> your variant trades a little bit of speed for a little bit more compression
> ratio.
> In the context of zram, it makes sense, and I would e
On 04/16/2018 02:27 PM, Michal Hocko wrote:
> On Mon 16-04-18 14:06:21, Vlastimil Babka wrote:
>>
>> For example the percpu (and other) array caches...
>>
>>> maybe it will turn out that such a large
>>> portion of the chache would need to duplicate the state that a
>>> completely new cache would b
On Mon, 16 Apr 2018 12:31:09 -0700
Linus Torvalds wrote:
>
> But the -stable tree?
>
> Seriously, what do you expect them to do if they get a report that a
> commit they added to the stable tree regresses?
>
> "Revert first, ask questions later" is definitely a very sane model there.
The topic
On Mon, Apr 16, 2018 at 01:36:45PM +0200, Petr Mladek wrote:
> Nikolai started to use shadow variables and found that list_head
> is not initialized correctly using the existing API.
>
> The problem is that LIST_HEAD_INIT() set pointers to itself.
> klp_shadow_alloc() then copies these pointers to
On Mon 16-04-18 21:30:09, Jann Horn wrote:
> On Mon, Apr 16, 2018 at 9:18 PM, Michal Hocko wrote:
[...]
> > Yes, reasonably well written application will not have this problem.
> > That, however, requires an external synchronization and that's why
> > called it error prone and racy. I guess that w
On Mon, Apr 16, 2018 at 12:38 PM, Steven Rostedt wrote:
>
> But I don't see in the git history that this was ever reverted. My reply
> saying that "I hope it wasn't reverted", was a response for it being
> reverted in stable, not mainline.
See my other email.
If your'e stable maintainer, and you
On Fri, Apr 13 2018 at 11:43 -0600, Stephen Boyd wrote:
Quoting Lina Iyer (2018-04-13 08:37:25)
On Tue, Apr 10 2018 at 22:39 -0600, Stephen Boyd wrote:
>Quoting Lina Iyer (2018-04-05 09:18:25)
>>
>> + */
>> +static irqreturn_t tcs_irq_handler(int irq, void *p)
>> +{
>> + struct rsc_drv *dr
On 04/16/2018 12:35 PM, Mathieu Poirier wrote:
> Adding a section that document how to use the Coresight framework and
> drivers from the perf tools.
>
> Signed-off-by: Mathieu Poirier
> ---
> Documentation/trace/coresight.txt | 50
> +++
> 1 file changed, 50
* Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 11:04 AM, Linus Torvalds
> wrote:
> >
> > I was going through the bisection, with just a couple more rounds to
> > go, but I guess I don't even need it.
>
> Ingo/Thomas: I will be just taking this directly, since it's so
> trivial and obvious a
On Thu, 2018-04-05 at 11:49 +0200, Enric Balletbo i Serra wrote:
> From: "Kristian H. Kristensen"
>
> To improve PSR exit latency, we speculatively start exiting when we
> receive input events. Occasionally, this may lead to false positives,
> but most of the time we get a head start on coming ou
On Mon, Apr 16, 2018 at 3:35 AM, Dmitry Vyukov wrote:
> On Fri, Apr 13, 2018 at 5:54 PM, Dmitry Vyukov wrote:
>> On Fri, Apr 13, 2018 at 2:43 PM, Dan Streetman wrote:
>>> On Thu, Apr 12, 2018 at 8:15 AM, Dmitry Vyukov wrote:
On Wed, Feb 21, 2018 at 3:53 PM, Tommi Rantala
wrote:
>
From: Fengguang Wu
sound/soc/codecs/rt1305.c:1174:3-8: No need to set .owner here. The core will
do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Fixes: 29bc643ddd7e ("ASoC: rt1305: Add RT1305/RT1306 ampl
On Mon, 16 Apr 2018 12:28:21 -0700
Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 12:24 PM, Steven Rostedt wrote:
> >
> > Right, but the fix to the API was also trivial. I don't understand why
> > you are arguing with me. I agree with you. I'm talking about this
> > specific instance. Where a b
Adding a section that document how to use the Coresight framework and
drivers from the perf tools.
Signed-off-by: Mathieu Poirier
---
Documentation/trace/coresight.txt | 50 +++
1 file changed, 50 insertions(+)
diff --git a/Documentation/trace/coresight.txt
Field "owner" of struct coresight_desc has been removed a while back but
the documentation was not updated to reflect the changes.
Signed-off-by: Mathieu Poirier
---
Documentation/trace/coresight.txt | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Documentation/trace/coresight.txt
b/Docum
This patch groups together section pertaining to the perf tools. That way
everything is at the same place rather than spread out.
Signed-off-by: Mathieu Poirier
---
Documentation/trace/coresight.txt | 72 +++
1 file changed, 36 insertions(+), 36 deletions(-)
Now that the perf tools CoreSight support is upstream this set adds
documentation to go with it and move things around so that topics
are located together.
Mathieu Poirier (3):
coresight: Remove obsolete reference to "owner" in CoreSight
descriptor
coresight: Add section for integration
Hi Singh
I don't have any strong opinion on this topic.
You made your case clear:
your variant trades a little bit of speed for a little bit more compression
ratio.
In the context of zram, it makes sense, and I would expect it to work, as
advertised in your benchmark results.
(disclaimer: I ha
| 40 +---
3 files changed, 38 insertions(+), 19 deletions(-)
--- linux-next-20180416.orig/Documentation/core-api/kernel-api.rst
+++ linux-next-20180416/Documentation/core-api/kernel-api.rst
@@ -136,6 +136,19 @@ Sorting
.. kernel-doc:: lib/list_sort.c
This patch introduces a flag SLAB_MINIMIZE_WASTE for slab and slub. This
flag causes allocation of larger slab caches in order to minimize wasted
space.
This is needed because we want to use dm-bufio for deduplication index and
there are existing installations with non-power-of-two block sizes (su
On Mon, Apr 16, 2018 at 12:28 PM, Linus Torvalds
wrote:
>
> If you know of the fix, fine. But clearly people DID NOT KNOW. So
> reverting was the right choice.
.. and this is obviously different in stable and in mainline.
For example, I start reverting very aggressively only at the end of a
rele
On Mon, Apr 16, 2018 at 9:18 PM, Michal Hocko wrote:
> On Mon 16-04-18 15:55:36, Jann Horn wrote:
>> On Mon, Apr 16, 2018 at 12:07 PM, Michal Hocko wrote:
>> > On Fri 13-04-18 18:17:36, Jann Horn wrote:
>> >> On Fri, Apr 13, 2018 at 6:05 PM, Jann Horn wrote:
>> >> > On Fri, Apr 13, 2018 at 6:04
On Mon, 16 Apr 2018 12:00:08 -0700
Linus Torvalds wrote:
> > On Mon, Apr 16, 2018 at 11:52 AM, Linus Torvalds
> > wrote:
> > >
> > > We're better off making *no* progress, than making "unsteady progress".
> > >
> > > Really. Seriously.
[ me inserted: ]
> On Mon, 16 Apr 2018 3:24:29 PM, Ste
Yeah, I definitely agree on the idea of expanding the use case to the
general domain where dmabuf sharing is used. However, what you are
targetting with proposed changes is identical to the core design of
hyper_dmabuf.
On top of this basic functionalities, hyper_dmabuf has driver level
inter-doma
On Mon, Apr 16, 2018 at 12:24 PM, Steven Rostedt wrote:
>
> Right, but the fix to the API was also trivial. I don't understand why
> you are arguing with me. I agree with you. I'm talking about this
> specific instance. Where a bug was fixed, and the API breakage was
> another fix that needed to b
On Mon, Apr 16, 2018 at 12:21 PM, Mathieu Desnoyers
wrote:
>
> And I try very hard to avoid being told I'm the one breaking
> user-space. ;-)
You *can't* be breaking user space. User space doesn't use this yet.
That's actually why I'd like to start with the minimal set - to make
sure we don't in
On Thu, Apr 12, 2018 at 04:37:15PM +0200, Lukasz Majewski wrote:
> This commit adds support for KOE's 5.7" display.
>
> Signed-off-by: Lukasz Majewski
> ---
> .../bindings/display/panel/koe,tx14d24vm1bpa.txt | 42
> ++
> drivers/gpu/drm/panel/panel-simple.c |
On Mon, 16 Apr 2018 11:52:48 -0700
Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 11:41 AM, Steven Rostedt wrote:
> >
> >I never said the second
> > bug fix should not have been backported. I even said that the first bug
> > "didn't go far enough".
>
> You're still not getting it.
>
> The "
On Thu, Apr 12, 2018 at 04:34:01PM +0200, Lukasz Majewski wrote:
> The 'kao' entry has been added to vendor-prefixes.txt to indicate
> products from Kaohsiung Opto-Electronics Inc.
kao or...
>
> Signed-off-by: Lukasz Majewski
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
On Thu, Apr 12, 2018 at 02:55:36PM +0100, Phil Elwell wrote:
> The Microchip LAN78XX family of devices are Ethernet controllers with
> a USB interface. Despite being discoverable devices it can be useful to
> be able to configure them from Device Tree, particularly in low-cost
> applications withou
On 4/13/18 5:03 AM, Dmitry Vyukov wrote:
> On Fri, Apr 6, 2018 at 6:10 PM, Darrick J. Wong
> wrote:
>> On Fri, Apr 06, 2018 at 07:38:44AM +1000, Dave Chinner wrote:
>>> On Thu, Apr 05, 2018 at 08:54:50PM +0200, Dmitry Vyukov wrote:
On Tue, Apr 3, 2018 at 6:38 AM, Dave Chinner wrote:
> O
- On Apr 16, 2018, at 2:39 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Mon, Apr 16, 2018 at 11:35 AM, Mathieu Desnoyers
> wrote:
>> Specifically for single-stepping, the __rseq_table section introduced
>> at user-level will allow newer debuggers and tools which do line and
>
On Mon, Apr 16, 2018 at 11:52 AM, Linus Torvalds
wrote:
>
> And yes, sometimes that means jumping through hoops. But that's what
> it takes to keep users happy.
The example of "jumping through hoops" I tend to give is the pipe "packet mode".
The kernel actually has a magic pipe mode for "packet
On Mon 16-04-18 15:55:36, Jann Horn wrote:
> On Mon, Apr 16, 2018 at 12:07 PM, Michal Hocko wrote:
> > On Fri 13-04-18 18:17:36, Jann Horn wrote:
> >> On Fri, Apr 13, 2018 at 6:05 PM, Jann Horn wrote:
> >> > On Fri, Apr 13, 2018 at 6:04 PM, Michal Hocko wrote:
> >> >> On Fri 13-04-18 17:04:09, J
linux-kernel@vger.kernel.org
Hi Christoph,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.17-rc1 next-20180416]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://git
On Mon, Apr 16, 2018 at 04:58:11PM +0200, Petr Mladek wrote:
> On Wed 2018-04-11 10:48:52, Josh Poimboeuf wrote:
> > On Wed, Apr 11, 2018 at 04:17:11PM +0200, Petr Mladek wrote:
> > > > I still agree with my original conclusion that enforcing stack order no
> > > > longer makes sense though.
> > >
On Mon, Apr 16, 2018 at 11:52 AM, Linus Torvalds
wrote:
>
> We're better off making *no* progress, than making "unsteady progress".
>
> Really. Seriously.
Side note: the original impetus for this was our suspend/resume mess.
It went on for *YEARS*, and it was absolutely chock-full of exactly
this
On Mon, 16 Apr 2018 18:35:44 +
Sasha Levin wrote:
> If I were to tell you that I have a crack team of 10 kernel hackers who
> dig through all mainline commits to find commits that should be
> backported to stable, and they do it with less mistakes than
> authors/maintainers make when they tag
On Fri, Apr 06, 2018 at 05:21:30PM -0700, Alison Schofield wrote:
> From: Alison Schofield
>
> Intel's Skylake Server CPUs have a different LLC topology than previous
> generations. When in Sub-NUMA-Clustering (SNC) mode, the package is
> divided into two "slices", each containing half the cores,
Add compatible string for R-Car M3-N (r8a77965) in gpio-rcar.
Signed-off-by: Jacopo Mondi
Reviewed-by: Geert Uytterhoeven
Reviewed-by: Simon Horman
Reviewed-by: Rob Herring
---
Renesas R-Car M3-N support has been merged for v4.17.
Document the missing device tree bindings.
v1 -> v2:
- Add Si
--
I Mikhail Fridman. has selected you specially as one of my beneficiaries
for my Charitable Donation, Just as I have declared on May 23, 2016 to
give
my fortune as charity.
Check the link below for confirmation:
http://www.ibtimes.co.uk/russias-second-wealthiest-man-mikhail-fridman-plans-l
On Mon, Apr 16, 2018 at 11:41 AM, Steven Rostedt wrote:
>
>I never said the second
> bug fix should not have been backported. I even said that the first bug
> "didn't go far enough".
You're still not getting it.
The "didn't go far enough" means that the bug fix is *BUGGY*. It needs
to be reverte
On Wed, Apr 11, 2018 at 10:42:57PM +0100, Ricardo Silva wrote:
> The pinctrl-mcp23s08 driver doesn't provide a specific gpiospec
> of_xlate() function, causing the gpiolib-of's of_gpio_simple_xlate()
> function to be used instead, which takes the gpiospec's second cell as
> the flags specifier acco
Hi David,
On Mon, Apr 16, 2018 at 10:17:55AM -0400, David Miller wrote:
> From: Jacopo Mondi
> Date: Mon, 16 Apr 2018 15:55:17 +0200
>
> > Add documentation for r8a77965 compatible string to renesas ravb device
> > tree bindings documentation.
> >
> > Signed-off-by: Jacopo Mondi
> > Reviewed-by:
On Wed, Apr 11, 2018 at 10:10:33PM +0530, Manivannan Sadhasivam wrote:
> Define power domains for Actions Semi S900 SoC Smart Power System (SPS).
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../devicetree/bindings/power/actions,owl-sps.txt | 2 ++
> include/dt-bindings/power/owl-s900-powe
On Wed, Apr 11, 2018 at 10:16:37PM +0800, Icenowy Zheng wrote:
> On some Allwinner SoCs the EMAC clock register needed by dwmac-sun8i is
> in another device's memory space. In this situation dwmac-sun8i can use
> a regmap exported by the other device with only the EMAC clock register.
If this is a
Linus,
please consider to pull the latest timers-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-core-for-linus
That's a branch which got forgotten during the merge window, but it
contains only fixes and hardware enablement. No fundamental chang
On 4/16/18 11:19 AM, Wei Xu wrote:
Add a new lightnvm quirk to identify CNEX’s Granby controller.
Signed-off-by: Wei Xu
---
drivers/nvme/host/pci.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index cb73bc8..9419e88 100644
--- a/dri
The patch
ASoC: topology: Modify clock gating parameter parsing to switch
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Wed, Apr 11, 2018 at 04:15:54PM +0200, Peter Rosin wrote:
> This is a current sense amplifier from Analog Devices.
>
> Signed-off-by: Peter Rosin
> ---
> .../devicetree/bindings/iio/afe/adi,lt6106.txt | 50
> ++
> MAINTAINERS|
On Mon, 16 Apr 2018 11:30:06 -0700
Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 11:26 AM, Steven Rostedt wrote:
> >
> > The problem is that it only fixed a critical bug, but didn't go far
> > enough to keep the bug fix from breaking API.
>
> An API breakage that gets noticed *is* a crtitic
On Mon, Apr 16, 2018 at 11:35 AM, Mathieu Desnoyers
wrote:
> Specifically for single-stepping, the __rseq_table section introduced
> at user-level will allow newer debuggers and tools which do line and
> instruction-level single-stepping to skip over rseq critical sections.
> However, this breaks
On Mon, Apr 16, 2018 at 10:53:23PM +0500, ahsan_huss...@mentor.com wrote:
> From: Ahsan Hussain
>
> Upstream commit 8d008c0c ("hwmon: (ina2xx) Make calibration register
> value fixed"), makes ina2xx_set_shunt() call mutex_lock on an
> un-initialized mutex. Initialize it prior so we don't get a NU
301 - 400 of 1099 matches
Mail list logo