From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: dri-devel@lists.freedesktop.org,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
stable@vger.kernel.org
Subject: Re: [PATCH] io-mapping: Indicate mapping failure
Date: Tue, 21 Jul 2020 17:47:22 +0300 [thread overview]
Message-ID: <20200721144722.GH3703480@smile.fi.intel.com> (raw)
In-Reply-To: <20200721141641.81112-2-michael.j.ruhl@intel.com>
On Tue, Jul 21, 2020 at 10:16:41AM -0400, Michael J. Ruhl wrote:
> Sometimes it is good to know when your mapping failed.
Can you elaborate...
> Fixes: cafaf14a5d8f ("io-mapping: Always create a struct to hold metadata about the io-mapping"
...especially taking into account that Fixes implies regression / bug?
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] io-mapping: Indicate mapping failure
Date: Tue, 21 Jul 2020 17:47:22 +0300 [thread overview]
Message-ID: <20200721144722.GH3703480@smile.fi.intel.com> (raw)
In-Reply-To: <20200721141641.81112-2-michael.j.ruhl@intel.com>
On Tue, Jul 21, 2020 at 10:16:41AM -0400, Michael J. Ruhl wrote:
> Sometimes it is good to know when your mapping failed.
Can you elaborate...
> Fixes: cafaf14a5d8f ("io-mapping: Always create a struct to hold metadata about the io-mapping"
...especially taking into account that Fixes implies regression / bug?
--
With Best Regards,
Andy Shevchenko
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-07-21 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 14:16 io-mapping: Indicate mapping failure Michael J. Ruhl
2020-07-21 14:16 ` [PATCH] " Michael J. Ruhl
2020-07-21 14:16 ` Michael J. Ruhl
2020-07-21 14:47 ` Andy Shevchenko [this message]
2020-07-21 14:47 ` Andy Shevchenko
2020-07-21 15:00 ` Ruhl, Michael J
2020-07-21 15:00 ` Ruhl, Michael J
2020-07-21 15:06 ` Mike Rapoport
2020-07-21 15:06 ` Mike Rapoport
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=20200721144722.GH3703480@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=michael.j.ruhl@intel.com \
--cc=rppt@linux.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.