From: Greg KH <gregkh@linuxfoundation.org>
To: MBKCHEL <mbkchelofficialdev@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: make g_fbmode array const
Date: Thu, 29 Oct 2026 16:25:11 +0100 [thread overview]
Message-ID: <2026102953-scaling-palpable-46ae@gregkh> (raw)
In-Reply-To: <CA+YDrKAaU1EXGhCtJ_yqBrVxKRs0ykyAibvtevVhRwWyU-BLLQ@mail.gmail.com>
On Thu, Oct 29, 2026 at 03:32:38PM +0200, MBKCHEL wrote:
> Hi,
>
> Please note that I made a typo in my last name in the "From" and
> "Signed-off-by" lines. My correct name is "Ivan Tverdokhleb".
>
> If the patch is accepted, could you please apply it with the corrected name?
Why would we accept a patch that was not even built?
Always test-build your changes.
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-29 15:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 7:49 [PATCH] staging: sm750fb: make g_fbmode array const Ivan Tverdohleb
2026-10-28 20:08 ` MBKCHEL
2026-10-29 13:32 ` MBKCHEL
2026-10-29 15:25 ` Greg KH [this message]
2026-10-29 13:50 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2026-10-28 7:42 Ivan Tverdohleb
2026-10-07 10:10 pdsj2807
2026-10-07 14:33 ` Ahmet Sezgin Duran
[not found] ` <CANNUkNj7WJ0TNZUGAdJh9r7FQRQDvj8DmB9_HDD7sonNDHkRnA@mail.gmail.com>
2026-10-12 14:13 ` Ahmet Sezgin Duran
2026-07-01 4:14 Ruziev Miraly
2026-07-01 5:06 ` Dan Carpenter
[not found] ` <CAOW+FoFQVdBXMVfF2n2eV0_2u71apaQM8fV+uO1JVasqcqq-vQ@mail.gmail.com>
2026-07-01 7:26 ` Greg KH
2026-07-03 4:12 ` kernel test robot
2026-07-03 14:39 ` kernel test robot
2026-06-21 4:44 Arnav Kapoor
2026-06-09 1:17 Brock Haftner
2026-06-09 6:12 ` Ahmet Sezgin Duran
2026-06-10 0:58 ` Brock Haftner
2026-02-02 2:32 James
2026-02-02 7:50 ` kernel test robot
2026-02-02 9:02 ` kernel test robot
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=2026102953-scaling-palpable-46ae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbkchelofficialdev@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.