From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>, Andrew Morton <akpm@linux-foundation•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patch in the tty tree
Date: Fri, 25 Jul 2025 11:42:42 +1000 [thread overview]
Message-ID: <20250725114242.6f7a01fe@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
Hi all,
The following commit is also in the mm-nonmm-unstable tree as a different
commit (but the same patch):
a8d455db2621 ("serial: 8250_dw: Fix typo "notifer"")
This is commit
6e1663784e61 ("serial: 8250_dw: fix typo "notifer"")
in the mm-nonmm-unstable tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-25 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 1:42 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 6:31 linux-next: duplicate patch in the tty tree Stephen Rothwell
2025-03-25 23:56 ` Greg KH
2025-03-24 8:44 Stephen Rothwell
2025-03-24 13:28 ` Greg KH
2023-11-27 0:57 Stephen Rothwell
2023-11-27 13:14 ` Greg KH
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=20250725114242.6f7a01fe@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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