All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM] U-Boot ARM/PXA maintainership
Date: Sun, 18 Apr 2010 16:17:43 +0200	[thread overview]
Message-ID: <201004181617.43741.marek.vasut@gmail.com> (raw)
In-Reply-To: <4BCB075C.20803@bumblecow.com>

Dne Ne 18. dubna 2010 15:21:32 Tom Rix napsal(a):
> Marek Vasut wrote:
> > Dne So 17. dubna 2010 23:27:56 Tom Rix napsal(a):
> >> Marek Vasut wrote:
> >>> Dne Ne 11. dubna 2010 22:53:44 Tom napsal(a):
> >>>> Marek Vasut wrote:
> >>>>> Hello,
> >>> 
> >>> Hi
> >>> 
> >>>>> It seems my patches for the PXA2xx and PXA3xx in U-Boot are ignored.
> >>>>> I'd be willing to take over PXA maintainance in U-Boot. I already
> >>>>> maintain various PXA- based devices in mainline Linux kernel. I also
> >>>>> maintain the OpenPXA project (IPL for PXA3xx devices).
> >>>> 
> >>>> The correct thing to do is to ping me!
> >>> 
> >>> Fine, good to know, thanks.
> >>> 
> >>>> If it looks like your patches are being ignored it is likely an
> >>>> oversight on my part.  I will search through what you have posted
> >>>> recently and take care of these.
> >>> 
> >>> Look for:
> >>> [PATCH] PXA: Align stack to 8 bytes
> >>> [PATCH] PXAMMC: Drop different delays for PXA27X
> >>> [PATCH 1/2] Enable PXAFB for PXA27X and PXA3XX
> >>> [PATCH 2/2] PXAMCI Monahans support
> >>> 
> >>> Or I can just resend you the whole patchset. There are more patches for
> >>> PXA in my tree, that's why I'd like to take over that bit (PXA of
> >>> course, not the whole ARM tree!).
> >> 
> >> I see the first two in the u-boot-pxa tree.
> >> When you are comfortable with the tree, please send me a pull request
> >> and I will merge the commits specified in the request into Arm.
> >> 
> >> If you want to do this now or after the other two are in is up to you.
> >> 
> >> Welcome aboard!
> >> Tom
> > 
> > Hi,
> > I see no reply on the PXAMCI one so I'll push that. Also I'll push the
> > delay fix for PXAMCI. The PXAFB one will need further rework now that I
> > think of it. I also added a few register definitions that were missing
> > and were quite important.
> > 
> > I'd like you to pull that now if possible. Thanks!
> 
> Please review how other folks ask for pull requests on the list.
> 
> You will need to post the output of this git request-pull command to the
> mailing list.
> 
> something like

Yup, will send.
> 
> git request-pull 8d321b81c5441db93425ee37cb79cc51d9ce2fb0
> git://git.denx.de/u-boot-pxa/master
> fatal: The remote end hung up unexpectedly
> warn: No branch of git://git.denx.de/u-boot-pxa/master is at:
> warn:   97bc89c: PXA: Add missing MDREFR bits
> warn: Are you sure you pushed HEAD there?
> 
> 
> The following changes since commit
> 8d321b81c5441db93425ee37cb79cc51d9ce2fb0: Peter Tyser (1):
>          Update README to reflect new directory structure
> 
> are available in the git repository at:
> 
>    git://git.denx.de/u-boot-pxa/master ..BRANCH.NOT.VERIFIED..
> 
> --- BRANCH.NOT.VERIFIED is an error..
> --- Do not submit a pull request with this message

Noticed that, but I'm unsure what I messed up. I'll look into this and send a 
request once fixed.
> 
> Marek Vasut (6):
>        PXA: Align stack to 8 bytes
>        PXA: Fix abort stack
>        PXA: Drop different delays in PXAMMC for PXA27X
>        PXA: PXAMMC: Add Monahans support
>        PXA: Add UP2OCR register bit definitions
>        PXA: Add missing MDREFR bits
> 
>   arch/arm/cpu/pxa/start.S                 |    5 ++++-
>   arch/arm/include/asm/arch-pxa/pxa-regs.h |   23 +++++++++++++++++++----
>   drivers/mmc/pxa_mmc.c                    |   17 ++++++-----------
>   3 files changed, 29 insertions(+), 16 deletions(-)
> 
>  From a really quick review, the last patch
> 
> PXA: Add missing MDREFR bits
> 
> Has not been posted to the mailing list.
> In general it is a requirement that all commits must be posted.

Ok, will git send-email them. Those are quite trivial things so I hope nothing 
much happened.
> 
> Once you issue a pull request, I can work around new commits
> appended to your tree.  Meaning you can add stuff after
> the pull request.

Sure, or I can prepare a branch for you.
> 
> Tom

Cheers
> 
> > Also, thanks for welcoming me, happy to be here :)
> > 
> > Cheers!

  reply	other threads:[~2010-04-18 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11  0:43 [U-Boot] U-Boot ARM/PXA maintainership Marek Vasut
2010-04-11 20:53 ` Tom
2010-04-12  1:56   ` [U-Boot] [ARM] " Marek Vasut
2010-04-17 21:27     ` Tom Rix
2010-04-18  8:53       ` Marek Vasut
2010-04-18 13:21         ` Tom Rix
2010-04-18 14:17           ` Marek Vasut [this message]
2010-04-13 15:45 ` [U-Boot] " Wolfgang Denk
2010-04-14 11:26   ` Tom
2010-04-14 18:26     ` Wolfgang Denk
2010-04-14 18:42       ` Marek Vasut
2010-04-15  6:37         ` Prafulla Wadaskar

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=201004181617.43741.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.