public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@linux.vnet.ibm.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Damien Le Moal <dlemoal@kernel.org>
Cc: jejb@linux.ibm.com, linux-scsi@vger.kernel.org,
	damien.lemoal@opensource.wdc.com, john.g.garry@oracle.com,
	wenxiong@linux.ibm.com
Subject: Re: [PATCH] ipr: Remove SATA support
Date: Wed, 19 Apr 2023 13:58:20 -0500	[thread overview]
Message-ID: <f667d600-4eee-126e-c14f-60cd64109fae@linux.vnet.ibm.com> (raw)
In-Reply-To: <yq1cz40ot8n.fsf@ca-mkp.ca.oracle.com>

On 4/19/23 9:17 AM, Martin K. Petersen wrote:
> 
> Damien,
> 
>> There was a build bot warning. Was that fixed ? I did not see a v2...
> 
> I couldn't correlate those build bot warnings to the code changes.  I
> put the patch in staging to see what will get reported there.
> 

I was working on a v2 with fixes for the build bot complaints.
One was a complaint about an used variable that is only unused when
a compile option is turned off, but the reset were valid unused variables
that can be cleaned up. 

Since you've pulled this in, should I just send a new patch on top
for just these minor build bot fixes?

Thanks,

Brian

-- 
Brian King
Power Linux I/O
IBM Linux Technology Center



  reply	other threads:[~2023-04-19 18:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 17:40 [PATCH] ipr: Remove SATA support Brian King
2023-04-12 22:26 ` Damien Le Moal
2023-04-12 23:56 ` kernel test robot
2023-04-13  2:11 ` kernel test robot
2023-04-13  7:35 ` John Garry
2023-04-13  7:49   ` Damien Le Moal
2023-04-19  3:10 ` Martin K. Petersen
2023-04-19 13:16   ` Damien Le Moal
2023-04-19 14:17     ` Martin K. Petersen
2023-04-19 18:58       ` Brian King [this message]
2023-04-19 19:13         ` Martin K. Petersen
     [not found] <CABa-fKRfE8B2TLVJASB9xQaOXDiYH3YCw0YEEg1UcGu2Le8xWw@mail.gmail.com>
2024-02-29 22:04 ` Damien Le Moal

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=f667d600-4eee-126e-c14f-60cd64109fae@linux.vnet.ibm.com \
    --to=brking@linux.vnet.ibm.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dlemoal@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=john.g.garry@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=wenxiong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox