public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Saeed Mahameed <saeed@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Leon Romanovsky <leonro@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	Leonid Bloch <lbloch@nvidia.com>,
	Itay Avraham <itayavr@nvidia.com>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/5] misc: mlx5ctl: Add mlx5ctl misc driver
Date: Mon, 20 Nov 2023 23:25:31 -0800	[thread overview]
Message-ID: <ZVxba6KqmPKLuZGO@x130> (raw)
In-Reply-To: <2023111956-strangle-pantyhose-0814@gregkh>

On 19 Nov 10:51, Greg Kroah-Hartman wrote:
>On Sun, Nov 19, 2023 at 01:24:47AM -0800, Saeed Mahameed wrote:
>> igned-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
>Something went wrong here :(

:(, Just sent V3 now, I needed to fix two new kernel robot warnings
anyways.


  reply	other threads:[~2023-11-21  7:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19  9:24 [PATCH V2 0/5] mlx5 ConnectX diagnostic misc driver Saeed Mahameed
2023-11-19  9:24 ` [PATCH V2 1/5] mlx5: Add aux dev for ctl interface Saeed Mahameed
2023-11-19  9:24 ` [PATCH V2 2/5] misc: mlx5ctl: Add mlx5ctl misc driver Saeed Mahameed
2023-11-19  9:51   ` Greg Kroah-Hartman
2023-11-21  7:25     ` Saeed Mahameed [this message]
2023-11-19  9:24 ` [PATCH V2 3/5] misc: mlx5ctl: Add info ioctl Saeed Mahameed
2023-11-19  9:24 ` [PATCH V2 4/5] misc: mlx5ctl: Add command rpc ioctl Saeed Mahameed
2023-11-19  9:24 ` [PATCH V2 5/5] misc: mlx5ctl: Add umem reg/unreg ioctl Saeed Mahameed
2023-11-19 19:29   ` [PATCH v2 " kernel test robot
2023-11-19 20:06   ` kernel test robot
2023-11-19 21:34   ` kernel test robot

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=ZVxba6KqmPKLuZGO@x130 \
    --to=saeedm@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=itayavr@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=lbloch@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saeed@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox