From: David Howells <dhowells@redhat.com>
To: Siddh Raman Pant <code@siddh.me>
Cc: dhowells@redhat.com, "mauro carvalho chehab" <mchehab@kernel.org>,
"randy dunlap" <rdunlap@infradead.org>,
"jonathan corbet" <corbet@lwn.net>,
"fabio m. de francesco" <fmdefrancesco@gmail.com>,
"eric dumazet" <edumazet@google.com>,
"christophe jaillet" <christophe.jaillet@wanadoo.fr>,
"eric biggers" <ebiggers@kernel.org>,
"keyrings" <keyrings@vger.kernel.org>,
"linux-security-module" <linux-security-module@vger.kernel.org>,
"linux-fsdevel" <linux-fsdevel@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] include/linux/watch_queue: Improve documentation
Date: Wed, 11 Jan 2023 15:48:05 +0000 [thread overview]
Message-ID: <2430913.1673452085@warthog.procyon.org.uk> (raw)
In-Reply-To: <1859d17668d.7b9d5469421579.5464668634216421773@siddh.me>
Siddh Raman Pant <code@siddh.me> wrote:
> But what about the second patch? Should I send that without these doc
> changes?
Can you repost it without the first patch being present?
David
next prev parent reply other threads:[~2023-01-11 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 10:36 [PATCH v3 0/2] watch_queue: Clean up some code Siddh Raman Pant
2023-01-08 10:36 ` [PATCH v3 1/2] include/linux/watch_queue: Improve documentation Siddh Raman Pant
2023-01-08 10:36 ` [PATCH v3 2/2] kernel/watch_queue: NULL the dangling *pipe, and use it for clear check Siddh Raman Pant
2023-01-10 14:09 ` [PATCH v3 1/2] include/linux/watch_queue: Improve documentation David Howells
2023-01-10 19:10 ` Siddh Raman Pant
2023-01-11 15:48 ` David Howells [this message]
2023-01-11 15:50 ` Siddh Raman Pant
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=2430913.1673452085@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=code@siddh.me \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=fmdefrancesco@gmail.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®