From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"saravanak@google.com" <saravanak@google.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Seiya Wang (王迺君)" <seiya.wang@mediatek.com>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>
Subject: Re: [PATCH] Revert "drm/mipi-dsi: Set the fwnode for mipi_dsi_device"
Date: Mon, 28 Oct 2024 06:02:10 +0000 [thread overview]
Message-ID: <d295d1c384f4af46c2c4a11894fbdd8048984b46.camel@mediatek.com> (raw)
In-Reply-To: <2024102855-untitled-unfixed-2b9d@gregkh>
[snip]
> > > >
> > > > Please don't mind me make a confirmation.
> > > > I just need to add this line here and send it again, right?
> > > >
> > > > Cc: <stable@vger.kernel.org> #5.15.169
> > >
> > > Yes.
> >
> > Hi Greg,
> >
> > Thanks for your confirmation!
> >
> > I've sent the patch again without adding `v2` after the [PATCH]:
> >
https://lore.kernel.org/all/20241024-fixup-5-15-v1-1-62f21a32b5a5@mediatek.com
> > Would that be fine with you?
>
> But it is a v2 patch, why not mark it as such?
I thought correcting format is not changing commit message or
modification, so I didn't increase the version number.
Anyway, I've sent the v2 again:
https://lore.kernel.org/all/20241028-fixup-5-15-v2-1-40216f0fe383@mediatek.com
Regards,
Jason-JH.Lin
next prev parent reply other threads:[~2024-10-28 6:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 9:37 [PATCH] Revert "drm/mipi-dsi: Set the fwnode for mipi_dsi_device" Jason-JH.Lin
2024-10-24 9:37 ` Jason-JH.Lin via B4 Relay
2024-10-24 9:47 ` Greg KH
2024-10-24 10:16 ` Jason-JH Lin (林睿祥)
2024-10-24 10:23 ` gregkh
2024-10-28 2:38 ` Jason-JH Lin (林睿祥)
2024-10-28 5:26 ` gregkh
2024-10-28 6:02 ` Jason-JH Lin (林睿祥) [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 10:30 Jason-JH.Lin
2024-10-24 10:30 ` Jason-JH.Lin via B4 Relay
2024-10-28 5:38 ` Greg KH
2024-10-28 6:08 ` Jason-JH Lin (林睿祥)
2024-10-28 6:32 ` Jason-JH Lin (林睿祥)
2024-10-28 6:33 ` gregkh
2024-10-29 1:17 ` Jason-JH 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=d295d1c384f4af46c2c4a11894fbdd8048984b46.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@google.com \
--cc=seiya.wang@mediatek.com \
--cc=stable@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 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.