All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jakub Sitnicki <jakub@cloudflare.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	kernel-team@cloudflare.com,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH] genirq: Own affinity hint
Date: Thu, 26 Oct 2023 02:48:35 +0800	[thread overview]
Message-ID: <202310260237.0IF4S81f-lkp@intel.com> (raw)
In-Reply-To: <20231025141517.375378-1-jakub@cloudflare.com>

Hi Jakub,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/irq/core]
[also build test WARNING on linus/master v6.6-rc7 next-20231025]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Jakub-Sitnicki/genirq-Own-affinity-hint/20231026-001606
base:   tip/irq/core
patch link:    https://lore.kernel.org/r/20231025141517.375378-1-jakub%40cloudflare.com
patch subject: [PATCH] genirq: Own affinity hint
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20231026/202310260237.0IF4S81f-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231026/202310260237.0IF4S81f-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310260237.0IF4S81f-lkp@intel.com/

All warnings (new ones prefixed by >>):

   kernel/irq/irqdesc.c: In function 'alloc_masks':
>> kernel/irq/irqdesc.c:79:1: warning: label 'err_effective_affinity' defined but not used [-Wunused-label]
      79 | err_effective_affinity:
         | ^~~~~~~~~~~~~~~~~~~~~~
>> kernel/irq/irqdesc.c:75:1: warning: label 'err_pending_mask' defined but not used [-Wunused-label]
      75 | err_pending_mask:
         | ^~~~~~~~~~~~~~~~


vim +/err_effective_affinity +79 kernel/irq/irqdesc.c

    68	
    69	#ifdef CONFIG_GENERIC_PENDING_IRQ
    70		if (!zalloc_cpumask_var_node(&desc->pending_mask, GFP_KERNEL, node))
    71			goto err_pending_mask;
    72	#endif
    73		return 0;
    74	
  > 75	err_pending_mask:
    76	#ifdef CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK
    77		free_cpumask_var(desc->irq_common_data.effective_affinity);
    78	#endif
  > 79	err_effective_affinity:
    80		free_cpumask_var(desc->irq_common_data.affinity_hint);
    81	err_affinity_hint:
    82		free_cpumask_var(desc->irq_common_data.affinity);
    83	err_affinity:
    84		return -ENOMEM;
    85	}
    86	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-10-25 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 14:15 [PATCH] genirq: Own affinity hint Jakub Sitnicki
2023-10-25 18:48 ` kernel test robot [this message]
2023-10-25 20:10 ` Thomas Gleixner
2023-10-26 13:05   ` Jakub Sitnicki
2023-10-26 12:34 ` kernel test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202310260237.0IF4S81f-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jakub@cloudflare.com \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=xuanzhuo@linux.alibaba.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.