All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Milan P. Gandhi" <mgandhi@redhat.com>
Cc: kernel-janitors@vger.kernel.org, qla2xxx-upstream@qlogic.com,
	jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	julia.lawall@lip6.fr
Subject: Re: [PATCH 0/2] scsi: qla2xxx: Fix for a formatting issue and typo in qla_bsg.c
Date: Tue, 12 Mar 2019 16:17:16 +0300	[thread overview]
Message-ID: <20190312131716.GJ2412@kadam> (raw)
In-Reply-To: <20190312124937.GA13922@machine1>

Looks good.  It might take a while for the maintainers to get around to
this because the merge window is open and it's a low priority cleanup.

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Milan P. Gandhi" <mgandhi@redhat.com>
Cc: kernel-janitors@vger.kernel.org, qla2xxx-upstream@qlogic.com,
	jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	julia.lawall@lip6.fr
Subject: Re: [PATCH 0/2] scsi: qla2xxx: Fix for a formatting issue and typo in qla_bsg.c
Date: Tue, 12 Mar 2019 13:17:16 +0000	[thread overview]
Message-ID: <20190312131716.GJ2412@kadam> (raw)
In-Reply-To: <20190312124937.GA13922@machine1>

Looks good.  It might take a while for the maintainers to get around to
this because the merge window is open and it's a low priority cleanup.

regards,
dan carpenter

  reply	other threads:[~2019-03-12 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 12:49 [PATCH 0/2] scsi: qla2xxx: Fix for a formatting issue and typo in qla_bsg.c Milan P. Gandhi
2019-03-12 12:49 ` Milan P. Gandhi
2019-03-12 13:17 ` Dan Carpenter [this message]
2019-03-12 13:17   ` Dan Carpenter
2019-03-19 21:34 ` Martin K. Petersen
2019-03-19 21:34   ` Martin K. Petersen

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=20190312131716.GJ2412@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=jejb@linux.ibm.com \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mgandhi@redhat.com \
    --cc=qla2xxx-upstream@qlogic.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.