public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
	linux-kernel@vger.kernel.org,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v1 1/1] ASoC: madera: Replace kernel.h with the necessary inclusions
Date: Mon, 24 Jan 2022 18:22:27 +0200	[thread overview]
Message-ID: <Ye7SQ7Na4Q5KyvOk@smile.fi.intel.com> (raw)
In-Reply-To: <20211229095345.GX18506@ediswmail.ad.cirrus.com>

On Wed, Dec 29, 2021 at 09:53:45AM +0000, Charles Keepax wrote:
> On Wed, Dec 22, 2021 at 06:45:34PM +0200, Andy Shevchenko wrote:
> > When kernel.h is used in the headers it adds a lot into dependency hell,
> > especially when there are circular dependencies are involved.
> > 
> > Replace kernel.h inclusion with the list of what is really being used.

> Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>

Thanks!

Takashi, should I resend this?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-01-24 16:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 16:45 [PATCH v1 1/1] ASoC: madera: Replace kernel.h with the necessary inclusions Andy Shevchenko
2021-12-29  9:53 ` Charles Keepax
2022-01-24 16:22   ` Andy Shevchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-03 17:07 Andy Shevchenko
2022-06-06  9:29 ` Richard Fitzgerald
2022-07-03 15:36   ` Andy Shevchenko
2022-07-04 10:36     ` Mark Brown
2022-07-04 15:30       ` Andy Shevchenko
2022-07-04 15:35         ` Mark Brown
2022-07-04 15:51           ` Andy Shevchenko
2022-07-04 16:24             ` Mark Brown
2022-07-05 18:52 ` Mark Brown

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=Ye7SQ7Na4Q5KyvOk@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=tiwai@suse.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