All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH printk] printk: htmldocs: add missing description
Date: Tue, 22 Nov 2022 12:06:29 +0100	[thread overview]
Message-ID: <Y3ytNTzRGjvlD1fQ@alley> (raw)
In-Reply-To: <87zgcjpdvo.fsf@jogness.linutronix.de>

On Tue 2022-11-22 10:01:23, John Ogness wrote:
> Variable and return descriptions were missing from the SRCU read
> lock functions. Add them.
> 
> Signed-off-by: John Ogness <john.ogness@linutronix.de>

JFYI, the patch is comitted in printk/linux.git,
branch rework/console-list-lock.

Best Regards,
Petr

      reply	other threads:[~2022-11-22 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  7:10 linux-next: build warning after merge of the printk tree Stephen Rothwell
2022-11-22  8:55 ` [PATCH printk] printk: htmldocs: add missing description John Ogness
2022-11-22 11:06   ` Petr Mladek [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=Y3ytNTzRGjvlD1fQ@alley \
    --to=pmladek@suse.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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 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.