From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Kun-Fa Lin <milkfafa@gmail.com>
Cc: tmaimon77@gmail.com, andrew@aj.id.au, openbmc@lists.ozlabs.org,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
joel@jms.id.au, kflin@nuvoton.com
Subject: Re: [PATCH v1 0/5] Support Nuvoton NPCM Video Capture/Encode Engine
Date: Mon, 10 Oct 2022 19:31:26 +0200 [thread overview]
Message-ID: <Y0RW7rOfUrvWXgdv@probook> (raw)
In-Reply-To: <CADnNmFq-_pVFSDRFJ07HAt0Z+=CMwbHaiSPamaJiUXOU9haD-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Mon, Oct 10, 2022 at 09:01:25PM +0800, Kun-Fa Lin wrote:
> Hi Jonathan,
>
> Previous patchset was aimed for torvalds/linux and we would also like
> to upstream to openbmc/llinux.
> So this new v1 patchset is specifically aimed for openbmc/linux branch dev-6.0.
> https://github.com/openbmc/linux/tree/dev-6.0
Ah, I missed that, thank you for the explanation!
To avoid such confusion, I'd suggest perhaps indicating the branch in the
subject line, e.g. using [PATCH openbmc-6.0 v1 0/5] or similar instead of
[PATCH v1 0/5]. "git format-patch" can do this with the --subject-prefix option.
Best regards,
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-10 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 2:54 [PATCH v1 0/5] Support Nuvoton NPCM Video Capture/Encode Engine Marvin Lin
2022-10-07 2:54 ` [PATCH v1 1/5] arm64: dts: nuvoton: Add node for " Marvin Lin
2022-10-07 2:54 ` [PATCH v1 2/5] dt-bindings: media: Add dt-bindings " Marvin Lin
2022-10-07 2:54 ` [PATCH v1 3/5] dt-bindings: arm/npcm: Add dt-bindings for Graphics Core Information Marvin Lin
2022-10-07 2:54 ` [PATCH v1 4/5] media: Add HEXTILE compressed format Marvin Lin
2022-10-07 2:54 ` [PATCH v1 5/5] drivers: media: platform: Add NPCM Video Capture/Encode Engine driver Marvin Lin
2022-10-07 13:41 ` [PATCH v1 0/5] Support Nuvoton NPCM Video Capture/Encode Engine Jonathan Neuschäfer
2022-10-10 13:01 ` Kun-Fa Lin
2022-10-10 17:31 ` Jonathan Neuschäfer [this message]
2022-10-11 13:20 ` Kun-Fa Lin
-- strict thread matches above, loose matches on Subject: below --
2022-05-12 7:27 Marvin Lin
2022-05-12 7:27 ` Marvin Lin
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=Y0RW7rOfUrvWXgdv@probook \
--to=j.neuschaefer@gmx.net \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=kflin@nuvoton.com \
--cc=milkfafa@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tmaimon77@gmail.com \
/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.