All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christoph Volkert <linux@christoph-volkert.de>
Cc: Fabian Huegel <fabian_huegel@web.de>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	James Simmons <jsimmons@infradead.org>,
	Lai Siyao <lai.siyao@intel.com>,
	"John L . Hammond" <john.hammond@intel.com>,
	devel@driverdev.osuosl.org, lustre-devel@lists.lustre.org,
	linux-kernel@vger.kernel.org, linux-kernel@i4.cs.fau.de
Subject: [lustre-devel] [PATCH 1/8] staging: lustre: Enclose complex macros in parantheses
Date: Mon, 8 Jan 2018 15:52:28 +0100	[thread overview]
Message-ID: <20180108145228.GA32682@kroah.com> (raw)
In-Reply-To: <4195720f60859773624344ef220517d9@christoph-volkert.de>

On Thu, Dec 21, 2017 at 04:43:27PM +0100, Christoph Volkert wrote:
> This is a duplicate patch. We fixed a typo and this was still left as a
> temporary file. (emacs?) Sorry. The patch with Message-Id
> <1513869932-27407-3-git-send-email-fabian_huegel@web.de> is the right one.
> 
> We can provide a new patch series without the fix, if needed.

Please do, as I have no idea what to do otherwise.

Consider this patch series dropped.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christoph Volkert <linux@christoph-volkert.de>
Cc: Fabian Huegel <fabian_huegel@web.de>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	James Simmons <jsimmons@infradead.org>,
	Lai Siyao <lai.siyao@intel.com>,
	"John L . Hammond" <john.hammond@intel.com>,
	devel@driverdev.osuosl.org, lustre-devel@lists.lustre.org,
	linux-kernel@vger.kernel.org, linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH 1/8] staging: lustre: Enclose complex macros in parantheses
Date: Mon, 8 Jan 2018 15:52:28 +0100	[thread overview]
Message-ID: <20180108145228.GA32682@kroah.com> (raw)
In-Reply-To: <4195720f60859773624344ef220517d9@christoph-volkert.de>

On Thu, Dec 21, 2017 at 04:43:27PM +0100, Christoph Volkert wrote:
> This is a duplicate patch. We fixed a typo and this was still left as a
> temporary file. (emacs…) Sorry. The patch with Message-Id
> <1513869932-27407-3-git-send-email-fabian_huegel@web.de> is the right one.
> 
> We can provide a new patch series without the fix, if needed.

Please do, as I have no idea what to do otherwise.

Consider this patch series dropped.

thanks,

greg k-h

  reply	other threads:[~2018-01-08 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 15:25 staging: lustre: Cleanup of obd_class.h Fabian Huegel
2017-12-21 15:25 ` [PATCH 1/8] staging: lustre: Enclose complex macros in parantheses Fabian Huegel
2017-12-21 15:43   ` Christoph Volkert
2018-01-08 14:52     ` Greg Kroah-Hartman [this message]
2018-01-08 14:52       ` Greg Kroah-Hartman
2017-12-21 15:25 ` [PATCH 1/8] staging: lustre: Enclose complex macros in parentheses Fabian Huegel
2017-12-21 15:25 ` [PATCH 2/8] staging: lustre: Enclose complex macros in do-while loops Fabian Huegel
2017-12-21 15:25 ` [PATCH 3/8] staging: lustre: Remove DECLARE_LU_VARS macro Fabian Huegel
2017-12-21 15:25 ` [PATCH 4/8] staging: lustre: Fix comment style Fabian Huegel
2017-12-21 15:25 ` [PATCH 5/8] staging: lustre: Add identifier names to function declarations Fabian Huegel
2017-12-21 15:25 ` [PATCH 6/8] staging: lustre: Fix overlong lines Fabian Huegel
2017-12-21 15:25 ` [PATCH 7/8] staging: lustre: Align struct member identifiers Fabian Huegel
2017-12-21 15:25 ` [PATCH 8/8] staging: lustre: Align backslashes in multi-line macros Fabian Huegel

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=20180108145228.GA32682@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fabian_huegel@web.de \
    --cc=john.hammond@intel.com \
    --cc=jsimmons@infradead.org \
    --cc=lai.siyao@intel.com \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@christoph-volkert.de \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@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.