All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Alan Cox <alan@linux.intel.com>,
	torvalds@linux-foundation.org, Baruch Siach <baruch@tkos.co.il>,
	Rong Wang <Rong.Wang@csr.com>, Bin Shi <Bin.Shi@csr.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org, workgroup.linux@csr.com,
	linux-serial@vger.kernel.org, Barry Song <Baohua.Song@csr.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] UART: add CSR SiRFprimaII SoC on-chip uart drivers
Date: Tue, 1 Nov 2011 06:10:21 -0700	[thread overview]
Message-ID: <20111101131021.GA9109@kroah.com> (raw)
In-Reply-To: <CAGsJ_4wGRv9=fbWtK-0jkmXDcd=y2r6qxae99tNgim4=BmxJ+w@mail.gmail.com>

On Tue, Nov 01, 2011 at 08:48:29PM +0800, Barry Song wrote:
> 2011/11/1 Alan Cox <alan@linux.intel.com>:
> >> i am not sure whether i will make Linus confused if i send a new
> >> version at this moment. how about i send a seperate patch to fix this
> >> after the driver is applied?
> >
> > That would be the best idea - its a trivial typo so doesn't really
> > matter much.
> ok, Alan.
> 
> Linus, have you gotten it? and can you apply it?
> or do you want this to go through tty tree and merge it until next merge window?

That's probably the easiest thing to do, right?  Send it to me and I can
handle it.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] UART: add CSR SiRFprimaII SoC on-chip uart drivers
Date: Tue, 1 Nov 2011 06:10:21 -0700	[thread overview]
Message-ID: <20111101131021.GA9109@kroah.com> (raw)
In-Reply-To: <CAGsJ_4wGRv9=fbWtK-0jkmXDcd=y2r6qxae99tNgim4=BmxJ+w@mail.gmail.com>

On Tue, Nov 01, 2011 at 08:48:29PM +0800, Barry Song wrote:
> 2011/11/1 Alan Cox <alan@linux.intel.com>:
> >> i am not sure whether i will make Linus confused if i send a new
> >> version at this moment. how about i send a seperate patch to fix this
> >> after the driver is applied?
> >
> > That would be the best idea - its a trivial typo so doesn't really
> > matter much.
> ok, Alan.
> 
> Linus, have you gotten it? and can you apply it?
> or do you want this to go through tty tree and merge it until next merge window?

That's probably the easiest thing to do, right?  Send it to me and I can
handle it.

thanks,

greg k-h

  reply	other threads:[~2011-11-01 13:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  3:27 [PATCH] UART: add CSR SiRFprimaII SoC on-chip uart drivers Barry Song
2011-10-28  3:27 ` Barry Song
2011-10-28  3:27 ` Barry Song
2011-10-28  7:11 ` Baruch Siach
2011-10-28  7:11   ` Baruch Siach
2011-10-28  7:11   ` Baruch Siach
2011-10-28  7:35   ` Barry Song
2011-10-28  7:35     ` Barry Song
2011-10-28  7:35     ` Barry Song
2011-11-01 11:42     ` Alan Cox
2011-11-01 11:42       ` Alan Cox
2011-11-01 12:48       ` Barry Song
2011-11-01 12:48         ` Barry Song
2011-11-01 13:10         ` Greg KH [this message]
2011-11-01 13:10           ` Greg KH
2011-11-01 13:28           ` Barry Song
2011-11-01 13:28             ` Barry Song
2011-11-01 13:40             ` Greg KH
2011-11-01 13:40               ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2011-11-17 15:17 Barry Song
2011-10-13  6:28 Barry Song
2011-10-13  6:28 ` Barry Song
2011-10-13  9:55 ` Alan Cox
2011-10-13  9:55   ` Alan Cox
2011-10-13 13:45   ` Barry Song
2011-10-13 13:45     ` Barry Song
2011-10-13 14:27     ` Alan Cox
2011-10-13 14:27       ` Alan Cox
2011-10-13 14:49       ` Barry Song
2011-10-13 14:49         ` Barry Song

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=20111101131021.GA9109@kroah.com \
    --to=greg@kroah.com \
    --cc=21cnbao@gmail.com \
    --cc=Baohua.Song@csr.com \
    --cc=Bin.Shi@csr.com \
    --cc=Rong.Wang@csr.com \
    --cc=alan@linux.intel.com \
    --cc=baruch@tkos.co.il \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=workgroup.linux@csr.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 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.