From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
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: Fri, 28 Feb 2025 20:52:51 +0200 [thread overview]
Message-ID: <Z8IGA821OAgYN-K1@smile.fi.intel.com> (raw)
In-Reply-To: <Z8IERmwHXUuJoD4S@black.fi.intel.com>
On Fri, Feb 28, 2025 at 08:45:26PM +0200, Raag Jadav wrote:
> On Fri, Feb 28, 2025 at 08:42:10PM +0200, Andy Shevchenko wrote:
> > On Fri, Feb 28, 2025 at 08:41:33PM +0200, Andy Shevchenko wrote:
> > > On Fri, Feb 28, 2025 at 07:41:55PM +0200, Raag Jadav wrote:
> > > > On Fri, Feb 28, 2025 at 06:11:16PM +0100, Arnd Bergmann wrote:
> > > > > On Thu, Feb 27, 2025, at 16:25, Andy Shevchenko wrote:
> > > > > > On Thu, Feb 27, 2025 at 12:37:45PM +0530, Raag Jadav wrote:
> > > > > >> This series attempts to cleanup io.h with "include what you use" approach.
> > > > > >> This depends on changes available on immutable tag[1].
> > > > > >>
> > > > > >> Although this series is too trivial in the grand scheme of things, it is
> > > > > >> still a tiny step towards untangling core headers. I have success results
> > > > > >> from LKP for this series but there can still be corner cases. So perhaps
> > > > > >> we can queue this on a temporary branch which we can use to submit fixes
> > > > > >> in case of fallout.
> > > > > >>
> > > > > >> Future plan is to use the excellent analysis[2][3] by Arnd to cleanup other
> > > > > >> headers.
> > > > > >>
> > > > > >> [1] https://lore.kernel.org/r/Z7xGpz3Q4Zj6YHx7@black.fi.intel.com
> > > > > >> [2] https://lore.kernel.org/r/2342b516-2c6e-42e5-b4f4-579b280823ba@app.fastmail.com
> > > > > >> [3] https://lore.kernel.org/r/f6eb011b-40fb-409a-b2b2-a09d0e770bbd@app.fastmail.com
> > > > > >
> > > > > > I believe Arnd can take it through his tree for headers as DRM part is
> > > > > > Acked already.
> > > > >
> > > > > I've applied it yesterday and not seen any regression reports so far.
> > > >
> > > > Probably because the immutable tag is already in -next?
> > >
> > > Is there any?
> >
> > 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?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-28 18:52 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 [this message]
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
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=Z8IGA821OAgYN-K1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.