From: John Ogness <john.ogness@linutronix.de>
To: paulmck@kernel.org
Cc: Petr Mladek <pmladek@suse.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: next-20221122: tinyconfig: ppc n s390: kernel/printk/printk.c:95:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Werror,-Wimplicit-int]
Date: Wed, 30 Nov 2022 09:59:46 +0106 [thread overview]
Message-ID: <877czcx1ph.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20221130001834.GA552288@paulmck-ThinkPad-P17-Gen-1>
Hi Paul,
On 2022-11-29, "Paul E. McKenney" <paulmck@kernel.org> wrote:
> And this seems have avoided breaking things, so I moved it on top of
> the earlier srcunmisafe.2022.11.09a stack with a new
> srcunmisafe.2022.11.29a branch name.
>
> If you need me to, I can push this into the upcoming merge window. Or
> you could rebase on top of it, so that when the printk() series goes
> in, this commit will come along for the ride.
It would be great if the series could land in linux-next, to give any
other issues with the series a chance to show up.
Also, since the series is relatively significant, it would probably be
better if it was pushed into the 6.2 merge window by you. Petr will need
to make sure the printk series for the merge window is properly rebased
for it.
Thanks for helping us out here.
John
next prev parent reply other threads:[~2022-11-30 8:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 9:08 next-20221122: tinyconfig: ppc n s390: kernel/printk/printk.c:95:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Werror,-Wimplicit-int] Naresh Kamboju
2022-11-22 14:27 ` John Ogness
2022-11-22 14:48 ` Paul E. McKenney
2022-11-22 15:27 ` John Ogness
2022-11-22 15:55 ` Petr Mladek
2022-11-22 18:20 ` Paul E. McKenney
2022-11-22 22:00 ` Paul E. McKenney
2022-11-22 22:11 ` Randy Dunlap
2022-11-22 23:14 ` John Ogness
2022-11-22 23:42 ` Paul E. McKenney
2022-11-30 0:18 ` Paul E. McKenney
2022-11-30 8:53 ` John Ogness [this message]
2022-11-30 10:37 ` Petr Mladek
2022-11-30 21:59 ` Paul E. McKenney
2022-11-22 16:35 ` Paul E. McKenney
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=877czcx1ph.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.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