From: Vinod Koul <vkoul@kernel.org>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
linux-arm-kernel@lists.infradead.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Microchip UNG Driver List <UNGLinuxDriver@microchip.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH linux-next v2 1/1] phy: Sparx5 Eth SerDes: Use direct register operations
Date: Tue, 6 Apr 2021 10:38:09 +0530 [thread overview]
Message-ID: <YGvsuVMz54R5O7Eb@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20210329141309.612459-2-steen.hegelund@microchip.com>
On 29-03-21, 16:13, Steen Hegelund wrote:
> Use direct register operations instead of a table of register
> information to lower the stack usage.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2021-04-06 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 14:13 [PATCH linux-next v2 0/1] Sparx5 SerDes: Fixed stack frame size warning Steen Hegelund
2021-03-29 14:13 ` [PATCH linux-next v2 1/1] phy: Sparx5 Eth SerDes: Use direct register operations Steen Hegelund
2021-04-06 5:08 ` Vinod Koul [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=YGvsuVMz54R5O7Eb@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=steen.hegelund@microchip.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