From: Jonathan Corbet <corbet@lwn.net>
To: Eric Biggers <ebiggers@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Theodore Ts'o <tytso@mit.edu>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the random tree with the jc_docs tree
Date: Fri, 22 Apr 2022 01:21:56 -0600 [thread overview]
Message-ID: <87wnfhzip7.fsf@meer.lwn.net> (raw)
In-Reply-To: <YmJMBnBV8wO4aco9@sol.localdomain>
Eric Biggers <ebiggers@kernel.org> writes:
> That's not exactly the correct resolution, since it dropped the change to the
> text of this paragraph that my patch made ("HalfSipHash" => "the hsiphash
> functions").
>
> We should get the updates to this file to go through one tree. Jason, probably
> you'd want it to be yours?
If you want changes to parts of Documentation/ to not go through the
docs tree, just say the word and I'll avoid it. A MAINTAINERS file
addition to direct those patches youward would also not be misplaced.
Meanwhile, Jason, if you want to pick up the offending patches directly,
I can drop them from docs-next.
Thanks,
jon
next prev parent reply other threads:[~2022-04-22 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 3:59 linux-next: manual merge of the random tree with the jc_docs tree Stephen Rothwell
2022-04-22 6:32 ` Eric Biggers
2022-04-22 7:21 ` Jonathan Corbet [this message]
2022-04-22 9:02 ` Jason A. Donenfeld
2022-04-22 9:16 ` Jason A. Donenfeld
2022-04-22 15:49 ` Jonathan Corbet
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=87wnfhzip7.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Jason@zx2c4.com \
--cc=bagasdotme@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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