From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] zorro: Use helpers from ioport.h
Date: Fri, 26 Apr 2024 18:32:57 +0300 [thread overview]
Message-ID: <ZivJKZ8Pp_bfLcvO@smile.fi.intel.com> (raw)
In-Reply-To: <CAMuHMdVoDDV-VgPJL75u_t3KeAPhb1xEFX2VigVC3oS51pG6wA@mail.gmail.com>
On Mon, Sep 04, 2023 at 11:31:03AM +0200, Geert Uytterhoeven wrote:
> On Thu, Aug 31, 2023 at 2:16 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > We can use the DEFINE_RES_MEM_NAMED() macro and resource_contains() helper
> > instead of reimplementing them in the code. No functional change intended.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Thanks for your patch!
>
> > --- a/drivers/zorro/zorro.c
> > +++ b/drivers/zorro/zorro.c
> > @@ -117,17 +117,13 @@ static struct resource __init *zorro_find_parent_resource(
> > int i;
> >
> > for (i = 0; i < bridge->num_resources; i++) {
> > - struct resource *r = &bridge->resource[i];
> > -
> > - if (zorro_resource_start(z) >= r->start &&
> > - zorro_resource_end(z) <= r->end)
> > - return r;
> > + if (resource_contains(&bridge->resource[i], &z->resource)
>
> Missing closing parenthesis. What happened to your cross-compiler?
>
> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
> i.e. will queue in the m68k for-v6.7 branch, with the above fixed.
Seems never got queued, should I send a v2 with the above fixed?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-26 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 12:16 [PATCH v1 1/1] zorro: Use helpers from ioport.h Andy Shevchenko
2023-09-04 9:31 ` Geert Uytterhoeven
2023-09-04 9:54 ` Andy Shevchenko
2024-04-26 15:32 ` Andy Shevchenko [this message]
2024-04-26 15:42 ` Geert Uytterhoeven
2024-04-26 15:49 ` Andy Shevchenko
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=ZivJKZ8Pp_bfLcvO@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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