public inbox for ntb@lists.linux.dev
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: kernel test robot <lkp@intel.com>,
	perex@perex.cz, tiwai@suse.com, broonie@kernel.org,
	lgirdwood@gmail.com, deller@gmx.de, sre@kernel.org,
	sakari.ailus@linux.intel.com, mchehab@kernel.org,
	hverkuil-cisco@xs4all.nl, jdmason@kudzu.us,
	fancer.lancer@gmail.com, oe-kbuild-all@lists.linux.dev,
	linux-sound@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-media@vger.kernel.org,
	ntb@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 07/13] fbdev: pxafb: use devm_kmemdup_array()
Date: Mon, 24 Feb 2025 14:28:35 +0200	[thread overview]
Message-ID: <Z7xl80RPM6YQgOTj@smile.fi.intel.com> (raw)
In-Reply-To: <Z7xkb9m_Qc54znOH@black.fi.intel.com>

On Mon, Feb 24, 2025 at 02:22:07PM +0200, Raag Jadav wrote:
> On Mon, Feb 24, 2025 at 01:41:05PM +0200, Andy Shevchenko wrote:
> > On Mon, Feb 24, 2025 at 01:24:08PM +0200, Raag Jadav wrote:
> > > On Mon, Feb 24, 2025 at 12:58:35PM +0200, Andy Shevchenko wrote:
> > > > On Sat, Feb 22, 2025 at 05:41:24AM +0800, kernel test robot wrote:
> > > > > Hi Raag,
> > > > > 
> > > > > kernel test robot noticed the following build warnings:
> > > > > 
> > > > > [auto build test WARNING on b16e9f8547a328b19af59afc213ce323124d11e9]
> > > > > 
> > > > > url:    https://github.com/intel-lab-lkp/linux/commits/Raag-Jadav/ASoC-Intel-avs-use-devm_kmemdup_array/20250222-010322
> > > > > base:   b16e9f8547a328b19af59afc213ce323124d11e9
> > > > > patch link:    https://lore.kernel.org/r/20250221165333.2780888-8-raag.jadav%40intel.com
> > > > > patch subject: [PATCH v1 07/13] fbdev: pxafb: use devm_kmemdup_array()
> > > > > config: arm-randconfig-004-20250222 (https://download.01.org/0day-ci/archive/20250222/202502220449.DvJuMgsL-lkp@intel.com/config)
> > > > > compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
> > > > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250222/202502220449.DvJuMgsL-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/202502220449.DvJuMgsL-lkp@intel.com/
> > > > > 
> > > > > All warnings (new ones prefixed by >>):
> > > > > 
> > > > >    drivers/video/fbdev/pxafb.c: In function 'pxafb_probe':
> > > > > >> drivers/video/fbdev/pxafb.c:2236:13: warning: unused variable 'i' [-Wunused-variable]
> > > > >     2236 |         int i, irq, ret;
> > > > >          |             ^
> > > > 
> > > > Ragg, please, fix this, and issue a v2 with the link to fixed PR:
> > > > https://lore.kernel.org/r/Z7xGpz3Q4Zj6YHx7@black.fi.intel.com.
> > > 
> > > Sure, but perhaps wait a few days for review comments.
> > 
> > Then perhaps answering to the cover letter that the maintainers who want to
> > apply should use the updated PR?
> 
> Okay, but I'm not sure how this plays out for those who already pulled
> the old PR, i.e. Sebastian.
> 
> Anything to worry about here?

I already informed him and Stephen about a new PR I just sent a few hours ago.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-02-24 12:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 16:53 [PATCH v1 00/13] Convert to use devm_kmemdup_array() Raag Jadav
2025-02-21 16:53 ` [PATCH v1 01/13] ASoC: Intel: avs: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 02/13] ASoC: hdac_hdmi: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 03/13] ASoC: tlv320dac33: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 04/13] ASoC: uda1380: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 05/13] ASoC: meson: axg-tdm-interface: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 06/13] ASoC: uniphier: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 07/13] fbdev: pxafb: " Raag Jadav
2025-02-21 21:41   ` kernel test robot
2025-02-24 10:58     ` Andy Shevchenko
2025-02-24 11:24       ` Raag Jadav
2025-02-24 11:41         ` Andy Shevchenko
2025-02-24 12:22           ` Raag Jadav
2025-02-24 12:28             ` Andy Shevchenko [this message]
2025-02-21 16:53 ` [PATCH v1 08/13] power: supply: sc27xx: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 09/13] regulator: devres: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 10/13] regulator: cros-ec: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 11/13] media: atmel-isi: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 12/13] media: stm32-dcmi: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 13/13] ntb: idt: " Raag Jadav
2025-02-21 17:05   ` Dave Jiang
2025-02-22  9:27     ` Raag Jadav
2025-02-21 22:51 ` (subset) [PATCH v1 00/13] Convert to " Sebastian Reichel
2025-02-24 12:39 ` Raag Jadav
2025-02-24 13:46 ` Mark Brown
2025-02-24 14:29   ` Raag Jadav
2025-02-28 21:22 ` (subset) " Mark Brown

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=Z7xl80RPM6YQgOTj@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=deller@gmx.de \
    --cc=fancer.lancer@gmail.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jdmason@kudzu.us \
    --cc=lgirdwood@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mchehab@kernel.org \
    --cc=ntb@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=perex@perex.cz \
    --cc=raag.jadav@intel.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sre@kernel.org \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox