Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Bilge Aydin <b.aydin@samsung.com>
Cc: stable@vger.kernel.org
Subject: Re: [APS-24624] Missing patch in K5.15 against kernel panic
Date: Tue, 10 Dec 2024 14:34:05 +0100	[thread overview]
Message-ID: <2024121023-unrushed-envelope-477d@gregkh> (raw)
In-Reply-To: <0bd701db4b06$b7cbdf00$27639d00$@samsung.com>

On Tue, Dec 10, 2024 at 02:23:35PM +0100, Bilge Aydin wrote:
> This communication (including any attachments) contains information which may be confidential and/or privileged. It is for the exclusive use of the intended recipient(s) so, if you have received this communication in error, please do not distribute, copy or use this communication or its contents but notify the sender immediately and then destroy any copies of it. Due to the nature of the Internet, the sender is unable to ensure the integrity of this message. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of the company the sender works for.

Note, this footer is not compatible with kernel development at all, and
normally causes emails to be automatically deleted.  For some reason it
snuck through my filters, but for many others, it might not have.
Please remove it on your responses.

thanks,

greg k-h

      parent reply	other threads:[~2024-12-10 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20241210132338eucas1p2228b89f17ab46f90075c07806765a5aa@eucas1p2.samsung.com>
2024-12-10 13:23 ` [APS-24624] Missing patch in K5.15 against kernel panic Bilge Aydin
2024-12-10 13:33   ` Greg KH
2024-12-10 13:48     ` Bilge Aydin
2024-12-10 14:01       ` 'Greg KH'
2024-12-10 13:34   ` Greg KH [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=2024121023-unrushed-envelope-477d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=b.aydin@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox