On Wed, Oct 19, 2016 at 05:21:13PM +0200, Jerome Brunet wrote:
>
> This commit adds the device tree bindings description for Amlogic's GPIO
> interrupt controller available on the meson8, meson8b and gxbb SoC families
>
> Signed-off-by: Jerome Brunet
> ---
> Rob, I did not include the Ack you ga
On Sat, 22 Oct 2016, Fenghua Yu wrote:
> This version should cover all comments from Thomas.
Emphasis on should :)
But this series is a major step forward and I decided to merge the first
lot:
> 0001-Documentation-ABI-Add-a-document-entry-for-cache-id.patch
> 0002-cacheinfo-Introduce-cache-id.p
On Wed, Oct 26, 2016 at 09:53:45PM +0200, Radim Krčmář wrote:
> 2016-10-14 20:21+0200, Paolo Bonzini:
> > On some benchmarks (e.g. netperf with ioeventfd disabled), APICv
> > posted interrupts turn out to be slower than interrupt injection via
> > KVM_REQ_EVENT.
> >
> > This patch optimizes a bit
2016-10-26 Brian Starkey :
> If userspace has asked for an out-fence for the writeback, we add a
> fence to malidp_mw_job, to be signaled when the writeback job has
> completed.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/arm/malidp_hw.c |5 -
> drivers/gpu/drm/arm/malidp_m
On Wed, Oct 19, 2016 at 01:51:43PM -0400, Sinan Kaya wrote:
> Adding a new binding for qcom,hidma-1.1 to distinguish HW supporting
> MSI interrupts from the older revision.
>
> Signed-off-by: Sinan Kaya
> ---
> Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt | 8 +++-
> 1 file chan
2016-10-26 Brian Starkey :
> Some parts of setting up the CRTC out-fence can be re-used for
> writeback out-fences. Factor this out into a separate function.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/drm_atomic.c | 64
> +++---
> 1 file chan
On Wed, 26 Oct 2016, Darren Hart wrote:
> On Mon, Oct 24, 2016 at 01:38:54PM +, Tirdea, Irina wrote:
> > intel_pmc_* drivers or is it enough to move it as a standalone driver for
> > now?
>
> If the functionality is substantially different, then I don't see a
> compelling, and certainly not a
On Wed, Oct 26, 2016 at 02:21:43PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.28 release.
> There are 112 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Wed, Oct 26, 2016 at 02:21:00PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.8.5 release.
> There are 140 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Wed, Oct 19, 2016 at 04:45:48AM -0700, Paul E. McKenney wrote:
> On Sun, Oct 16, 2016 at 05:29:24AM +0300, Michael S. Tsirkin wrote:
> > On Sat, Oct 15, 2016 at 03:47:45AM -0400, Paolo Bonzini wrote:
> > >
> > > > > On Oct 14, 2016, at 11:56 AM, Paolo Bonzini
> > > > > wrote:
> > > > >>>
> >
On 10/26/2016 12:36 PM, Jon Mason wrote:
> Add support for the variant of amac hardware present in the Broadcom
> Northstar2 based SoCs. Northstar2 requires an additional register to be
> configured with the port speed/duplexity (NICPM). This can be added to
> the link callback to hide it from th
Hi Meelis,
On Wed, Oct 07, 2015 at 12:25:19PM +0300, Meelis Roos wrote:
> First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation
> was failing for qla1280 scsi driver. Reading dmesg uncovered "can't
> claim BAR" errors. Looking for this in my other test machines I see more
> of
On Fri, Oct 14, 2016 at 08:21:26PM +0200, Paolo Bonzini wrote:
> On some benchmarks (e.g. netperf with ioeventfd disabled), APICv
> posted interrupts turn out to be slower than interrupt injection via
> KVM_REQ_EVENT.
>
> These patches save 40 cycles on kvm-unit-tests "inl" tests (1-2%), but I
> s
On 10/26/2016 04:00 PM, Chris Mason wrote:
>
>
> On 10/26/2016 03:06 PM, Linus Torvalds wrote:
>> On Wed, Oct 26, 2016 at 11:42 AM, Dave Jones wrote:
>>>
>>> The stacks show nearly all of them are stuck in sync_inodes_sb
>>
>> That's just wb_wait_for_completion(), and it means that some IO isn
On Wed, Oct 26, 2016 at 11:39:47PM +0200, Thomas Gleixner wrote:
> On Sat, 22 Oct 2016, Fenghua Yu wrote:
> > This version should cover all comments from Thomas.
>
> Emphasis on should :)
>
> But this series is a major step forward and I decided to merge the first
> lot:
>
> > 0001-Documentatio
On 10/26/2016 5:45 PM, Rob Herring wrote:
> On Wed, Oct 19, 2016 at 01:51:43PM -0400, Sinan Kaya wrote:
>> Adding a new binding for qcom,hidma-1.1 to distinguish HW supporting
>> MSI interrupts from the older revision.
>>
>> Signed-off-by: Sinan Kaya
>> ---
>> Documentation/devicetree/bindings/dm
On Wed, Oct 26, 2016 at 08:11:28PM +0200, Heiner Kallweit wrote:
> Instead it should be:
>
> if (rx_nr_bytes && mspi->rx) {
> *(u32 *)mspi->rx = rx_data;
> mspi->rx += 4;
> }
Please send a patch.
signature.asc
Description: PGP signature
On Mon, Oct 24, 2016 at 12:00 PM, Kevin Hilman wrote:
> Dave Gerlach writes:
>
>> Hi,
>> On 10/21/2016 01:48 PM, Kevin Hilman wrote:
>>> Dave Gerlach writes:
>>>
Add a generic power domain implementation, TI SCI PM Domains, that
will hook into the genpd framework and allow the TI SCI p
On Wed, Oct 26, 2016 at 11:43:24PM +0200, Thomas Gleixner wrote:
> On Wed, 26 Oct 2016, Darren Hart wrote:
> > On Mon, Oct 24, 2016 at 01:38:54PM +, Tirdea, Irina wrote:
> > > intel_pmc_* drivers or is it enough to move it as a standalone driver for
> > > now?
> >
> > If the functionality is
On Wed, Oct 26, 2016 at 02:26:57PM -0700, Linus Torvalds wrote:
> On Wed, Oct 26, 2016 at 1:31 PM, Mel Gorman
> wrote:
> >
> > IO wait activity is not all that matters. We hit the lock/unlock paths
> > during a lot of operations like reclaim.
>
> I doubt we do.
>
> Yes, we hit the lock/unlock i
On Wed, Oct 26, 2016 at 1:00 PM, Chris Mason wrote:
>
> Today I turned off every CONFIG_DEBUG_* except for list debugging, and
> ran dbench 2048:
>
> [ 2759.118711] WARNING: CPU: 2 PID: 31039 at lib/list_debug.c:33
> __list_add+0xbe/0xd0
> [ 2759.119652] list_add corruption. prev->next should be
On Tue, Oct 25, 2016 at 11:26:28AM +1100, Stephen Rothwell wrote:
> Hi Maxime,
>
> After merging the sunxi tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> ERROR (phandle_references): Reference to non-existent node or label
> "pwm1_pins_a"
> ERROR: Input tree has e
Hi Stephen,
On Tue, Oct 25, 2016 at 09:22:55AM +1100, Stephen Rothwell wrote:
> Hi Maxime,
>
> In today's sunxi tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git#sunxi/for-next)
> I noticed that commit
>
> 3861b711f8b5 ("ARM: sun5i: chip: add a node for the w1 gpio contro
Hi,
On Tue, Oct 25, 2016 at 12:11:38PM +0800, Icenowy Zheng wrote:
> On some newer Allwinner SoCs (H3 or A64), the PHY0 can be either routed to
> the MUSB controller (which is an OTG controller) or the OHCI/EHCI pair
> (which is a Host-only controller, but more stable and easy to implement).
>
>
On Wed, Oct 19, 2016 at 07:38:10PM -0700, Bjorn Andersson wrote:
> The label property can be used to specify a name of the edge, for
> consistent naming purposes.
>
> Signed-off-by: Bjorn Andersson
> ---
> Documentation/devicetree/bindings/soc/qcom/qcom,smd.txt | 7 +++
> 1 file changed, 7 i
On Wed, Oct 26, 2016 at 12:00:30AM -0700, Alexandru Gagniuc wrote:
> This is the seventh attempt to get this patch in. I was prompted to look
> into this again as someone recently remarked:
>
> " cool, to bad spi does not work properly on allwinner..."
>
> Two and a half years ago, we were told
Hi Linus,
On Tue, Oct 25, 2016 at 02:07:27PM +0200, Linus Walleij wrote:
> On Mon, Oct 24, 2016 at 9:49 PM, Maxime Ripard
> wrote:
>
> > However, it looks like the first patch from this serie is missing from
> > your tree, is there a reason for that?
>
> No can you point it out?
Sure:
http://l
On Tue, Oct 25, 2016 at 12:10:26PM +0800, Chen-Yu Tsai wrote:
> On Fri, Oct 21, 2016 at 1:07 AM, Maxime Ripard
> wrote:
> > On Thu, Oct 20, 2016 at 10:10:03PM +0800, Chen-Yu Tsai wrote:
> >> On Thu, Oct 20, 2016 at 4:12 PM, Maxime Ripard
> >> wrote:
> >> > The PWM controller has two different cha
On Tue, Oct 25, 2016 at 07:38:55AM +0200, LABBE Corentin wrote:
> On Mon, Oct 24, 2016 at 10:10:20PM +0200, Maxime Ripard wrote:
> > On Sat, Oct 22, 2016 at 03:53:28PM +0200, Corentin Labbe wrote:
> > > Since SID's content is constant over reboot,
> >
> > That's not true, at least not across all t
On Thu, Oct 20, 2016 at 11:43:37AM +0800, Chen-Yu Tsai wrote:
> Some rgb-to-vga bridges have an enable GPIO, either directly tied to
> an enable pin on the bridge IC, or indirectly controlling a power
> switch.
>
> Add support for it.
>
> Signed-off-by: Chen-Yu Tsai
> ---
> .../bindings/display
Hi,
On Tue, Oct 25, 2016 at 11:32:44AM +0800, Icenowy Zheng wrote:
>
>
> > On Mon, Oct 24, 2016 at 11:59:30AM +0800, Icenowy Zheng wrote:
> >
> >> Allwinner SoC's PHY 0, when used as OTG controller, have no pmu part.
> >> The code that poke some unknown bit of PMU for H3/A64 didn't check
> >> t
Hi Rob,
On Wed, Oct 26, 2016 at 05:13:46PM -0500, Rob Herring wrote:
> On Thu, Oct 20, 2016 at 11:43:37AM +0800, Chen-Yu Tsai wrote:
> > Some rgb-to-vga bridges have an enable GPIO, either directly tied to
> > an enable pin on the bridge IC, or indirectly controlling a power
> > switch.
> >
> > A
> The AHCI MSI handling change in rc1 was a bit broken and caused disk
> probing failures on some machines. These three patches should fix the
> issues.
My test machine fell foul of this using a PCIe M.2-attached SSD card.
The patches fix it for me.
Tested-by: David Howells
There has been some significant rework around
__alloc_pages_nodemask(), adding Mel and linux-mm.
-Robert
On 26.10.16 10:00:02, David Daney wrote:
> On 10/26/2016 06:43 AM, Robert Richter wrote:
> >On 25.10.16 14:31:00, David Daney wrote:
> >>From: David Daney
> >>
> >>On arm64 NUMA kernels we ca
On Wed, Oct 26, 2016 at 12:39 PM, Andrew Morton
wrote:
> On Wed, 26 Oct 2016 19:09:51 +0100 Will Deacon wrote:
>
>> On Tue, Oct 25, 2016 at 11:36:44AM -0700, Daniel Mentz wrote:
>> > gen_pool_alloc_algo() iterates over the chunks of a pool trying to find
>> > a contiguous block of memory that sat
On Thu, Oct 20, 2016 at 05:15:40PM +0800, zhichang.yuan wrote:
> On Hip06, the accesses to LPC peripherals work in an indirect way. A
> corresponding LPC driver configure some registers in LPC master at first, then
> the real accesses on LPC slave devices are finished by the LPC master, which
> is
On Tue, Oct 25, 2016 at 02:30:25PM +0300, Adrian Hunter wrote:
> On 24/10/16 18:48, Zach Brown wrote:
> > On Mon, Oct 24, 2016 at 10:34:46AM +0300, Adrian Hunter wrote:
> >> On 22/10/16 00:35, Zach Brown wrote:
> >>> When the sdhci-cap-speed-modes-broken DT property is set, the driver
> >>> will ig
On Tue, Oct 25, 2016 at 3:34 AM, tip-bot for Borislav Petkov
wrote:
> Commit-ID: 59c6f278bdeea4147e8be92a3ed50a9907e60088
> Gitweb: http://git.kernel.org/tip/59c6f278bdeea4147e8be92a3ed50a9907e60088
> Author: Borislav Petkov
> AuthorDate: Mon, 24 Oct 2016 19:38:44 +0200
> Committer: Ing
SLUB has better debugging support.
Signed-off-by: Nitin Gupta
---
arch/sparc/configs/sparc64_defconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/sparc/configs/sparc64_defconfig
b/arch/sparc/configs/sparc64_defconfig
index 3583d67..0a615b0 100644
--- a/arch/spar
On Thu, Oct 20, 2016 at 05:15:39PM +0800, zhichang.yuan wrote:
> Currently if the range property is not specified of_translate_one
> returns an error. There are some special devices that work on a
> range of I/O ports where it's is not correct to specify a range
> property as the cpu addresses are
On Wed, Oct 26, 2016 at 2:52 PM, Chris Mason wrote:
>
> This one is special because CONFIG_VMAP_STACK is not set. Btrfs triggers in
> < 10 minutes.
> I've done 30 minutes each with XFS and Ext4 without luck.
Ok, see the email I wrote that crossed yours - if it's really some
list corruption on c
On Tue, Oct 25, 2016 at 01:08:31AM +0800, Icenowy Zheng wrote:
> When the patch is applied, the allwinner,driver and allwinner,pull
> properties are removed.
>
> Although they're described to be optional in the devicetree binding,
> without them, the pinmux cannot be initialized, and the uart cann
On Wed, Oct 26, 2016 at 3:03 PM, Mel Gorman wrote:
>
> To be clear, are you referring to PeterZ's patch that avoids the lookup? If
> so, I see your point.
Yup, that's the one. I think you tested it. In fact, I'm sure you did,
because I remember seeing performance numbers from you ;)
So yes, I'd
On Wed, Oct 26, 2016 at 03:21:53PM -0700, Linus Torvalds wrote:
> Could you try the attached patch? It adds a couple of sanity tests:
>
> - a number of tests to verify that 'rq->queuelist' isn't already on
> some queue when it is added to a queue
>
> - one test to verify that rq->mq_ctx
On Wed, Oct 26, 2016 at 02:30:49PM -0700, Linus Torvalds wrote:
> Ok, similar issue, I think - passing a non-1:1 address to __phys_addr().
>
> But the call trace has nothing to do with gfs2 or the bitlocks:
>
> > [2.504561] Call Trace:
> > [2.507005] save_microcode_in_initrd_amd+0x31/0x
The r8152 driver has been broken since (approx) 3.6.16,
when support was added for hardware rx checksum on newer chip versions.
Symptoms include random segfaults and silent data corruption over NFS.
This does not work on the VER_02 dongle I have here
when used with a slow embedded system CPU.
Goo
On Wed, Oct 26, 2016 at 05:56:39PM +0100, Steve Twiss wrote:
> From: Steve Twiss
>
> Copyright header is updated to add DA9061 in its description and the module
> description macro is extended to include DA9061.
>
> Minor change to the code, alters dev_dbg() statements to report a generic
> "PMI
On Wed, Oct 26, 2016 at 3:40 PM, Dave Jones wrote:
>
> I gave it a shot too for shits & giggles.
> This falls out during boot.
>
> [9.278420] WARNING: CPU: 0 PID: 1 at block/blk-mq.c:1181
> blk_sq_make_request+0x465/0x4a0
Hmm. That's the
WARN_ON_ONCE(rq->mq_ctx != ctx);
that I added to
On Wed, 26 Oct 2016, Richard Cochran wrote:
> On Wed, Oct 26, 2016 at 09:56:13AM -0400, Nicolas Pitre wrote:
> > So if my Fedora usage doesn't need them, we can infer that
> > the number of embedded systems also not needing them might tend towards
> > a high percentage.
>
> (I wouldn't call Fed
On Wed, Oct 19, 2016 at 03:33:45PM -0500, Dave Gerlach wrote:
> Add a generic power domain implementation, TI SCI PM Domains, that
> will hook into the genpd framework and allow the TI SCI protocol to
> control device power states.
>
> Also, provide macros representing each device index as underst
On 10/26/2016 04:40 PM, Dave Jones wrote:
On Wed, Oct 26, 2016 at 03:21:53PM -0700, Linus Torvalds wrote:
> Could you try the attached patch? It adds a couple of sanity tests:
>
> - a number of tests to verify that 'rq->queuelist' isn't already on
> some queue when it is added to a queue
>
Hi Richard,
On 2016-10-25 22:50, Richard Weinberger wrote:
> Peter,
>
> On 25.10.2016 22:09, Richard Weinberger wrote:
>>> /bin/mkdir -p /mnt/ovl/ovl
>>> /bin/mkdir -p /mnt/ovl/work
>>> # with c83ed4c9dbb3, the following mount fails with
>>> # mount: mounting overlay on /mnt/merge failed: No such
On 16-10-26 06:36 PM, Mark Lord wrote:
The r8152 driver has been broken since (approx) 3.6.16,
Correction: broken since 3.16.xx.
when support was added for hardware rx checksum on newer chip versions.
Symptoms include random segfaults and silent data corruption over NFS.
This does not work
Hi,
I was playing around with overflowing stacks and I managed to generate a test
case that hung the kernel with vmapped stacks. The test case is just
static void noinline foo1(void)
{
pr_info("%p\n", (void *)current_stack_pointer());
foo2();
}
where foo$n is the same function wit
On 10/26/2016 04:51 PM, Linus Torvalds wrote:
On Wed, Oct 26, 2016 at 3:40 PM, Dave Jones wrote:
I gave it a shot too for shits & giggles.
This falls out during boot.
[9.278420] WARNING: CPU: 0 PID: 1 at block/blk-mq.c:1181
blk_sq_make_request+0x465/0x4a0
Hmm. That's the
WARN_ON_O
On Wed, Oct 26, 2016 at 3:51 PM, Linus Torvalds
wrote:
>
> Dave: it might be a good idea to split that "WARN_ON_ONCE()" in
> blk_mq_merge_queue_io() into two
I did that myself too, since Dave sees this during boot.
But I'm not getting the warning ;(
Dave gets it with ext4, and thats' what I hav
On Tue, Oct 25, 2016 at 11:59:22AM +0200, Arnd Bergmann wrote:
> On Monday, October 24, 2016 4:45:13 PM CEST Dmitry Torokhov wrote:
> > > diff --git a/drivers/input/keyboard/tca8418_keypad.c
> > > b/drivers/input/keyboard/tca8418_keypad.c
> > > index 9002298698fc..3048ef3e3e16 100644
> > > --- a/d
On Wed, Oct 26, 2016 at 03:51:01PM -0700, Linus Torvalds wrote:
> Dave: it might be a good idea to split that "WARN_ON_ONCE()" in
> blk_mq_merge_queue_io() into two, since right now it can trigger both
> for the
>
> blk_mq_bio_to_request(rq, bio);
>
> path _and_ for the
>
On 10/26/2016 05:01 PM, Dave Jones wrote:
On Wed, Oct 26, 2016 at 03:51:01PM -0700, Linus Torvalds wrote:
> Dave: it might be a good idea to split that "WARN_ON_ONCE()" in
> blk_mq_merge_queue_io() into two, since right now it can trigger both
> for the
>
> blk_mq_bio_to_requ
On 10/26/2016 04:58 PM, Linus Torvalds wrote:
On Wed, Oct 26, 2016 at 3:51 PM, Linus Torvalds
wrote:
Dave: it might be a good idea to split that "WARN_ON_ONCE()" in
blk_mq_merge_queue_io() into two
I did that myself too, since Dave sees this during boot.
But I'm not getting the warning ;(
On Wed, Oct 26, 2016 at 05:03:45PM -0600, Jens Axboe wrote:
> On 10/26/2016 04:58 PM, Linus Torvalds wrote:
> > On Wed, Oct 26, 2016 at 3:51 PM, Linus Torvalds
> > wrote:
> >>
> >> Dave: it might be a good idea to split that "WARN_ON_ONCE()" in
> >> blk_mq_merge_queue_io() into two
> >
> >
On Wed, Oct 26, 2016 at 03:09:41PM -0700, Linus Torvalds wrote:
> On Wed, Oct 26, 2016 at 3:03 PM, Mel Gorman
> wrote:
> >
> > To be clear, are you referring to PeterZ's patch that avoids the lookup? If
> > so, I see your point.
>
> Yup, that's the one. I think you tested it. In fact, I'm sure y
On Wed, Oct 26, 2016 at 4:03 PM, Jens Axboe wrote:
>
> Actually, I think I see what might trigger it. You are on nvme, iirc,
> and that has a deep queue.
Yes. I have long since moved on from slow disks, so all my systems are
not just flash, but m.2 nvme ssd's.
So at least that could explain why
On Thu, Oct 20, 2016 at 02:59:16PM -0500, Franklin S Cooper Jr wrote:
> Some goodix touchscreen controllers aren't programed properly to match the
> display panel it is used on. Although the defaults may largely work it is
> also likely that the screen resolution will be incorrect. Therefore,
> add
+++ Jiri Kosina [26/10/16 10:17 +0200]:
On Wed, 26 Oct 2016, Rusty Russell wrote:
>> Hm, quick question, which tree would this patch go to? Though the
>> cleanup is for modules, there is an indirect cross-tree dependency
>> (taint_flag.module needs to be true for TAINT_LIVEPATCH for Josh's
>> p
On Wed, Oct 26, 2016 at 05:01:24PM -0400, Bob Peterson wrote:
> Hm. It didn't even boot, at least on my amd box in the lab.
> I've made no attempt to debug this.
Btw, can you send me your .config so that I can try to reproduce?
I'm assuming you're booting latest Linus' tree on it?
I'd need to ta
On Wed, Oct 26, 2016 at 03:07:10PM -0700, Linus Torvalds wrote:
On Wed, Oct 26, 2016 at 1:00 PM, Chris Mason wrote:
Today I turned off every CONFIG_DEBUG_* except for list debugging, and
ran dbench 2048:
[ 2759.118711] WARNING: CPU: 2 PID: 31039 at lib/list_debug.c:33
__list_add+0xbe/0xd0
[
On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> From: Nicolas Pitre
> Subject: [PATCH v2 0/5] make POSIX timers optional with some Kconfig help
This doesn't work. I received this message with an empty subject.
If you'll have to send another update don't bother including Yann. Yann
hasn
On Thu, Oct 20, 2016 at 02:59:17PM -0500, Franklin S Cooper Jr wrote:
> On systems with a fixed display/touchscreen orientation it is important to
> pass in the "correct" x and y coordinates based on the orientation.
> Currently, to support landscape and portrait touchscreen-swapped-x-y
> simply do
On Thu, Oct 20, 2016 at 07:42:45PM -0200, Sergio Prado wrote:
> Adds the device tree bindings description for Samsung S3C2410 and
> compatible NAND flash controller.
>
> Signed-off-by: Sergio Prado
> ---
> .../devicetree/bindings/mtd/samsung-s3c2410.txt| 56
> ++
> 1 fil
This will be the initial landing point for readers, so give them a bit of
introductory material. Also split the TOC into area-specific chunks to
make the whole thing a bit more approachable.
Signed-off-by: Jonathan Corbet
---
Documentation/index.rst | 45
This is ancient stuff and we don't do things this way anymore. In the
absence of simply deleting the document, at least add a warning to it.
Signed-off-by: Jonathan Corbet
---
Documentation/process/applying-patches.rst | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/proces
The admin guide is a good start, but it's time to turn it into something
better than an unordered blob of files. This is a first step in that
direction. The TOC has been split up and annotated, the guides have been
reordered, and minor tweaks have been applied to a few of them.
One consequence o
This is crufty stuff and should maybe just be deleted, but I'm not quite
ready to do that yet.
Signed-off-by: Jonathan Corbet
---
Documentation/process/submitting-drivers.rst | 8
1 file changed, 8 insertions(+)
diff --git a/Documentation/process/submitting-drivers.rst
b/Documentation
On 10/26/2016 05:08 PM, Linus Torvalds wrote:
On Wed, Oct 26, 2016 at 4:03 PM, Jens Axboe wrote:
Actually, I think I see what might trigger it. You are on nvme, iirc,
and that has a deep queue.
Yes. I have long since moved on from slow disks, so all my systems are
not just flash, but m.2 nvm
I believe this makes the page as a whole more approachable.
Signed-off-by: Jonathan Corbet
---
Documentation/process/index.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/process/index.rst b/Documentation/process/index.rst
index 0cbc62adbbb1..0557144ce
Larry McVoy's advice on how to manually bisect 1.3.x kernel bugs is of
historical interest, but that's what the repository is for. It is not
useful to users now.
Signed-off-by: Jonathan Corbet
---
Documentation/admin-guide/bug-hunting.rst | 249 --
Documentation/admi
On Wed, Oct 26, 2016 at 05:03:45PM -0600, Jens Axboe wrote:
On 10/26/2016 04:58 PM, Linus Torvalds wrote:
On Wed, Oct 26, 2016 at 3:51 PM, Linus Torvalds
wrote:
Dave: it might be a good idea to split that "WARN_ON_ONCE()" in
blk_mq_merge_queue_io() into two
I did that myself too, since Dave
Put like documents together, with the essential ones at the top, and split
the TOC into sections.
Signed-off-by: Jonathan Corbet
---
Documentation/process/changes.rst | 2 +-
Documentation/process/index.rst | 37 -
2 files changed, 29 insertions(+), 10 dele
The main goal here was to get the subsections to show in the TOC as they do
for all the other documents. Also call out the DCO in the section title
since it's important.
Signed-off-by: Jonathan Corbet
---
Documentation/process/submitting-patches.rst | 16 ++--
1 file changed, 6 inse
On Oct 26, 2016 12:21 PM, "David Herrmann" wrote:
>
> From: Tom Gundersen
>
> Add the CONFIG_BUS1 option to enable the bus1 kernel messaging bus. If
> enabled, provide the bus1.ko module with a stub cdev /dev/bus1. So far
> it does not expose any API, but the full intended uapi is provided in
> i
The document has not been touched in over 11 years and doesn't reflect how
profiling is done in the perf era.
Signed-off-by: Jonathan Corbet
---
Documentation/admin-guide/basic-profiling.rst | 68 ---
Documentation/admin-guide/index.rst | 1 -
2 files changed,
Let's make the title of this document (which shows up in the top page)
better describe its contents.
Cc: Jani Nikula
Signed-off-by: Jonathan Corbet
---
Documentation/kernel-documentation.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/kernel-documenta
On 10/26/2016 05:19 PM, Chris Mason wrote:
On Wed, Oct 26, 2016 at 05:03:45PM -0600, Jens Axboe wrote:
On 10/26/2016 04:58 PM, Linus Torvalds wrote:
On Wed, Oct 26, 2016 at 3:51 PM, Linus Torvalds
wrote:
Dave: it might be a good idea to split that "WARN_ON_ONCE()" in
blk_mq_merge_queue_io()
The creation of the admin and process guides is a great thing, but, without
care, we risk replacing a messy docs directory with a few messy Sphinx
books. In an attempt to head that off and show what I'm thinking, here's a
set of tweaks that, I think, make the existing Sphinx-formatted docs a bit
m
The last release of this tool was for 2.6.28; it's hard to see how it has
any relevance to current kernels.
Signed-off-by: Jonathan Corbet
---
Documentation/admin-guide/bad-memory.rst | 50
Documentation/admin-guide/index.rst | 1 -
2 files changed, 51 dele
On 10/26/2016 08:05 AM, Benjamin Gaignard wrote:
2016-10-26 16:44 GMT+02:00 Sumit Semwal :
On 26 October 2016 at 20:11, Benjamin Gaignard
wrote:
2016-10-26 15:51 GMT+02:00 Sumit Semwal :
Hello Benjamin,
On 26 October 2016 at 19:02, Benjamin Gaignard
wrote:
It is more or less a copy of Hisi
On Thu, Oct 13, 2016 at 01:23:30PM +0200, Benjamin Tissoires wrote:
> it's always easier to retrieve these information in bug reports when
> it is always printed in the dmesg.
>
> Signed-off-by: Benjamin Tissoires
Applied, thank you.
>
> ---
>
> changes in v2:
> - split the version informatio
On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> SUBSYSTEM_X can still be configured out, and it can be set as a
> module when none of the drivers are selected or all of them are also
> modular.
Short note, to highlight a pet peeve: "select" (and therefor
"selected") has a special meani
The cleanup_if() callback is the inverse of init_if(). We allocate our
'card' interface structure in the probe() function, but we free it in
cleanup_if(). That gives a few problems:
(a) we leak this memory if probe() fails before we reach init_if()
(b) we can't safely utilize 'card' after cleanup_i
Initial pinctrl driver for QCOM msm8994 platforms.
In order to continue the initial board support for QCOM msm8994/msm8992
presented in patches from Jeremy McNicoll , let's put
a proper pinctrl driver in place.
Currently, the DT for these platforms uses the msm8x74 pinctrl driver to enable
basic
On Wed, Oct 26, 2016 at 3:55 PM, Laura Abbott wrote:
>
> I was playing around with overflowing stacks and I managed to generate a
> test
> case that hung the kernel with vmapped stacks. The test case is just
>
> static void noinline foo1(void)
> {
>pr_info("%p\n", (void *)current_stack_poi
On Wed, 2016-10-26 at 14:56 +0200, Uwe Kleine-König wrote:
> Hello,
>
> these were found by
>
> git grep -i 0x%[lh]*[du]
>
> Maybe it would make sense to catch this type of unconvenience in
> checkpatch?
Already there.
On Wed, Oct 26, 2016 at 04:29:20PM -0700, Brian Norris wrote:
> The cleanup_if() callback is the inverse of init_if(). We allocate our
> 'card' interface structure in the probe() function, but we free it in
> cleanup_if(). That gives a few problems:
> (a) we leak this memory if probe() fails before
On Wed, Oct 26, 2016 at 05:20:01PM -0600, Jens Axboe wrote:
On 10/26/2016 05:08 PM, Linus Torvalds wrote:
On Wed, Oct 26, 2016 at 4:03 PM, Jens Axboe wrote:
Actually, I think I see what might trigger it. You are on nvme, iirc,
and that has a deep queue.
Yes. I have long since moved on from
On Thu, 27 Oct 2016, Paul Bolle wrote:
> On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> > From: Nicolas Pitre
> > Subject: [PATCH v2 0/5] make POSIX timers optional with some Kconfig help
>
> This doesn't work. I received this message with an empty subject.
Hmmm... must have dome som
Hi Maxime,
On Tue, 25 Oct 2016 11:44:09 +0200 Maxime Ripard
wrote:
>
> On Tue, Oct 25, 2016 at 09:22:55AM +1100, Stephen Rothwell wrote:
> > Hi Maxime,
> >
> > In today's sunxi tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git#sunxi/for-next)
> > I noticed that commit
>
On Thu, 27 Oct 2016, Paul Bolle wrote:
> On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> > SUBSYSTEM_X can still be configured out, and it can be set as a
> > module when none of the drivers are selected or all of them are also
> > modular.
>
> Short note, to highlight a pet peeve: "s
On Wed, Oct 26, 2016 at 04:35:54PM -0700, Dmitry Torokhov wrote:
> On Wed, Oct 26, 2016 at 04:29:20PM -0700, Brian Norris wrote:
> > diff --git a/drivers/net/wireless/marvell/mwifiex/sdio.c
> > b/drivers/net/wireless/marvell/mwifiex/sdio.c
> > index 8718950004f3..f04cf5a551b3 100644
> > --- a/dri
On Fri, Oct 14, 2016 at 01:00:18PM -0300, Javier Martinez Canillas wrote:
> If the driver is built as a module, autoload won't work because the module
> alias information is not filled. So user-space can't match the registered
> device with the corresponding module.
>
> Export the module alias inf
201 - 300 of 1294 matches
Mail list logo
