From: Jens Axboe <[email protected]>
To: Alex Deucher <[email protected]>, Yang Rong <[email protected]>
Cc: "Harry Wentland" <[email protected]>,
"Leo Li" <[email protected]>,
"Rodrigo Siqueira" <[email protected]>,
"Alex Deucher" <[email protected]>,
"Christian König" <[email protected]>,
"Pan, Xinhui" <[email protected]>,
"David Airlie" <[email protected]>,
"Daniel Vetter" <[email protected]>,
"Michael S. Tsirkin" <[email protected]>,
"Jason Wang" <[email protected]>,
"Xuan Zhuo" <[email protected]>,
"David S. Miller" <[email protected]>,
"Eric Dumazet" <[email protected]>,
"Jakub Kicinski" <[email protected]>,
"Paolo Abeni" <[email protected]>,
"Pavel Begunkov" <[email protected]>,
"Alvin Lee" <[email protected]>, "Jun Lei" <[email protected]>,
"Qingqing Zhuo" <[email protected]>,
"Max Tseng" <[email protected]>,
"Josip Pavic" <[email protected]>,
"Cruise Hung" <[email protected]>,
"open list:AMD DISPLAY CORE" <[email protected]>,
"open list:DRM DRIVERS" <[email protected]>,
"open list" <[email protected]>,
"open list:VIRTIO CORE AND NET DRIVERS"
<[email protected]>,
"open list:NETWORKING DRIVERS" <[email protected]>,
"open list:IO_URING" <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH] Fix max/min warnings in virtio_net, amd/display, and io_uring
Date: Thu, 6 Jul 2023 08:03:51 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADnq5_MSkJf=-QMPYNQp03=6mbb+OEHnPFW0=WKiS0VMc6ricQ@mail.gmail.com>
On 7/6/23 7:58?AM, Alex Deucher wrote:
> On Thu, Jul 6, 2023 at 3:37?AM Yang Rong <[email protected]> wrote:
>>
>> The files drivers/net/virtio_net.c, drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c, and io_uring/io_uring.c were modified to fix warnings.
>> Specifically, the opportunities for max() and min() were utilized to address the warnings.
>
> Please split this into 3 patches, one for each component.
Don't bother with the io_uring one, code is far more readable as-is.
--
Jens Axboe
next prev parent reply other threads:[~2023-07-06 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 2:06 [PATCH] Fix max/min warnings in virtio_net, amd/display, and io_uring Yang Rong
2023-07-06 13:58 ` Alex Deucher
2023-07-06 14:03 ` Jens Axboe [this message]
2023-07-06 14:02 ` Michael S. Tsirkin
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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