All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
To: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Linus Walleij
	<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Srinidhi KASAGAR
	<srinidhi.kasagar-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Subject: Re: [PATCH] i2c-nomadik: fix kerneldoc warning
Date: Tue, 28 Jun 2011 07:25:25 +0200	[thread overview]
Message-ID: <4E0965C5.30600@stericsson.com> (raw)
In-Reply-To: <20110627220449.GB23027-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>

On 06/28/2011 12:04 AM, Ben Dooks wrote:
> On Wed, Jun 15, 2011 at 12:42:02PM +0200, Linus Walleij wrote:
>    
>> From: Linus Walleij<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>>
>> There was a missing struct item in the kerneldoc, add it and fix
>> another pretty-printing formatting issue with a missing space.
>>      
> weird, it didn't apply to 3.0-rc4.
>    

In my topic branch I also have a patch from Srinidhi Kasagar
titled "i2c-nomadik: Do not use _interruptible_ variant call",
that went on the list some time back, could it be that you
missed that one?

If you want to I can resend it.

Thanks,
Linus Walleij

      parent reply	other threads:[~2011-06-28  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 10:42 [PATCH] i2c-nomadik: fix kerneldoc warning Linus Walleij
     [not found] ` <1308134522-30858-1-git-send-email-linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
2011-06-27 22:04   ` Ben Dooks
     [not found]     ` <20110627220449.GB23027-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>
2011-06-28  5:25       ` Linus Walleij [this message]

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=4E0965C5.30600@stericsson.com \
    --to=linus.walleij-0is4wlfg1ojsueelwk9/pw@public.gmane.org \
    --cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=srinidhi.kasagar-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.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: 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.