linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vaibhav Jain <vaibhav@linux.ibm.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the scsi-fixes tree
Date: Wed, 6 Feb 2019 15:34:55 +1100	[thread overview]
Message-ID: <20190206153406.0febc79c@canb.auug.org.au> (raw)
In-Reply-To: <87tvhhmuzj.fsf@vajain21.in.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]

Hi Vaibhav,

On Wed, 06 Feb 2019 09:25:12 +0530 Vaibhav Jain <vaibhav@linux.ibm.com> wrote:
>
> Martin, should I resend the patch with this fixed ?

I wouldn't bother, it is a really picky report (I almost didn't send
it) :-)

Consider it just a reminder for next time.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-02-06  4:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 20:20 linux-next: Fixes tag needs some work in the scsi-fixes tree Stephen Rothwell
2019-02-06  3:55 ` Vaibhav Jain
2019-02-06  4:34   ` Stephen Rothwell [this message]
2019-02-06 13:03   ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2020-09-03  8:47 Stephen Rothwell
2020-09-04  1:51 ` Martin K. Petersen
2020-06-24  7:07 Stephen Rothwell
2020-06-24  7:14 ` SeongJae Park
2020-06-24  7:23   ` Stephen Rothwell
2020-05-08 11:33 Stephen Rothwell
2020-05-11 23:54 ` Martin K. Petersen
2019-01-29 20:53 Stephen Rothwell
2019-01-23  5:34 Stephen Rothwell

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=20190206153406.0febc79c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=vaibhav@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;
as well as URLs for NNTP newsgroup(s).