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.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,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 3A64CC43381 for ; Sat, 9 Mar 2019 08:29:41 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D0C4F20866 for ; Sat, 9 Mar 2019 08:29:40 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="OwmXzwdq"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="EafySVFn" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D0C4F20866 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kroah.com Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1h2XLz-0006qV-Qw; Sat, 09 Mar 2019 03:29:11 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1h2XLx-0006qP-ER for kernelnewbies@kernelnewbies.org; Sat, 09 Mar 2019 03:29:10 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 837ED21EED; Sat, 9 Mar 2019 03:29:07 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sat, 09 Mar 2019 03:29:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=+bs90CpjYQlgi2SZhigtWbPqSFy p9OL68ERJqjRentM=; b=OwmXzwdqtiM6Df1uBvIYSaCupS5e6i+AhxZaeQObW5T 7tYNZr6e+NEDHL/UWTCeavgd+WVt0laIPQe2d/0XxPMG5Ng+0UGBYg44S0NYrjxh 1pvKKlc4NG8AJQlArWKO2YD3EQ/xiwKtMB34K84iQ1HQNWwN61BWSEn24p8kWdeQ 7uSDbBLuSbbZbm9hE6aHN36yEPYyOZHmR7jrNONfLDtH3P/sXenH8QzHqMrbFdyB 8HE46DyWXeVUGEJXLxnzcYW+oYNeCO4rOnpum2nJ6dTI5xE8HFTAxn1Vv81BXxFd TMiD4jRzDZDaV/7PMg9vWrVi/LBY+WWrI5SEeiRrzcg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=+bs90C pjYQlgi2SZhigtWbPqSFyp9OL68ERJqjRentM=; b=EafySVFnNzjkS+CZqZymig PvgxHE8AK8zXcWpb2Jsruv6MuLaqc4bhbiA9skN0w0nIi1rd8+iFFWpYlSJ5x/fX /X3f72DrP3hcEOaqvh08bCjoPZ6shufrzBen9sX0TlYFdfYvLyGNurPVz91WwBFM sLdcqEX14Fop7VnTMPpJL6phzbKh9KX+kPbFKxxIcx1lhaBNwPGj7Xv8mdgo2ZT+ E5wgRC44yx26vGJHNAJu6s0JUrqENZ9HKIeSvTPg8+Bm+jZzyf4OAptLCBg3EB9k 0FU4mRXFaZwpAAgLKz9mDmrlislsu6CAZ8xWo5peZIGn9A+2RXJXJJsC2npwR46g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgedugdduvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecukfhppeekfedrkeeirdekledrud dtjeenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhmnecu vehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (5356596b.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 76D98100E5; Sat, 9 Mar 2019 03:29:06 -0500 (EST) Date: Sat, 9 Mar 2019 09:29:04 +0100 From: Greg KH To: Andy Nicholas Subject: Re: Finding all modules which consume kernel lib? Message-ID: <20190309082904.GA12998@kroah.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Sat, Mar 09, 2019 at 12:07:00AM -0800, Andy Nicholas wrote: > Hello, > > Is there a website or service or tool or package or script or something > which allows me to determine which pieces of the compiled kernel > (especially modules) contained the source-code changes I might make to any > given directory? Like a kernel-code dependency graph website? > > For instance, assume I made a change to code in net/wireless/. How do I > figure out which pieces of the kernel or modules get linked against the > library built from this directory? > > I could attempt to trace the kernel's build output line-by-line and then > grep through the output looking for which other code is linking against > cfg80211. That is way too tedious. In this case I would like to know which > kernel modules I would need to, potentially, re-test because I apply a > patch to this directory.... without examining the build logs. Just look at the build logs, it will show you exactly what gets rebuilt when you touch a single file (or multiple files.) That's the simplest way to do what you want here. good luck! greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies