From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: "Jiri Slaby" <jirislaby@kernel.org>,
linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
greybus-dev@lists.linaro.org, linux-iio@vger.kernel.org,
netdev@vger.kernel.org, chrome-platform@lists.linux.dev,
platform-driver-x86@vger.kernel.org,
linux-serial@vger.kernel.org, linux-sound@vger.kernel.org,
"Francesco Dolcini" <francesco.dolcini@toradex.com>,
"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
"Johan Hovold" <johan@kernel.org>,
"Alex Elder" <elder@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lee Jones" <lee@kernel.org>, "Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Eric Dumazet" <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Benson Leung" <bleung@chromium.org>,
"Tzung-Bi Shih" <tzungbi@kernel.org>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v1] treewide, serdev: change receive_buf() return type to size_t
Date: Fri, 15 Dec 2023 14:26:48 +0100 [thread overview]
Message-ID: <2023121535-coveting-destruct-f567@gregkh> (raw)
In-Reply-To: <ZXs94Mf1eOMCmGpT@francesco-nb.int.toradex.com>
On Thu, Dec 14, 2023 at 06:39:44PM +0100, Francesco Dolcini wrote:
> On Thu, Dec 14, 2023 at 06:01:46PM +0100, Francesco Dolcini wrote:
> > From: Francesco Dolcini <francesco.dolcini@toradex.com>
> >
> > receive_buf() is called from ttyport_receive_buf() that expects values
> > ">= 0" from serdev_controller_receive_buf(), change its return type from
> > ssize_t to size_t.
> >
> > Suggested-by: Jiri Slaby <jirislaby@kernel.org>
> > Link: https://lore.kernel.org/all/087be419-ec6b-47ad-851a-5e1e3ea5cfcc@kernel.org/
> > Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> > ---
> > hello,
> > patch is based on current linux next.
> >
> > It has an obvious problem, it touches files from multiple subsystem in a single
> > patch that is complicated to review and eventually merge, just splitting this
> > would however not work, it will break bisectability and the build.
> >
> > I am looking for advise on the best way to move forward.
> >
> > I see the following options:
> > - keep it as it is
> > - break it down with a patch with each subsystem, and squash before applying
> > from a single (tty?) subsystem
> > - go for a multi stage approach, defining a new callback, move to it and in
> > the end remove the original one, likewise it was done for i2c lately
>
> whoops. I just noticed Greg applied commit 475fc6e2de6f ("tty: serdev:
> convert to u8 and size_t") that touch the exact same files without much
> of an issue.
>
> Probably the "keep it as it is" is just the way to go.
Yeah, looks good to me, now queued up, thanks!
greg k-h
next prev parent reply other threads:[~2023-12-15 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 17:01 [PATCH v1] treewide, serdev: change receive_buf() return type to size_t Francesco Dolcini
2023-12-14 17:39 ` Francesco Dolcini
2023-12-15 13:26 ` Greg Kroah-Hartman [this message]
2023-12-15 13:36 ` Johan Hovold
2023-12-15 13:55 ` Francesco Dolcini
2023-12-15 16:18 ` Johan Hovold
2023-12-15 17:07 ` Francesco Dolcini
2023-12-18 8:35 ` Johan Hovold
2023-12-15 14:11 ` Greg Kroah-Hartman
2023-12-15 13:51 ` Johan Hovold
2023-12-15 13:59 ` Francesco Dolcini
2023-12-15 16:32 ` Johan Hovold
2023-12-17 12:37 ` Jonathan Cameron
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=2023121535-coveting-destruct-f567@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=greybus-dev@lists.linaro.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jic23@kernel.org \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tzungbi@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 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 NNTP newsgroup(s).