From: Jonathan Cameron <jic23@kernel.org>
To: "Mereena Mathai Liquancin (MS/EMS3-BST)"
<Liquancin.MereenaMathai@in.bosch.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Subject: Query Regarding IIO Patch Submission and Inclusion in linux-next
Date: Sat, 6 Jul 2024 11:28:07 +0100 [thread overview]
Message-ID: <20240706112807.6fd69e5b@jic23-huawei> (raw)
In-Reply-To: <AS2PR10MB77388143DBA2ACC76CFD6568C0DF2@AS2PR10MB7738.EURPRD10.PROD.OUTLOOK.COM>
On Fri, 5 Jul 2024 11:53:22 +0000
"Mereena Mathai Liquancin (MS/EMS3-BST)" <Liquancin.MereenaMathai@in.bosch.com> wrote:
> Dear IIO Maintainers and Community,
>
> I hope this message finds you well.
>
> We are planning to submit a patch to the IIO subsystem and would like to clarify the process for its inclusion in the linux-next branch.
>
> Our question is: Once our patch is approved by the IIO maintainer and merged into the iio.git<https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git> repository, can we expect it to be included in the linux-next<https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git> integration testing tree (kernel/git/next/linux-next.git)?
>
> Understanding this process will help us manage our expectations and timelines more effectively.
Normally there is a short (typically around one week, a little longer when merge windows
are open or about to open) gap between when I pick a patch up and inclusion in linux-next
(that includes the togreg branch of the above tree). The reason for that is to provide an
opportunity for early feedback from 0-day on any build issues etc before making a mess of Linux next.
That automation runs against the test branch of iio.git.
Jonathan
>
> Thank you for your time and assistance.
> Best regards,
>
> Liquancin Mereena Mathai
>
> BST Projects (MS/EAC3-AE)
> Bosch Global Software Technologies Private Limited
> (CIN: U72400KA1997PTC023164) | KGISL Infrastructures Private Ltd - SEZ Keeranatham Village | Coimbatore | Tamil Nadu - 641035 | INDIA | www.bosch-softwaretechnologies.com
> Liquancin.MereenaMathai@in.bosch.com<mailto:Liquancin.MereenaMathai@in.bosch.com>
>
> Registered Office: Bosch Global Software Technologies Private Limited - (CIN: U72400KA1997PTC023164)
> (Formerly known as Robert Bosch Engineering and Business Solutions Pvt. Ltd.)
> 123, Industrial Layout, Hosur Road, Koramangala, Bengaluru - 560095, India
> Managing Director: Mr. Dattatri Salagame
>
parent reply other threads:[~2024-07-06 10:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AS2PR10MB77388143DBA2ACC76CFD6568C0DF2@AS2PR10MB7738.EURPRD10.PROD.OUTLOOK.COM>]
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=20240706112807.6fd69e5b@jic23-huawei \
--to=jic23@kernel.org \
--cc=Liquancin.MereenaMathai@in.bosch.com \
--cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox