public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Madhusudhan Chikkature Rajashekar" <madhu.cr@ti.com>
To: 'Tony Lindgren' <tony@atomide.com>
Cc: 'Evgeniy Polyakov' <johnpol@2ka.mipt.ru>,
	linux-omap@vger.kernel.org,
	linux-omap-open-source@linux.omap.com
Subject: RE: [RFC/PATCH 0/5] HDQ/1-wire support for OMAP2430/3430
Date: Mon, 17 Dec 2007 10:53:23 +0530	[thread overview]
Message-ID: <005f01c8406c$f3409240$fe8818ac@ent.ti.com> (raw)
In-Reply-To: <20071216002148.GC7388@atomide.com>

 

> -----Original Message-----
> From: Tony Lindgren [mailto:tony@atomide.com] 
> Sent: Sunday, December 16, 2007 5:52 AM
> To: Madhusudhan Chikkature Rajashekar
> Cc: 'Evgeniy Polyakov'; linux-omap@vger.kernel.org; 
> linux-omap-open-source@linux.omap.com
> Subject: Re: [RFC/PATCH 0/5] HDQ/1-wire support for OMAP2430/3430
> 
> * Madhusudhan Chikkature Rajashekar <madhu.cr@ti.com> [071210 04:02]:
> > Hi,
> > 
> > >You resolved all issues with patchet we were talking 
> about, so I only
> > >would like to see documentation update about how hdq operates in w1
> > >stack and kernel parameters you are using in the driver.
> >  Sure. I will write the necessary documentation.
> > 
> > Thanks,
> > Madhu
> > 
> > -----Original Message-----
> > From: Evgeniy Polyakov [mailto:johnpol@2ka.mipt.ru] 
> > Sent: Monday, December 10, 2007 5:04 PM
> > To: Madhusudhan Chikkature Rajashekar
> > Cc: linux-omap-open-source@linux.omap.com; 
> linux-omap@vger.kernel.org
> > Subject: Re: [RFC/PATCH 0/5] HDQ/1-wire support for OMAP2430/3430
> > 
> > Hi.
> > 
> > On Mon, Dec 10, 2007 at 03:45:25PM +0530, Madhusudhan 
> Chikkature Rajashekar (madhu.cr@ti.com) wrote:
> > > I am posting a five patches series to support HDQ/1-wire 
> module of OMAP2430 and 3430 platforms. The HDQ support is internally
> > tested
> > > using a bq27000 battery driver.
> > > 
> > > Please let me know if there are any comments on my patch set.
> > > 
> > > Evgeniy Polyakov,
> > > I would like to thank you for clearing my doubts about 
> the W1 subsystem.
> > > Please let me know if you have any further comments on my patches.
> > 
> > Ack, thanks a lot for your work.
> > 
> > You resolved all issues with patchet we were talking about, 
> so I only
> > would like to see documentation update about how hdq operates in w1
> > stack and kernel parameters you are using in the driver.
> 
> Madhu, can you please repost your complete series one more 
> time? Please
> make sure the message subject describes what the patch does instead of
> the same subject for all of them. The subject line appears in 
> the git-commit
> message, and it's a pain to re-edit each patch before applying.
Okay. I will repost the series with appropriate subject line.

> 
> Thanks,
> 
> Tony
> 

  reply	other threads:[~2007-12-17  5:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071210113407.GD28406@2ka.mipt.ru>
2007-12-10 12:01 ` [RFC/PATCH 0/5] HDQ/1-wire support for OMAP2430/3430 Madhusudhan Chikkature Rajashekar
2007-12-16  0:21   ` Tony Lindgren
2007-12-17  5:23     ` Madhusudhan Chikkature Rajashekar [this message]
2007-12-10 10:15 Madhusudhan Chikkature Rajashekar

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='005f01c8406c$f3409240$fe8818ac@ent.ti.com' \
    --to=madhu.cr@ti.com \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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