From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Robin Holt <robinmholt@gmail.com>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
kernel-janitors@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] SGI-XPC: Adjustments for some function implementations
Date: Thu, 11 Jan 2018 20:21:49 +0000 [thread overview]
Message-ID: <20180111202149.GA31382@kroah.com> (raw)
In-Reply-To: <CAPp3RGoGnPegWSEQUd-m=-Mf3wtAYL6YNwFR7Cpw_s_8AwOEEA@mail.gmail.com>
On Thu, Jan 11, 2018 at 12:19:37PM -0600, Robin Holt wrote:
> If you need to resubmit, please consider re-ordering the changes to
> due the comparison to NULL changes in your first patch, followed by the
> other two in either order. I think it will clear up some of the inconsistency
> in your first patch.
Note you are responding to someone who is on my, and many other kernel
maintainers, blacklists, so I never see the patches. So it's not really
worth reviewing, as I'll not be picking them up myself, sorry.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Robin Holt <robinmholt@gmail.com>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
kernel-janitors@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] SGI-XPC: Adjustments for some function implementations
Date: Thu, 11 Jan 2018 21:21:49 +0100 [thread overview]
Message-ID: <20180111202149.GA31382@kroah.com> (raw)
In-Reply-To: <CAPp3RGoGnPegWSEQUd-m=-Mf3wtAYL6YNwFR7Cpw_s_8AwOEEA@mail.gmail.com>
On Thu, Jan 11, 2018 at 12:19:37PM -0600, Robin Holt wrote:
> If you need to resubmit, please consider re-ordering the changes to
> due the comparison to NULL changes in your first patch, followed by the
> other two in either order. I think it will clear up some of the inconsistency
> in your first patch.
Note you are responding to someone who is on my, and many other kernel
maintainers, blacklists, so I never see the patches. So it's not really
worth reviewing, as I'll not be picking them up myself, sorry.
greg k-h
next prev parent reply other threads:[~2018-01-11 20:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 14:03 [PATCH 0/3] SGI-XPC: Adjustments for some function implementations SF Markus Elfring
2018-01-10 14:03 ` SF Markus Elfring
2018-01-10 14:04 ` [PATCH 1/3] sgi-xpc: Delete error messages for a failed memory allocation in three functions SF Markus Elfring
2018-01-10 14:04 ` SF Markus Elfring
2018-01-11 18:16 ` Robin Holt
2018-01-11 18:16 ` Robin Holt
2018-01-10 14:05 ` [PATCH 2/3] sgi-xpc: Improve a size determination in two functions SF Markus Elfring
2018-01-10 14:05 ` SF Markus Elfring
2018-01-11 18:16 ` Robin Holt
2018-01-11 18:16 ` Robin Holt
2018-01-10 14:06 ` [PATCH 3/3] sgi-xpc: Adjust 27 checks for null pointers SF Markus Elfring
2018-01-10 14:06 ` SF Markus Elfring
2018-01-11 18:17 ` Robin Holt
2018-01-11 18:17 ` Robin Holt
2018-01-11 18:19 ` [PATCH 0/3] SGI-XPC: Adjustments for some function implementations Robin Holt
2018-01-11 18:19 ` Robin Holt
2018-01-11 20:21 ` Greg Kroah-Hartman [this message]
2018-01-11 20:21 ` Greg Kroah-Hartman
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=20180111202149.GA31382@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robinmholt@gmail.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.