All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Jackson <iggy@theiggy.com>
To: Thomas Mueller <thomas@chaschperli.ch>
Cc: ceph-devel@vger.kernel.org
Subject: Re: PATCH: link ceph-client version to kernel version
Date: Wed, 7 Jul 2010 13:04:18 -0500	[thread overview]
Message-ID: <201007071304.18434.iggy@theiggy.com> (raw)
In-Reply-To: <201007071234.35911.iggy@theiggy.com>

On Wednesday, July 07, 2010 12:34:35 pm Brian Jackson wrote:
> On Wednesday, July 07, 2010 03:54:00 am Thomas Mueller wrote:
> > hi
> > 
> > reading the version in ceph_fs.h made me think, that now that ceph is in
> > vanilla kernel, it would be nice to have the version linked to the kernel
> > version. this is how the kvm guys work for their backported module.
> 
> That makes sense for KVM because it's reached a level of maturity where
> they only bother doing the backports of specific kernel releases. I don't
> think it's a good idea for ceph to go this direction yet. Mostly I'd hate
> to see the standalone client packages only released when there's a new
> kernel. It seems like something that would be more useful once ceph has
> some kernel releases under it's belt.


Cancel that. Talked to sagewk on irc and he said development of the kclient is 
taking place in upstream git now, so I guess this does make sense.



> 
> > I've also patched super.c to expose the version to modinfo.
> > 
> > - Thomas
> 
> <snip>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-07-07 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  8:54 PATCH: link ceph-client version to kernel version Thomas Mueller
2010-07-07 15:03 ` Sage Weil
2010-07-07 15:11   ` Thomas Mueller
2010-07-07 17:34 ` Brian Jackson
2010-07-07 18:04   ` Brian Jackson [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=201007071304.18434.iggy@theiggy.com \
    --to=iggy@theiggy.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=thomas@chaschperli.ch \
    /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.