linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the ieee1394 tree
Date: Tue, 30 May 2023 19:44:23 +0900	[thread overview]
Message-ID: <20230530104423.GA67264@workstation.local> (raw)
In-Reply-To: <20230530122450.1603af75@canb.auug.org.au>

Hi Stephen,

On Tue, May 30, 2023 at 12:24:50PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the ieee1394 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> ERROR: modpost: missing MODULE_LICENSE() in drivers/firewire/firewire-uapi-test.o
> 
> Caused by commit
> 
>   dc7c51638f46 ("firewire: add KUnit test to check layout of UAPI structures")
> 
> I have used the ieee1394 tree from next-20230525 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell

Indeed. I overlooked that the code can be configured for tristate.
I posted a patch to fix it and applied it to my for-next branch.

* https://git.kernel.org/ieee1394/linux1394/c/e003498ec055

I'm sorry to interrupt your work flow.


Thanks

Takashi Sakamoto

  reply	other threads:[~2023-05-30 10:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  2:24 linux-next: build failure after merge of the ieee1394 tree Stephen Rothwell
2023-05-30 10:44 ` Takashi Sakamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02  0:16 Stephen Rothwell
2024-02-02  1:04 ` Takashi Sakamoto
2010-07-27  1:48 Stephen Rothwell
2010-07-27  8:07 ` Stefan Richter

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=20230530104423.GA67264@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).