All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Venture <venture@google.com>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Linux 4-10 v 4.13 patching
Date: Mon, 27 Nov 2017 18:49:05 -0800	[thread overview]
Message-ID: <CAO=notxMHYoZgxBJQpXOoP=TxcZFXJaNjFw=uFnw=4R9zyxSzQ@mail.gmail.com> (raw)
In-Reply-To: <CACPK8Xcv8F4WHs8bynxDSLK6pg4hYTm2w-044RmJ6dOEcYevJA@mail.gmail.com>

Thanks.  When sending to both, do I need to send a patch for each,
dev-4.10, dev-4.13 in the header or is it better to not specify the
branch in this case?

On Mon, Nov 27, 2017 at 6:39 PM, Joel Stanley <joel@jms.id.au> wrote:
> On Tue, Nov 28, 2017 at 1:52 AM, Patrick Venture <venture@google.com> wrote:
>> I'm sorry as I probably missed the email, should I send patches
>> against linux 4.10 or 4.13 or both?
>
> Good question. If you want something to boot this week, send them to both.
>
> If you're just wanting to get them in the tree, then just send them to 4.13.
>
> I am working on 4.13 but it's not ready to go yet.
>
> Cheers,
>
> Joel

  reply	other threads:[~2017-11-28  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 15:22 Linux 4-10 v 4.13 patching Patrick Venture
2017-11-28  2:39 ` Joel Stanley
2017-11-28  2:49   ` Patrick Venture [this message]
2017-11-28  2:51     ` Joel Stanley

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='CAO=notxMHYoZgxBJQpXOoP=TxcZFXJaNjFw=uFnw=4R9zyxSzQ@mail.gmail.com' \
    --to=venture@google.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.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.