From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Michael Ellerman" <mpe@ellerman.id.au>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the tty tree
Date: Mon, 27 Nov 2023 13:14:07 +0000 [thread overview]
Message-ID: <2023112757-enamel-degrading-38e5@gregkh> (raw)
In-Reply-To: <20231127115718.7ad1701c@canb.auug.org.au>
On Mon, Nov 27, 2023 at 11:57:18AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the powerpc tree as a different commit
> (but the same patch):
>
> aa46b225ebbf ("tty: hvc: hvc_opal: Convert to platform remove callback returning void")
>
> This is commit
>
> f99c0e0d0859 ("tty: hvc: hvc_opal: Convert to platform remove callback returning void")
>
> in the powerpc tree.
Should be fine, thanks for the notice.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux Next Mailing List" <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: linux-next: duplicate patch in the tty tree
Date: Mon, 27 Nov 2023 13:14:07 +0000 [thread overview]
Message-ID: <2023112757-enamel-degrading-38e5@gregkh> (raw)
In-Reply-To: <20231127115718.7ad1701c@canb.auug.org.au>
On Mon, Nov 27, 2023 at 11:57:18AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the powerpc tree as a different commit
> (but the same patch):
>
> aa46b225ebbf ("tty: hvc: hvc_opal: Convert to platform remove callback returning void")
>
> This is commit
>
> f99c0e0d0859 ("tty: hvc: hvc_opal: Convert to platform remove callback returning void")
>
> in the powerpc tree.
Should be fine, thanks for the notice.
greg k-h
next prev parent reply other threads:[~2023-11-27 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 0:57 linux-next: duplicate patch in the tty tree Stephen Rothwell
2023-11-27 0:57 ` Stephen Rothwell
2023-11-27 13:14 ` Greg KH [this message]
2023-11-27 13:14 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2025-03-24 8:44 Stephen Rothwell
2025-03-24 13:28 ` Greg KH
2025-03-25 6:31 Stephen Rothwell
2025-03-25 23:56 ` Greg KH
2025-07-25 1:42 Stephen Rothwell
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=2023112757-enamel-degrading-38e5@gregkh \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.