All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [Linux-nvdimm] [GIT PULL] PMEM driver for v4.1
Date: Wed, 27 May 2015 09:50:42 +0200	[thread overview]
Message-ID: <20150527075042.GA32160@gmail.com> (raw)
In-Reply-To: <20150525181654.GE2729@linux.intel.com>


* Matthew Wilcox <willy@linux.intel.com> wrote:

> On Mon, Apr 13, 2015 at 11:33:09AM +0200, Ingo Molnar wrote:
> > Please pull the latest x86-pmem-for-linus git tree from:
> > 
> >    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pmem-for-linus
> > 
> >    # HEAD: 4c1eaa2344fb26bb5e936fb4d8ee307343ea0089 drivers/block/pmem: Fix 32-bit build warning in pmem_alloc()
> > 
> > This is the initial support for the pmem block device driver: 
> > persistent non-volatile memory space mapped into the system's physical 
> > memory space as large physical memory regions.
> 
> Ingo, this sucks.  You collapsed all of the separate patches into a single "add 
> new driver" patch, which makes it impossible to bisect which of the recent 
> changes broke xfstests.  Please don't do this again.

You ignored my previous reply, so let me ask this again more forcefully: what the 
hell are you talking about??

As you can see it from the fine commit 9e853f2313e5:

  Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
  Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
  Signed-off-by: Christoph Hellwig <hch@lst.de>
  Acked-by: Dan Williams <dan.j.williams@intel.com>
  ...
  Link: http://lkml.kernel.org/r/1427872339-6688-3-git-send-email-hch@lst.de
  [ Minor cleanups. ]
  Signed-off-by: Ingo Molnar <mingo@kernel.org>

I didn't do any 'collapsing' of patches, I applied the patches as sent by hch:

  9e853f2313e5 ("drivers/block/pmem: Add a driver for persistent memory")
  ec776ef6bbe1 ("x86/mm: Add support for the non-standard protected e820 type")

Thanks,

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-nvdimm@ml01.01.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [Linux-nvdimm] [GIT PULL] PMEM driver for v4.1
Date: Wed, 27 May 2015 09:50:42 +0200	[thread overview]
Message-ID: <20150527075042.GA32160@gmail.com> (raw)
In-Reply-To: <20150525181654.GE2729@linux.intel.com>


* Matthew Wilcox <willy@linux.intel.com> wrote:

> On Mon, Apr 13, 2015 at 11:33:09AM +0200, Ingo Molnar wrote:
> > Please pull the latest x86-pmem-for-linus git tree from:
> > 
> >    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pmem-for-linus
> > 
> >    # HEAD: 4c1eaa2344fb26bb5e936fb4d8ee307343ea0089 drivers/block/pmem: Fix 32-bit build warning in pmem_alloc()
> > 
> > This is the initial support for the pmem block device driver: 
> > persistent non-volatile memory space mapped into the system's physical 
> > memory space as large physical memory regions.
> 
> Ingo, this sucks.  You collapsed all of the separate patches into a single "add 
> new driver" patch, which makes it impossible to bisect which of the recent 
> changes broke xfstests.  Please don't do this again.

You ignored my previous reply, so let me ask this again more forcefully: what the 
hell are you talking about??

As you can see it from the fine commit 9e853f2313e5:

  Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
  Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
  Signed-off-by: Christoph Hellwig <hch@lst.de>
  Acked-by: Dan Williams <dan.j.williams@intel.com>
  ...
  Link: http://lkml.kernel.org/r/1427872339-6688-3-git-send-email-hch@lst.de
  [ Minor cleanups. ]
  Signed-off-by: Ingo Molnar <mingo@kernel.org>

I didn't do any 'collapsing' of patches, I applied the patches as sent by hch:

  9e853f2313e5 ("drivers/block/pmem: Add a driver for persistent memory")
  ec776ef6bbe1 ("x86/mm: Add support for the non-standard protected e820 type")

Thanks,

	Ingo

  parent reply	other threads:[~2015-05-27  7:50 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  9:33 [GIT PULL] PMEM driver for v4.1 Ingo Molnar
2015-04-13  9:33 ` Ingo Molnar
2015-04-13  9:35 ` Christoph Hellwig
2015-04-13  9:35   ` Christoph Hellwig
2015-04-13 10:45   ` Ingo Molnar
2015-04-13 10:45     ` Ingo Molnar
2015-04-13 11:11     ` [Linux-nvdimm] " Yigal Korman
2015-04-13 11:11       ` Yigal Korman
2015-04-13 17:19       ` Christoph Hellwig
2015-04-13 17:19         ` Christoph Hellwig
2015-04-14  6:41         ` Boaz Harrosh
2015-04-14  6:41           ` Boaz Harrosh
2015-04-13 12:21     ` Boaz Harrosh
2015-04-13 12:21       ` Boaz Harrosh
2015-04-13 12:35       ` Ingo Molnar
2015-04-13 12:35         ` Ingo Molnar
2015-04-13 13:36         ` Boaz Harrosh
2015-04-13 13:36           ` Boaz Harrosh
2015-04-13 17:22         ` Christoph Hellwig
2015-04-13 17:22           ` Christoph Hellwig
2015-04-13 17:18     ` Christoph Hellwig
2015-04-13 17:18       ` Christoph Hellwig
2015-04-14 12:41       ` Ingo Molnar
2015-04-14 12:41         ` Ingo Molnar
2015-04-14 13:45         ` Boaz Harrosh
2015-04-14 13:45           ` Boaz Harrosh
2015-04-14 14:08         ` [Linux-nvdimm] " Elliott, Robert (Server Storage)
2015-04-14 14:08           ` Elliott, Robert (Server Storage)
2015-04-14 16:34           ` Dan Williams
2015-04-14 16:34             ` Dan Williams
2015-04-14 21:46             ` Elliott, Robert (Server Storage)
2015-04-14 21:46               ` Elliott, Robert (Server Storage)
2015-04-15  8:03           ` Ingo Molnar
2015-04-15  8:03             ` Ingo Molnar
2015-04-14 16:04         ` Dan Williams
2015-04-14 16:04           ` Dan Williams
2015-04-15  8:45           ` Ingo Molnar
2015-04-15  8:45             ` Ingo Molnar
2015-04-16  4:31             ` Dan Williams
2015-04-16  4:31               ` Dan Williams
2015-04-17  6:38 ` Christoph Hellwig
2015-04-17  6:38   ` Christoph Hellwig
2015-04-18 15:42   ` Linus Torvalds
2015-04-18 15:42     ` Linus Torvalds
2015-05-25 18:16 ` [Linux-nvdimm] " Matthew Wilcox
2015-05-25 18:16   ` Matthew Wilcox
2015-05-25 18:30   ` Ingo Molnar
2015-05-25 18:30     ` Ingo Molnar
2015-05-26  8:41   ` Boaz Harrosh
2015-05-26  8:41     ` Boaz Harrosh
2015-05-26 19:31     ` Matthew Wilcox
2015-05-26 19:31       ` Matthew Wilcox
2015-05-27  8:10       ` Boaz Harrosh
2015-05-27  8:10         ` Boaz Harrosh
2015-05-27  8:11         ` Christoph Hellwig
2015-05-27  8:11           ` Christoph Hellwig
2015-05-27  8:26           ` Boaz Harrosh
2015-05-27  8:26             ` Boaz Harrosh
2015-05-27  7:50   ` Ingo Molnar [this message]
2015-05-27  7:50     ` Ingo Molnar

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=20150527075042.GA32160@gmail.com \
    --to=mingo@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@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.