On Mon, 27 Mar 2023 23:25:49 -0700 John Hubbard wrote:
> On the patch process, I see that this applies to linux-stable's 6.1.y
> branch. I'd suggest two things:
>
> 1) Normally, what I've seen done is to post against either the current
> top of tree linux.git, or else against one of the
On Fri, 21 Oct 2022 15:53:19 -0400 Lyude Paul wrote:
> > Hi Andrew/Ben, apologies I must have accidentally dropped this small hunk
> > when rebasing prior to sending v2 of the original series. Without this
> > migration from GPU to CPU won't work in Nouveau so hopefully one of you can
> > take
On Wed, 28 Sep 2022 22:01:22 +1000 Alistair Popple wrote:
> @@ -1401,22 +1494,7 @@ static int dmirror_device_init(struct dmirror_device
> *mdevice, int id)
>
> static void dmirror_device_remove(struct dmirror_device *mdevice)
> {
> - unsigned int i;
> -
> - if
On Wed, 16 Jun 2021 20:59:27 +1000 Alistair Popple wrote:
> This is my series to add support for SVM atomics in Nouveau
Can we please have a nice [0/n] overview for this patchset?
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
On Mon, 24 May 2021 23:27:22 +1000 Alistair Popple wrote:
> Some devices require exclusive write access to shared virtual
> memory (SVM) ranges to perform atomic operations on that memory. This
> requires CPU page tables to be updated to deny access whilst atomic
> operations are occurring.
>
>
On Fri, 1 May 2020 15:20:44 -0300 Jason Gunthorpe wrote:
> From: Jason Gunthorpe
>
> There is no reason for a user to select this or not directly - it should
> be selected by drivers that are going to use the feature, similar to how
> CONFIG_HMM_MIRROR works.
>
> Currently all drivers
On Sun, 29 Mar 2020 19:12:35 +0530 Anshuman Khandual
wrote:
>
>
> On 03/20/2020 10:24 AM, Anshuman Khandual wrote:
> > This series renames pmd_mknotpresent() as pmd_mknotvalid(). Before that it
> > drops an existing pmd_mknotpresent() definition from powerpc platform which
> > was never
On Fri, 28 Jun 2019 12:14:44 -0700 Dan Williams
wrote:
> I believe -mm auto drops patches when they appear in the -next
> baseline. So it should "just work" to pull it into the series and send
> it along for -next inclusion.
Yup. Although it isn't very "auto" - I manually check that the patch
On Thu, 13 Jun 2019 14:24:20 -0600 Logan Gunthorpe wrote:
>
>
> On 2019-06-13 2:21 p.m., Dan Williams wrote:
> > On Thu, Jun 13, 2019 at 1:18 PM Logan Gunthorpe wrote:
> >>
> >>
> >>
> >> On 2019-06-13 12:27 p.m., Dan Williams wrote:
> >>> On Thu, Jun 13, 2019 at 2:43 AM Christoph Hellwig
On Thu, 3 Jan 2013 11:40:47 -0800
Linus Torvalds torva...@linux-foundation.org wrote:
On Thu, Jan 3, 2013 at 5:11 AM, Alan Cox a...@lxorguk.ukuu.org.uk wrote:
The fb layer locking was broken. I posted patches early December which
should have fixed the ones we know about. ('fb: Rework
On Fri, 19 Nov 2010 10:53:52 -0500
Matthew Garrett m...@redhat.com wrote:
There may be multiple ways of controlling the backlight on a given machine.
Allow drivers to expose the type of interface they are providing, making
it possible for userspace to make appropriate policy decisions.
...
On Fri, 19 Nov 2010 20:25:59 +
Matthew Garrett mj...@srcf.ucam.org wrote:
On Fri, Nov 19, 2010 at 12:05:23PM -0800, Andrew Morton wrote:
On Fri, 19 Nov 2010 10:53:52 -0500
Matthew Garrett m...@redhat.com wrote:
There may be multiple ways of controlling the backlight on a given
On Tue, 20 Jul 2010 21:19:23 +0200
Marcin Slusarz marcin.slus...@gmail.com wrote:
We don't want vga16fb to mess with hardware initialized by other driver.
Detect it and refuse to load.
It fixes nouveau interrupt storm on some machines.
Signed-off-by: Marcin Slusarz marcin.slus...@gmail.com
13 matches
Mail list logo
