Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1195822 > unrolled thread

Re: [PATCH v2 1/3] iTCO_wdt: Expose watchdog properties using platform data

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v2 1/3] iTCO_wdt: Expose watchdog properties using  platform data Lee Jones <lee.jones@linaro.org> - 2015-07-30 11:00 +0200
    Re: [PATCH v2 1/3] iTCO_wdt: Expose watchdog properties using  platform data Matt Fleming <matt@codeblueprint.co.uk> - 2015-07-30 11:20 +0200
      Re: [PATCH v2 1/3] iTCO_wdt: Expose watchdog properties using  platform data Lee Jones <lee.jones@linaro.org> - 2015-07-30 13:10 +0200

#1195822 — Re: [PATCH v2 1/3] iTCO_wdt: Expose watchdog properties using platform data

On Wed, 29 Jul 2015, Matt Fleming wrote:

> On Wed, 29 Jul, at 04:35:56PM, Lee Jones wrote:
> > 
> > For my own reference (I assume this will go through the MFD tree):
> >   Acked-by: Lee Jones <lee.jones@linaro.org>
> 
> Great, thanks Lee!
> 
> I've no strong opinion on which tree these 3 patches go through but at
> the very least patches 1 and 2 need to go through the same tree to avoid
> build breakage (since PATCH 1 introduces 'struct itco_wdt_platform_data'
> which is used in PATCH 2).
> 
> For reference, the other patches are here,
> 
>   https://lkml.kernel.org/r/1438171844-24861-3-git-send-email-matt@codeblueprint.co.uk
>   https://lkml.kernel.org/r/1438171844-24861-4-git-send-email-matt@codeblueprint.co.uk

Obviously this makes things more difficult.  Once you have the other
Acks you need, I suggest you re-submit the set using --threaded, so we
can all see what's going on.

FYI: I usually do this as a matter of course, as separated patches are
a pain to manage, particularly if there are dependencies between them.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1195840

On Thu, 30 Jul, at 09:53:47AM, Lee Jones wrote:
> On Wed, 29 Jul 2015, Matt Fleming wrote:
> 
> > On Wed, 29 Jul, at 04:35:56PM, Lee Jones wrote:
> > > 
> > > For my own reference (I assume this will go through the MFD tree):
> > >   Acked-by: Lee Jones <lee.jones@linaro.org>
> > 
> > Great, thanks Lee!
> > 
> > I've no strong opinion on which tree these 3 patches go through but at
> > the very least patches 1 and 2 need to go through the same tree to avoid
> > build breakage (since PATCH 1 introduces 'struct itco_wdt_platform_data'
> > which is used in PATCH 2).
> > 
> > For reference, the other patches are here,
> > 
> >   https://lkml.kernel.org/r/1438171844-24861-3-git-send-email-matt@codeblueprint.co.uk
> >   https://lkml.kernel.org/r/1438171844-24861-4-git-send-email-matt@codeblueprint.co.uk
> 
> Obviously this makes things more difficult.  Once you have the other
> Acks you need, I suggest you re-submit the set using --threaded, so we
> can all see what's going on.
 
Umm... I submitted *this* version using --threaded. In fact, that's
plain to see from the Message-Id format in the links above. It's just
that I only Cc'd you on the patch that touched the mfd code.

I can resubmit with the Ack/Review tags and copy you on the whole series
if you'd like.

-- 
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1195911

On Thu, 30 Jul 2015, Matt Fleming wrote:

> On Thu, 30 Jul, at 09:53:47AM, Lee Jones wrote:
> > On Wed, 29 Jul 2015, Matt Fleming wrote:
> > 
> > > On Wed, 29 Jul, at 04:35:56PM, Lee Jones wrote:
> > > > 
> > > > For my own reference (I assume this will go through the MFD tree):
> > > >   Acked-by: Lee Jones <lee.jones@linaro.org>
> > > 
> > > Great, thanks Lee!
> > > 
> > > I've no strong opinion on which tree these 3 patches go through but at
> > > the very least patches 1 and 2 need to go through the same tree to avoid
> > > build breakage (since PATCH 1 introduces 'struct itco_wdt_platform_data'
> > > which is used in PATCH 2).
> > > 
> > > For reference, the other patches are here,
> > > 
> > >   https://lkml.kernel.org/r/1438171844-24861-3-git-send-email-matt@codeblueprint.co.uk
> > >   https://lkml.kernel.org/r/1438171844-24861-4-git-send-email-matt@codeblueprint.co.uk
> > 
> > Obviously this makes things more difficult.  Once you have the other
> > Acks you need, I suggest you re-submit the set using --threaded, so we
> > can all see what's going on.
>  
> Umm... I submitted *this* version using --threaded. In fact, that's
> plain to see from the Message-Id format in the links above. It's just
> that I only Cc'd you on the patch that touched the mfd code.

Ah yes, similar result.  Again, unless the set is particularlly large
or touches many subsystems, I tend to Cc all affected Maintainers (if
I'm sending, or like to be Cc'ed if I'm the recipient) on all of the
patches.  Set status is much easier to track that way and issues which
might be relevant to more than one patch in the set can be seen by
all.

> I can resubmit with the Ack/Review tags and copy you on the whole series
> if you'd like.

That would be perfect.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web