From: Vinod Koul <vkoul@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com,
rdunlap@infradead.org
Subject: Re: [PATCH v2] soundwire: bus: Make IRQ handling conditionally built
Date: Mon, 2 Oct 2023 21:31:53 +0530 [thread overview]
Message-ID: <ZRrpcfKHY4/jJiCS@matsya> (raw)
In-Reply-To: <20231002085252.GM103419@ediswmail.ad.cirrus.com>
On 02-10-23, 08:52, Charles Keepax wrote:
> On Thu, Sep 21, 2023 at 11:37:53AM +0200, Vinod Koul wrote:
> >
> > On Wed, 20 Sep 2023 17:04:01 +0100, Charles Keepax wrote:
> > > SoundWire has provisions for a simple callback for the IRQ handling so
> > > has no hard dependency on IRQ_DOMAIN, but the recent addition of IRQ
> > > handling was causing builds without IRQ_DOMAIN to fail. Resolve this by
> > > moving the IRQ handling into its own file and only add it to the build
> > > when IRQ_DOMAIN is included in the kernel.
> > >
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/1] soundwire: bus: Make IRQ handling conditionally built
> > commit: 3b6c4a11bf2b810f772f5c2c1ef6eef3fc268246
> >
>
> Did something go wrong here? I still don't see a commit with
> that SHA in your tree.
It was applied to fixes and I missed pushing that, it is pushed now
--
~Vinod
prev parent reply other threads:[~2023-10-02 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 16:04 [PATCH v2] soundwire: bus: Make IRQ handling conditionally built Charles Keepax
2023-09-21 9:37 ` Vinod Koul
2023-10-02 8:52 ` Charles Keepax
2023-10-02 16:01 ` Vinod Koul [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=ZRrpcfKHY4/jJiCS@matsya \
--to=vkoul@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rdunlap@infradead.org \
--cc=sanyog.r.kale@intel.com \
--cc=yung-chuan.liao@linux.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