public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	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 s390 tree
Date: Tue, 10 Jan 2023 15:22:38 +0100	[thread overview]
Message-ID: <Y710ri9sVzmWNpE6@osiris> (raw)
In-Reply-To: <20230110202221.2e284ba0@canb.auug.org.au>

On Tue, Jan 10, 2023 at 08:22:21PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the s390 tree, today's linux-next build (s390 allmodconfig)
> failed like this:
> 
> drivers/s390/char/con3270.c:43:24: error: 'condev' defined but not used [-Werror=unused-variable]
>  static struct tty3270 *condev;
>                         ^~~~~~
> 
> Caused by commit
> 
>   c17fe081ac1f ("s390/3270: unify con3270 + tty3270")

Thank you for reporting. This should be fixed now:
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features&id=9cab4f7d98eee90b762ffbc87055c9499d51a635

  reply	other threads:[~2023-01-10 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  9:22 linux-next: build failure after merge of the s390 tree Stephen Rothwell
2023-01-10 14:22 ` Heiko Carstens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-08  3:58 Stephen Rothwell
2024-09-11  8:09 ` Stephen Rothwell
2011-05-20  1:56 Stephen Rothwell
2011-05-20  9:24 ` Martin Schwidefsky

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=Y710ri9sVzmWNpE6@osiris \
    --to=hca@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=svens@linux.ibm.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