All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Dan Ehrenberg <dehrenberg@chromium.org>
Cc: viro@zeniv.linux.org.uk, agk@redhat.com, grundler@chromium.org,
	gwendal@chromium.org, dm-devel@redhat.com,
	linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Re: [PATCH v2 1/3] init: Export name_to_dev_t and mark it const
Date: Wed, 18 Mar 2015 17:28:43 -0400	[thread overview]
Message-ID: <20150318212842.GA17483@redhat.com> (raw)
In-Reply-To: <1423610451-22600-1-git-send-email-dehrenberg@chromium.org>

On Tue, Feb 10 2015 at  6:20pm -0500,
Dan Ehrenberg <dehrenberg@chromium.org> wrote:

> name_to_dev_t is useful in other pieces of code to initialize rootfs.
> In the case of dm, the code is sometimes built in a module and other
> times used to construct the rootfs; therefore it must be exported
> as a symbol.
> 
> Signed-off-by: Dan Ehrenberg <dehrenberg@chromium.org>

I'm going to pick these changes up and stage them in linux-dm.git's
'for-next' for Linux 4.1.

Al and/or others, if you have any objections to the simple
name_to_dev_t() changes in the first 2 patches of this set please
shout.

Thanks,
Mike

  parent reply	other threads:[~2015-03-18 21:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 23:20 [PATCH v2 1/3] init: Export name_to_dev_t and mark it const Dan Ehrenberg
2015-02-10 23:20 ` [PATCH v2 2/3] init: Stricter checking of major:minor root= values Dan Ehrenberg
2015-02-10 23:20 ` [PATCH v2 3/3] dm: Get devices using name_to_dev_t Dan Ehrenberg
2015-03-18 21:28 ` Mike Snitzer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-10 23:20 [PATCH v2 1/3] init: Export name_to_dev_t and mark it const Dan Ehrenberg

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=20150318212842.GA17483@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dehrenberg@chromium.org \
    --cc=dm-devel@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=grundler@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.