All of lore.kernel.org
 help / color / mirror / Atom feed
From: Punit Agrawal <punitagrawal@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: John Ogness <john.ogness@linutronix.de>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	senozhatsky@chromium.org, rostedt@goodmis.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Move EXPORT_SYMBOL() closer to vprintk definition
Date: Wed, 16 Jun 2021 22:52:12 +0900	[thread overview]
Message-ID: <87sg1hsyr7.fsf@stealth> (raw)
In-Reply-To: <YMnBQW2pInXyW3vv@alley> (Petr Mladek's message of "Wed, 16 Jun 2021 11:15:45 +0200")

Hi Petr,

Apologies for the delayed response.

Petr Mladek <pmladek@suse.com> writes:

> On Wed 2021-06-16 09:57:11, John Ogness wrote:
>> On 2021-06-16, Petr Mladek <pmladek@suse.com> wrote:
>> >>> Petr, as this is causing trouble for the -rt patchset, please
>> >>> consider if this could make it to Linus before v5.13 release.
>> >
>> > Punit, John, would you mind when I queue this change for-5.14?  It
>> > seems that, you, RT-guys already handled this, so it will not help
>> > much if I sent it now. It does not look appropriate to send just a
>> > single cosmetic fix few days before rc7.
>> 
>> Since this cosmetic problem was introduced during the 5.13 merge window,
>> it would help if it is fixed before the 5.13 release. Obviously this is
>> not a reason to have an rc7. But if there is going to be an rc7, I think
>> this fix should be included.
>
> OK, I have committed the patch into printk/linux.git, branch
> for-5.13-fixup.
>
> I am going to send the pull request later this week, most likely
> tomorrow.

Thanks for picking this up.

It's good to have to the patch go in early, but 5.14 would also be fine.

Punit

[...]


  reply	other threads:[~2021-06-16 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 23:56 [PATCH] printk: Move EXPORT_SYMBOL() closer to vprintk definition Punit Agrawal
2021-06-15  6:50 ` Rasmus Villemoes
2021-06-15 13:36   ` Punit Agrawal
2021-06-16  6:56   ` Petr Mladek
2021-06-16  7:21     ` Petr Mladek
2021-06-16  7:51       ` John Ogness
2021-06-16  9:15         ` Petr Mladek
2021-06-16 13:52           ` Punit Agrawal [this message]
2021-06-16  1:30 ` Sergey Senozhatsky

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=87sg1hsyr7.fsf@stealth \
    --to=punitagrawal@gmail.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --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 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.