From: Jonathan Corbet <corbet@lwn.net>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "André Almeida" <andrealmeid@collabora.com>,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, axboe@kernel.dk,
kernel@collabora.com, krisman@collabora.com
Subject: Re: [PATCH 4/4] coding-style: add explanation about pr_fmt macro
Date: Sat, 14 Sep 2019 01:08:08 -0600 [thread overview]
Message-ID: <20190914010808.7003db2e@lwn.net> (raw)
In-Reply-To: <125475bd-ca6d-5d2a-712d-9cb37a4b8164@acm.org>
On Fri, 13 Sep 2019 13:22:18 -0700
Bart Van Assche <bvanassche@acm.org> wrote:
> On 9/13/19 11:57 AM, André Almeida wrote:
> > The pr_fmt macro is useful to format log messages printed by pr_XXXX()
> > functions. Add text to explain the purpose of it, how to use and an
> > example.
> >
> > Signed-off-by: André Almeida <andrealmeid@collabora.com>
>
> Since Jonathan Corbet is documentation maintainer, shouldn't he be Cc'ed
> explicitly for documentation patches? See also the MAINTAINERS file.
...and indeed I was CC'd on the patch - and your response :)
Thanks,
jon
next prev parent reply other threads:[~2019-09-14 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 18:57 [PATCH 0/4] null_blk: fixes around nr_devices and log improvements André Almeida
2019-09-13 18:57 ` [PATCH 1/4] null_blk: do not fail the module load with zero devices André Almeida
2019-09-13 18:57 ` [PATCH 2/4] null_blk: match the type of parameter nr_devices André Almeida
2019-09-13 18:57 ` [PATCH 3/4] null_blk: format pr_* logs with pr_fmt André Almeida
2019-09-13 20:18 ` Chaitanya Kulkarni
2019-09-13 18:57 ` [PATCH 4/4] coding-style: add explanation about pr_fmt macro André Almeida
2019-09-13 19:08 ` Joe Perches
2019-09-13 19:36 ` André Almeida
2019-09-13 20:22 ` Bart Van Assche
2019-09-14 7:08 ` Jonathan Corbet [this message]
2019-09-13 19:03 ` [PATCH 0/4] null_blk: fixes around nr_devices and log improvements Jens Axboe
2019-09-13 19:22 ` André Almeida
2019-09-13 20:50 ` Jens Axboe
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=20190914010808.7003db2e@lwn.net \
--to=corbet@lwn.net \
--cc=andrealmeid@collabora.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.