All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/4] sparc32,leon: Uart polling support, KGDB with SPARC32
Date: Fri, 30 Sep 2011 13:01:08 +0000	[thread overview]
Message-ID: <4E85BD94.4040109@gaisler.com> (raw)
In-Reply-To: <1317381862-24939-1-git-send-email-konrad@gaisler.com>

Julian Calaby wrote:
> Hi Konrad,
> 
> On Fri, Sep 30, 2011 at 21:24, Konrad Eisele <konrad@gaisler.com> wrote:
>> I have some patches that are used by SPARC_LEON to connect to
>> KGDB.
>> 0001-apbuart-add-polling-callbacks-to-apbuart-driver.patch adds polling functions
>>  to apbuart.c
>> 0002-apbuart-add-support-for-virtual-KGDB-GRMON-channel.patch is a bit special: when
>>  the user doesnt have a hardware serial device he can use the debug monitor GRMON
>>  as a tunnel. GRMON will poll a memory region to put/get characters.
>> 0003-sparc32-leon-Add-support-for-KGDB-when-SMP-and-SPARC.patch this adds KGDB when
>>  SMP is enabled. Inplemented only for SPARC_LEON, on other SPARC32 platforms KGDB
>>  wont still be enabled.
> 
> Stupid question: is there a fourth patch? The subject line implies
> there might be.

No, I've created the numbering by hand and added a 0000-m.patch file
"[PATCH 0/4] sparc32,leon: Uart polling support, KGDB with SPARC32 SMP."
to have  an introduction text.
Then I used "git send-email ... 00*.patch" to send them.
-- Konrad

> 
> Thanks,
> 


  parent reply	other threads:[~2011-09-30 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 11:24 [PATCH 0/4] sparc32,leon: Uart polling support, KGDB with SPARC32 SMP Konrad Eisele
2011-09-30 12:50 ` Julian Calaby
2011-09-30 13:01 ` Konrad Eisele [this message]
2011-09-30 13:47 ` Konrad Eisele

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=4E85BD94.4040109@gaisler.com \
    --to=konrad@gaisler.com \
    --cc=sparclinux@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: 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.