From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Alexey Klimov <alexey.klimov@linaro.org>
Subject: Re: linux-next: duplicate patch in the v4l-dvb tree
Date: Wed, 16 Oct 2024 08:14:19 +0200 [thread overview]
Message-ID: <20241016081419.1d65c93d@foz.lan> (raw)
In-Reply-To: <20241016114013.37522900@canb.auug.org.au>
Em Wed, 16 Oct 2024 11:40:13 +1100
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:
> Hi all,
>
> The following commit is also in the mm tree as a different commit (but
> the same patch):
>
> c5120f3b20a1 ("MAINTAINERS: mailmap: update Alexey Klimov's email address")
>
> This is commit
>
> d6f369d3d989 ("MAINTAINERS: mailmap: update Alexey Klimov's email address")
>
> in the mm-unstable branch of the mm tree.
>
Heh, Alexey sent it for both Andrew any me:
To: mchehab@kernel.org, akpm@linux-foundation.org
Cc: linux-media@vger.kernel.org, klimov.linux@gmail.com, srinivas.kandagatla@linaro.org, linux-kernel@vger.kernel.org, alexey.klimov@linaro.org
making it being merged twice on different trees.
Thanks,
Mauro
next prev parent reply other threads:[~2024-10-16 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 0:40 linux-next: duplicate patch in the v4l-dvb tree Stephen Rothwell
2024-10-16 6:14 ` Mauro Carvalho Chehab [this message]
2024-11-06 14:35 ` Alexey Klimov
-- strict thread matches above, loose matches on Subject: below --
2025-06-17 21:49 Stephen Rothwell
2025-05-12 3:08 Stephen Rothwell
2024-11-10 21:03 Stephen Rothwell
2024-10-16 0:36 Stephen Rothwell
2024-10-16 6:07 ` Mauro Carvalho Chehab
2023-12-22 2:49 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=20241016081419.1d65c93d@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexey.klimov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sfr@canb.auug.org.au \
/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