public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Raag Jadav <raag.jadav@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Dave Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Cleanup io.h
Date: Mon, 3 Mar 2025 11:44:19 +0200	[thread overview]
Message-ID: <Z8V587DSa1VE_BO3@smile.fi.intel.com> (raw)
In-Reply-To: <fa3b2ef5-e2f8-473f-9e9c-c855d70230cf@app.fastmail.com>

On Mon, Mar 03, 2025 at 09:31:06AM +0100, Arnd Bergmann wrote:
> On Mon, Mar 3, 2025, at 08:48, Andy Shevchenko wrote:
> > On Fri, Feb 28, 2025 at 09:08:15PM +0200, Raag Jadav wrote:
> >> > > > Ah, you mean devres related?
> >> > > 
> >> > > Yeah, couldn't find it on Arnd's tree and I'm not sure if this series
> >> > > works without it.
> >> > 
> >> > But err.h is included in the io.h, no? Or did I misunderstand the point?
> >> 
> >> First patch on the immutable tag moves IOMEM_ERR_PTR() to err.h and here
> >> we're dropping err.h from io.h. So without the tag this series will probably
> >> break IOMEM_ERR_PTR().
> >
> > I see, I think it might be due to some other includes that make this happen.
> > Whatever, I assume that Arnd heavily tested this anyway, so it's good to go
> > independently on the immutable tag..
> 
> I see that err.h gets included through at least linux/string.h,
> linux/logic_pio.h and (depending on the architecture architectures)
> asm/page.h, so there is no huge risk of something breaking here ;-)
> 
> Ideally all of the above should be removed here, but to do
> it right, the linux/pgtable.h dependency needs to also be replaced
> with a smaller pgprot_t specific one, which takes a bit of
> cross-platform work as the definition is not in a consistent
> place at the moment.
> 
> The change below still builds fine, and that likely indicates
> that the same headers are still included from either asm/io.h
> or asm/pgtable.h on the architectures I'm testing.

Sounds even better. Can you submit a formal patch that other CIs will have
a chance to go through this?

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2025-03-03  9:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  7:07 [PATCH v3 0/2] Cleanup io.h Raag Jadav
2025-02-27  7:07 ` [PATCH v3 1/2] drm/draw: include missing headers Raag Jadav
2025-02-27  7:07 ` [PATCH v3 2/2] io.h: drop unused headers Raag Jadav
2025-02-27 15:25 ` [PATCH v3 0/2] Cleanup io.h Andy Shevchenko
2025-02-28 17:11   ` Arnd Bergmann
2025-02-28 17:41     ` Raag Jadav
2025-02-28 18:41       ` Andy Shevchenko
2025-02-28 18:42         ` Andy Shevchenko
2025-02-28 18:45           ` Raag Jadav
2025-02-28 18:52             ` Andy Shevchenko
2025-02-28 19:08               ` Raag Jadav
2025-03-03  7:48                 ` Andy Shevchenko
2025-03-03  8:31                   ` Arnd Bergmann
2025-03-03  9:44                     ` Andy Shevchenko [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=Z8V587DSa1VE_BO3@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=arnd@arndb.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raag.jadav@intel.com \
    --cc=simona@ffwll.ch \
    /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