linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH] staging: ath6kl: Including a header file to fix a compilation error
Date: Fri, 17 Sep 2010 22:12:44 -0700	[thread overview]
Message-ID: <20100918051244.GB18733@kroah.com> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F23A27636@SC1EXMB-MBCL.global.atheros.com>

On Fri, Sep 17, 2010 at 07:00:56PM -0700, Vipin Mehta wrote:
> > 
> > Please, fix your email client to wrap lines at a sane place...
> Do you have any recommendation for the email client? 
> I am using outlook currently.

Anything except outlook (thunderbird, evolution, mutt, etc.)

> > If the problem is due to another change in a different tree, send me the
> > patch and I'll hold on to it until the mmc tree is merged with Linus
> > (during the .37 merge window) and then I'll apply it and push it out.
> > 
> > Until then, we can ask Stephen to hold the patch in linux-next to fix
> > the build issue.
> >
> I have sent out a patch for the linux-next tree that
> fixes the problem. BTW, is there a way I can include
> comments in the patch. How do you establish a context
> between what is discussed in these emails with the
> patches sent to you?

Read Documentation/SubmittingPatches, section 15, for how to do this.

> > But I'd still like the .h file fixup patch to be resolved and in my tree
> > first, right?
> I have sent you the patch.

I got them, I'll process them next week.

thanks,

greg k-h

  reply	other threads:[~2010-09-18  5:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17 16:54 [PATCH] staging: ath6kl: Including a header file to fix a compilation error Vipin Mehta
2010-09-17 17:23 ` Randy Dunlap
2010-09-17 18:00   ` Greg KH
2010-09-17 23:26     ` Vipin Mehta
2010-09-17 23:46       ` Greg KH
2010-09-18  2:06         ` Vipin Mehta
2010-09-18  5:11           ` Greg KH
2010-09-17 23:11   ` Vipin Mehta
2010-09-17 23:26     ` Greg KH
2010-09-18  2:00       ` Vipin Mehta
2010-09-18  5:12         ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-17  0:08 Vipin Mehta
2010-09-17  0:10 ` Luis R. Rodriguez
2010-09-17  0:13   ` Vipin Mehta
2010-09-17  0:17     ` Greg KH
2010-09-17  0:14 ` 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=20100918051244.GB18733@kroah.com \
    --to=greg@kroah.com \
    --cc=Vipin.Mehta@Atheros.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=randy.dunlap@oracle.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).