From: James Bottomley <jbottomley@parallels.com>
To: "merez@codeaurora.org" <merez@codeaurora.org>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
'Vinayak Holikatti' <vinholikatti@gmail.com>,
'Santosh Y' <santoshsy@gmail.com>
Subject: Re: [PATCH v2 3/7] scsi: ufs: amend interrupt configuration
Date: Mon, 6 May 2013 14:22:30 +0000 [thread overview]
Message-ID: <1367850149.1868.1.camel@dabdike> (raw)
In-Reply-To: <a4a34657e8957d3ee2d6dc2f6212b4cd.squirrel@www.codeaurora.org>
On Mon, 2013-05-06 at 03:40 -0700, merez@codeaurora.org wrote:
> Hi James,
>
> Can you please merge this patch?
Well, no. a) because it's part of a series which still seems to be
under development and b) because it needs a maintainer ack.
James
prev parent reply other threads:[~2013-05-06 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 16:06 [PATCH 3/5] scsi: ufs: amend interrupt configuration Seungwon Jeon
2013-04-30 11:50 ` Subhash Jadavani
2013-05-01 7:50 ` merez
2013-05-02 7:00 ` Seungwon Jeon
2013-05-04 8:45 ` [PATCH v2 3/7] " Seungwon Jeon
2013-05-06 10:40 ` merez
2013-05-06 14:22 ` James Bottomley [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=1367850149.1868.1.camel@dabdike \
--to=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=merez@codeaurora.org \
--cc=santoshsy@gmail.com \
--cc=tgih.jun@samsung.com \
--cc=vinholikatti@gmail.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