From: Jeff Garzik <jeff@garzik.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>
Subject: Re: linux-next: build warning after merge of the libata tree
Date: Fri, 24 Feb 2012 12:01:56 -0500 [thread overview]
Message-ID: <4F47C284.6050703@garzik.org> (raw)
In-Reply-To: <20120224232212.caf992ef1200adb2b761890c@canb.auug.org.au>
On 02/24/2012 07:22 AM, Stephen Rothwell wrote:
> Hi Jeff,
>
> On Fri, 24 Feb 2012 15:14:10 +1100 Stephen Rothwell<sfr@canb.auug.org.au> wrote:
>>
>> On Thu, 23 Feb 2012 23:06:11 -0500 Jeff Garzik<jeff@garzik.org> wrote:
>>>
>>> A build fix and oops fix were both just pushed out.
>>
>> Excellent, thanks.
>
> Except the commits in the current version of the libata tree destined for
> linux-next do not fix the warnings I was reporting where the "inline"
> keyword is missing from several static function definitions in
> drivers/ata/libata.h ...
Patchset backed out, and hopefully this will get fixed before it appears
again in linux-next.
Jeff
next prev parent reply other threads:[~2012-02-24 17:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 5:27 linux-next: build warning after merge of the libata tree Stephen Rothwell
2012-02-24 3:08 ` Stephen Rothwell
2012-02-24 4:06 ` Jeff Garzik
2012-02-24 4:14 ` Stephen Rothwell
2012-02-24 12:22 ` Stephen Rothwell
2012-02-24 17:01 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-28 5:51 Stephen Rothwell
2017-06-28 18:28 ` Tejun Heo
2018-01-18 4:26 Stephen Rothwell
2018-02-13 3:04 Stephen Rothwell
2018-02-13 14:42 ` Tejun Heo
2018-03-20 4:57 Stephen Rothwell
2018-03-20 4:59 ` Richard Zhu
2022-06-20 0:34 Stephen Rothwell
2022-06-20 0:43 ` Damien Le Moal
2022-06-20 8:21 ` Stephen Rothwell
2022-06-20 8:53 ` Damien Le Moal
2022-06-20 10:57 ` Sergey Shtylyov
2022-06-20 11:07 ` Damien Le Moal
2022-06-20 20:07 ` Sergey Shtylyov
2022-06-20 20:08 ` Sergey Shtylyov
2022-09-19 2:40 Stephen Rothwell
2022-09-19 8:01 ` Damien Le Moal
2022-09-19 23:56 ` Damien Le Moal
2022-09-20 19:25 ` Serge Semin
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=4F47C284.6050703@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=sfr@canb.auug.org.au \
/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