All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Borislav Petkov <bp@alien8.de>
Cc: Dinh Nguyen <dinguyen@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	James Morse <james.morse@arm.com>,
	Robert Richter <rric@kernel.org>, <linux-edac@vger.kernel.org>
Subject: Re: [PATCH 1/2] edac: altera: fix deferred probing
Date: Fri, 28 Jan 2022 22:53:33 +0300	[thread overview]
Message-ID: <475867ea-eb32-0106-728b-ec4cd2f99c55@omp.ru> (raw)
In-Reply-To: <YfRBCPRPkf+gD18/@zn.tnic>

On 1/28/22 10:16 PM, Borislav Petkov wrote:

[...]

>> Ah, you were wondering about returing -EPROBE_DEFER? It started to be returned
>> by the commit 9ec36cafe43bf835f8f29273597a5b0cbc8267ef several months before that...
> 
> More precisely, I'm wondering after which commit does the deferred
> probing code interpret -EPROBE_DEFER properly so that a backport of this
> commit would be even worth the trouble?

   That was even longer ago, done by the commit d1c3414c2a9d10ef7f0f7665f5d2947cd088c093
in 20212, if you must know. :-)

> Because if we backport it to kernel where there's not even deferred
> probing support, then that backport is a waste of time.

   I think you're overly caustious in this case. :-)

MBR, Sergey

  parent reply	other threads:[~2022-01-28 19:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 18:55 [PATCH 0/2] Fix deferred probing in the EDAC drivers Sergey Shtylyov
2022-01-24 18:55 ` [PATCH 1/2] edac: altera: fix deferred probing Sergey Shtylyov
2022-01-26 16:52   ` Dinh Nguyen
2022-01-28 18:36     ` Borislav Petkov
2022-01-28 18:53       ` Sergey Shtylyov
2022-01-28 19:02         ` Sergey Shtylyov
2022-01-28 19:16           ` Borislav Petkov
2022-01-28 19:17             ` Sergey Shtylyov
2022-01-28 19:20               ` Borislav Petkov
2022-01-28 19:35                 ` Sergey Shtylyov
2022-01-28 19:47                   ` Sergey Shtylyov
2022-01-29  6:48                 ` Greg KH
2022-01-29 10:33                   ` Borislav Petkov
2022-01-28 19:53             ` Sergey Shtylyov [this message]
2022-01-28 19:56               ` Sergey Shtylyov
2022-01-24 18:55 ` [PATCH 2/2] edac: xgene: " Sergey Shtylyov
2022-01-28 22:39 ` [PATCH 0/2] Fix deferred probing in the EDAC drivers Borislav Petkov

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=475867ea-eb32-0106-728b-ec4cd2f99c55@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=bp@alien8.de \
    --cc=dinguyen@kernel.org \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rric@kernel.org \
    --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 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.