public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Mauro Rossi <issor.oruam@gmail.com>,
	Chih-Wei Huang <cwhuang@android-x86.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: fix build errors in paged buffer handling code
Date: Mon, 22 Jul 2019 14:28:48 +0200	[thread overview]
Message-ID: <s5hr26i8d8f.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190722121202.GB31543@kroah.com>

On Mon, 22 Jul 2019 14:12:02 +0200,
Greg Kroah-Hartman wrote:
> 
> On Mon, Jul 22, 2019 at 01:55:20PM +0200, Takashi Iwai wrote:
> > On Mon, 22 Jul 2019 07:55:36 +0200,
> > Takashi Iwai wrote:
> > > 
> > > From: Mauro Rossi <issor.oruam@gmail.com>
> > > 
> > > fw_{grow,map}_paged_buf() need to be defined as static inline
> > > when CONFIG_FW_LOADER_PAGED_BUF is not enabled,
> > > infact fw_free_paged_buf() is also defined as static inline
> > > when CONFIG_FW_LOADER_PAGED_BUF is not enabled.
> > > 
> > > Fixes the following mutiple definition building errors for Android kernel:
> > > 
> > > drivers/base/firmware_loader/fallback_efi.o: In function `fw_grow_paged_buf':
> > > fallback_efi.c:(.text+0x0): multiple definition of `fw_grow_paged_buf'
> > > drivers/base/firmware_loader/main.o:(.text+0x73b): first defined here
> > > drivers/base/firmware_loader/fallback_efi.o: In function `fw_map_paged_buf':
> > > fallback_efi.c:(.text+0xf): multiple definition of `fw_map_paged_buf'
> > > drivers/base/firmware_loader/main.o:(.text+0x74a): first defined here
> > > 
> > > [ slightly corrected the patch description -- tiwai ]
> > > 
> > > Fixes: 5342e7093ff2 ("firmware: Factor out the paged buffer handling code")
> > > Fixes: 82fd7a8142a1 ("firmware: Add support for loading compressed files")
> > > Signed-off-by: Mauro Rossi <issor.oruam@gmail.com>
> > > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > 
> > Please discard this one.  It's missing the inline, as Mauro already
> > suggested in another mail.
> > 
> > Will resubmit the revised one.  Sorry for inconvenience.
> 
> Ugh, I already applied it, if there is no code difference, can we just
> leave what I have already committed in the tree?

Well, the compiler would optimize it out, so the binary would be
almost same, but it's still ugly to keep the obvious mistake there...
If necessary, I'll resubmit a patch on top of the first version to
correct that.


thanks,

Takashi

      reply	other threads:[~2019-07-22 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  5:55 [PATCH] firmware: fix build errors in paged buffer handling code Takashi Iwai
2019-07-22 11:55 ` Takashi Iwai
2019-07-22 12:12   ` Greg Kroah-Hartman
2019-07-22 12:28     ` Takashi Iwai [this message]

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=s5hr26i8d8f.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=cwhuang@android-x86.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=issor.oruam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=rafael@kernel.org \
    /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