From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v1 1/1] drm/i915: Include only needed headers in ascii85.h
Date: Wed, 7 Apr 2021 16:41:25 +0300 [thread overview]
Message-ID: <YG22hduvvsEB3JcM@smile.fi.intel.com> (raw)
In-Reply-To: <YG22OhNg3iQ8DFXW@smile.fi.intel.com>
On Wed, Apr 07, 2021 at 04:40:10PM +0300, Andy Shevchenko wrote:
> On Wed, Apr 07, 2021 at 03:46:37PM +0300, Jani Nikula wrote:
> > On Wed, 07 Apr 2021, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > > The ascii85.h is user of exactly two headers, i.e. math.h and types.h.
> > > There is no need to carry on entire kernel.h.
> > >
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > That's hardly drm/i915 specific!
>
> It was originated from i915!
>
> > Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Thanks!
>
> > But who's going to pick it up and, hopefully, change the subject prefix
> > to ascii85 or something?
>
> It's drm specific. Should I leave drm and resend? Or what is the general rule
> for drm misc changes?
Since the topic comes up about drm misc, can somebody approve push access from
me to that?
https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/311
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-04-07 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 12:23 [PATCH v1 1/1] drm/i915: Include only needed headers in ascii85.h Andy Shevchenko
2021-04-07 12:46 ` Jani Nikula
2021-04-07 13:40 ` Andy Shevchenko
2021-04-07 13:41 ` Andy Shevchenko [this message]
2021-05-17 12:19 ` Andy Shevchenko
2021-05-17 12:29 ` Christoph Hellwig
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=YG22hduvvsEB3JcM@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.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