All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: James Bottomley
	<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>,
	Greg Kroah-Hartman
	<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
	Douglas Gilbert
	<dgilbert-qazKcTl6WRFWk0Htik3J/w@public.gmane.org>,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 2/2] uas: Make uas work with blk-mq
Date: Sun, 05 Oct 2014 11:18:49 +0200	[thread overview]
Message-ID: <54310CF9.8040503@redhat.com> (raw)
In-Reply-To: <20141005091015.GA29855-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

Hi,

On 10/05/2014 11:10 AM, Christoph Hellwig wrote:
> On Sun, Oct 05, 2014 at 11:06:00AM +0200, Hans de Goede wrote:
>> This patch sits on top of a lot of other uas fixes which are already
>> in usb-next, so this needs to go in through usb-next.
> 
> What is the actual conflict? If it's just your revert of the
> disable_blk_mq flag

Yes, the conclict is just my revert of the disable_blk_mq flag

> you might want to skip that for this pull request
> and send it on after both scsi and usb trees make it to Linus.

Since the patch with the conclict actually makes the flag unnecessary,
to me this belongs in the same patch.

> If there's more conflict around the host template you could cherry pick
> my patch for your tree.

Yes, Greg cherry picking the patch in question into his tree to resolv
the conflict would be my preferred solution to this, but ultimately
that is Greg's call.

Regards,

Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-10-05  9:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 10:08 [PATCH v2 1/2] uas: Reduce number of function arguments for uas_alloc_foo functions Hans de Goede
2014-10-03 10:08 ` [PATCH v2 2/2] uas: Make uas work with blk-mq Hans de Goede
     [not found]   ` <1412330937-22630-2-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-10-03 21:47     ` Greg Kroah-Hartman
2014-10-04  8:53       ` Hans de Goede
2014-10-04 14:46         ` James Bottomley
     [not found]           ` <1412433981.21548.6.camel-doHRWNlmrt9+urZeOPWqwQ@public.gmane.org>
2014-10-05  9:06             ` Hans de Goede
     [not found]               ` <543109F8.3030303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-10-05  9:10                 ` Christoph Hellwig
     [not found]                   ` <20141005091015.GA29855-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-10-05  9:18                     ` Hans de Goede [this message]
2014-10-06  0:10                       ` Greg Kroah-Hartman

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=54310CF9.8040503@redhat.com \
    --to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
    --cc=dgilbert-qazKcTl6WRFWk0Htik3J/w@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.