From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jonathan Lemon <jonathan.lemon@gmail.com>,
Richard Cochran <richardcochran@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v1 1/1] ptp: ocp: Use DEFINE_RES_*() in place
Date: Thu, 21 Dec 2023 14:58:53 +0000 [thread overview]
Message-ID: <5e5fb1fa-33a3-470c-b479-24019f322ed3@linux.dev> (raw)
In-Reply-To: <20231221140607.2760115-1-andriy.shevchenko@linux.intel.com>
On 21/12/2023 14:06, Andy Shevchenko wrote:
> There is no need to have an intermediate functions as DEFINE_RES_*()
> macros are represented by compound literals. Just use them in place.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/ptp/ptp_ocp.c | 26 ++++++--------------------
> 1 file changed, 6 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/ptp/ptp_ocp.c b/drivers/ptp/ptp_ocp.c
> index 4021d3d325f9..306353a69231 100644
> --- a/drivers/ptp/ptp_ocp.c
> +++ b/drivers/ptp/ptp_ocp.c
> @@ -1716,20 +1716,6 @@ ptp_ocp_get_mem(struct ptp_ocp *bp, struct ocp_resource *r)
> return __ptp_ocp_get_mem(bp, start, r->size);
> }
>
> -static void
> -ptp_ocp_set_irq_resource(struct resource *res, int irq)
> -{
> - struct resource r = DEFINE_RES_IRQ(irq);
> - *res = r;
> -}
> -
> -static void
> -ptp_ocp_set_mem_resource(struct resource *res, resource_size_t start, int size)
> -{
> - struct resource r = DEFINE_RES_MEM(start, size);
> - *res = r;
> -}
> -
> static int
> ptp_ocp_register_spi(struct ptp_ocp *bp, struct ocp_resource *r)
> {
> @@ -1741,15 +1727,15 @@ ptp_ocp_register_spi(struct ptp_ocp *bp, struct ocp_resource *r)
> int id;
>
> start = pci_resource_start(pdev, 0) + r->offset;
> - ptp_ocp_set_mem_resource(&res[0], start, r->size);
> - ptp_ocp_set_irq_resource(&res[1], pci_irq_vector(pdev, r->irq_vec));
> + res[0] = DEFINE_RES_MEM(start, r->size);
> + res[1] = DEFINE_RES_IRQ(pci_irq_vector(pdev, r->irq_vec));
>
> info = r->extra;
> id = pci_dev_id(pdev) << 1;
> id += info->pci_offset;
>
> p = platform_device_register_resndata(&pdev->dev, info->name, id,
> - res, 2, info->data,
> + res, ARRAY_SIZE(res), info->data,
> info->data_size);
> if (IS_ERR(p))
> return PTR_ERR(p);
> @@ -1768,11 +1754,11 @@ ptp_ocp_i2c_bus(struct pci_dev *pdev, struct ocp_resource *r, int id)
>
> info = r->extra;
> start = pci_resource_start(pdev, 0) + r->offset;
> - ptp_ocp_set_mem_resource(&res[0], start, r->size);
> - ptp_ocp_set_irq_resource(&res[1], pci_irq_vector(pdev, r->irq_vec));
> + res[0] = DEFINE_RES_MEM(start, r->size);
> + res[1] = DEFINE_RES_IRQ(pci_irq_vector(pdev, r->irq_vec));
>
> return platform_device_register_resndata(&pdev->dev, info->name,
> - id, res, 2,
> + id, res, ARRAY_SIZE(res),
> info->data, info->data_size);
> }
>
Thanks, Andy!
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2023-12-21 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 14:06 [PATCH net-next v1 1/1] ptp: ocp: Use DEFINE_RES_*() in place Andy Shevchenko
2023-12-21 14:58 ` Vadim Fedorenko [this message]
2023-12-23 16:40 ` Simon Horman
2024-01-02 12:40 ` patchwork-bot+netdevbpf
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=5e5fb1fa-33a3-470c-b479-24019f322ed3@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=jonathan.lemon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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).