All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tanous <ed@tanous.net>
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	"Czarnowski,
	Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@linux.intel.com>
Subject: Re: Virtual Media repository request
Date: Wed, 15 Dec 2021 11:26:33 -0800	[thread overview]
Message-ID: <CACWQX819tsUA6t190mVp8LrrHbteiP4w-35MEH9LG9mWTvYgxw@mail.gmail.com> (raw)
In-Reply-To: <5c98b6d46d71907242f1d868cc3d918db99cea53.camel@codeconstruct.com.au>

On Mon, Dec 13, 2021 at 6:11 PM Jeremy Kerr <jk@codeconstruct.com.au> wrote:
>
> Hi all,
>
> > Maybe Ed's proposal of using an existing repository solves that.  We
> > would need to make sure the current maintainer is accepting of
> > whatever design direction you've decided to go though.
>
> I'm fine with replacing the jsnbd code with a newer implementation,
> provided there's general community acceptance for doing so. If that's
> the case, I'm happy to use the existing repo, or replacing openbmc/jsnbd
> entirely - whatever suits best.
>
> [Perhaps in your design document, you can expand the Alternatives
> Considered section, to provide some motivation to change over]
>
> However, I'm *not* OK with just introducing a completely alternate VM
> implementation and leaving jsnbd as-is, where some platforms use one,
> and some the other. We have way too many instances where there are two
> separate implementations and/or repos that deliver the same
> functionality. I would like to avoid making that problem worse.

+1

>
> So, either:
>
>  - submit these as updates to jsnbd, which implement the new structure as
>    you like. I'd be happy to hand over the repo to the new maintainers.
>
>  or
>
>  - provide the new VM implementation as a new repo, propose to change
>    platforms to use the new implementation, and we can delete jsnbd.
>
> Cheers,
>
>
> Jeremy

  reply	other threads:[~2021-12-15 19:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 15:50 Virtual Media repository request Hawrylewicz Czarnowski, Przemyslaw
2021-12-08 16:56 ` Patrick Williams
2021-12-09  8:56   ` Czarnowski, Przemyslaw
2021-12-09 10:41     ` i.kononenko
2021-12-13 16:10     ` Patrick Williams
2021-12-13 19:44       ` Czarnowski, Przemyslaw
2021-12-14  2:11       ` Jeremy Kerr
2021-12-15 19:26         ` Ed Tanous [this message]
2021-12-17  9:28           ` Czarnowski, Przemyslaw
2021-12-17  9:45             ` Jeremy Kerr
2021-12-20 12:54               ` Czarnowski, Przemyslaw
2021-12-23  1:01                 ` Czarnowski, Przemyslaw
2022-12-19 14:01                   ` Czarnowski, Przemyslaw
2022-12-19 17:43                     ` Ed Tanous
2023-01-03  5:36                     ` Jeremy Kerr
2021-12-11 21:13 ` Ed Tanous
2021-12-13 19:17   ` Czarnowski, Przemyslaw

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=CACWQX819tsUA6t190mVp8LrrHbteiP4w-35MEH9LG9mWTvYgxw@mail.gmail.com \
    --to=ed@tanous.net \
    --cc=jk@codeconstruct.com.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=przemyslaw.hawrylewicz.czarnowski@linux.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.