All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] i2c: Use IS_REACHABLE() for substituting empty ACPI functions
Date: Wed, 14 Aug 2024 16:07:16 +0200	[thread overview]
Message-ID: <87ikw3jizv.wl-tiwai@suse.de> (raw)
In-Reply-To: <Zry4eIOLOTwaYdaC@ninjato>

On Wed, 14 Aug 2024 16:00:24 +0200,
Wolfram Sang wrote:
> 
> 
> > > Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> > > Fixes: f17c06c6608a ("i2c: Fix conditional for substituting empty ACPI functions")
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Closes: https://lore.kernel.org/oe-kbuild-all/202408141333.gYnaitcV-lkp@intel.com/
> > 
> > I suppose Wolfram will take this?
> > 
> > Reviewed-by: Takashi Iwai <tiwai@suse.de>
> 
> Yes, for rc4. I wonder why buildbot did not spot it for the branch I
> submitted to rc3. Things happen, I guess...

Maybe because there was no user that can hit with randconfig.
It was a preliminary fix for the change I recently put after the rc3
release, and now it surfaced.


thanks,

Takashi

  reply	other threads:[~2024-08-14 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 12:16 [PATCH] i2c: Use IS_REACHABLE() for substituting empty ACPI functions Richard Fitzgerald
2024-08-14 13:43 ` Takashi Iwai
2024-08-14 14:00   ` Wolfram Sang
2024-08-14 14:07     ` Takashi Iwai [this message]
2024-08-14 15:41       ` Wolfram Sang
2024-08-14 17:50 ` Wolfram Sang

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=87ikw3jizv.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.com \
    --cc=tiwai@suse.com \
    --cc=wsa+renesas@sang-engineering.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.