From: Tejun Heo <tj@kernel.org>
To: Terry Suereth <terry.suereth@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the libata tree
Date: Mon, 19 Aug 2013 09:40:39 -0400 [thread overview]
Message-ID: <20130819134039.GB6176@htj.dyndns.org> (raw)
In-Reply-To: <CANQSiW2n1qo0YyR_jEYkNkDaDAukH6EEqNYA0nBxO1Sv7aUTAg@mail.gmail.com>
On Sun, Aug 18, 2013 at 08:18:55PM -0700, Terry Suereth wrote:
> Per my original patch, "0x3x26" in code should be "0x3726" (as in the
> unpatched version). I refer to "x26" in comments as a forward-looking
> assumption, but AFAIK only 3726 and 3826 exist at this time.
Heh... No idea how that happened. Fixed. Sorry about the trouble.
--
tejun
next prev parent reply other threads:[~2013-08-19 13:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 1:54 linux-next: build failure after merge of the libata tree Stephen Rothwell
2013-08-19 3:18 ` Terry Suereth
2013-08-19 13:40 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-06 14:08 Stephen Rothwell
2022-01-06 23:58 ` Damien Le Moal
2022-01-07 0:17 ` Stephen Rothwell
2022-01-07 1:28 ` Damien Le Moal
2016-05-09 0:14 Stephen Rothwell
2015-09-17 4:03 Stephen Rothwell
2015-09-17 11:14 ` Luis de Bethencourt
2014-04-24 1:17 Stephen Rothwell
2014-04-24 12:25 ` Tejun Heo
2014-02-26 2:55 Stephen Rothwell
2014-02-26 13:49 ` Tejun Heo
2013-08-27 2:50 Stephen Rothwell
2013-08-27 5:52 ` Aaron Lu
2013-08-27 18:09 ` Tejun Heo
2012-07-02 2:10 Stephen Rothwell
2012-07-02 2:19 ` huang ying
2010-08-18 0:40 Stephen Rothwell
2010-08-18 0:46 ` Gwendal Grignou
2010-08-19 20:15 ` Jeff Garzik
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=20130819134039.GB6176@htj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stable@vger.kernel.org \
--cc=terry.suereth@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;
as well as URLs for NNTP newsgroup(s).