From: Stephen Rothwell <sfr@canb.auug.org.au>
To: John Johansen <john.johansen@canonical.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the apparmor tree
Date: Mon, 10 Jul 2023 08:22:23 +1000 [thread overview]
Message-ID: <20230710082223.7585feb8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
0bb84cff96af ("apparmor: fix missing error check for rhashtable_insert_fast")
1079ff8963ca ("AppArmor: Fix some kernel-doc comments")
97a79eea1797 ("apparmor: Fix kernel-doc header for verify_dfa_accept_index")
b45be9bd7cf9 ("apparmor: fix policy_compat permission remap with extended permissions")
c96a8a8c021b ("apparmor: aa_buffer: Convert 1-element array to flexible array")
cb60752f0c37 ("apparmor: fix use of strcpy in policy_unpack_test")
e31dd6e412f7 ("apparmor: fix: kzalloc perms tables for shared dfas")
fd18ddebace4 ("apparmor: Return directly after a failed kzalloc() in two functions")
ff9b84eade6d ("apparmor: add missing failure check in compute_xmatch_perms")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-07-09 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 22:22 Stephen Rothwell [this message]
2023-07-10 0:59 ` linux-next: duplicate patches in the apparmor tree John Johansen
-- strict thread matches above, loose matches on Subject: below --
2024-12-08 20:43 Stephen Rothwell
2024-12-08 21:06 ` John Johansen
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=20230710082223.7585feb8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox