All of lore.kernel.org
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Jon Mason <jdmason@kudzu.us>
Cc: Xiangliang Yu <Xiangliang.Yu@amd.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Allen Hubbe <Allen.Hubbe@emc.com>, Joe Perches <joe@perches.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-ntb@googlegroups.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Style fixes: open code obfuscating macros
Date: Wed, 1 Feb 2017 15:11:44 -0700	[thread overview]
Message-ID: <e5dbac43-6ca0-1adf-251c-b288e9fae814@deltatee.com> (raw)
In-Reply-To: <CAPoiz9zyATQRw=5ydnSteAqrZkvQ3D24xwt7kR-1aASysquJkQ@mail.gmail.com>

Cool, Thanks.

Let me know if you need anything from me.

Logan

On 01/02/17 01:08 PM, Jon Mason wrote:
> On Thu, Jan 26, 2017 at 3:00 PM, Logan Gunthorpe <logang@deltatee.com> wrote:
>> Hi,
>>
>> It's been a couple weeks... Any thoughts on this?
> 
> My apologies for not responding sooner.  A large rework of the core
> NTB code was done prior to your patches (for IDT NTB support).
> Unfortunately, after those changes this series does not apply cleanly.
> I understand the changes being made, and will fix-up the patches to
> make it apply cleanly on the updated code base.
> 
> Thanks,
> Jon
> 
>>
>> Thanks,
>>
>> Logan
>>
>> On 10/01/17 05:33 PM, Logan Gunthorpe wrote:
>>> Hi,
>>>
>>> Here's an updated version of the style fixes patchset. The differences
>>> from v1 are:
>>>
>>> 1) Rebased onto Jon Mason's current NTB branch
>>>
>>> 2) Added two more patches to convert the print lines to use the ntb
>>> device and not the pci one. This seems more sane, shortens a bunch
>>> of lines and removes the need for temporaries.
>>>
>>> Note with (2): I've tried my best to ensure that statements that print
>>> before the ntb device is registered still use the PCI device. However,
>>> someone should probably review and test this as I don't have access
>>> to all types of hardware to do that.
>>>
>>> Thanks,
>>>
>>> Logan
>>>
>>>
>>>
>>> Logan Gunthorpe (4):
>>>   ntb_hw_amd: Style fixes: open code macros that just obfuscate code
>>>   ntb_hw_intel: Style fixes: open code macros that just obfuscate code
>>>   ntb_hw_amd: Print kernel messages with the ntb device not the pci one
>>>   ntb_hw_intel: Print kernel messages with the ntb device not the pci
>>>     one
>>>
>>>  drivers/ntb/hw/amd/ntb_hw_amd.c     |  60 +++++------
>>>  drivers/ntb/hw/amd/ntb_hw_amd.h     |   3 -
>>>  drivers/ntb/hw/intel/ntb_hw_intel.c | 192 +++++++++++++++++-------------------
>>>  drivers/ntb/hw/intel/ntb_hw_intel.h |   3 -
>>>  4 files changed, 124 insertions(+), 134 deletions(-)
>>>
>>> --
>>> 2.1.4
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups "linux-ntb" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to linux-ntb+unsubscribe@googlegroups.com.
>> To post to this group, send email to linux-ntb@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/linux-ntb/5ed3be6c-c94e-1ade-e4cd-a8e8293296cd%40deltatee.com.
>> For more options, visit https://groups.google.com/d/optout.

      reply	other threads:[~2017-02-01 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  0:33 [PATCH v2 0/4] Style fixes: open code obfuscating macros Logan Gunthorpe
2017-01-11  0:33 ` [PATCH v2 1/4] ntb_hw_amd: Style fixes: open code macros that just obfuscate code Logan Gunthorpe
2017-03-08 16:41   ` Jon Mason
2017-01-11  0:33 ` [PATCH v2 2/4] ntb_hw_intel: " Logan Gunthorpe
2017-03-08 16:41   ` Jon Mason
2017-01-11  0:33 ` [PATCH v2 3/4] ntb_hw_amd: Print kernel messages with the ntb device not the pci one Logan Gunthorpe
2017-03-08 16:43   ` Jon Mason
2017-01-11  0:33 ` [PATCH v2 4/4] ntb_hw_intel: " Logan Gunthorpe
2017-01-26 20:00 ` [PATCH v2 0/4] Style fixes: open code obfuscating macros Logan Gunthorpe
2017-02-01 20:08   ` Jon Mason
2017-02-01 22:11     ` Logan Gunthorpe [this message]

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=e5dbac43-6ca0-1adf-251c-b288e9fae814@deltatee.com \
    --to=logang@deltatee.com \
    --cc=Allen.Hubbe@emc.com \
    --cc=Xiangliang.Yu@amd.com \
    --cc=dave.jiang@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdmason@kudzu.us \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntb@googlegroups.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.