From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A2032C282D7 for ; Wed, 30 Jan 2019 17:52:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 792762087F for ; Wed, 30 Jan 2019 17:52:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548870726; bh=nwPDXFqT+jGX8Jyo78XGFQonJo9DJU5OfWvYCWfhv0M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=UDJTWwUBldUIk+W5Dk5psAJ2thJkQLioSjvWRis+62KFKC2AXedK+NGoFv6j4d/Gy Pn3mxH+GhqoNLTHbgTnJvEl7f7RcT4helw18Caea1LEmQz2GOPBVg6ej0/3j2gE9Vk 2guScjkKJ3wwGLVfo/SDk3f0e1GOYWGStTDAMHeE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729636AbfA3RwG (ORCPT ); Wed, 30 Jan 2019 12:52:06 -0500 Received: from mail.kernel.org ([198.145.29.99]:40890 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727169AbfA3RwF (ORCPT ); Wed, 30 Jan 2019 12:52:05 -0500 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 22F562087F; Wed, 30 Jan 2019 17:52:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548870724; bh=nwPDXFqT+jGX8Jyo78XGFQonJo9DJU5OfWvYCWfhv0M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=TaeVLOwbey8c056aUDkIyb8NSD8pmKK8y9NgxvAwfsY1IFtdtUPsAUssJv7/aq0W4 n9P0tLkVy3nRHu8MLfgsylMW75ncQVZ7E/BTy3yOlP7IDbf3VV4jzSCBjuXdAcSNgp EgqrZpQncA67dLq4FKJENlazGpLxMl7dd/O+POkQ= Date: Wed, 30 Jan 2019 12:52:02 -0500 From: Sasha Levin To: Jiri Kosina Cc: Vladis Dronov , stable@vger.kernel.org Subject: Re: [PATCH v3] HID: debug: fix the ring buffer implementation Message-ID: <20190130175202.GS3973@sasha-vm> References: <20190129105835.4723-1-vdronov@redhat.com> <20190130144646.2C96A218A4@mail.kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Jan 30, 2019 at 05:59:43PM +0100, Jiri Kosina wrote: >On Wed, 30 Jan 2019, Sasha Levin wrote: > >> Hi, >> >> [This is an automated email] >> >> This commit has been processed because it contains a "Fixes:" tag, >> fixing commit: cd667ce24796 HID: use debugfs for events/reports dumping. >> >> The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96, v4.9.153, v4.4.172, v3.18.133. >> >> v4.20.5: Build OK! >> v4.19.18: Build OK! >> v4.14.96: Failed to apply! Possible dependencies: >> 0eecc636e5a2 ("bus: ti-sysc: Add minimal TI sysc interconnect target driver") >> 49a0a3d805df ("bus: ti-sysc: Make omap_hwmod_sysc_fields into sysc_regbits platform data") >> 566a9b05e1fa ("bus: ti-sysc: Handle module quirks based dts configuration") >> 6396bb221514 ("treewide: kzalloc() -> kcalloc()") >> 695eea3d2c7f ("ARM: OMAP2+: Enable ti-sysc to use device tree data for smartreflex") >> 70a65240efb1 ("bus: ti-sysc: Add register bits for interconnect target modules") >> a7199e2b91de ("bus: ti-sysc: Detect i2c interconnect target module based on register layout") >> bf8070522298 ("ARM: OMAP2+: Move all omap_hwmod_sysc_fields to omap_hwmod_common_data.c") >> c5a2de97fbd2 ("bus: ti-sysc: Add parsing of module capabilities") >> d060b40523dc ("ARM: OMAP2+: Prepare to pass auxdata for smartreflex") >> ef70b0bdeaf8 ("bus: ti-sysc: Add support for platform data callbacks") >> >> v4.9.153: Failed to apply! Possible dependencies: >> 174cd4b1e5fb ("sched/headers: Prepare to move signal wakeup & sigpending methods from into ") >> 1cec20f0ea0e ("dma-buf: Restart reservation_object_wait_timeout_rcu() after writes") >> 555570d744f8 ("sched/clock: Update static_key usage") >> 78010cd9736e ("dma-buf/fence: add an lockdep_assert_held()") >> 983de5f97169 ("firmware: tegra: Add BPMP support") >> 9881b024b7d7 ("sched/clock: Delay switching sched_clock to stable") >> acb04058de49 ("sched/clock: Fix hotplug crash") >> ae7e81c077d6 ("sched/headers: Prepare for new header dependencies before moving code to ") >> b52992c06c90 ("drm/i915: Support asynchronous waits on struct fence from i915_gem_request") >> ca791d7f4256 ("firmware: tegra: Add IVC library") >> e601757102cf ("sched/headers: Prepare for new header dependencies before moving code to ") >> ea8b1c4a6019 ("drivers: psci: PSCI checker module") >> f54d1867005c ("dma-buf: Rename struct fence to dma_fence") >> fedf54132d24 ("dma-buf: Restart reservation_object_get_fences_rcu() after writes") >> >> v4.4.172: Failed to apply! Possible dependencies: >> 0529900a01cb ("crypto: omap-aes - Support crypto engine framework") >> 0bc40be85f33 ("drm/i915: Rename intel_engine_cs function parameters") >> 174cd4b1e5fb ("sched/headers: Prepare to move signal wakeup & sigpending methods from into ") >> 2589ad84047f ("crypto: engine - move crypto engine to its own header") >> 4cba7cf025f3 ("crypto: engine - permit to enqueue ashash_request") >> 735d37b5424b ("crypto: engine - Introduce the block request crypto engine framework") >> ae7e81c077d6 ("sched/headers: Prepare for new header dependencies before moving code to ") >> c81d46138da6 ("drm/i915: Convert trace-irq to the breadcrumb waiter") >> ca82580c9cea ("drm/i915: Do not call API requiring struct_mutex where it is not available") >> cbdc12a9fc9d ("drm/i915: make A0 wa's applied to A1") >> e87a005d90c3 ("drm/i915: add helpers for platform specific revision id range checks") >> ea8b1c4a6019 ("drivers: psci: PSCI checker module") >> ef712bb4b700 ("drm/i915: remove parens around revision ids") >> f1b77aaca85a ("crypto: omap-des - Integrate with the crypto engine framework") >> fffda3f4fb49 ("drm/i915/bxt: add revision id for A1 stepping and use it") >> >> v3.18.133: Failed to apply! Possible dependencies: >> 00aa37206e1a ("of/reconfig: Add debug output for OF_RECONFIG notifiers") >> 0529900a01cb ("crypto: omap-aes - Support crypto engine framework") >> 174cd4b1e5fb ("sched/headers: Prepare to move signal wakeup & sigpending methods from into ") >> 2589ad84047f ("crypto: engine - move crypto engine to its own header") >> 310b0d55f030 ("crypto: omap-aes - Fix CTR mode") >> 4cba7cf025f3 ("crypto: engine - permit to enqueue ashash_request") >> 596103cf8fb0 ("crypto: drivers - Fix Kconfig selects") >> 6c5063434098 ("crypto: ccp - Add ACPI support") >> 7011a122383e ("crypto: nx - add NX-842 platform frontend driver") >> 735d37b5424b ("crypto: engine - Introduce the block request crypto engine framework") >> 8c98ebd7a6ff ("crypto: img-hash - CRYPTO_DEV_IMGTEC_HASH should depend on HAS_DMA") >> a5bd093af0d1 ("crypto: ccp - Update CCP build support") >> ae7e81c077d6 ("sched/headers: Prepare for new header dependencies before moving code to ") >> b53a2340d0d3 ("of/reconfig: Add of_reconfig_get_state_change() of notifier helper.") >> cfa8e7e70341 ("crypto: img-hash - Fix Kconfig selections") >> d2e3ae6f3aba ("crypto: vmx - Enabling VMX module for PPC64") >> d358f1abbf71 ("crypto: img-hash - Add Imagination Technologies hw hash accelerator") >> f1b77aaca85a ("crypto: omap-des - Integrate with the crypto engine framework") >> f5242e5a883b ("of/reconfig: Always use the same structure for notifiers") >> f6892d193fb9 ("of/reconfig: Add empty stubs for the of_reconfig methods") >> fdd05e4b9ae2 ("crypto: nx - rename nx-842.c to nx-842-pseries.c") > >FWIW the list of possible dependencies looks completely confused. If this >is not some interminnent bug, the way how it's generated should probably >be revisited. It's actually somewhat accurate, but useless in this case :) The reason for that mess is that on <=4.14 kernels, there is a dependency on 6396bb22151 ("treewide: kzalloc() -> kcalloc()"), but since that patch is a treewide change, to bring that in we need a big pile of seemingly random patches from all over the tree, which is the output you see. -- Thanks, Sasha