public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: cam enih <nanericwang@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	stable@vger.kernel.org, KY Srinivasan <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: stable 5.10: please revert c4dc584a2d4c8d74b054f09d67e0a076767bdee5
Date: Thu, 14 Apr 2022 09:17:18 +0200	[thread overview]
Message-ID: <YlfKfrisuU/BoBrd@kroah.com> (raw)
In-Reply-To: <CAPB3MF7HGfbVtdAYrzsTtgw59tcVRpVk4qi3Nz4=WbsA73nn5w@mail.gmail.com>

On Thu, Apr 14, 2022 at 03:00:30PM +0800, cam enih wrote:
> sorry for confusion.

Again, please do not top-post.

> 1. MR=merge request;

We do not have merge requests in the kernel, so I do not understand what
you are saying we do differently here.

> 2. In this case, the change depends on a non-existing config option which I
> believe can be detected at compile time.

Specifically, please show us how we should have caught this so we can do
that in the future.  I do not see how this can be detected at compile
time as it is no different from a normal config option not being
selected.

thanks,

greg k-h

      parent reply	other threads:[~2022-04-14  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 16:07 stable 5.10: please revert c4dc584a2d4c8d74b054f09d67e0a076767bdee5 Randy Dunlap
2022-04-10  2:07 ` Sasha Levin
     [not found]   ` <CAPB3MF52aRsiq8wxFmQfK+KO=AVEhD+ww2O-0hj1KW5ntf3LXw@mail.gmail.com>
2022-04-14  5:57     ` Greg Kroah-Hartman
     [not found]       ` <CAPB3MF7HGfbVtdAYrzsTtgw59tcVRpVk4qi3Nz4=WbsA73nn5w@mail.gmail.com>
2022-04-14  7:17         ` Greg Kroah-Hartman [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=YlfKfrisuU/BoBrd@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=nanericwang@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=sashal@kernel.org \
    --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