mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Philipp Reisner" <philipp.reisner@linbit.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Lars Ellenberg" <lars.ellenberg@linbit.com>
Subject: Re: Unexport of blk_get_queue and blk_put_queue
Date: Wed, 23 Apr 2008 08:12:41 +0200	[thread overview]
Message-ID: <e2e108260804222312u673df0bbic3e30089f1d4a238@mail.gmail.com> (raw)
In-Reply-To: <20080421122413.GD6011@cs181133002.pp.htv.fi>

On Mon, Apr 21, 2008 at 2:24 PM, Adrian Bunk <bunk@kernel.org> wrote:
> On Fri, Apr 18, 2008 at 01:43:17PM +0200, Bart Van Assche wrote:
>  > I noticed that blk_get_queue and blk_put_queue were unexported in the
>  > 2.6.25 kernel. Are you aware that this breaks DRBD (an out-of-tree
>  > kernel module) ?
>
>  no, I verify that my patches don't break Linus' tree and often also peek
>  at -mm, but not at external modules.
>
>  And I'm a proponent of "no stable kernel API, but as many external
>  modules as reasonably possible should be part of the kernel", so emails
>  like yours are always a good point to start asking why the code isn't in
>  Linus' tree.
>
>  What happened to DRBD?
>  It didn't seem that far from getting merged half a year ago.

You mean this message: http://lkml.org/lkml/2007/7/21/255 ?
(Added Lars Ellenberg in CC.)

Bart.

  reply	other threads:[~2008-04-23  6:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 11:43 Bart Van Assche
2008-04-21 12:24 ` Adrian Bunk
2008-04-23  6:12   ` Bart Van Assche [this message]
2008-04-23  8:06     ` Philipp Reisner

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=e2e108260804222312u673df0bbic3e30089f1d4a238@mail.gmail.com \
    --to=bart.vanassche@gmail.com \
    --cc=bunk@kernel.org \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.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®