From: Luis Chamberlain <mcgrof@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [4.14] Security fixes (blktrace, i40e)
Date: Thu, 12 Nov 2020 22:38:37 +0000 [thread overview]
Message-ID: <20201112223837.GH4332@42.do-not-panic.com> (raw)
In-Reply-To: <20201108091214.GB44749@kroah.com>
On Sun, Nov 08, 2020 at 10:12:14AM +0100, Greg Kroah-Hartman wrote:
> On Sun, Nov 08, 2020 at 03:04:14AM -0600, Luis Chamberlain wrote:
> > I'd like some more time for this, to review on older kernels. Don't think
> > it's the best yet
>
> What is "this" and what is "the best yet"? Which patch(s) here are you
> referring to in your context-less top-post? :)
Sorry, I had to send the email as I did as I was not able to access a
computer to properly reply on time (local hurricane cut power off and
internet for a while), and in proper form, and so I figured it would be
more prudent to request to *yield* merging until I do proper review.
Given I am replying to patches which I authored I figured you could
at least infer the email was about blktrace... so you are really
exagerating contextless comment here.
Anyway, you can carry on with the fix for blktrace to be merged,
the concerne would be if you decide to backport the other important
fix "block: revert back to synchronous request_queue removal".
That is, do not merge that loosely, even if you don't see any issues.
This requires a bit more work to backport.
Luis
prev parent reply other threads:[~2020-11-12 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 0:17 [Intel-wired-lan] [4.14] Security fixes (blktrace, i40e) Ben Hutchings
2020-11-07 15:28 ` Greg Kroah-Hartman
2020-11-08 9:04 ` Luis Chamberlain
2020-11-08 9:12 ` Greg Kroah-Hartman
2020-11-12 22:38 ` Luis Chamberlain [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=20201112223837.GH4332@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=intel-wired-lan@osuosl.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