From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] serial: sh-sci: HSCIF support
Date: Thu, 20 Jun 2013 12:08:37 +0000 [thread overview]
Message-ID: <20130620120836.GB27177@verge.net.au> (raw)
In-Reply-To: <201306191708.46525.arnd@arndb.de>
On Wed, Jun 19, 2013 at 05:08:46PM +0200, Arnd Bergmann wrote:
> On Wednesday 19 June 2013, Simon Horman wrote:
> > > This is of course trivially fixed, but I have completely lost track of
> > > the transmogrifications this patch has been subjected to. What's the
> > > procedure?
> >
> > Hi Ulrich,
> >
> > perhaps the best way forward would be for you to post an incremental patch
> > on top of either the sh-sci branch or renesas-next-20130618 tag of
> > my renesas tree on kernel.org.
>
> I'm not sure where we stand on this series at the moment. Should
> I pull v3, has Olof already pulled it, or should I wait for an
> update?
Hi Arnd,
my preference is for you to wait for an update.
In order to move things forwards I will post a proposed
fix shortly. I believe that the warnings are for conditions
that can never occur and thus in my patch I will propose initialising the
variables that are flagged as being used uninitialised.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] serial: sh-sci: HSCIF support
Date: Thu, 20 Jun 2013 21:08:37 +0900 [thread overview]
Message-ID: <20130620120836.GB27177@verge.net.au> (raw)
In-Reply-To: <201306191708.46525.arnd@arndb.de>
On Wed, Jun 19, 2013 at 05:08:46PM +0200, Arnd Bergmann wrote:
> On Wednesday 19 June 2013, Simon Horman wrote:
> > > This is of course trivially fixed, but I have completely lost track of
> > > the transmogrifications this patch has been subjected to. What's the
> > > procedure?
> >
> > Hi Ulrich,
> >
> > perhaps the best way forward would be for you to post an incremental patch
> > on top of either the sh-sci branch or renesas-next-20130618 tag of
> > my renesas tree on kernel.org.
>
> I'm not sure where we stand on this series at the moment. Should
> I pull v3, has Olof already pulled it, or should I wait for an
> update?
Hi Arnd,
my preference is for you to wait for an update.
In order to move things forwards I will post a proposed
fix shortly. I believe that the warnings are for conditions
that can never occur and thus in my patch I will propose initialising the
variables that are flagged as being used uninitialised.
next prev parent reply other threads:[~2013-06-20 12:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 3:38 [GIT PULL 0/2 v2] Renesas sh-sci updates for v3.11 Simon Horman
2013-06-17 3:38 ` Simon Horman
2013-06-17 3:38 ` [PATCH 1/2] serial: sh-sci: HSCIF support Simon Horman
2013-06-17 3:38 ` Simon Horman
2013-06-17 12:54 ` Arnd Bergmann
2013-06-17 12:54 ` Arnd Bergmann
2013-06-18 1:19 ` Simon Horman
2013-06-18 1:19 ` Simon Horman
2013-06-19 8:46 ` Ulrich Hecht
2013-06-19 8:46 ` Ulrich Hecht
2013-06-19 12:33 ` Simon Horman
2013-06-19 12:33 ` Simon Horman
2013-06-19 15:08 ` Arnd Bergmann
2013-06-19 15:08 ` Arnd Bergmann
2013-06-20 12:08 ` Simon Horman [this message]
2013-06-20 12:08 ` Simon Horman
2013-06-17 3:38 ` [PATCH 2/2] ARM: shmobile: r8a7790: don't use external clock for SCIFs Simon Horman
2013-06-17 3:38 ` Simon Horman
2013-06-17 8:59 ` [GIT PULL 0/2 v2] Renesas sh-sci updates for v3.11 Simon Horman
2013-06-17 8:59 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2013-06-17 2:42 [PATCH 0/2] serial: sh-sci: HSCIF support Simon Horman
2013-06-17 2:42 ` [PATCH 1/2] " Simon Horman
2013-06-17 2:42 ` Simon Horman
2013-06-17 2:42 ` Simon Horman
2013-06-17 3:00 ` Greg Kroah-Hartman
2013-06-17 2:59 ` Greg Kroah-Hartman
2013-06-17 3:00 ` Greg Kroah-Hartman
2013-06-13 7:00 [GIT PULL 0/2] Renesas sh-sci updates for v3.11 Simon Horman
2013-06-13 7:00 ` [PATCH 1/2] serial: sh-sci: HSCIF support Simon Horman
2013-06-13 7:00 ` Simon Horman
2013-06-15 1:03 ` Olof Johansson
2013-06-15 1:03 ` Olof Johansson
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=20130620120836.GB27177@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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.