From: Ingo Molnar <mingo@elte.hu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: steven@uplinklabs.net, linux-kernel@vger.kernel.org,
tglx@linutronix.de, hpa@zytor.com
Subject: Re: [PATCH] x86: unused variable in dma_alloc_coherent_gfp_flags()
Date: Tue, 9 Sep 2008 09:13:38 +0200 [thread overview]
Message-ID: <20080909071338.GB3412@elte.hu> (raw)
In-Reply-To: <20080909160455J.fujita.tomonori@lab.ntt.co.jp>
* FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> On Tue, 9 Sep 2008 08:57:36 +0200
> Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * Steven Noonan <steven@uplinklabs.net> wrote:
> >
> > > Fixed a warning caused by a badly placed ifdef.
> > >
> > > Signed-off-by: Steven Noonan <steven@uplinklabs.net>
> >
> > applied to tip/x86/iommu - thanks Steven,
>
> Did you apply the same patch yesterday?
>
> http://lkml.org/lkml/2008/9/8/274
yes, but i havent pushed it out in time yesterday night. In such
scenarios i generally zap the patch i generated and replace it with the
fix that is being sent against the last publicly available tree. That is
what happened here too. This makes it all symmetric and fair (i as a
maintainer have no time advantage to get fixes in first) and it also
teaches me to push out fixes faster :-)
Ingo
next prev parent reply other threads:[~2008-09-09 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 23:19 [PATCH] x86: fix HPET compiler error when not using CONFIG_PCI_MSI Steven Noonan
2008-09-08 23:19 ` [PATCH] init/initramfs.c: unused function when compiling without CONFIG_BLK_DEV_RAM Steven Noonan
2008-09-08 23:19 ` [PATCH] x86: unused variable in dma_alloc_coherent_gfp_flags() Steven Noonan
2008-09-09 6:57 ` Ingo Molnar
2008-09-09 7:04 ` FUJITA Tomonori
2008-09-09 7:13 ` Ingo Molnar [this message]
2008-09-09 6:51 ` [PATCH] init/initramfs.c: unused function when compiling without CONFIG_BLK_DEV_RAM Ingo Molnar
2008-09-09 6:56 ` [PATCH] x86: fix HPET compiler error when not using CONFIG_PCI_MSI Ingo Molnar
2008-09-09 0:13 ` Steven Noonan
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=20080909071338.GB3412@elte.hu \
--to=mingo@elte.hu \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steven@uplinklabs.net \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®