From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Oliver Neukum <oneukum@suse.com>,
mathias.nyman@intel.com, linux-usb@vger.kernel.org
Cc: Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] xhci: omit mem read just after allocation of trb
Date: Fri, 18 Feb 2022 10:26:45 +0200 [thread overview]
Message-ID: <4632126f-97da-65c9-a240-b86f4490afe0@linux.intel.com> (raw)
In-Reply-To: <20220217133549.27961-1-oneukum@suse.com>
On 17.2.2022 15.35, Oliver Neukum wrote:
> This has been allocated just a few lines earlier with a
> zalloc(). The value is known and "|=" is a waste of memory
> cycles.
>
> Signed-off-by: Oliver Neukum <oneukum@suse.com>
Thanks
In case Greg wants to pick this up now directly:
Acked-by: Mathias Nyman <mathias.nyman@linux.intel.com>
Otherwise I'll submit it later with other small changes
-Mathias
next prev parent reply other threads:[~2022-02-18 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 13:35 [PATCH] xhci: omit mem read just after allocation of trb Oliver Neukum
2022-02-18 8:26 ` Mathias Nyman [this message]
2022-02-24 10:19 ` Greg KH
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=4632126f-97da-65c9-a240-b86f4490afe0@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=oneukum@suse.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 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).