From: Luciano Coelho <luciano.coelho@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Avraham Stern <avraham.stern@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 4.19] iwlwifi: mvm: Send LQ command as async when necessary
Date: Thu, 24 Jan 2019 19:55:30 +0200 [thread overview]
Message-ID: <83b55431ab3d8c5470b268f488413c78e81bb7bb.camel@intel.com> (raw)
In-Reply-To: <20190124175033.GA7484@kroah.com>
On Thu, 2019-01-24 at 18:50 +0100, Greg KH wrote:
> On Thu, Jan 24, 2019 at 10:47:12AM +0200, Luciano Coelho wrote:
> > Hi Greg,
> >
> > This patch fixes a few bugs reported in bugzilla, about scheduling
> > while atomic. There were at least 4 reports[1], so it seems to be
> > a
> > common occurrence.
> >
> > The patch looks large, but it's basically just a new boolean been
> > passed around in order to decide whether we send a message
> > synchronously or not.
> >
> > Is it possible to queue it for 4.19.y?
> >
> > [1] https://bugzilla.kernel.org/show_bug.cgi?id=200991
> > https://bugzilla.kernel.org/show_bug.cgi?id=202219
> > https://bugzilla.kernel.org/show_bug.cgi?id=201297
> > https://bugzilla.kernel.org/show_bug.cgi?id=201355
>
> Now queued up, thanks.
Thanks, Greg!
> Note, apis that add "booleans" to them are horrid, good luck
> maintaining that mess :(
Yeah, you're right. This patch demonstrates that, the boolean needs to
be passed from and to everywhere. We should probably just split that
function in two. Thanks for the comment.
--
Cheers,
Luca.
prev parent reply other threads:[~2019-01-24 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 11:50 [PATCH 4.19] iwlwifi: mvm: Send LQ command as async when necessary Emmanuel Grumbach
2019-01-24 8:47 ` Luciano Coelho
2019-01-24 17:50 ` Greg KH
2019-01-24 17:55 ` Luciano Coelho [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=83b55431ab3d8c5470b268f488413c78e81bb7bb.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=avraham.stern@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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