All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Vaibhav Jain <vaibhav@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, linux-nvdimm@lists.01.org,
	linux-kernel@vger.kernel.org,
	"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Piotr Maziarz <piotrx.maziarz@linux.intel.com>,
	Cezary Rojewski <cezary.rojewski@intel.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v13 2/6] seq_buf: Export seq_buf_printf
Date: Mon, 15 Jun 2020 17:24:29 -0400	[thread overview]
Message-ID: <20200615172429.6e66ed0f@oasis.local.home> (raw)
In-Reply-To: <20200615125552.GI14668@zn.tnic>

On Mon, 15 Jun 2020 14:55:52 +0200
Borislav Petkov <bp@alien8.de> wrote:

> Can you please resend your patchset once a week like everyone else and
> not flood inboxes with it?

Boris,

Haven't you automated your inbox yet? I have patchwork reading my INBOX
and it's smart enough to understand new series, and the old one simply
disappears as "superseded".

Email is just the wires to our infrastructure. Get with the times man! ;-)

-- Steve
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Vaibhav Jain <vaibhav@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, linux-nvdimm@lists.01.org,
	linux-kernel@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Oliver O'Halloran <oohall@gmail.com>,
	Santosh Sivaraj <santosh@fossix.org>,
	Ira Weiny <ira.weiny@intel.com>,
	Piotr Maziarz <piotrx.maziarz@linux.intel.com>,
	Cezary Rojewski <cezary.rojewski@intel.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v13 2/6] seq_buf: Export seq_buf_printf
Date: Mon, 15 Jun 2020 17:24:29 -0400	[thread overview]
Message-ID: <20200615172429.6e66ed0f@oasis.local.home> (raw)
In-Reply-To: <20200615125552.GI14668@zn.tnic>

On Mon, 15 Jun 2020 14:55:52 +0200
Borislav Petkov <bp@alien8.de> wrote:

> Can you please resend your patchset once a week like everyone else and
> not flood inboxes with it?

Boris,

Haven't you automated your inbox yet? I have patchwork reading my INBOX
and it's smart enough to understand new series, and the old one simply
disappears as "superseded".

Email is just the wires to our infrastructure. Get with the times man! ;-)

-- Steve

WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Santosh Sivaraj <santosh@fossix.org>,
	Ira Weiny <ira.weiny@intel.com>,
	linux-nvdimm@lists.01.org,
	"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
	Cezary Rojewski <cezary.rojewski@intel.com>,
	linux-kernel@vger.kernel.org,
	Piotr Maziarz <piotrx.maziarz@linux.intel.com>,
	Christoph Hellwig <hch@infradead.org>,
	Oliver O'Halloran <oohall@gmail.com>,
	Vaibhav Jain <vaibhav@linux.ibm.com>,
	Dan Williams <dan.j.williams@intel.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v13 2/6] seq_buf: Export seq_buf_printf
Date: Mon, 15 Jun 2020 17:24:29 -0400	[thread overview]
Message-ID: <20200615172429.6e66ed0f@oasis.local.home> (raw)
In-Reply-To: <20200615125552.GI14668@zn.tnic>

On Mon, 15 Jun 2020 14:55:52 +0200
Borislav Petkov <bp@alien8.de> wrote:

> Can you please resend your patchset once a week like everyone else and
> not flood inboxes with it?

Boris,

Haven't you automated your inbox yet? I have patchwork reading my INBOX
and it's smart enough to understand new series, and the old one simply
disappears as "superseded".

Email is just the wires to our infrastructure. Get with the times man! ;-)

-- Steve

  parent reply	other threads:[~2020-06-15 21:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 12:44 [PATCH v13 0/6] powerpc/papr_scm: Add support for reporting nvdimm health Vaibhav Jain
2020-06-15 12:44 ` Vaibhav Jain
2020-06-15 12:44 ` Vaibhav Jain
2020-06-15 12:44 ` [PATCH v13 1/6] powerpc: Document details on H_SCM_HEALTH hcall Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:44 ` [PATCH v13 2/6] seq_buf: Export seq_buf_printf Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:55   ` Borislav Petkov
2020-06-15 12:55     ` Borislav Petkov
2020-06-15 12:55     ` Borislav Petkov
2020-06-15 19:40     ` Dan Williams
2020-06-15 19:40       ` Dan Williams
2020-06-15 19:40       ` Dan Williams
2020-06-15 21:24     ` Steven Rostedt [this message]
2020-06-15 21:24       ` Steven Rostedt
2020-06-15 21:24       ` Steven Rostedt
2020-06-15 12:44 ` [PATCH v13 3/6] powerpc/papr_scm: Fetch nvdimm health information from PHYP Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-16  2:23   ` Ira Weiny
2020-06-16  2:23     ` Ira Weiny
2020-06-16  2:23     ` Ira Weiny
2020-06-15 12:44 ` [PATCH v13 4/6] powerpc/papr_scm: Improve error logging and handling papr_scm_ndctl() Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:44 ` [PATCH v13 5/6] ndctl/papr_scm,uapi: Add support for PAPR nvdimm specific methods Vaibhav Jain
2020-06-15 12:44   ` [PATCH v13 5/6] ndctl/papr_scm, uapi: " Vaibhav Jain
2020-06-15 12:44   ` [PATCH v13 5/6] ndctl/papr_scm,uapi: " Vaibhav Jain
2020-06-15 12:44 ` [PATCH v13 6/6] powerpc/papr_scm: Implement support for PAPR_PDSM_HEALTH Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain
2020-06-15 12:44   ` Vaibhav Jain

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=20200615172429.6e66ed0f@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=cezary.rojewski@intel.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=piotrx.maziarz@linux.intel.com \
    --cc=vaibhav@linux.ibm.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.