From: b-ak <anur.bhargav@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: tlv320aic32x4: Kernel OOPS while entering DAPM standby mode
Date: Mon, 7 Jan 2019 23:10:30 +0530 [thread overview]
Message-ID: <20190107174030.GA12944@Ideapad-330S> (raw)
In-Reply-To: <20190107125907.GC9570@sirena.org.uk>
On Mon, Jan 07, 2019 at 12:59:07PM +0000, Mark Brown wrote:
> On Sat, Jan 05, 2019 at 10:16:22AM +0530, b-ak wrote:
>
> >
> > Hi Mark,
> >
> > Fixed the build error.
> >
> > Thanks,
> > Bhargav
> >
>
> Please submit patches following the process covered in
> submitting-patches.rst, don't send them as attachments to replies in the
> middle of threads. Doing that confuses all the tooling for handling
> patches.
Ok. I made a mistake while sending it with Mutt.
Will be sending it inline now.
next prev parent reply other threads:[~2019-01-07 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 17:06 [PATCH] ASoC: tlv320aic32x4: Kernel OOPS while entering DAPM standby mode b-ak
2019-01-03 12:45 ` Mark Brown
2019-01-03 19:34 ` b-ak
2019-01-04 16:40 ` b-ak
2019-01-05 4:46 ` b-ak
2019-01-07 12:59 ` Mark Brown
2019-01-07 17:40 ` b-ak [this message]
2019-01-07 17:45 ` [PATCH v2] " b-ak
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=20190107174030.GA12944@Ideapad-330S \
--to=anur.bhargav@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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