On Fri, 25 Mar 2022 17:38:40 +0000, Mark Brown <[email protected]> wrote:
> On Fri, Mar 25, 2022 at 06:26:16PM +0100, Stephen Kitt wrote:
>
> > Which tree should I check for conflicts? I’ve got similar patches across
> > all the i2c-using sound/soc/codecs files, I wouldn’t want to waste
> > anyone’s time if I can check beforehand...
>
> Since we're in the merge window non-fixes patches just aren't getting
> applied at the minute, you need to follow what's going on on the list at
> the minute.
Apologies, please ignore all my patches then, I’ll re-submit them at a more
convenient time.
Regards,
Stephen
On Fri, Mar 25, 2022 at 06:51:34PM +0100, Stephen Kitt wrote:
> On Fri, 25 Mar 2022 17:38:40 +0000, Mark Brown <[email protected]> wrote:
> > Since we're in the merge window non-fixes patches just aren't getting
> > applied at the minute, you need to follow what's going on on the list at
> > the minute.
> Apologies, please ignore all my patches then, I’ll re-submit them at a more
> convenient time.
There's no harm in them if nobody else is doing anything at the same
time, it's just that a mechanical cleanup like this is going to get
dropped in favour of essentially anything else if it causes conflicts.
> > Apologies, please ignore all my patches then, I’ll re-submit them at a more
> > convenient time.
>
> There's no harm in them if nobody else is doing anything at the same
> time, it's just that a mechanical cleanup like this is going to get
> dropped in favour of essentially anything else if it causes conflicts.
Sending right after and based on -rc1 is usually a good timing for such
cleanups. BTW do you plan to convert the whole tree or just bits you are
interested in? Would be good to know to avoid someone else working on
the same topic.