From: Greg KH <gregkh@suse.de>
To: Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, hjlipp@web.de, tilman@imap.cc,
gigaset307x-common@lists.sourceforge.net, kkeil@suse.de,
isdn4linux@listserv.isdn4linux.de, mac@melware.de,
linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH resend] Make the dev_*() family of macros in device.hcomplete
Date: Fri, 2 Nov 2007 08:35:13 -0700 [thread overview]
Message-ID: <20071102153513.GA7485@suse.de> (raw)
In-Reply-To: <598D5675D34BE349929AF5EDE9B03E270174CCE0@az33exm24.fsl.freescale.net>
On Fri, Nov 02, 2007 at 04:59:48AM -0700, Medve Emilian-EMMEDVE1 wrote:
> Hello Andrew,
>
>
> Thanks for the detailed background.
>
> By now I also submitted a patch with extra spaces. Which one would be a
> better candidate for applying in a maintainer's tree (which tree?)?
> Could you please pick up one of the versions? Should I resubmit the
> first version without extra spaces?
The second patch looks good to me, it's "safer" and I'll add it to my
queue.
thanks,
greg k-h
next prev parent reply other threads:[~2007-11-02 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 22:43 [PATCH resend] Make the dev_*() family of macros in device.h complete Emil Medve
2007-10-29 23:08 ` Tilman Schmidt
2007-10-30 0:00 ` Greg KH
2007-10-30 12:11 ` [PATCH resend] Make the dev_*() family of macros in device.hcomplete Medve Emilian-EMMEDVE1
2007-10-30 12:11 ` Medve Emilian-EMMEDVE1
2007-10-30 15:29 ` Randy Dunlap
2007-10-30 15:29 ` Randy Dunlap
2007-10-30 15:40 ` Greg KH
2007-11-01 23:57 ` Andrew Morton
2007-11-02 11:59 ` Medve Emilian-EMMEDVE1
2007-11-02 11:59 ` Medve Emilian-EMMEDVE1
2007-11-02 15:35 ` Greg KH [this message]
2007-11-02 15:35 ` Greg KH
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=20071102153513.GA7485@suse.de \
--to=gregkh@suse.de \
--cc=Emilian.Medve@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=gigaset307x-common@lists.sourceforge.net \
--cc=hjlipp@web.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap-open-source@linux.omap.com \
--cc=mac@melware.de \
--cc=tilman@imap.cc \
/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.