All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Adriana Kobylak <anoo@linux.ibm.com>
Cc: Jeremy Kerr <jk@ozlabs.org>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	medadyoung@gmail.com
Subject: Re: [PATCH] nbd:clear NBD_BOUND flag when NBD connection is closed
Date: Mon, 21 Jan 2019 12:43:45 +1100	[thread overview]
Message-ID: <CACPK8Xc-jB-vW60-+xGgf3igWTw=ZLBdjJG0niwbwU66_gA0KA@mail.gmail.com> (raw)
In-Reply-To: <c2c5408cf1a715df1e7ac6447620b5de@linux.vnet.ibm.com>

On Sat, 19 Jan 2019 at 02:38, Adriana Kobylak <anoo@linux.ibm.com> wrote:
>
> Hi Joel,
>
> Why has this patch been archived and marked as "Not Applicable"? -

This is a patch for the upstream kernel, not openbmc.

OpenBMC patches follow this process and contain the target branch they
want the maintainer to apply them to:

https://github.com/openbmc/linux/wiki/DevelopmentProcess#patch-submitters-wishing-to-have-a-change-included-through-this-process

If you want this backported to the openbmc kernel I suggest you follow
this process.

(I notice that this patch has not been accepted upstream. I suggest
you follow up on the upstream list before asking it to be submitted).

Cheers,

Joel

  reply	other threads:[~2019-01-21  1:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11  6:17 [PATCH] nbd:clear NBD_BOUND flag when NBD connection is closed medadyoung
2018-12-13 14:21 ` Adriana Kobylak
2019-01-18 15:44   ` Adriana Kobylak
2019-01-21  1:43     ` Joel Stanley [this message]
2019-04-03 17:13   ` Adriana Kobylak
2019-04-03 17:49     ` Josef Bacik
2019-04-03 17:49       ` Josef Bacik
2019-04-04 15:31       ` Adriana Kobylak

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='CACPK8Xc-jB-vW60-+xGgf3igWTw=ZLBdjJG0niwbwU66_gA0KA@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=anoo@linux.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=medadyoung@gmail.com \
    --cc=openbmc@lists.ozlabs.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 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.