All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Piyush Sachdeva <piyushs@linux.ibm.com>
Cc: stable@vger.kernel.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	Tarun Sahu <tsahu@linux.ibm.com>,
	Joao Martins <joao.m.martins@oracle.com>,
	Muchun Song <songmuchun@bytedance.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.2.16] mm/vmemmap/devdax: fix kernel crash when probing devdax devices
Date: Thu, 1 Jun 2023 10:44:11 +0100	[thread overview]
Message-ID: <2023060128-kindness-vision-7ce7@gregkh> (raw)
In-Reply-To: <43baafa1897127eb0e362bba3e785740017afc50.1684485577.git.piyushs@linux.ibm.com>

On Tue, May 30, 2023 at 06:51:46PM +0530, Piyush Sachdeva wrote:
> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
> 
> [ Upstream commit 87a7ae75d7383afa998f57656d1d14e2a730cc47 ]

6.2.y is long end-of-life, so there's nothing we can do here.  Always
remember to check the front page of kernel.org to see the list of
kernels to check if they are active or not.

thanks,

greg k-h

  reply	other threads:[~2023-06-01  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07 13:10 FAILED: patch "[PATCH] mm/vmemmap/devdax: fix kernel crash when probing devdax" failed to apply to 6.2-stable tree gregkh
2023-05-19 11:09 ` [PATCH 6.3.2] mm/vmemmap/devdax: fix kernel crash when probing devdax devices Piyush Sachdeva
2023-05-30 13:21   ` [PATCH 6.2.16] " Piyush Sachdeva
2023-05-30 13:03   ` [PATCH 6.1.30] " Piyush Sachdeva
2023-06-01  9:44   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-07 13:10 FAILED: patch "[PATCH] mm/vmemmap/devdax: fix kernel crash when probing devdax" failed to apply to 6.1-stable tree gregkh

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=2023060128-kindness-vision-7ce7@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=dan.j.williams@intel.com \
    --cc=joao.m.martins@oracle.com \
    --cc=mike.kravetz@oracle.com \
    --cc=piyushs@linux.ibm.com \
    --cc=songmuchun@bytedance.com \
    --cc=stable@vger.kernel.org \
    --cc=tsahu@linux.ibm.com \
    /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.