From: Ian Pilcher <arequipeno@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: "Disappearing" file in Documentation/ABI/testing
Date: Mon, 14 Mar 2022 12:36:51 -0500 [thread overview]
Message-ID: <t0nufk$mmg$1@ciao.gmane.io> (raw)
I am working on resubmitting a patch that adds an entry to
Documentation/ABI/testing/sysfs-block. That file does not exist in
Linus's most recent tree. All (presumably) of the entries documented in
that file have been merged into Documentation/ABI/stable/sysfs-block.
How should I handle this? Should my patch now add its entry to the
"stable" file, or should it recreate the "testing" file?
Thanks!
--
========================================================================
Google Where SkyNet meets Idiocracy
========================================================================
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2022-03-14 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 17:36 Ian Pilcher [this message]
2022-03-14 18:59 ` "Disappearing" file in Documentation/ABI/testing Greg KH
2022-03-14 19:19 ` Ozgur Kara
2022-03-14 19:24 ` Ozgur Kara
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='t0nufk$mmg$1@ciao.gmane.io' \
--to=arequipeno@gmail.com \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).