From: Greg KH <gregkh@linuxfoundation.org>
To: Karthikey Kadati <karthikey3608@gmail.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Unix Antigravity <unix.antigravity@test.com>
Subject: Re: [PATCH 1/4] staging: sm750fb: Convert sw_i2c_read_sda to return bool
Date: Mon, 12 Jan 2026 11:31:28 +0100 [thread overview]
Message-ID: <2026011212-strongbox-snore-e1cc@gregkh> (raw)
In-Reply-To: <20260112102502.19761-1-karthikey3608@gmail.com>
On Mon, Jan 12, 2026 at 03:55:02PM +0530, Karthikey Kadati wrote:
> The sw_i2c_read_sda function currently returns unsigned char (1 or 0).
>
> Standardize it to return bool (true or false) to match kernel standards.
>
> Signed-off-by: Unix Antigravity <unix.antigravity@test.com>
You have to be a legal person to sign off on a patch, with a valid email
address :(
Also, your patches were a patch series, but not connected to each other,
nor were they related. I see them in my inbox as:
1 T Jan 12 Karthikey Kadat (2.0K) [PATCH 4/4] staging: atomisp: Replace ia_css_region with v4l2_rect
2 T Jan 12 Karthikey Kadat (2.4K) [PATCH 2/4] staging: octeon: Remove port status typedefs
3 T Jan 12 Karthikey Kadat (9.1K) [PATCH 3/4] staging: atomisp: Remove input_system typedefs
4 T Jan 12 Karthikey Kadat (1.1K) [PATCH 1/4] staging: sm750fb: Convert sw_i2c_read_sda to return bool
But not threaded, so that's a bit odd. Perhaps you didn't use git
send-email for these?
thanks,
greg k-h
prev parent reply other threads:[~2026-01-12 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 10:25 [PATCH 1/4] staging: sm750fb: Convert sw_i2c_read_sda to return bool Karthikey Kadati
2026-01-12 10:31 ` Greg KH [this message]
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=2026011212-strongbox-snore-e1cc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=karthikey3608@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
--cc=unix.antigravity@test.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.