From: Peter Huewe <PeterHuewe@gmx.de> To: Greg KH <gregkh@suse.de> Cc: Jiri Kosina <jkosina@suse.cz>, Alan Cox <alan@linux.intel.com>, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH] staging/et131x: adding __init/__exit macros Date: Tue, 20 Oct 2009 00:04:23 +0200 [thread overview] Message-ID: <200910200004.23875.PeterHuewe@gmx.de> (raw) In-Reply-To: <20091019214351.GA15014@suse.de> Am Monday 19 October 2009 23:43:51 schrieb Greg KH: > These patches are still in my queue, sorry, been really busy, and am now > at the Linux kernel summit this week. I should get to them next week > when I return. > > thanks for your patience, > > greg k-h Absolutely no problem - sorry for bugging you. Have a good time at the summit. Peter > -- > To unsubscribe from this list: send the line "unsubscribe kernel-janitors" > in the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Peter Huewe <PeterHuewe@gmx.de> To: Greg KH <gregkh@suse.de> Cc: Jiri Kosina <jkosina@suse.cz>, Alan Cox <alan@linux.intel.com>, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH] staging/et131x: adding __init/__exit macros Date: Mon, 19 Oct 2009 22:04:23 +0000 [thread overview] Message-ID: <200910200004.23875.PeterHuewe@gmx.de> (raw) In-Reply-To: <20091019214351.GA15014@suse.de> Am Monday 19 October 2009 23:43:51 schrieb Greg KH: > These patches are still in my queue, sorry, been really busy, and am now > at the Linux kernel summit this week. I should get to them next week > when I return. > > thanks for your patience, > > greg k-h Absolutely no problem - sorry for bugging you. Have a good time at the summit. Peter > -- > To unsubscribe from this list: send the line "unsubscribe kernel-janitors" > in the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-19 22:04 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-28 23:34 [PATCH] staging/et131x: adding __init/__exit macros Peter Huewe 2009-09-28 23:34 ` Peter Huewe 2009-09-29 9:10 ` Jiri Kosina 2009-09-29 9:10 ` Jiri Kosina 2009-09-29 15:30 ` Greg KH 2009-09-29 15:30 ` Greg KH 2009-10-19 15:24 ` Peter Hüwe 2009-10-19 15:24 ` Peter Hüwe 2009-10-19 21:43 ` Greg KH 2009-10-19 21:43 ` Greg KH 2009-10-19 22:04 ` Peter Huewe [this message] 2009-10-19 22:04 ` Peter Huewe 2009-09-29 10:57 ` Alan Cox 2009-09-29 10:57 ` Alan Cox
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=200910200004.23875.PeterHuewe@gmx.de \ --to=peterhuewe@gmx.de \ --cc=alan@linux.intel.com \ --cc=devel@driverdev.osuosl.org \ --cc=gregkh@suse.de \ --cc=jkosina@suse.cz \ --cc=kernel-janitors@vger.kernel.org \ --cc=linux-kernel@vger.kernel.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: linkBe 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.