From: Greg KH <gregkh@linuxfoundation.org>
To: Dorine Tipo <dorine.a.tipo@gmail.com>
Cc: linux-staging@lists.linux.dev, outreachy@lists.linux.dev
Subject: Re: [PATCH v3 8/8] Revert "Staging: sm750fb: Rename variable sii164GetDeviceID"
Date: Thu, 7 Mar 2024 14:20:10 +0000 [thread overview]
Message-ID: <2024030726-scion-buddy-9aee@gregkh> (raw)
In-Reply-To: <20240306054458.102288-9-dorine.a.tipo@gmail.com>
On Wed, Mar 06, 2024 at 05:44:58AM +0000, Dorine Tipo wrote:
> This reverts commit 30c83463c8dcdc808d4f10d44c5a4f19d3b5f1f4.
This is not an object in Linus's tree, or my development tree, it is
local only to your tree, right?
And you aren't saying _why_ it must be reverted, what is wrong with it?
confused,
greg k-h
next prev parent reply other threads:[~2024-03-07 14:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 5:44 [PATCH v3 0/8] Rename variables in sm750fb driver Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 1/8] Staging: sm750fb: Rename sii164ResetChip Dorine Tipo
2024-03-07 14:06 ` Dan Carpenter
2024-03-07 14:21 ` Greg KH
2024-03-08 9:10 ` Apology and Request for Resubmitting Patch Dorine Tipo
2024-03-08 9:52 ` Julia Lawall
2024-03-09 12:48 ` Dan Carpenter
2024-03-06 5:44 ` [PATCH v3 2/8] Staging: sm750fb: Rename variable sii164GetChipString Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 3/8] Staging: sm750fb: Rename variable sii164SetPower Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 4/8] Staging: sm750fb: Rename variable sii164EnableHotPlugDetection Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 5/8] Staging: sm750fb: Rename variable sii164IsConnected Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 6/8] Staging: sm750fb: Rename variable sii164CheckInterrupt Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 7/8] Staging: sm750fb: Rename Variable sii164ClearInterrupt Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 8/8] Revert "Staging: sm750fb: Rename variable sii164GetDeviceID" Dorine Tipo
2024-03-07 14:20 ` Greg KH [this message]
2024-03-07 17:12 ` [PATCH v3 0/8] Rename variables in sm750fb driver Julia Lawall
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=2024030726-scion-buddy-9aee@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dorine.a.tipo@gmail.com \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).