From: <Mario.Limonciello@dell.com>
To: <andy.shevchenko@gmail.com>, <pali.rohar@gmail.com>
Cc: <dvhart@infradead.org>, <linux-kernel@vger.kernel.org>,
<platform-driver-x86@vger.kernel.org>
Subject: RE: [PATCH v2] platform/x86: dell-laptop: Allocate buffer on heap rather than globally
Date: Mon, 5 Feb 2018 16:49:35 +0000 [thread overview]
Message-ID: <9b01161fb81043b79cf9ade8ec348fff@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <CAHp75VcnDKP=kNPh7pU1v_f0+oP64ByKAOmkZzXNUVaXg=wDSg@mail.gmail.com>
> -----Original Message-----
> From: Andy Shevchenko [mailto:andy.shevchenko@gmail.com]
> Sent: Sunday, February 4, 2018 8:28 AM
> To: Pali Rohár <pali.rohar@gmail.com>
> Cc: Limonciello, Mario <Mario_Limonciello@Dell.com>; Darren Hart
> <dvhart@infradead.org>; LKML <linux-kernel@vger.kernel.org>; Platform Driver
> <platform-driver-x86@vger.kernel.org>
> Subject: Re: [PATCH v2] platform/x86: dell-laptop: Allocate buffer on heap rather
> than globally
>
> On Sun, Feb 4, 2018 at 2:09 PM, Pali Rohár <pali.rohar@gmail.com> wrote:
> > On Wednesday 31 January 2018 11:47:35 Mario Limonciello wrote:
> >> There is no longer a need for the buffer to be defined in
> >> first 4GB physical address space.
> >>
> >> Furthermore there may be race conditions with multiple different functions
> >> working on a module wide buffer causing incorrect results.
> >>
> >> Fixes: 549b4930f057658dc50d8010e66219233119a4d8
>
> He-h, I had to notice this earlier...
>
> > Ok, you can add my:
> > Reviewed-by: Pali Rohár <pali.rohar@gmail.com>
>
> Thanks and sorry, Pali, it's in for-next already, can't rebase.
Andy,
Since it's already in for-next it's probably too late to add the stable CC too right?
So what's the proper time now to send this to @stable? And should I just forward existing
patch?
Thanks,
next prev parent reply other threads:[~2018-02-05 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 17:47 Mario Limonciello
2018-01-31 18:40 ` Andy Shevchenko
2018-02-04 12:09 ` Pali Rohár
2018-02-04 14:27 ` Andy Shevchenko
2018-02-05 16:49 ` Mario.Limonciello [this message]
2018-02-06 0:57 ` Darren Hart
2018-02-07 20:17 ` Mario.Limonciello
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=9b01161fb81043b79cf9ade8ec348fff@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®