mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Tony Luck <tony.luck@intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"Joseph, Jithu" <jithu.joseph@intel.com>,
	markgross@kernel.org, ashok.raj@intel.com,
	ravi.v.shankar@intel.com, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH 0/2] Two fixes for IFS
Date: Sun, 10 Jul 2022 21:57:13 +0200	[thread overview]
Message-ID: <9ce8aa53-ed70-823f-3410-1f50d5b902c9@redhat.com> (raw)
In-Reply-To: <20220710182521.60642-1-tony.luck@intel.com>

Hi Tony,

On 7/10/22 20:25, Tony Luck wrote:
> Hans ... if you are pushing to Linus to add "BROKEN", then could
> you include these two patches to make it fractionally less broken?

Since the driver is going to be marked as BROKEN now anyways,
I don't see much value in getting these send last minute to Linus.

At this point in the kernel cycle (rc6 will be out in a couple
of hours likely) we really should avoid churn as much as possible.

Regards,

Hans



      parent reply	other threads:[~2022-07-10 19:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 15:19 [PATCH] platform/x86/intel/ifs: Allow non-default names for IFS image Jithu Joseph
2022-07-08 15:28 ` Greg KH
2022-07-08 18:34   ` Joseph, Jithu
2022-07-10 10:15     ` Greg KH
2022-07-10 13:42       ` Hans de Goede
2022-07-10 13:53         ` Greg KH
2022-07-10 14:08           ` Hans de Goede
2022-07-10 16:04             ` Joseph, Jithu
2022-07-10 16:09               ` Hans de Goede
2022-07-10 18:25             ` [PATCH 0/2] Two fixes for IFS Tony Luck
2022-07-10 18:25               ` [PATCH 1/2] Documentation: Correct IFS reload documentation Tony Luck
2022-07-10 20:00                 ` Greg KH
2022-07-10 18:25               ` [PATCH 2/2] platform/x86/intel/ifs: return error on load failure Tony Luck
2022-07-10 19:57               ` Hans de Goede [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=9ce8aa53-ed70-823f-3410-1f50d5b902c9@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jithu.joseph@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®