From: Jens Axboe <axboe@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
Ronny Hegewald <Ronny.Hegewald@online.de>,
Dan Williams <dan.j.williams@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Block driver changes for 3.20
Date: Thu, 12 Feb 2015 15:50:47 -0700 [thread overview]
Message-ID: <54DD2E47.7060601@fb.com> (raw)
In-Reply-To: <CA+55aFyiSmpJWPqUq8cO+fukmZTyO6U5V_hXi9iFQ+Quvj6ryw@mail.gmail.com>
On 02/12/2015 03:37 PM, Linus Torvalds wrote:
> On Thu, Feb 12, 2015 at 12:57 PM, Jens Axboe <axboe@fb.com> wrote:
>>
>> - Switching libata to use the new blk-mq tagging policy, removing code
>> (and a suboptimal implementation) from libata. This will throw you a
>> merge conflict, since a bug in the original libata tagging code was
>> fixed since this code was branched. Trivial. From Shaohua.
>
> Somebody should still check my resolution, since the code had been
> moved to another file. Tejun / Dan, it's your commit 72dd299d5039
> ("libata: allow sata_sil24 to opt-out of tag ordered submission") that
> added a ATA_FLAG_LOWTAG, which conflicts with commit 98bd4be1ba95
> ("libata: move sas ata tag allocation to libata-scsi.c") that moved
> the code.
>
> I verified that it all looks sane, and still compiles, but somebody
> should verify that the tag allocation changes still *work*,
> particularly for that sata_sil24 case.
>
> (I haven't pushed out quite yet, I'm waiting for the rest to compile
> cleanly too, and then I'll do a local compile and boot to see that it
> all works for me, but I'm writing this as a heads-up)
When the code was moved, it also morphed into the sas specific tag
allocation. And the LOWTAG part was for sil24, which doesn't call that
code anymore. So either resolution is fine:
1) Drop the LOWTAG part of ata_sas_allocate_tag(), which is the easy
resolve. Or,
2) Add the two LOWTAG lines in ata_sas_allocate_tag().
So don't worry too much about it, if it compiles, it's good...
--
Jens Axboe
next prev parent reply other threads:[~2015-02-12 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 20:57 [GIT PULL] Block driver changes for 3.20 Jens Axboe
2015-02-12 22:37 ` Linus Torvalds
2015-02-12 22:50 ` Jens Axboe [this message]
2015-02-12 22:55 ` Linus Torvalds
2015-02-12 22:58 ` Jens Axboe
2015-02-12 23:01 ` Linus Torvalds
2015-02-12 23:02 ` Jens Axboe
2015-02-13 12:03 ` Tejun Heo
2015-02-12 22:42 ` 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=54DD2E47.7060601@fb.com \
--to=axboe@fb.com \
--cc=Ronny.Hegewald@online.de \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox